Re: NSLog
Re: NSLog
- Subject: Re: NSLog
- From: "Gerriet M. Denkmann" <email@hidden>
- Date: Sun, 11 Aug 2002 20:11:59 +0200
Date: Sat, 10 Aug 2002 23:52:52 +0200
Subject: Re: NSLog
From: j o a r <email@hidden>
To: Cocoa Dev <email@hidden>
Perhaps the first one doesn't properly adhere to the NSObject protocol?
Is it a subclass of NSObject? There is a known problem (ie. bug) with
printing objects descending from NSProxy (or at least NSDistantObject)
this way.
j o a r
On Saturday, Aug 10, 2002, at 23:33 Europe/Stockholm, Gerriet M.
Denkmann wrote:
I have noticed that
NSLog(@"my object is: %@", myObject);
has the same result as:
NSLog(@"my object is: %@", [myObject description] );
Is this documented somewhere?
And I have also have one situation, where the first call creates an
EA_BAD_ACCESS , and the second call works ok.
Why might this be the case?
Gerriet.
Yes, this probably was the reason: the thing which did not work with the
first call was a Proxy of some real NSObject descendant.
Thanks for the hint!
Gerriet.
_______________________________________________
cocoa-dev mailing list | email@hidden
Help/Unsubscribe/Archives:
http://www.lists.apple.com/mailman/listinfo/cocoa-dev
Do not post admin requests to the list. They will be ignored.