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

Hi,

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

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

I think that is not happen until 2.x because 1.x has a
backward compatibility. If a new required argument is
introduced, Subversion can't provide old API. To keep
backward compatibility, Subversion will keep the new
argument as optional.

Thanks,

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