Re: Bindings question: do keyword args make us name-sensitive?

Karl Fogel <kfogel@red-bean.com> writes:

> "David Glasser" <glasser@davidglasser.net> writes:
> > A little voice in the back of my head tells me that it's not OK to
> > change parameter names in public APIs, because in some bindings you
> > can use the parameter name as a keyword-style arg in calls. Am I just
> > making that up?

Weeell, I know the swig-python bindings don't make use of this.
But that's been a long-standing gripe of mine. I don't know if
the ctypes stuff can do this, but I hope so.

So, yeah, I'd rather not change the names of parameters. But, I
don't think any binding uses them *yet*, so changes are OK for
now. I'd say we don't have to lock the parameter names down
until a binding starts using them.

-- 
Eric Gillespie <*> epg@pretzelnet.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org