Okay, thanks! (Sounds good to me, thoughts from others welcome, but
send 'em quick, 'cause I'm gonna write this soon. :-) )
-K
"Paul D. Smith" <pausmith@nortelnetworks.com> writes:
> %% kfogel@collab.net writes:
>
> k> We don't even need to insist that they be shell scripts, they'll just
> k> be programs that are passed certain arguments in a certain order.
>
> You might want to avoid depending on particular ordering. In my
> experience, this can make upgrades more painful than necessary.
>
> Passing arguments as command line options (e.g. use "-flag1 value1
> -flag2 value2" instead of order-specific "value1 value2") is quite a bit
> more flexible, since you can add more options and even remove obsolete
> ones, and old scripts will continue to work (unless they used the
> removed option of course).
>
> Also consider using the environment... that's very flexible as well and
> if you have lots of constant data it can save some work (you can have
> one function that sets the environment properly, then invokes the
> command).
>
> --
> -------------------------------------------------------------------------------
> Paul D. Smith <psmith@baynetworks.com> HASMAT--HA Software Methods & Tools
> "Please remain calm...I may be mad, but I am a professional." --Mad Scientist
> -------------------------------------------------------------------------------
> These are my opinions---Nortel Networks takes no responsibility for them.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
> For additional commands, e-mail: dev-help@subversion.tigris.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sat Oct 21 14:36:35 2006