They are poison. You should only use them when you have to, like forcing an array or subroutine reference. Here's two typical examples:
sub my_grep(&) { ... }
sub my_pop(\@) { ... }
Putting in scalars (i.e. ($$)) is asking for trouble since it converts any arrays to scalars automatically. I found this really quite worrying, and you can see my brief rant in
Function Prototypes and Array vs. List (Pt. 2).
This all comes from a technique of jamming arrays into functions, which I do all the time to be efficient. Things like this:
my $sth = $dbh->prepare("SELECT id,name,age FROM foo");
$sth->execute();
while (my $row = $sth->fetchrow())
{
$self->some_function(@$row);
}
Now, if you've prototyped your function, you're going to get the number 3 every time. This is put in to the 'id' field, so you might actually think it's valid data, too.
Instead, just leave those things off. That's why
merlyn says "...and this is why we tell people DO NOT USE PROTOTYPES".
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.