At 02:15 PM 3/10/00 -0500, Charles Bailey wrote:
>>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 changed the tests for the debugging question just a minute or three ago.
The string comparisons (and the dain bramaged "T"/"F" options for some
questions) are in because of my relative inexperience with DCL when I was
assaulting Peter's original CONFIGURE.COM.
I figured I'd fix 'em when subconfigure went modular, and I'd hack out all
traces of VAX C along the way, too. That should clean things up a bunch.
>>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...)
Dan
--------------------------------------"it's like this"-------------------
Dan Sugalski even samurai
[EMAIL PROTECTED] have teddy bears and even
teddy bears get drunk
