Re: Passing unused opts to every command considered harmful

On Dec 17, 2007, at 8:36 AM, David Glasser wrote:

> This means that authors of a program
> like svnmerge.py which invoke "svn" with many different subcommands
> need to carefully figure out which subcommands take --non-interactive
> and which do not;

As a writer of scripts that invoke svn myself, I'm baffled here. Does
not svnmerge.py also have to "carefully figure out which subcommands"
take two arguments (as diff), or which can only use an URL, or which
need a "--force", or myriad other matters not so susceptible to this
blanket-acceptance approach?

> and worse still, if in a future version we suddenly
> come up with a new interactive mode in a subcommand that didn't take
> --non-interactive before, the script will suddenly stop working.

That sounds like an API change to me, and "presumptively a bug," as
someone or other opined in IRC just Friday.

-==-
Jack Repenning
Chief Technology Officer
CollabNet, Inc.
8000 Marina Boulevard, Suite 600
Brisbane, California 94005
office: +1 650.228.2562
mobile: +1 408.835.8090
raindance: +1 877.326.2337, x844.7461
aim: jackrepenning
skype: jrepenning

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Mon Dec 17 19:20:34 2007