Displaying 3 results from an estimated 3 matches for "95923b63".
2011 Oct 04
2
[LLVMdev] [cfe-dev] Unicode path handling on Windows
...you can get it to work the same way. I'm not sure what locale that would have to be, but it needs to match whatever NTFS uses for its $upcase file.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20111003/95923b63/attachment.html>
2011 Oct 03
0
[LLVMdev] [cfe-dev] Unicode path handling on Windows
CharLowerW does the right thing. But I still need Windows.h to use it :)
On Mon, Oct 3, 2011 at 8:43 PM, Bryce Cogswell <bryceco at gmail.com> wrote:
> Locale-specific is not what we want, but I don't believe Windows exposes an
> alternative API that does what we want. (Does CharLower give a different
> answer than tolower?)
>
> However, looking over the FileManager code
2011 Oct 03
5
[LLVMdev] [cfe-dev] Unicode path handling on Windows
Locale-specific is not what we want, but I don't believe Windows exposes an alternative API that does what we want. (Does CharLower give a different answer than tolower?)
However, looking over the FileManager code a little more I'm not even sure using the path is the best solution, it seems it would be better to use inode like the unix code does. Windows doesn't support inode (the