in reply to Getopt::Long good style?

I don't have much to say myself, because others have done so before me:

You might want to peruse Super Search next time before posting a question like this… :-)

Also, I'd advise against using a hash with Getopt::Long. It looks tidier, but you lose the advantage of strictures — the only clue that you misspelt a hash key is odd behaviour from the script. Instead, use my variables (and declare them in-place, as per above link), and use strict, so that Perl will find your typos for you.

Makeshifts last the longest.

Replies are listed 'Best First'.
Re^2: Getopt::Long good style?
by Skeeve (Parson) on Jul 28, 2004 at 18:12 UTC
    I'd love to use Super Search for questions like this. But tell me: If you were in my shoes? What would you have searched for? I had no clue what to search. Please show me what I would have found and how it should have answered my question.
[reply]
      Cutting and pasting the title of the OP itself turns up useful nodes like 241367.
[reply]

In Section Seekers of Perl Wisdom