Beefy Boxes and Bandwidth Generously Provided by pair Networks
Keep It Simple, Stupid

comment on

( #3333=superdoc: print w/replies, xml ) Need Help??

Is line 7 (now commented out) what you referred to?

no error here on:
#!C:/perl/bin use warnings; use strict; BEGIN { local $@; # call_undefined_subroutine_or_another_error("argument"); } print "blabla\n";
from perldoc perlvar
 Error Indicators
   The variables $@, $!, $^E, and $? contain information about different
   types of error conditions that may appear during execution of a Perl
   program. The variables are shown ordered by the "distance" between the
   subsystem which reported the error and the Perl process. They correspond
   to errors detected by the Perl interpreter, C library, operating system,
   or an external program, respectively.

   To illustrate the differences between these variables, consider the
   following Perl expression, which uses a single-quoted string:

       eval q{
           open my $pipe, "/cdrom/install |" or die $!;
           my @res = <$pipe>;
           close $pipe or die "bad pipe: $?, $!";

   After execution of this statement all 4 variables may have been set.

   $@ is set if the string to be "eval"-ed did not compile (this may happen
   if "open" or "close" were imported with bad prototypes), or if Perl code
   executed during evaluation die()d . In these cases the value of $@ is
   the compile error, or the argument to "die" (which will interpolate $!
   and $?). (See also Fatal, though.)

In reply to Re^3: Unexpected result after localizing eval_error variable "$@" within "BEGIN" block by ww
in thread Unexpected result after localizing eval_error variable "$@" within "BEGIN" block by bdimych

Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post; it's "PerlMonks-approved HTML":

  • 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.
Log In?

What's my password?
Create A New User
Domain Nodelet?
and the web crawler heard nothing...

How do I use this?Last hourOther CB clients
Other Users?
Others romping around the Monastery: (3)
As of 2023-12-10 07:30 GMT
Find Nodes?
    Voting Booth?
    What's your preferred 'use VERSION' for new CPAN modules in 2023?

    Results (38 votes). Check out past polls.