CGAL users discussion list

[Andreas Fabri <>]

Wesley Smith wrote:
> I actually had exactly the same problem yesterday with min and max
> defines.  This was with VS2008.  I had to do the following:
>
>
> #ifdef min
>   #define MIN_MACRO min
>   #define MAX_MACRO max
>   #undef min
>   #undef max
> #else
>   #define MIN_MACRO
>   #define MAX_MACRO
> #endif
>
> /*
> my code
> */
>
> #define min MIN_MACRO
> #define max MAX_MACRO
>
>
> I was kind of surprised that there were macros with names min and max
> in CGAL since these are such common names, they're bound to conflict.

Wesley,

But where did you find them?  As I wrote, we all replaced them,
so if we missed one it's a bug and you could help us to fix it.

andreas


> wes
>
>
>
> On Thu, Apr 24, 2008 at 10:23 AM, Andreas Fabri
> <>
>  wrote:
> >  Angelina,
> >
> >
> >  
> >
> >  wrote:
> >
> > > Andreas was right (as usual) Thanks! - it was not as hopeless as I thought
> > to look through the huge error list :)
> > > Here what does the job(in case someone else needs it too):
> > > #undef min
> > > #undef max
> >
> >
> >  That's strange. We made quite an effort to live with the
> >  #define of min and max  as they are also defined in the
> >  Microsoft header file windows.h.
> >
> >  Undefining them is in general a bad idea, as Microsoft products
> >  simply need these defines.
> >
> >  In case the appearances of min(a,b) are in your own code, the
> >  workaround is to wrap the word "min" as follows
> >
> >  (min)(a,b)
> >
> >  The additional parethesis prevents the preprocessor to do its work.
> >
> >
> >  andreas (who is not always right)
> >
> >
> >  --
> >  You are currently subscribed to cgal-discuss.
> >  To unsubscribe or access the archives, go to
> >  https://lists-sop.inria.fr/wws/info/cgal-discuss