Displaying 3 results from an estimated 3 matches for "14a4f67c".
Did you mean:
14a4f4c
2011 Oct 04
0
[LLVMdev] [cfe-dev] Unicode path handling on Windows
>
>
> + for (int i = 0; i != argc; ++i)
> + {
> + // check lenght
>
> May want to correct the typo.
>
>
Fixed
>
> I think this should be formatted more like this to meet our coding
> standards (but am not 100% sure, so I will defer to others):
>
> if (ch < (UTF32)0x80)
> bytesToWrite = 1;
> else if (ch < (UTF32)0x800)
>
2011 Oct 10
2
[LLVMdev] [cfe-dev] Unicode path handling on Windows
ping
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20111010/14a4f67c/attachment.html>
2011 Oct 04
2
[LLVMdev] [cfe-dev] Unicode path handling on Windows
On Tue, Oct 4, 2011 at 4:19 AM, Nikola Smiljanic <popizdeh at gmail.com> wrote:
> In that case I think that this is it :)
>
> On Tue, Oct 4, 2011 at 8:24 AM, Bryce Cogswell <bryceco at gmail.com> wrote:
>>
>> 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