3 ms·
I hope one day Microsoft will deprecate their non-unicode API, remove that TCHAR mess. I think they supported these legacy APIs long enough already. There's sti
by xvilka 5y ago
I hope one day Microsoft will deprecate their non-unicode API, remove that TCHAR mess. I think they supported these legacy APIs long enough already. There's still a problem with PATH_MAX, see, for example, the dotnet MSBuild[1][2][3]. Maybe even switch to the UTF-8 instead.
[1] https://github.com/dotnet/msbuild/issues/53 https://github.com/dotnet/msbuild/issues/53
[2] https://github.com/dotnet/msbuild/issues/5331 https://github.com/dotnet/msbuild/issues/5331
[3] https://github.com/dotnet/msbuild/issues/4200 https://github.com/dotnet/msbuild/issues/4200
- j16sdiz 5y agoThis would upset many librarian and archivist
- CodesInChaos 5y agoI hope one day Microsoft will remove support for arbitrary 16-bit code-units from their API and only accept valid UTF-16. That shouldn't break too many applications, but will finally allow people to use unicode strings to handle filenames. Switching the default "ANSI" encoding to UTF-8 (or WTF-8) would be pretty nice as well, unless an application is running in compatibility mode. That should avoid most of the problems with the 8-bit API, without breaking everything. And in the long run perhaps even switch to UTF-8 internally, making the 16-bit API legacy (one can dream).