Re: Xcode-users Digest, Vol 7, Issue 153
Re: Xcode-users Digest, Vol 7, Issue 153
- Subject: Re: Xcode-users Digest, Vol 7, Issue 153
- From: "Paul Sanders" <email@hidden>
- Date: Wed, 14 Apr 2010 11:50:52 +0100
|
> Unfortunately, using that flag [-fshort-wchar] makes your
code binary-incompatible with libraries that use wchar_t and were not compiled
with that flag. That's why I was told we can't use it in Chromium.
I was thinking about this, and I realise that you (and
indeed I) could use that flag if one controls all the relevant libraries
and can compile them all in the same way. And in fact it's only
libaries that use wchar_t in their API's that would need to be recompiled with
this flag.
What's missing is support for 'wchar_t_16' in the
runtime library, and it is not so hard to provide replacements for that
yourself. Had I known about this flag when I was putting my app and
libraries together I might have used it, but everything is working fine now with
wchar_t_32 so I will most likely stick with what I've got.
There's nothing wrong with wchar_t as a concept. You
can't beat being able to iterate through and index into a string of fixed-size
elements for speed and convenience. It's the runtime library support
that's a bit of a mess. And those surrogate pairs, of course.
Paul Sanders.
|
_______________________________________________
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