Macro defintion of max?

[pokemoen]

CEGUIBase.h

Code: Select all

00063 // Detect macros for min / max and undefine (with a warning where possible)
00064 #if defined(max)
00065 #   if defined(_MSC_VER)
00066 #       pragma message("Macro defintion of max detected - undefining")
00067 #   elif defined (__GNUC__)
00068 #       warning ("Macro defintion of max detected - undefining")
00069 #   endif
00070 #   undef max
00071 #endif
00072 #if defined(min)
00073 #   if defined(_MSC_VER)
00074 #       pragma message("Macro defintion of min detected - undefining")
00075 #   elif defined (__GNUC__)
00076 #       warning ("Macro defintion of min detected - undefining")
00077 #   endif
00078 #   undef min
00079 #endif

1st: What is a "defintion"?
2nd: Why am I getting this message exactly? I don't know when this check was added, but I didn't get the warnings before.. What could I have changed to start defining min and max?

Just curious..

TIA!
Alex

[Dalfy]

a definition is a preprocessor command of the form

Code: Select all

#define var value.

The preprocessor will make use of this definition and substitute every where in the code var by value. There is possibly to kind of definition:
macro and constant.

For a detailed description of the preprocessor you might have a look on any book on C or look foward cpp on google.

[pokemoen]

I know what a definition is, read carefully

[lindquist]

hehe. a little type we have

You're seeing this because of some M$ stupidity there min and max are defined as macros.

min, max are so common names that this is truely dumb. therefore cegui removes these definitions if found.

HTH

[edit] I have fixed this typo in CVS head btw [/edit]

[pokemoen]

Okay, cool, thanks

[baxissimo]

2nd: Why am I getting this message exactly? I don't know when this check was added, but I didn't get the warnings before.. What could I have changed to start defining min and max?

It might have also started to appear because either you or CEGUI changed the order in which some headers are included. If Microsoft's header gets included after CEGUI then you won't get the message. If before, then you will.

[muhkuh]

2nd: Why am I getting this message exactly? I don't know when this check was added, but I didn't get the warnings before.. What could I have changed to start defining min and max?

It might have also started to appear because either you or CEGUI changed the order in which some headers are included. If Microsoft's header gets included after CEGUI then you won't get the message. If before, then you will.

This happened serveral times for me so I put a NOMINMAX preprocessor definition in every visual studio project of CEGUI. May be this could be applied to svn trunk so it's more robust when the order of included headers changes?