On Wed, Jul 18, 2012 at 03:58:18PM -0400, Michael Mol wrote: > On Wed, Jul 18, 2012 at 3:49 PM, Peter Stuge <[email protected]> wrote: > > William Hubbs wrote: > >> /etc/init.d/foo stop start > >> > >> would no longer work the way you might expect because there would be no > >> way to tell whether start is a command or an argument to stop. > >> > >> What are your thoughts about this change? > > > > /etc/init.d/foo stop start > > > > along with all other commands can work like before. > > > > /etc/init.d/foo stop -- start > > > > can pass start as an argument to the stop command. > > I like this approach, because its use of -- continues expected > commandline parsing behaviors from other commands, making it > intuitive. > > I.e. > > touch -- -an-ugly-filename > ls -l -- -an-ugly-filename > rm -- -an-ugly-filename
Theis still breaks backward compatibility though, e.g. /etc/init.d/foo command1 -- arg1 arg2 command2 has issues. The other approach, which is on the bug, still has this issue, e.g. /etc/init.d/foo command1 arg1 arg2 command2 arg3 arg4 command3 arg5 gets pretty ugly pretty quick. which arguments go with which commands is subject to interpretation. William
pgpOp3VKyhnRD.pgp
Description: PGP signature
