Hi,<div><br></div><div>This week, Alessio Stalla and I are trying to get Parenscript to compile on ABCL. We&#39;re using Parenscript 2.3 as distributed with Quicklisp.</div><div><br></div><div>Parenscript 2.2 worked fine, after fixing a potential readtables issue. However, Parenscript 2.3 fails compilation during the compilation of the (DEFINE-EXPRESSION-OPERATOR LET # ...) toplevel form.</div>
<div><br></div><div>The problem is that it generates an expression (VAR X), which is then expanded to (DEFPARAMETER X). However, that&#39;s non-conforming because the initial value is required according to the CLHS. Looking at the definition of the VAR macro, I see the problem:</div>
<div><br></div><div>(defmacro VAR (name &amp;optional value docstring)</div><div>  `(defparameter ,name ,@(when value (list value)) ...))</div><div><br></div><div>can indeed lead to a (DEFPAMETER X)</div><div><br></div><div>
<br></div><div>I haven&#39;t found out if/why this isn&#39;t a problem on Parenscript 2.2 or why Parenscript 2.3 would cleanly compile on SBCL, because - like ABCL - it rejects forms like that.</div><div><br></div><div><br>
</div><div>If it is ABCL that&#39;s broken here, could you help us fix it? If not, could you fix parenscript to work on ABCL?</div><div><br></div><div>I&#39;m eager to learn about your analysis of the situation. If you need help on settin up ABCL, I&#39;ll gladly provide it.</div>
<div><br></div><div><br></div><div>Bye,</div><div><br></div><div>Erik</div>