------- Comment #1 from pspe...@earthlink.net 2010-07-06 10:28 PST8PDT -------
Four years ago I implemented use of the NOMINMAX macro in win16.h (winnt.h
already used it) to allow the code to compile.
I don't believe the compiler blew up at that time, however; that part is new
and, when confirmed, a problem to be fixed.
As far as the code goes, it would be best to #define NOMINMAX before including
<windows.h> if you are also including any C++ header that relies on or defines
the min() and max() functions/function templates. If you don't then the macro
will be applied and, even if the compiler doesn't gp fault, the result will
still not be satisfactory.
I haven't actually tested this, although I did confirm that the OW 1.9 win16.h
does, in fact, use NOMINMAX properly.
--
Configure bugmail: http://bugzilla.openwatcom.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
------- Comment #2 from leonid....@atisgroup.ru 2010-07-06 13:17 PST8PDT -------
This issue appears to be 100% reproducible. I’ve just performed “clean”
experiment: installed Windows XP, installed OW 1.9, and tried to compile same
piece of code. It yields the same result: exception.