From: matz@... (Yukihiro Matsumoto)
Date: 2001-06-27T03:03:58+09:00
Subject: [ruby-talk:16920] Re: Method overloading (option) Was: Re:

Hi,

In message "[ruby-talk:16916] Re: Method overloading (option) Was: Re:"
    on 01/06/27, "Wayne Blair" <wayne.blair@relian.com> writes:

|You must admit, though, that absent explicit dispatch based on type most of
|us will need to at least occasionally type check arguments and use a switch
|or other pattern to vary behavior.  When you need to do this often, I think
|method overloading is a reasonably neat way to organize and maintain code.
|Admittedly, though, we might be better served if you were to explain
|(publish?) a better paradigm for handling such a scenario with ruby.

I admint explicit dispatch based on type often comes first to mind.
But I think things go better if we design programs based on protocols
(i.e. based on set of methods that objects can respond).

							matz.