Re: How do I process many (conflicting) command line parameters?

Maybe you should split the processing into a number of tasks and use pipes to plumb them together? Instead of one complicated uber tool you end up with a small number of simple tools that you can chain together to do complicated things. That can work just as well for Windows as it does for *nix.

Premature optimization is the root of all job security

Comment on Re: How do I process many (conflicting) command line parameters?

Replies are listed 'Best First'.
Re^2: How do I process many (conflicting) command line parameters? by ozboomer (Friar) on Jun 30, 2017 at 03:59 UTC
Heh... it's actually the way I most often build my utilities - the whole idea of a 'software tool' - but there's a trade-off point between having a single tool with lots of options compared to having a lot of different tools (and remembering how everything works); in Linux parlance, you could pipe input/output data streams between cp, sed and cut or you could run a single Perl program with command line options to do one, some or all of the same functions as the individual tools. 'Your mileage may vary' as they say...	[reply]

Replies are listed 'Best First'.

Re^2: How do I process many (conflicting) command line parameters?
by ozboomer (Friar) on Jun 30, 2017 at 03:59 UTC

Heh... it's actually the way I most often build my utilities - the whole idea of a 'software tool' - but there's a trade-off point between having a single tool with lots of options compared to having a lot of different tools (and remembering how everything works); in Linux parlance, you could pipe input/output data streams between cp, sed and cut or you could run a single Perl program with command line options to do one, some or all of the same functions as the individual tools.

'Your mileage may vary' as they say...

[reply]