Hi, yes I’ve done that. The thing is, it actually works like a pure virtual function if I was to define it inside a child class - so that’s all good, it allows me to build without actually defining it in the .cpp.
However, if I don’t define it and simply designate it as PURE_VIRTUAL I’d expect a warning or compilation error but it seems to build fine and and play fine.
Just curious as to if I’m doing something incorrectly as I’ve read from other posts I’m supposed to be getting a warning similar to standard C++.
I’ve never actually not derived a pure virtual so haven’t seen any errors either, but having a look at the macro, it does seem to throw an error - but needs defined CHECK_PUREVIRTUALS:
I just tried adding this to my code and compiling, and didn’t get any errors, it seems to only be defined in Build.h so I’m thinking adding that to your project will fix it:
#if CHECK_PUREVIRTUALS
something to generate an error....
#endif