chad fowler  <chadfowler / yahoo.com> wrote:
>> Which pitfall?
>> 
>> In my experience, overloading based on the number of
>> arguments
>> is usually not a good programming style, but
>> overloading 
>> based on the type of arguments often is.
>> 
>
>But, Josh, there isn't much "type" to overload based
>on in Ruby.  I know where you're coming from, though.

Of course there are types in Ruby.  Variables don't
have a fixed type, and both types and methods can
be created dynamically, but there are types, and
every Ruby object has one.


-= Josh