On Saturday, 7 September 2019 02:07:33 PDT Niall Douglas wrote:
> > The mistake was to use argv. If you're on Windows and you want to deal
> > with
> > proper file names on the command-line, call GetCommandLineW and get the
> > actual command-line.
>
> No, no, no.
>
> We are getting within a cat's whisker of UTF-8 being the default narrow
> encoding on Windows for new Visual Studio projects i.e. all the ANSI and
> char APIs on Windows would default to speaking UTF-8 in new or upgraded
> code. What you propose would ruin that effort.

Once that happens, the problems go away. That creates the theoretical group
(b) in my Analysis section.

Until then, don't use the ANSI API if you want a non-defective tool on
Windows.

> You may not be aware, but after a discussion with some Microsoft folk, I
> went ahead and submitted that as a feature request for the next major
> release of Visual Studio. And from what I am told, they are seriously
> considering it. The Windows console supports it, Windows supports it,
> the MSVCRT runtime supports it when asked. All someone needs to do is
> flip the switch for new projects targeting latest Windows 10 only, and
> we've done it.
>
> Having char = utf8 across all the major platforms would be an *enormous*
> win. Please aid that effort.

Of course. How can I help?

-- 
Thiago Macieira - thiago (AT) macieira.info - thiago (AT) kde.org
   Software Architect - Intel System Software Products