This would be sufficient:

BEGIN {
    if( eval "use fakemodule; 1;") {
        print STDERR "Loaded fakemodule";
    }
    else {
        print STDERR "Couldn't load fakemodule.";
    }
}
[download]

Don't put BEGIN blocks inside a subroutine, they won't do what you want.

Don't print in the BEGIN block, it will come before the Content-type header

Calling a subroutine with the '&a' syntax has the following effects, from perlsub:

• &NAME(LIST); # Circumvent prototypes.
  
• &NAME; # Makes current @_ visible to called subroutine.

In your code you used the &a; form, which would make the current @_ visible to the called subroutine. For example:

first(1,2,3);

sub first {
  &second;
}

sub second {
    print for @_;
}

# Output is 123
[download]

Although it isn't relevant for this particular case it is still good to be aware of the prototype circumvention behaviour. Here is an example:

use strict;
use warnings;
use Data::Dumper;

sub pro(\@) {
    print Dumper \@_;
}

my @list = (1,2,3);
pro(@list);
&pro(@list);
[download]

Output:

$VAR1 = [
          [
            1,
            2,
            3
          ]
        ];
$VAR1 = [
          1,
          2,
          3
        ];
[download]

---

---

• Are you posting in the right place? Check out Where do I post X? to know for sure.
• Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:

  <code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>

• Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
• Want more info? How to link or How to display code and escape characters are good places to start.