From: Ronald Oussoren <ronald.oussoren@xs...> - 2003-03-09 17:29:05
This is bug is basicly fixed, but is still open because of a cosmetic
issue: the name of the method that is used to access the NSString that
is proxied by our unicode subclass.
That method is currently called 'pyobjc_NSString' which is overly
verbose. I'm inclined to change this to 'nsstring'. Another convenient
name is 'asNSString', but that implies conversion (which we don't do).
BTW. Should we add a method to resync the unicode-object contents to
the data in the NSString? Adding
this isn't too hard and might be convenient when dealing with mutable