[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Couple of problems with current SVN
From: |
David Chisnall |
Subject: |
Re: Couple of problems with current SVN |
Date: |
Sat, 2 Jun 2012 10:06:48 +0100 |
On 2 Jun 2012, at 06:37, Germán A. Arias wrote:
> This is caused
> by the NSString class method -stringWithUTF8String:. If the argument is
> a const char that contains letters like "áéñ", this method return "nil".
If it contains those characters in UTF-8, then that's a bug. If it's a string
literal, then you would probably be better off creating it as an Objective-C
string literal in the first place (since those will always be UTF-8). As Fred
and Richard said, you need to be very careful about the encoding of string
literals, as anything non-ASCII is implementation-defined behaviour. Clang
assumes that the source is UTF-8, gcc assumes it's whatever the current locale
is set to (so if someone Japanese tries compiling code written by someone in
Korea you get all sorts of interesting things happening).
David
-- Sent from my STANTEC-ZEBRA
- Re: Couple of problems with current SVN, A. Arias, 2012/06/02
- Re: Couple of problems with current SVN, Fred Kiefer, 2012/06/02
- Re: Couple of problems with current SVN, Richard Frith-Macdonald, 2012/06/02
- Re: Couple of problems with current SVN, A. Arias, 2012/06/02
- Re: Couple of problems with current SVN, Richard Frith-Macdonald, 2012/06/02
- Re: Couple of problems with current SVN, A. Arias, 2012/06/02
- Re: Couple of problems with current SVN, Eric Wasylishen, 2012/06/02
- Re: Couple of problems with current SVN, Eric Wasylishen, 2012/06/02
- Re: Couple of problems with current SVN, A. Arias, 2012/06/03
- Re: Couple of problems with current SVN, Richard Frith-Macdonald, 2012/06/03
Re: Couple of problems with current SVN,
David Chisnall <=
Re: Couple of problems with current SVN, Richard Frith-Macdonald, 2012/06/02