> Hello!
> I have a problem with porting to XCode.
[quoted text clipped - 4 lines]
> In code "check" is a macro, and virtual member of class.
> Build fail on class member declaration "chak" with this message.
That's a really bad idea. Macros get applied long before the compiler
itself sees anything, and therefore aren't subject to namespaces. This
means that macros *must* be unique relative to basically everything else
in the areas where they are visible. If both the macro and the virtual
member are visible in the same place, then you must rename one of them.
This is why you usually see macro names in all caps, as it won't interfere
with other normally-named identifiers. Following this idea, you should
rename your macro to CHECK so it no longer conflicts with the virtual
member.

Signature
Michael Ash
Rogue Amoeba Software
Fonarix - 25 Oct 2006 16:29 GMT
> > Hello!
> > I have a problem with porting to XCode.
[quoted text clipped - 19 lines]
> Michael Ash
> Rogue Amoeba Software
Thanks for reply!
I've done #undef badmakros )))