If you're planning to read through a list of files from the command line, then you should really use <> - it saves you all the work of opening all the files etc..

And, rather than all that work with $in_pod, I'd just use the range operator.

A line containing no alphanumerics is not counted as a line of code

Not sure I'd agree with that. Haven't you seen some of the JAPHs posted :) I'd personally check for absence of non-whitespace.

So, personally, I'd reduce all this down to:

#!/usr/bin/perl -w

use strict;
my $total = my $pod = my $comment = my $blank = my $code = 0;

while(<>) {
  $total++;
  if ( /^=\w+/ .. /^=cut/ ) { $pod++; next }
  if ( /^\s*#/ )            { $comment++; next }
  unless ( /\S/ )           { $blank++; next }
  $code++;
}

print <<END;
 Total:    $total
 POD:      $pod
 Comments: $comment
 Blank:    $blank
 Code:     $code
END
[download]

Tony

---

---

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.