Re: swprintf (Xcode issue)
Re: swprintf (Xcode issue)
- Subject: Re: swprintf (Xcode issue)
- From: Thomas Engelmeier <email@hidden>
- Date: Tue, 29 May 2007 10:20:32 +0200
Am 28.05.2007 um 20:50 schrieb Alexander von Below:
I fully subscribe to Andy Finnell's rant on his blog:
>> Mac OS X, being a Unix variant, had implemented wchar_t as
UTF-32! All the cross platform code, code that used to work on
Windows and Mac, no longer worked. Apple felt their pain, and
issued this technical note, which essentially says: “instead of
using wchar_t, which used to be cross platform before we destroyed
it, use CFStringRef, which is not cross platform, has never been,
and never will be. P.S. This is really your own fault for ever
using wchar_t. Suckers.” <<
http://www.losingfight.com/blog/2006/07/28/wchar_t-unsafe-at-any-size/
I wouldn't subscribe it. wchar_t is a sucky concept. My personal
preference in this case is to have
- one "compressed" representation that typically gives maximum text
per memory (that is for roman languages UTF-8)
- one "raw" representation that ALWAYS gives one codepoint per array
index (and that is UTF-32 and NOT UFT-16)
UTF-16 is for i18n the same source of bugs as signed char * as
character representation. As typically in the developers test setup
never 16+ bit (as before 7+ bits) codepoints occur, a bunch of bugs
potentially ship undetected...
Regards,
Tom_E
_______________________________________________
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