Displaying 3 results from an estimated 3 matches for "expandargv".
2011 Sep 01
3
[LLVMdev] [cfe-dev] Unicode path handling on Windows
...m::sys::path converts strings
to utf16 on windows and calls W API functions.
If somebody would like to take a look at my changes and comment on them.
Here's a brief explanation of what I did:
- Convert argv to utf8 using current system locale for win32 (this is done
as soon as possible inside ExpandArgv). This makes the driver happy since
calls to llvm::sys::path::exists succeed.
- Change calls to ::open (inside FileSystemStatCache and MemoryBuffer) to
::_wopen on win32 by converting the path to utf16.
- In order to do the conversions I had to expose two functions, one of them
was already there bu...
2011 Sep 01
0
[LLVMdev] [cfe-dev] Unicode path handling on Windows
Op 1 sep. 2011 14:12 schreef "NAKAMURA Takumi" <geek4civic at gmail.com> het
volgende:
>
> Guys, welcome to the too weird i18n world!
> We, Japanese, has got suffered for multibyte charset for 20 years.
>
> I have added a comment in http://llvm.org/bugs/show_bug.cgi?id=10348 .
> Of course I know, I don't think it would be a practical resolution.
>
> FYI,
2011 Sep 01
3
[LLVMdev] [cfe-dev] Unicode path handling on Windows
Guys, welcome to the too weird i18n world!
We, Japanese, has got suffered for multibyte charset for 20 years.
I have added a comment in http://llvm.org/bugs/show_bug.cgi?id=10348 .
Of course I know, I don't think it would be a practical resolution.
FYI, it seems clang can retrieve mbcs path with s/CP_UTF8/CP_ACP/g.
E>bin\clang.exe -S なかむら\たくみ.c
なかむら\たくみ.c:4:2: error: #error
#error
^
1