Hi Peter,

That’s a good idea! We could keep a list of warnings that should be ignored and write a tiny script to filter all Qt, 3rdParty and ignored warnings! That would be a perfect solution!

I’m actually using a simple bash script that does this, so I got only errors/warnings from our sources and ./tester output. It has a few bugs, though, but I think I’ll be able to create a better script (in Python, in order to make it multi-platform).

You’re right! But are operator== and != generated automatically by the compiler? I think rather not (but have to check again). Another idea would be to implement these operators like return this == &other;, which would be useless if we always use pointers for ReferenceObjects rather references.

No, they’re not. I just thought that disabling these would cause that we won’t implement them (for sure). But if we (and other developers) are aware of what a reference object is, we won’t implement them anyway, so it’s not really necessary to disable these in that macro.

Regards,

Petr