After a bit of discussion Tim and I devised the following little
program that solves the problem -- especially helpful for students
who need to track down mistyped identifiers, etc. If they have mistyped
the same thing twice, then correcting one occurrence and re-compiling
is a problem because they won't get a warning the second time, and so
obscure run-time errors can remain.
But after
ENTER resetvars
they will get the warning when they recompile!
define ved_resetvars();
;;; cancel all automatically declared variables and reset popwarnings
applist(popwarnings, syscancel);
[] -> popwarnings;
vedputmessage('"popwarnings" has been reset')
enddefine;
Nice and simple!
(Doesn't work for sections, but people who know enough to use sections
should know enough to sort themselves out.)
Then of course this can be used to re-set and re-compile.
define ved_recompile;
ved_resetvars();
ved_l1();
enddefine;
Aaron
|