GNU bug report logs - #40088
27.0.90; Symbol’s value as variable is void: debugger-outer-match-data

Previous Next

Full log

View this message in rfc822 format

From: Drew Adams <drew.adams <at> oracle.com>
To: Michael Heerdegen <michael_heerdegen <at> web.de>, Dmitry Gutov <dgutov <at> yandex.ru>
Cc: Joost Kremers <joostkremers <at> fastmail.fm>, 40088 <at> debbugs.gnu.org
Subject: bug#40088: 27.0.90; Symbol?s value as variable is void: debugger-outer-match-data
Date: Tue, 17 Mar 2020 17:12:48 -0700 (PDT)

> > It doesn't look like this bug should be solved this way. Having
> > "... is unbound" is better because it points at some function
> > forgetting to let-bind this variable (someone should find out which
> > and to which values).
> >
> > Whereas if it had an init value, that would mask such problems because
> > nil is a somewhat valid value.
> 
> If there are lots of cases like this under the cited thousands then I
> guess we need a way to declare a variable special without assigning an
> init value.
> 
> I don't like the (defvar var) syntax we have now.  It's different than
> the (defvar var value) syntax in more than one way, and it's too
> easily overseeable that it doesn't make a variable special.

FWIW, I agree with this.

I was going to say something similar a
while back, but chickened out. ;-)

Not sure what a good alternative would be,
or whether it would be considered too late.

Common Lisp handles it differently, but its
approach can also be complicated, as Stefan
knows.

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.