Hi kir,

One way to do this is with caller. Also I've included the error checking suggested in do.

sub include {
  my $file = shift;
  unless (my $return = do $file) {
    my (undef, $callerfile, $callerline) = caller;
    my $from = "included from $callerfile line $callerline";
    die "Couldn't parse $file, $from:\n$@" if $@;
    die "Couldn't do $file, $from: $!" unless defined $return;
    die "Couldn't run $file, $from" unless $return;
  }
}

[download]

Using some test code in which test.pl uses include on A.pm, which in turn includes B.pm, then X.pm with a die, I get this output:

Couldn't parse A.pm, included from test.pl line 8:
Couldn't parse B.pm, included from A.pm line 7:
Couldn't parse X.pm, included from B.pm line 7:
Blammo at X.pm line 6.

[download]

Hope this helps,
-- Hauke D

In reply to Re: print stack of "do" files on error by haukex
in thread print stack of "do" files on error by kir

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


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.