#85: CL-JSON throws an error under ABCL where SBCL doesn't. -------------------------+-------------------------------------------------- Reporter: ehuelsmann | Owner: somebody Type: defect | Status: new Priority: major | Milestone: Component: other | Version: Resolution: | Keywords: -------------------------+-------------------------------------------------- Comment(by mevenson): Indeed it does point to something quite mysterious. After a couple hours of fiddling around, it seems that PROGV forms in nested function calls are somehow "leaking" the binding out to improper references. I wasn't able to distill a test case outside of CL-JSON, but the following simpler form causes the same type of error: {{{ (decode-json-from-string "{\"foo\": [1]}") }}} -- Ticket URL: <http://trac.common-lisp.net/armedbear/ticket/85#comment:1> armedbear <http://common-lisp.net/project/armedbear> armedbear

#85: CL-JSON throws an error under ABCL where SBCL doesn't. -------------------------+-------------------------------------------------- Reporter: ehuelsmann | Owner: mevenson Type: defect | Status: assigned Priority: major | Milestone: Component: compiler | Version: Resolution: | Keywords: -------------------------+-------------------------------------------------- Changes (by mevenson): * owner: ehuelsmann => mevenson * status: new => assigned Comment: Reproduction of the bug away from CL-JSON: {{{ (defvar *a* "initial") (defun foo () (progv '(*a*) '((symbol-value '*a*)) (setf *a* "foo") (return-from foo))) (defun bar () (format t "before: ~A~%" *a*) (foo) (format t "after: ~A~%" *a*)) }}} Compiling and executing BAR shows {{{ CL-USER> (bar) before: initial after: foo NIL }}} Which shows that the special binding hasn't been reset. -- Ticket URL: <http://trac.common-lisp.net/armedbear/ticket/85#comment:3> armedbear <http://common-lisp.net/project/armedbear> armedbear