On Thu, Jul 24, 2008 at 1:35 PM, Nate Weaver <[EMAIL PROTECTED]> wrote: > You're right, of course (I forgot about this). > > I think I decided not to worry about it too much since it shouldn't make it > into production code (if it does, then I did something wrong). My main goal > was to keep the macro as simple as I could (or at least, not have to break > it onto multiple lines), and having the full path to a file felt like it > would add to the clutter.
Putting potentially subtle and difficult-to-find bugs in your debugging code is in many ways worse than putting into your production code, since it's really tough to debug stuff if you can't even rely on the code that lets you find out what's wrong. As a real simple fix, [[NSString stringWithUTF8String:__FILE__] lastPathComponent] will give you equivalent functionality without the mess, if you use %@ instead of %s in the format string. Mike _______________________________________________ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) Please do not post admin requests or moderator comments to the list. Contact the moderators at cocoa-dev-admins(at)lists.apple.com Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to [EMAIL PROTECTED]
