CONDITION and ACTION;
[download]

E.g the code I've used for ages for flexible switch parsing, as the original simple arg handling module went against my tastes:

# maybe replace @ARGV below with my(@A)=@ARGV or similar, as we destro
+y the array
while($_=$ARGV[0]){
   /^(-V|-?-verbose)$/o  and do{shift; $verbose=1; ...; next};
   /^(-v|-?-negate)$/o   and do{shift; $negate=1;  ...; next};
   ...
   /^--?$/o              and do{shift;             ...; last}; # early
+ loop exit
   last;
}
[download]

Update 1:

Considering Bloodnok's variant below:

If your Perl's sufficiently recent, use my($_) instead of local to protect your caller while also protecting from anything called functions might do.

Also note that I'm using both next and last (loop exit condition) above. If you want a stronger distinction between looping and switching while retaining early loop exiting, you need either a second target label before the while() or set an explicit loop-exit flag variable for testing after the switch block. Simply saying last SWITCH in case of -- when restructuring does introduce a bug and changes semantics of -- to a NOP, with additional problems further down the line for non-option args.

Footnotes to my example above:

• For a cleaner syntax, you can use for my $_ (@ARGV) instead of the while if your loop nevers needs to access/eat multiple array members per iteration.
  But don't attempt the parens you normally should use with local, my and our: for my($_) (@ARGV)... will fail.
• To fall through, you can either set $_ suitably or unshift one or more values.
• Note the structural similarity of the lines above to, say, the suggestions in the mass pattern matching thread (->qr//, closures) or dispatch table methods (e.g. removing next, saying last whileloop depending on method-rc, and assuming NOP as default method)

Non-famous last words: I simply prefer the above solution over given/when and if-cascades for readability and perceived elegance. But given the ascii art readjustment and byte counts, it's not faster to maintain nor that much shorter.

---

---

Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!

Titles consisting of a single word are discouraged, and in most cases are disallowed outright.

Read Where should I post X? if you're not absolutely sure you're posting in the right place.

Please read these before you post! —

• How do I compose an effective node title?
• How do I post a question effectively?
• Markup in the Monastery

Posts may use any of the Perl Monks Approved HTML tags:

a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr

You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)

	For:		Use:
	&		&
	<		&lt;
	>		&gt;
	[		&#91;
	]		&#93;

Link using PerlMonks shortcuts! What shortcuts can I use for linking?

See Writeup Formatting Tips and other pages linked from there for more info.