comment on

With no command line parameters I get:

Use of uninitialized value in string eq at perl-assoc.pl line 64.
[download]

three times interspersed with the expected output. All the ARGV tests should be wrapped in a if (@ARGV) {...} block. The current default case else then belongs to the new outer if block (do the else if there are no command line args).

Your example uses /f, but /F is required for formatting.

It would be worth running your code through perltidy - the indentation is rather arbitary in places.

unless($warnalert = 1) is an error. It should probably be unless($warnalert)

chop $ext; is an error. It is not required at all. There can be no line ends in command line arguments in Windows.

print "$ext=$class \n" would be better as print "$ext = $class\n".

DWIM is Perl's answer to Gödel

In reply to Re: perl-assoc 0.2 by GrandFather
in thread perl-assoc 0.4 by Maze

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 How to display code and escape characters are good places to start.


Just another Perl shrine
	PerlMonks