At 02:27 PM 3/10/00 -0500, Dan Sugalski wrote:
>At 02:15 PM 3/10/00 -0500, Charles Bailey wrote:
>
>>>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?
>
>I'll default it to off, then. Or shall I make it platform sensitive--off
>for VAXen and on for Alphas? (Under the presumptions that vaxen have less
>CPU power to burn. I can see it making quite a difference on some of the
>slower vaxen...)
Okay, I double-checked, and it turns out that I was a tad confused. The
perl debugger's always available. It's the extra added goodies you get with
the -D flag that get enabled by the DEBUGGING macro. Given this (how often
does anyone trace opcodes or dump the parse tree?) I think I'll default it
to off and leave it at that.
Dan
--------------------------------------"it's like this"-------------------
Dan Sugalski even samurai
[EMAIL PROTECTED] have teddy bears and even
teddy bears get drunk
