Luddite Wacko wrote:
> This way, where ever you are having a problem, change the "objectAtIndex:
> " message to "theObjectAtIndex:" and place breakpoints as noted above.
> Then you will hit a breakpoint only if there is something wrong with
> your code - oece you have it fixed, change the message back.
Yeah, I had thought of something similar but when this occurs I've no
idea where; it'd be a bit tedious to implement in a large project. I
take to eyeballing recent modifications but
What I was going after was say a catch handler per class. If an error
occurred the class would halt to the debugger vs. the 1 line console log
output; now if it'd give me a stack trace I could work with that.
Now it's sort of like getting a 'you have an error in your app' message.
--
/los "I was a teenage net-random"
|
Similar Threads
Linear Mode
