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

On 11/20/07, Kouhei Sutou <kou@cozmixng.org> wrote:
> Hi,
>

>
> 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.
>
>

Ah. You are thinking in terms of a required argument becoming
optional. I was thinking in terms of a new required argument.
Won't we still have to rev the API if there is a new required argument?
(Granted that doesn't seem like it should happen very often).

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