comment on

Let me explain my suggestion in more detail.

You're having errors in the eval, and you want to trap them. The eval will trap any die and store it in $@, which you're then processing. The problem is that a warn does not get trapped by eval, it just goes to STDERR. So the error is printed to that file, and then when you test $@ you have no sign that there was a problem.

My suggestion turns warns into dies so that eval can trap them so that the code that you presented does something closer to what you say that you want. You're right that I've left warns as dies afterwards. That's fixable. In fact try the following variation of the eval and tell me whether it works better:

  # create an IMAP connection
  eval {
    # This is the inserted line.
    local $SIG{__WARN__} = sub {die @_};
    $imap = Mail::IMAPClient->new(  
      Server    => $IMAP,
      User      => $UNAME,
      Password  => $PWD, 
      Uid       => 0, 
      Debug     => $DEBUGGING,
    ) or carp "Cannot connect to $IMAP as $UNAME: $@";
  };
[download]

I give you good odds that this will cause your eval to do what you want it to do, and it won't make warns into dies later in your program.

In reply to Re^3: Understanding compiletime vs. runtime by tilly
in thread Understanding compiletime vs. runtime by punkish

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.


"be consistent"
	PerlMonks