comment on

And off the top of my head, I think most cli utilities take args before paths.. Why?

Certainly there is some historical technical reason for the practice. Why has it never changed? Two reasons. By having a common standard we simplify understanding and increase usability. And if it ain't broke, don't fix it.

--Solo

--
You said you wanted to be around when I made a mistake; well, this could be it, sweetheart.

In reply to Re: Why is it good practice for a cli script to take switch args before file list? by Solo
in thread Why is it good practice for a cli script to take switch args before file list? by leocharre

Are you posting in the right place? Check out Where do I post X? to know for sure.
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>
Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
Want more info? How to link or or How to display code and escape characters are good places to start.


Your skill will accomplish what the force of many cannot
	PerlMonks