On 13 Mar '08, at 4:01 AM, Thomas Engelmeier wrote:
As of Leopard or as of Xcode 3.x?
I think it just matters which version of gcc is being used, so that would make it an Xcode feature, basically.
And, if I read the paragraph above correctly, the compiler will expand @"UTF-8 string" in the source code to UTF16 in the string constant in the TEXT section?
The email you quoted just said "there are cases" where this happens. My hunch, from what I know of CFString, is that ascii string constants will be stored in 8-bit, while ones containing any non-ascii characters would be 16-bit. (CFStrings are never stored in UTF-8 form internally. It's either ascii or the 'default C string encoding', which is locale-dependent, e.g. MacRoman for the English language.)
Of course you should never write any code that relies on this... —Jens
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) Please do not post admin requests or moderator comments to the list. Contact the moderators at cocoa-dev-admins(at)lists.apple.com Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to [EMAIL PROTECTED]
