From: James Edward Gray II <james@...>
Date: 2006-05-10T04:41:03+09:00
Subject: Re: Method Size - Best Practices

On May 9, 2006, at 1:46 PM, Eric Hodel wrote:

> A good and acceptable method size should be almost entirely based  
> on comfort.

This is a good point, I think.

I'm generally of the opinion the smaller the better.  The bigger  
stuff makes me think too much.

However, there are other factors to consider.  For example, the  
primary parser in FasterCSV is basically one method and it's longer  
than I prefer to have them.  Unfortunately, method calls are pretty  
expensive in Ruby and busting that tight loop into a bunch of small  
pieces degrades performance a fair amount.  Since the primary reason  
FasterCSV exists is to be quick, I leave it alone.  Now, I've  
commented it as much as possible and tested it as thoroughly as I can  
think to.  To use Eric's term, I am comfortable with the result.

James Edward Gray II