Re: RFC: Script testers needed


laziness, impatience, and hubris
	PerlMonks

by Athanasius (Archbishop)

on Jun 06, 2013 at 16:10 UTC ( [id://1037480]=note: print w/replies, xml )

Need Help??

Some comments on the code:

Digest::MD5::md5_hex is imported but not used.
$location is initialised via user input but then not used.
Line 61 could be simplified to: my $ext = $1;
Lines 71 and 72 could be written as a single line: $filename =~ s{.*/(.*)$}{$1};
The next statements on lines 76 and 94 are redundant, as each occurs immediately before the loop iterates anyway.
In addition, on line 94 the or clause does nothing. next can’t “fail”, and it doesn’t return a value.
Lines 101 to 105 could be rewritten as a single line: print $error eq '' ? "No errors.\n" : "\nErrors: $error";

Hope that helps,

Comment on Re: RFC: Script testers needed Select or Download Code

Replies are listed 'Best First'.

Re^2: RFC: Script testers needed
by AI Cowboy (Beadle) on Jun 06, 2013 at 17:13 UTC

In order:

You're right! Digest::MD5::md5_hex was used previously to check the md5 hash of the file. I will remove it now that it is no longer used.
Whoa, that's a bit of a big error on my part. I guess I edited the use of $location out, but that's not how it's supposed to be. Thanks for catching that.
Good point. I'm not very well versed on the intricacies of regular expressions, thanks for the tip.
Alright, thanks for the help there, once again regular expressions aren't something I'm used to using much of; usually just simple substitution or word-matching regex's.
Good catch, they will be removed.
Kind of a newby error to make, on my part. I was trying to simply make sure that many of the possible errors were found and reported to the user, and I didn't take the time to figure out if next even CAN have an error. I'll remove the or statement.
Awesome, thanks for that tip :)

That was a lot of help, I'll be sure to tweak the code up using your help! Thanks!

In Section Meditations