Andy Ross writes: > Curtis L. Olson wrote: > > Do we know which source files are having problems with min/max under > > cygwin? > > My impression (watching from the peanut gallery) is that min and max > are useful functions that simply can't be used portably, not unlike > alloca or snprintf.
It's a little worse then that :-( libstdc++3.2 introduced internal headers that do a using __STD::min; and the Microsoft headers define min() and max() macros in the GLOBAL namespace unless you use the NOMINMAX hack So including any of the < at least most > stl headers will trigger this Hopefully the next release of libstdc++ will use a different mechanism as I doubt that M$oft will change <windows.h> Norman _______________________________________________ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
