From: Tom Christiansen [mailto:tchrist@chthon.perl.com] > >Test 2 uses this to silence the debugger > > > $ENV{'PERLDB_OPTS'} = 'noTTY' ; > > >This feature of the debugger seems to be broken in 5.6.0-RC2. > ... > > Back to your option ssue. The fix is to designate "noTTY" a boolean. > But this just dodges the real bug, which was that it was a design > flaw that some variables are 0 or 1, others are null or nonnull, > and at least one--this case in particular--you've got a "foo" and > a "nofoo" option. No wonder it doesn't make sense. So you've > you've got three different conventions, and yet one "default" for > setting, a default that displays no smarts at all about what it's > defaulting. The whole option thing is one massive design nightmare, > something from another dimension. Here is a patch that makes "TTY" and "noTTY" booleans. *** perl5db.pl.orig Fri Mar 17 11:06:37 2000 --- perl5db.pl Fri Mar 17 11:08:26 2000 *************** *** 1828,1835 **** # too dangerous to let intuitive usage overwrite important things # defaultion should never be the default my %opt_needs_val = map { ( $_ => 1 ) } qw{ ! arrayDepth hashDepth LineInfo maxTraceLen noTTY ornaments ! pager quote ReadLine recallCommand RemotePort ShellBang TTY }; while (length) { my $val_defaulted; --- 1828,1835 ---- # too dangerous to let intuitive usage overwrite important things # defaultion should never be the default my %opt_needs_val = map { ( $_ => 1 ) } qw{ ! arrayDepth hashDepth LineInfo maxTraceLen ornaments ! pager quote ReadLine recallCommand RemotePort ShellBang }; while (length) { my $val_defaulted;Thread Previous | Thread Next