Re: _UNICODE vs UNICODE

[Francois Gouget]

On Fri, 18 Jan 2002, Andriy Palamarchuk wrote:
> Using macro name "UNICODE" instead of "_UNICODE" is a
> typo, right?

No, not necessarily. Windows has both and dinput.h, for instance,
uses UNICODE, not _UNICODE.

But I have no idea why they have two.

--
Francois Gouget         [e-mail]        http://fgouget.free.fr/
              Linux: Because rebooting is for adding new hardware

_UNICODE vs UNICODE

[Andriy Palamarchuk]

Francois Gouget wrote:
> On Fri, 18 Jan 2002, Andriy Palamarchuk wrote:
> > Using macro name "UNICODE" instead of "_UNICODE" is a
> > typo, right?
>
> No, not necessarily. Windows has both and dinput.h, for instance,
> uses UNICODE, not _UNICODE.
>
> But I have no idea why they have two.

I came across this problem when I found out that _T("sss") preprocesses 
to "sss" in both - Unicode (should be L"sss") and ANSI modes.
The change in winnt.h fixed it. I assumed that the same problem was in 
other places.

Andriy Palamarchuk