Re: [Pyobjc-dev] NSString & mutability
Brought to you by:
ronaldoussoren
From: <bb...@ma...> - 2003-02-05 01:24:00
|
On Tuesday, Feb 4, 2003, at 18:28 US/Eastern, Just van Rossum wrote: >> It is unreasonable to expect that the internal implementation will >> remain consistent over time, yet that is exactly what a partial >> conversion solution expects. > > Ok, I'm about to give in. Can we table this for a bit? I'm in the middle of an implementation that *may* actually solve this problem in a somewhat graceful fashion that makes both of us happy. I'm not sure and it'll take more time for me to figure out how to explain it than to do some more research programming to determine if it'll work. That, and I'm tired of tossing a bunch of words out there without backing it with useful examples/code.... and I'm tired of having time sucked from forward progress for the sake of a [very interesting] argument. I'm sure that there are a lot of others on this list-- yourself at the head of the list-- in the same boat. BTW: I do have Python->ObjC working nicely -- Python strings pop into ObjC world without copying data. b.bum |