An OT stylistic note.
I find that explicit referencing of @_ inside of functions
is problematic. It is too easy when modifying code to
accidentally access this when you meant that.
For which reason the two main styles you see go like:
sub FileCheck {
my $file = shift;
my $perm = shift;
my $oot = shift;
# etc
}
# or
sub FileCheck {
my ($file, $perm, $oot) = @_;
# etc
}
And now if you decide while developing code that you
want to change the order of arguments, you are much less
likely to make a mistake.
(I also don't much like StudlyCaps, but that is one of
those "important irrelevancies". It is good to be
consistent about naming patterns, but which consistent
choice you make is irrelevant. InOtherWords I don't
code that way, but there is nothing wrong with doing so.)
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: |
| & | | & |
| < | | < |
| > | | > |
| [ | | [ |
| ] | | ] |
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.
|
|