On Tue, Dec 02, 2008 at 07:00:01AM -0800, Nicholas Clark wrote:
> Change 34979 by [EMAIL PROTECTED] on 2008/12/02 14:46:17
>
> Add two more flags, PERLDBf_SAVESRC_NOSUBS and PERLDBf_SAVESRC_INVALID,
> which give total control over when source code from evals is stored.
> The debugger doesn't need them, but I forsee that profilers might.
The foresight is strong in you young Nicholas!
Here's an item from my Christmas wishlist:
We have:
0x100 Provide informative "file" names for evals based on the place they
were compiled.
0x200 Provide informative names to anonymous subroutines based on the place
they were compiled.
I'd like to see a similar option to give BEGIN and END subs 'informative
names' in the same way.
At the moment a package can have multiple BEGINs, including implicit
ones for 'use' statements but they all have the same name so only one
entry ends up in %DB::sub (if $^P & 0x10). It's the same with END
blocks, though multiple ENDs in a package are rare.
If non-trivial perhaps it could find a home in the TODO file.
Tim.
