Re: Use of NSLog() for debugging
Re: Use of NSLog() for debugging
- Subject: Re: Use of NSLog() for debugging
- From: Glen Simmons <email@hidden>
- Date: Mon, 23 Jul 2001 12:24:21 -0500
Clark, what you haven't stumbled across, is that you can type "po
myObject" in the console to find out the contents of these objects. The
reason you haven't stumbled across this is because it isn't documented
anywhere. Apparently, it's folklore that has to be handed down.
<rant>
What I don't understand is, if "po myObject" is what I'm gonna do the
majority of the time, why isn't this part of the GUI? A disclosure
triangle that only shows an isa variable is about as useful as an extra
butt-cheek. No offense to the Next vets / command line gurus, but I
don't like typing "po myObject". I like the debugger in CodeWarrior,
Visual Studio, insert-a-modern-IDE-here. The debugger is my number one
complaint about PB.
</rant>
Glen
On Monday, July 23, 2001, at 12:05 PM, Clark S. Cox III wrote:
On Friday, July 20, 2001, at 08:08 , Art Isbell wrote:
Many postings to this mailing list discuss using NSLog() for
debugging. I'd like to encourage you to learn to use the debugger,
not NSLog() because
Using NSLog() for debugging does not preclude the use of gdb.
Often, there is no way to view the more complex types used in Cocoa.
For example,
I often insert NSLog() statements just before gdb breakpoints so that
I can see the value(s) held in an NSString, NSNumber, NSArray, etc.
--
Clark S. Cox, III
email@hidden
http://www.whereismyhead.com/clark/
_______________________________________________
cocoa-dev mailing list
email@hidden
http://www.lists.apple.com/mailman/listinfo/cocoa-dev