parenscript issueshttps://gitlab.common-lisp.net/parenscript/parenscript/-/issues2020-05-13T07:52:30Zhttps://gitlab.common-lisp.net/parenscript/parenscript/-/issues/8compile-file-error for src/special-operators with ECL 20.4.24:2020-05-13T07:52:30ZPierre Neidhardtcompile-file-error for src/special-operators with ECL 20.4.24:Using the recently released ECL 20.4.24 (Guix package) and Parenscript from Quicklisp 2020-04-27 I get
```
COMPILE-FILE-ERROR while compiling
#<cl-source-file "parenscript" "src" "special-operators">
[Condition of type UIOP/LISP-B...Using the recently released ECL 20.4.24 (Guix package) and Parenscript from Quicklisp 2020-04-27 I get
```
COMPILE-FILE-ERROR while compiling
#<cl-source-file "parenscript" "src" "special-operators">
[Condition of type UIOP/LISP-BUILD:COMPILE-FILE-ERROR]
Restarts:
0: [RETRY] Retry compiling #<cl-source-file "parenscript" "src" "special-operators">.
1: [ACCEPT] Continue, treating compiling #<cl-source-file "parenscript" "src" "special-operators"> as having been successful.
2: [RETRY] Retry ASDF operation.
3: [CLEAR-CONFIGURATION-AND-RETRY] Retry ASDF operation after resetting the configuration.
4: [RETRY] Retry ASDF operation.
5: [CLEAR-CONFIGURATION-AND-RETRY] Retry ASDF operation after resetting the configuration.
--more--
Backtrace:
0: G1175
1: #<bytecompiled-function BYTECODES 0x7fad53b18000>
2: G81
3: TRACK-PACKAGE
4: G80
5: G79
6: G462
7: REPL-EVAL
8: LISTENER-EVAL
9: #<bytecompiled-function BYTECODES 0x7fad53b18050>
10: G540
11: G537
12: G571
13: REPL-LOOP
14: G50
15: G49
16: NIL
```https://gitlab.common-lisp.net/parenscript/parenscript/-/issues/2Document __PS_MV_REG2020-04-11T21:03:58ZBill St. ClairDocument __PS_MV_REGThe JavaScript variable `__PS_MV_REG` is used to return multiple values from functions. In Parenscript version 2.6, it was set only when you actually RETURNED multiple values. In 2.7, it is set to `[]` before every function return. If yo...The JavaScript variable `__PS_MV_REG` is used to return multiple values from functions. In Parenscript version 2.6, it was set only when you actually RETURNED multiple values. In 2.7, it is set to `[]` before every function return. If your JavaScript happens to `"use strict";`, this will cause a runtime error, unless you include the following before that code executes:
var __PS_MV_REG;
This declaration either needs to be added somewhere or, since I can't think of a good place to put it, other than the header of the HTML file including the Parenscript output, which isn't under Parenscript's control, documented.https://gitlab.common-lisp.net/parenscript/parenscript/-/issues/1readtable case should maybe be different on allegro (10.1)2018-10-13T20:16:11ZSky Hesterreadtable case should maybe be different on allegro (10.1)Package names were getting inverted in `src/package.lisp` during execution of `#'ql:quickload`; the problem seems to be resolved by using `:preserve` case in the parenscript `defreadtable` form.
```
(:case #-allegro :invert #+allegro :p...Package names were getting inverted in `src/package.lisp` during execution of `#'ql:quickload`; the problem seems to be resolved by using `:preserve` case in the parenscript `defreadtable` form.
```
(:case #-allegro :invert #+allegro :preserve)
```