--- Comment #5 from ktietz at gcc dot gnu dot org 2009-06-09 06:52 ---
(In reply to comment #4)
> Subject: Re: GCC defines UNICODE instead of _UNICODE
> for -municode
>
> UNICODE is in the user's namespace; it should not be predefined if
> flag_iso (if you have to use specs rather th
--- 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
UNICOD
--- Comment #3 from ktietz at gcc dot gnu dot org 2009-06-08 09:09 ---
As further research has shown, is the definition of _UNICODE a thing the user
has to take care. The _UNICODE define is used in tchar.h and documentation for
this can be found on msdn.
--
ktietz at gcc dot gnu dot
--- Comment #2 from ktietz at gcc dot gnu dot org 2009-06-08 08:31 ---
Ok, it is no fiction, but a issue for tchar.h in CRT headers. See
http://blogs.msdn.com/oldnewthing/archive/2004/02/12/71851.aspx
so, we define UNICODE for PSDK, but _UNICODE is user defined AFAIU. But
possibly we co
--- Comment #1 from ktietz at gcc dot gnu dot org 2009-06-08 07:51 ---
Hi,
to define UNICODE is absolutely correct. The define _UNICODE is fiction (but I
agree it is in use). We can discuss about to define _UNICODE, too. But the
UNICODE defines is for the w64 runtime the proper thing to
