defvar: warn about prior lexical uses.

Now that the compiler has a more efficient treatment of global
lexical variables, code which accesses global variables that
have not yet been defined will misbehave if the intent is to
for those variables to be dynamically scoped.

There is such a bug in the op expander, in fact.

* eval.c (me_def_variable): When defvar/defparm are expanding,
they now check whether there is an outstanding unbound warning
against the variable. If so, then a warning is issued that the
variable was previously used lexically and is now being marked
special.

* unwind.c (uw_warning_exists): New function.

* unwind.h (uw_warning_exists): Declared.

1 files changed, 1 insertions, 0 deletions

diff --git a/unwind.h b/unwind.h
index b08f8dc9..33106a0a 100644
--- a/unwind.h
+++ b/unwind.h
@@ -137,6 +137,7 @@ noreturn val uw_throwfv(val sym, val fmt, struct args *);
 noreturn val uw_errorf(val fmt, ...);
 noreturn val uw_errorfv(val fmt, struct args *args);
 val uw_defer_warning(val args);
+val uw_warning_exists(val tag);
 val uw_dump_deferred_warnings(val stream);
 val uw_release_deferred_warnings(void);
 val uw_purge_deferred_warning(val tag);