'use strict' causing me an error

[nysus]

What's up dudes? Another late night. I'm having a problem here. The following bit of code I'm using is generating an error with 'use strict':

BEGIN {
    use CGI::Carp qw(carpout fatalsToBrowser);
    open (LOG, ">errorlog.txt") or
        die("Unable to open errorlog.txt: $!\n");
    carpout(LOG);
}

The error code reads:

BEGIN not safe after errors--compilation aborted at /site_path/cgi-bin
+/event/eventform.cgi line 12.

Any ideas?
Note: Line 12 is the closing brace in the code above.

$PM = "Perl Monk's";
$MCF = "Most Clueless Friar";
$nysus = $PM . $MCF;

[japhy]

The documentation suggests you do:

You can pass filehandles to carpout() in a variety of ways. The "correct" way according to Tom Christiansen is to pass a reference to a filehandle GLOB:

  carpout(\*LOG);



japhy -- Perl and Regex Hacker

[nysus]

Tried it, still getting error.

$PM = "Perl Monk's";
$MCF = "Most Clueless Friar";
$nysus = $PM . $MCF;

[snowcrash]

the code runs fine for me under use strict;, probably your error is somewhere else in your code, or you're running some really weird ancient version of perl.
supplying a link to the whole code and giving your version of perl and your plattform might help!

cheers
snowcrash

[chipmunk]

The error that you quoted only says that the BEGIN block couldn't be compiled; it doesn't say why the BEGIN couldn't be compiled.

This is the same situation that I explained to you in Re: Re: Re: Re: Gettin ALL errors with carp module; CGI::Carp qw(fatalsToBrowser) only captures the generic "Compilation failed" error message, not all the warnings that explain why compilation failed. The only difference is this time the compilation problems are in a BEGIN block.

Once again, you can easily avoid this situation by testing your scripts from the command line to make sure they compile, before running them through the web server. Otherwise, check the server error logs for all the compilation warnings.

[stuffy]

I'm not an expert or anything, but have you tried removing the paranthesis around the "Unable to open errorlog.txt: $!\n"


or die "unable to open errorlog.txt: $!\n";

I'm not sure if that maters or not, I just know that I don't use them in my code.

Stuffy



update:

Opps, I was wrong, oh well, can't blame a guy for trying

[nysus]

Problem solved. I think it was the first problem and I forgot to hit save. Need to go to bed.

$PM = "Perl Monk's";
$MCF = "Most Clueless Friar";
$nysus = $PM . $MCF;