Re: [patch] Use hash for optional args with long argument list in Ruby bindings

Hi,

In <ae6cb1100711191115u3c66b901h6249a65f705552e9@mail.gmail.com>
  "Re: [patch] Use hash for optional args with long argument list in Ruby bindings" on Mon, 19 Nov 2007 11:15:39 -0800,
  "Joe Swatosh" <joe.swatosh@gmail.com> wrote:

> > > BTW as I was changing switch_editor2 to be similar, I remembered that I
> > > hadn't asked yet: What is the reason for using the Hash for all arguments,
> > > instead of just the optional arguments?
> >
> > This is for consistency. Users who uses only required
> > arguments should use XXX API instead of XXX2 API.
> >
>
> Consistency with what?

All of XXX2 API in the Ruby bindings. Users of the Ruby
bindings will not be confused if all of XXX2 API accepts
only a Hash.

And if we use a Hash argument for all of XXX2 API, XXX2 API
will be more stable. If we use positional and optional
arguments for XXX2 API, we need to keep positional argument
as optional in the API's argument list when the feature
Subversion API changes a required argument to a optional
argument that is not optional argument in the current API.

Thanks,

--
kou
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org