I still don't understand why, with C++14, gcc is banning me from having a struct field with the same name as its type*, but clang and msvc both appear to be allowing this. I'm used to msvc disagreeing with clang/gcc, i'm not used to clang and msvc agreeing on something and gcc being the odd one out.
e.g.:
enum Abc { A, B, C };
struct Test { Abc Abc; };
int main() { return 3; }
@mcc my experience with gcc vs other compilers is that if the spec doesn't explicitly define a behavior, gcc will at best error and at worst manifest unpredictable results at runtime; msvc will just do what you meant with no argument; and clang will fall somewhere in the middle (but probably err on the side of a warning or error).
Explains I can make it work by putting a :: before Abc in the typename. Is there something I could put in my CMakeLists to make gcc just chill out about the friggin typenames, though?
Add comment