Re: [Pyobjc-dev] OC_PythonString implementation

[Just v. R. <ju...@le...>]

Ronald Oussoren wrote:

> 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.

My brief tests seem to indicate that things work great. Thanks!

[ ... ]
> - 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?

Since the wrapper get created on the fly, I think a method is most
apporpriate after all. I would call that method nsstring(), though. Hm,
maybe as_nsstring() is better. Yeah, I like that. Or as_NSString().

Just