I think what you discovered is a feature, not a bug.
From the first paragraph of the last section of perlsyn
Plain Old Comments (Not!) Much like the C preprocessor, Perl can process line directives. Using +this, one can control Perl's idea of filenames and line numbers in er +ror or warning messages (especially for strings that are processed wi +th eval()). The syntax for this mechanism is the same as for most C p +reprocessors: it matches the regular expression / ^#\s*line\s+(\d+)\s +*(?:\s"([^"]+)")?\s*$/ with $1 being the line number for the next lin +e, and $2 being the optional filename (specified within quotes).
I think the answer to your problem is, if you don't mean to do that, "Don't write lines like that!" :^)
Okay you lot, get your wings on the left, halos on the right. It's one size fits all, and "No!", you can't have a different color.
Pick up your cloud down the end and "Yes" if you get allocated a grey one they are a bit damp under foot, but someone has to get them.
Get used to the wings fast cos its an 8 hour day...unless the Govenor calls for a cyclone or hurricane, in which case 16 hour shifts are mandatory.
Just be grateful that you arrived just as the tornado season finished. Them buggers are real work.
In reply to Re: A F***ing bug in caller()
by BrowserUk
in thread A bug in caller() with Devel::Trace?
by shushu
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |