Re: NSString changes

[richard]

On Monday, November 6, 2000, at 04:16 PM, enrico@imago.ro wrote:

>  
> But now there is a new problem: selecting a matrix cell I get: 
> "NSCaracterConversionException: Can't get cString from Unicode strings" 
>  
> #0  0x4073a111 in __kill () 
> #1  0x40739d66 in raise (sig=6) at ../sysdeps/posix/raise.c:27 
> #2  0x4073b447 in abort () at ../sysdeps/generic/abort.c:88 
> #3  0x400a1c10 in _NSAppKitUncaughtExceptionHandler (exception=0x84b97c8) 
>     at NSApplication.m:92 
> #4  0x40435ee4 in _i_NSException__raise (self=0x84b97c8, _cmd=0x40528ad0) 
>     at NSException.m:110 
> #5  0x40435b44 in _c_NSException__raise_format_arguments_ 
> (self=0x40528a40, 
>     _cmd=0x40528ab8, name=0x817aab8, format=0x40519b50, 
> argList=0xbfffd648) 
>     at NSException.m:75 
> #6  0x40435a6a in _c_NSException__raise_format_ (self=0x40528a40, 
>     _cmd=0x405195a8, name=0x817aab8, format=0x40519b50) at 
> NSException.m:61 
> #7  0x403ceac4 in cString_u (self=0x849c660) at GSString.m:633 
> #8  0x403cb24b in _i_GSMutableString__cString (self=0x849c660, 
> _cmd=0x405389c0) 
>     at GSString.m:2165 
> #9  0x4048a6d8 in handle_printf_atsign (stream=0xbfffe3e4, 
> info=0xbfffd708, 
>     args=0xbfffd6e4) at NSString.m:276 
> #10 0x40764971 in _IO_vfprintf (s=0xbfffe3e4, format=0x80c00db "%@/%@", 
>     ap=0xbfffe58c) at vfprintf.c:1522 
> #11 0x4076eb81 in _IO_vasprintf (result_ptr=0xbfffe4c0, 
>     format=0x80c00db "%@/%@", args=0xbfffe58c) at vasprintf.c:58 
> #12 0x4048bd86 in _i_NSString__initWithFormat_locale_arguments_ ( 
>     self=0x812af30, _cmd=0x40538bb8, format=0x80ec854, locale=0x0, 
>     arg_list=0xbfffe58c) at NSString.m:840 
> #13 0x4048bcfe in _i_NSString__initWithFormat_arguments_ (self=0x812af30, 
>     _cmd=0x40538b00, format=0x80ec854, arg_list=0xbfffe58c) at 
> NSString.m:664 


Looks to me like the changes have probably exposed a bug in initWithFormat:
I'm guessing that you are getting the exception because the string being used
contains non-ascii characters, and the code is using -cString to get the
string contents.  I've added a quick temporary hack - to use the lossyCString
method instead, but what's really required is someone to write a proper unicode
version of initWithFormat: