Comments on: Ruby logging and performance http://brian.pontarelli.com/2006/07/03/ruby-logging-and-performance/ Brian Pontarelli Wed, 08 Feb 2012 15:34:20 +0000 hourly 1 http://wordpress.org/?v=3.0.4 By: Brian Pontarelli http://brian.pontarelli.com/2006/07/03/ruby-logging-and-performance/#comment-317 Brian Pontarelli Thu, 06 Jul 2006 15:21:15 +0000 http://brian.pontarelli.com/2006/07/03/ruby-logging-and-performance/#comment-317 Excellent point! They look very similar. This could help distinquish: logger.debug do "foo" end (Can you do blocks like that?) But that kinda looks like ass. I think the if statements perhaps are the cleanest way to handle it. Excellent point! They look very similar. This could help distinquish:

logger.debug do “foo” end

(Can you do blocks like that?) But that kinda looks like ass. I think the if statements perhaps are the cleanest way to handle it.

]]> By: David Thomas http://brian.pontarelli.com/2006/07/03/ruby-logging-and-performance/#comment-312 David Thomas Wed, 05 Jul 2006 23:11:19 +0000 http://brian.pontarelli.com/2006/07/03/ruby-logging-and-performance/#comment-312 Great example of improving performance while logging in Ruby. Though, from a maintenance perspective, I'd bet money that "the next guy" who comes along and starts logging will use parens. Why? Simply because he didn't know the trick and braces look like parens when quickly scanning example code. Otherwise, awesome post! Great example of improving performance while logging in Ruby. Though, from a maintenance perspective, I’d bet money that “the next guy” who comes along and starts logging will use parens. Why? Simply because he didn’t know the trick and braces look like parens when quickly scanning example code.

Otherwise, awesome post!

]]>