On Fri, 25 Aug 2006 12:53:44 +0900, Joel VanderWerf wrote:

> Why not just stick internal_helper in a nested module? (Or does 
> internal_helper need to access class state?)

That works for me in the current case; internal_helper routines don't need
any class state (and, in general, I try to avoid having any such state,
rebelling against my C days of static variables).  

Out of curiosity, though, if I did need my internal_helper routine to get
at state, what would you recommend?  Seems like the only solution in Ruby
is to extract the internals out to another object that's only called by my
public, interface object - but that seems so un-Rubyish.

Jay