On 11/01/11 14:07, Andrew Bell wrote:
Not that I've tried it, but can't you just #undef min and #undef max after you've included the windows header?
You can, but in many cases it will cause errors thrown from Windows API headers. It's better to do
#define NOMINMAX #include <windows.h> However, the best option is to follow Boost guidelines. The min/max are very popular as macros, not only on Windows but defined by various software packages, so personally, I prefer the extra () as most portable option. Best regards, -- Mateusz Loskot, http://mateusz.loskot.net Charter Member of OSGeo, http://osgeo.org Member of ACCU, http://accu.org _______________________________________________ Liblas-devel mailing list [email protected] http://lists.osgeo.org/mailman/listinfo/liblas-devel
