Re: Don't assume that UNICODE is not defined

[Jeffrey Walton]

On Sat, May 30, 2020 at 5:16 AM Bruno Haible <bruno@clisp.org> wrote:
>
> I wrote:
> > some types depend on
> > whether UNICODE is defined or not [1].
>
> Some functions also depend whether UNICODE is defined or not.
>
> Since UWP applications are meant to defined the macro UNICODE, but we want
> Gnulib to produce the same code, regardless whether UNICODE is defined or not,
> we need to either explicitly use the functions with 'A' suffix (which is ugly)
> or use #defines for redirection.
>
> Fortunately, packages that use gnulib don't need to do this stuff; nor do we
> need to do it in the tests/ directory. Only the gnulib/lib/ directory may
> reasonably be used with -DUNICODE, therefore only the gnulib/lib/ directory
> needs this workaround.

In case it matters, I believe Microsoft keys on _UNICODE, not UNICODE.

Microsoft source files often have something like this (or is it vice-versa):

#ifdef UNICODE
#  ifndef _UNICODE
#    define _UNICODE
#  endif
#endif

Also see 
https://docs.microsoft.com/en-us/cpp/text/generic-text-mappings-in-tchar-h.

Jeff