Re: [Pyobjc-dev] issues with NSURL and NSWindow?

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

On Apr 4, 2004, at 9:31 PM, Bob Ippolito wrote:
> That's not the correct way of looking at it.  The problem is precisely 
> that it is sending the release message to an object that is not 
> prepared to receive it.  It actually does try and throw an exception 
> due to the incorrect selector, you just don't see it because it does 
> some garbage collection in the process and the world ends before it 
> gets a chance to let you know what went wrong.

I disagree.

Regardless of the state of the underlying object or the bridge between, 
the user is attempting to send a method to an object where that method 
does not exist.

If I do the following from ObjC...

	    [[NSURL alloc] initWithString];

... the runtime responds with...

2004-04-04 22:28:02.775 asdfasdf[6043] *** -[NSURL initWithString]: 
selector not recognized
2004-04-04 22:28:02.777 asdfasdf[6043] *** Uncaught exception: 
<NSInvalidArgumentException> *** -[NSURL initWithString]: selector not 
recognized

... as I would expect.   That PyObjC crashes in, effectively, the same 
situation without a useful warning message means that there is a bug in 
PyObjC.

And now it is fixed.  That rocks.  Thanks, Bob!    :-)

b.bum