Marco Baringer mbaringer@common-lisp.net writes:
- swank-openmcl.lisp (*buffer-offset*, *buffer-name*): Supply
- default values. This avoids unbound value errors when compiling an
- asdf system signals errors.
Do you know why the errors come about?
I think the idea of not having default bindings for those variables is to trap bugs elsewhere. This might be one.
Luke Gorrie lgorrie@common-lisp.net writes:
Marco Baringer mbaringer@common-lisp.net writes:
- swank-openmcl.lisp (*buffer-offset*, *buffer-name*): Supply
- default values. This avoids unbound value errors when compiling an
- asdf system signals errors.
Do you know why the errors come about?
because swank:operate-on-system-for-emacs calls asdf:operate-on-system directly without going through a backend function (unlike compile-file and compile-string) and therefore the openmcl backend doesn't have the opportunity to bind *buffer-name* and *buffer-offset*, which are specific to the openmcl backend.
we could either make operate-on-system-for-emacs go through a backend function, or make swank-compiler (which all three functions use) a backend function/macro which implementations could use to bind whatever state variables they need.