Displaying 2 results from an estimated 2 matches for "2af4c8db".
2011 Oct 04
0
[LLVMdev] [cfe-dev] Unicode path handling on Windows
...sion is valid; for example the NTFS-3G driver uses a
> simplistic upcase table and seems to work fine. I suspect Windows does the
> same.
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20111004/2af4c8db/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: clang.patch
Type: application/octet-stream
Size: 15811 bytes
Desc: not available
URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20111004/2af4c8db/attachment.obj>
--------------...
2011 Oct 04
2
[LLVMdev] [cfe-dev] Unicode path handling on Windows
That should be fine. I don't believe the concern about performing a char-by-char conversion is valid; for example the NTFS-3G driver uses a simplistic upcase table and seems to work fine. I suspect Windows does the same.
On Oct 3, 2011, at 1:12 PM, Nikola Smiljanic wrote:
> How about this:
>
> for (int i = 0; i != NumWChars; ++i)
> absPath[i] = std::tolower(absPath[i],