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: Fri, 20 May 2011 05:46:29 -0700
On May 20, 2011, at 2:16 AM, Andreas Grosam <email@hidden> wrote:
> Of course, the source file will not be changed when compiling with different compilers.
No, but it can be if edited (say accidentally) between compilations. Opening and re-saving the file could change its composition, for example, to whatever the editor you're using prefers.
> However, the individual bytes of the source file can be interpreted differently - regardless of the actual encoding of the source file. For sure, gcc treats it as UTF-8 - and it IS UTF-8.
There are multiple valid UTF-8 representations for Unicode "ΓΌ" and which representation a particular compiler uses in a compiled string literal - regardless of which one you entered - is, so far as I know, entirely implementation-defined.
-- 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