Re: [Pyobjc-dev] Headache over hacking an XML editor

[<bb...@ma...>]

On Tuesday, Jan 14, 2003, at 11:51 US/Eastern, Just van Rossum wrote:
... interesting stuff deleted ...
> I searched, to no avail. Any specific pointers or google keywords?

Basically, it boils down to the same reason why we don't do name 
mangling -- it is easy to do something that works 90% of the time, 
impossible to do something that works 100% of the time and that 10% of 
the time is a real serious pain in the butt to debug/deal with.

When using PyObjC, you cannot ignore the fact that you are effectively 
using Objective-C from Python.  The memory management semantics of ObjC 
*will* leak through the bridge due to inconsistencies and 
idiosyncracies within the implementation of classes -- known and 
unknown (i.e. third party) -- on the ObjC side.

Thread starts here:

     http://sourceforge.net/mailarchive/message.php?msg_id=2347617

But this particular response [of mine] contains the most detailed 
explanation on why I don't believe it is possible to eliminate 
retain/release/autorelease entirely from the Python side of the bridge:

     http://sourceforge.net/mailarchive/message.php?msg_id=2349810

And another thread that may also be illuminating:

     http://sourceforge.net/mailarchive/message.php?msg_id=2342178

And another thread:

     http://sourceforge.net/mailarchive/message.php?msg_id=2331515

b.bum