Re^3: Profiling forking code?

According to perldebguts:
A hash %DB::sub is maintained, whose keys are subroutine names and whose values have the form "filename:startline-endline". "filename" has the form "(eval 34)" for subroutines defined inside "eval"s, or "(re_eval 19)" for those within regex code assertions.

It seems to me your profiler would be happier (and you would find the output more usable) if you pre-created the object packages and used them from files instead of creating them inside eval.

Comment on Re^3: Profiling forking code?

Replies are listed 'Best First'.
Re: Re^3: Profiling forking code? by Jeppe (Monk) on Jan 19, 2003 at 15:09 UTC
If I did that, I would remove quite a few reasons why I use perl rather than java. Hmm. I wonder if I can make a script that creates those classes for me, rather than loading those classes in the current way. Just for testing.	[reply]