wait, are we talking VMS debug support, or PERL debug support.
VMS debug support should NOT change the execution speed; it makes the image
a bit larger (the symbol tables are loaded in virutal memory) but I've never
found an "debug" image to be any different in speed than one without debug.
In fact, somewhere buried in ancient code, I have a little "trick" which
flips the debug bit in the header so you can turn on debugging dynamically
by remote control...
I assumed Dan was speaking about the Perl debugger, which is a pile of
psuedocode?
Carl
-----Original Message-----
From: Charles Bailey [mailto:[EMAIL PROTECTED]]
Sent: Friday, March 10, 2000 2:15 PM
To: Dan Sugalski
Cc: [EMAIL PROTECTED]
Subject: Re: 5.6.0 RC1 and the perl debugger
> I noticed that 5.6.0 RC doesn't build with the perl debugger enabled by
> default. (A silly error--things are checking for .eqs."Y" while the
> symbol's set with a lowercase y...)
When the rewrite comes, it may be easier to change these tests to
just C<$ If foo Then> and let DCL do the rest.
> I'm gonna add in a question to CONFIGURE.COM for this and get it back.
> Should it default to on (the way we've always done it) or to off, which
> gets you a faster perl?
I think we're at the point now where Perl's stable enough not to need
the DEBUG support by default, so we may be fine with it off. Anyone
have an idea how much difference in speed it makes?
Regards,
Charles Bailey [EMAIL PROTECTED]
