in reply to Re: Profiling forking code?
in thread Profiling forking code?
Hmm. It's never that easy.
As it turns out, DProf segfaults while Devel::Profiler screws up the file when confronted with my scary class definition logic. What I'm doing is VERY insecure, so only do this if you TRUST your users.
I've designed it so that one general class is a shell around the class I load. I've done this for several reasons
- If there is a syntax error in one of the classes, I don't want bring down the entire process.
- I want to give my customers the chance to create their own code that ties in, without altering the core code
- I got a performance improvement when using this method over regular inheritance
As it turns out, the profilers do not approve of this.
Any brilliant ideas, fellow monks? Need I rewrite, or do you see a way for me to work around my problem?
|
---|
Replies are listed 'Best First'. | |
---|---|
Re^3: Profiling forking code?
by tall_man (Parson) on Jan 13, 2003 at 22:44 UTC | |
by Jeppe (Monk) on Jan 19, 2003 at 15:09 UTC |
In Section
Seekers of Perl Wisdom