Your code fails to import prototypes early enough (at compile time) to influence
the proper parsing of the later code. For example, say a constant was defined
in GD as:
package GD;
sub BIGFONT () { 35 }
Your code would cause this to be misparsed:
my $result = BIGFONT + 3;
because without the empty prototype,
BIGFONT is a normal subroutine,
and the +3 will be parsed as an argument to the subroutine. With the prototype,
we get the proper behavior (and even compile-time constant folding). So, with
compile-time importing, we get 38 for the answer, and without, we get 35.
So, to fix this, wrap my code in a BEGIN block, like so:
my $have_GD = 0;
BEGIN {
eval { require GD };
unless ($@) {
GD->import();
$have_GD = 1;
}
}
Your code does OK without considering prototypes. You haven't been burned,
but I'd add the word "yet" there.
-- Randal L. Schwartz, Perl hacker
update: Get rid of the "= 0" on the intialization.
Sorry.
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.