3 ms·
For Ruby, never. Literally never since 2005. For Objective-C, quite often. Why? I'm not sure. Maybe because the Ruby has such good unit test support, and loggi
by damoncali 14y ago
For Ruby, never. Literally never since 2005.
For Objective-C, quite often.
Why? I'm not sure. Maybe because the Ruby has such good unit test support, and logging is pretty painless. It could very well be that I'm missing out by not using ruby-debug or some other tool, though.
In Xcode, the path of least resistance is the debugger. Maybe it's because I'm less familiar with Cocoa, but the code just seems more complicated and harder to trace from start to end. The debugger really helps with that. Even there, though, I use a lot of NSLog(). This helps when you have to track down a changing situation, and can't quite figure out when or how it breaks. Just log a bunch of stuff and let it rip.