Re: Possible Clang Bug in Initializing Wide String From String Literal?
Re: Possible Clang Bug in Initializing Wide String From String Literal?
- Subject: Re: Possible Clang Bug in Initializing Wide String From String Literal?
- From: Chris Hanson <email@hidden>
- Date: Thu, 19 May 2011 14:46:56 -0700
On May 19, 2011, at 2:17 PM, Mark Wagner wrote:
> On Thu, May 19, 2011 at 08:56, Andreas Grosam <email@hidden> wrote:
>
>> IMHO, if I read the standard correctly, clang seems to make an error here. I hope I'm terrible wrong here, since this is pretty basic stuff. Is there something left to be "implementation defined" what I may have overlooked?
>>
>
> Your source code isn't ASCII. How the compiler handles the non-ASCII
> bits (the string literal) is implementation-defined.
This includes normalization, decomposition, etc. So GCC may have compiled the wide string literal as one composed "ü" character, while clang may have compiled it as one "u" character and one "¨" combining mark. Both are legal representations and perfectly valid UTF-8.
It's even possible the (de)composition of the source file changed if you opened and saved it in an editor between your two compilations.
-- Chris
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden