On Thu, May 10, 2001 at 03:28:16PM -0700, Doug MacEachern wrote:
http://perl.apache.org/~dougm/condsub-0.01.tar.gz
see test.pl for the examples.
i'm open to names/interface changes
I've had good luck (on non performance critical code) doing something
like (from memory):
use
On Tue, 10 Apr 2001, Paul Lindner wrote:
Hi,
As part of my ongoing effort to streamline my mod_perl apps, I've come
to discover the joy of constant subroutines and perl's ability to
inline or eliminate code at compile time. I have a solution that
works, but would be interested in seeing
On Thu, May 10, 2001 at 03:28:16PM -0700, Doug MacEachern wrote:
On Tue, 10 Apr 2001, Paul Lindner wrote:
DBG debug('whoa there boy');
FWIW, you may find the opcode-identical
debug 'whoa there boy' if DBG ;
more readable. Don't go to values other than 0 or 1 (not even 0 or
1) for
Hi,
As part of my ongoing effort to streamline my mod_perl apps, I've come
to discover the joy of constant subroutines and perl's ability to
inline or eliminate code at compile time. I have a solution that
works, but would be interested in seeing if others had better
syntactic sugar.. Anyway:
On Tue, 10 Apr 2001, Paul Lindner wrote:
Now, my question is: Is there some trick I could use to retain the
simple syntax:
debug "foo bar";
I always liked using a preprocessor to turn debug code on or off. ePerl
is OK, and Perl can of course be its own preprocessor.
-jwb
As part of my ongoing effort to streamline my mod_perl apps, I've come
to discover the joy of constant subroutines and perl's ability to
inline or eliminate code at compile time. I have a solution that
works, but would be interested in seeing if others had better
syntactic sugar..
You
Ah yes...
I remember it well.
CricInfo's home grown advert engine (mod_perl resident) was running like
the proverbial drain, and being its author, I was tasked to find out why.
A brief course through Devel::DProf later, we found the top of the
profiling tree in terms of time spent to be a
