http://www.perlmonks.org?node_id=249354


in reply to Re: Re^2: use CGI::Carp qw(fatalsToBrowser); (is compile-time)
in thread use CGI::Carp qw(fatalsToBrowser);

A little experimentation reveals that perl throws syntax errors even before compilation really begins (or, at least before BEGIN blocks

No. You show me your experiement and I'll show you mine. ;) Heck, I'll show you mine anyway:

BEGIN { warn "Compiled first line of script"; } ....
gives
Compiled first line of script at - line 1. syntax error at - line 2, near "..."
or
use CGI::Carp qw( fatalsToBrowser ); ....
gives
Content-type: text/html <H1>Software error:</H1> <CODE>syntax error at - line 2, near &quot;...&quot; Execution of - aborted due to compilation errors. </C0DE> <P> For help, please send mail to this site's webmaster, giving this error + message and the time and date of the error. [Wed Apr 9 11:36:09 2003] -: syntax error at - line 2, near "..." [Wed Apr 9 11:36:09 2003] -: Execution of - aborted due to compilatio +n errors.

Syntax errors in code that appears before the use CGI::Carp line will not be caught. For many CGI scripts, this boils down to just the #! line. But as pointed out elsewhere in this thread, CGI::Application was being used and the CGI::Carp was being used in the wrong place for it to take affect soon enough.

Perl code is compiled one-statement-at-a-time and so-called "compile-time" constructs get executed right after the statment they are contained in has been compiled. So there is no single "compile time" nor a single "run time". So each statement has one compile time and zero or more run times.

Things like BEGIN and use cause statements' run times to happen sooner while things like eval cause statements' compile times to happen later.

                - tye