From: Bruno H. <br...@cl...> - 2005-01-20 16:35:41
|
Sam wrote: > unfortunately, when I de-activate the initial special bindings and > re-activate them at the end right before the implicit_progn(), > I get some additional test failures instead. But at least this modification handles the "free SPECIAL declarations" correctly. For the "bound SPECIAL declarations", i.e. those symbols with occur in both variable lists, you need to set the active_bit already when the corresponding binding is activated. When I look at funcall_iclosure / bind_next_var, it looks like the code should already do this. Which bind-eval tests exactly are still failing? > I wonder if keeping two separate vectors of special vars and args > and binding the specials only after argument processing right before the > implicit_progn() is a cleaner solution. It would consume more memory - gratuitously. Bruno |