Re: Use of NSLog() for debugging
Re: Use of NSLog() for debugging
- Subject: Re: Use of NSLog() for debugging
- From: "Clark S. Cox III" <email@hidden>
- Date: Mon, 23 Jul 2001 23:33:44 -0400
On Monday, July 23, 2001, at 01:47 , Finlay Dobbie wrote:
On Monday, July 23, 2001, at 06:24 pm, Glen Simmons wrote:
<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>
I'm sure I read somewhere that they're aware of this as a bad
limitation, and that having the hex address in memory is not overly
useful most of the time, when what you want is the contents of the
object... I think I also read that they're working on addressing it.
Project Builder still has some major bugs in it, though (like you can't
scroll the build output, and the Executable Settings panel (in target
settings) renders really weird unless you have a massive window
size...), so all we can do is wait and hope (I suspect that recently
their number one priority was implementing WO5 support and debugging
that... the PB team do deserve a lot of kudos, the new PB is much
better than the old one).
Yes, it's come a long way. but:
<rant>
Has anyone heard of multiple windows? Do we really need to control
every aspect of coding, building, debugging and running through the same
cramped window.
</rant>