The Most Useful Objective-C Code I’ve Ever Written

The Borkware NSLog replacement seems like a rather a large amount of overkill and unnecessary clutter. __FILE__ and __LINE__ should always be implicit parameters instead of having to be passed into a method, every time. Not a MLog() wrapper that calls a singleton to make them implicit.

I personally like to define a Log() as:

  #ifdef DEBUG
	#define MYLog(fmt, ...) NSLog(@"%s: " fmt, __PRETTY_FUNCTION__, ##__VA_ARGS__)
  #else
  	#define MYLog(...)
  #endif

This way, I can log on debug builds only (add -DDEBUG as an "Other C Flag" to Xcode), and it gives me the method name that it was called on. Just enough context to be useful to track something down, not enough to cause a sea of output noise.

You can use any of the C preprocessor macro's[1] this way.

1. http://gcc.gnu.org/onlinedocs/gcc-3.1.1/cpp/Standard-Predefi...

IIUC, your implementation does not solve the same problem.

The OP's implementation automatically determines the correct format string from the type of the variable. So you can simply do:

LOG_EXPR(some_int); LOG_EXPR(some_float); LOG_EXPR(some_complex_cocoa_type);

Render fine for me under OS X 10.6.4 both:

- Chrome: http://emberapp.com/pietrofmaggi/images/google-chrome

- Safari: http://emberapp.com/pietrofmaggi/images/safari

BTW: the article is not mine, I just posted it on HN.

It was screwed for me until I realized I was using different font sizes in my browser for proportional (13) and mono-spaced (12). Changing the size of the mono-spaced font to 13 solved it for me.