Here's a completely different approach as a self-contained program for quick testing.

( The Getopt::Long::Configure isn't necessary here, but I personally use it whenever I'm using Getopt::Long as programs tend to grow to where I'd want it. )

#!/usr/bin/perl use strict; use warnings; use Getopt::Long (); my %opt = ( 'do-stuff' => 0, 'do-more' => 0 ); Getopt::Long::Configure( 'gnu_getopt' ); Getopt::Long::GetOptions( \%opt, 'do-stuff+', 'do-more+' ); my $counter = 1; if ( $opt{ 'do-stuff' } ) { my @stuff_to_do = ( sub { print "some stuff\n"; } ); push @stuff_to_do, sub { print "some more stuff\n"; } if $opt{ 'do +-more' }; for my $s ( @stuff_to_do ) { $s->(); } $counter--; } print "$counter\n";

In reply to Re: at continue, last by mr_mischief
in thread at continue, last by djerius

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":



  • 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! —
  • 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:
    & &amp;
    < &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.