Re: [Pyobjc-dev] OC_PythonString implementation

[Ronald O. <ous...@ci...>]

I've just checked in working version of unicode-object.m (the bug was a 
pretty lame bug in the initialization of ObjCUnicode_Type). The 
resulting version of the bridge mostly passes the unit tests, the 
additional failures seem to be caused by a minor change in the 
semantics of the bridge.

Todo:
- ObjCUnicodeObject has a slot for weakrefs, make this known to the 
runtime (easy)
- objc-object.m contains a mapping from id's to weakrefs to Python 
proxies, use this to make sure that there is at most one 
ObjCUnicodeObject for an NSString
- More testing
- Determine, and use, best interface for accessing the NSString 
(currently method pyobjc_NSString). Using 'nsstring' as the name is 
probably better. Should this be a method or a (read-only) property?

Ronald