------- Comment #4 from joseph at codesourcery dot com 2009-06-08 09:40 -------
Subject: Re: GCC defines UNICODE instead of _UNICODE
for -municode
On Mon, 8 Jun 2009, ktietz at gcc dot gnu dot org wrote:
> to define UNICODE is absolutely correct. The define _UNICODE is fiction (but I
UNICODE is in the user's namespace; it should not be predefined if
flag_iso (if you have to use specs rather than hooks, you need
%{!ansi:%{!std=i*:%{!std=c*:-DUNICODE}}} to detect the various conformance
options). We should not add to the instances of bug 545 that are still
present. If the MinGW headers use a macro in the user's namespace as a
feature test macro of some sort, they are buggy and should be fixed (with
fixincludes if necessary for existing installations).
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=40376
