This is indeed a bug in named-readtables due to an incompatible API change from Allegro 8.1 to 8.2. I've emailed Robert Goldman and tried emailing Tobias Rittweiler (tcr@freebits.de bounces - does anyone know his current email address?) with the fix.

If you need to run Parenscript on ACL 8.2 right now: Line 88 of cruft.lisp in named-readtables has to be changed to: #+ :allegro (excl:named-readtable (readtable-name-for-allegro name) nil)

About the Parenscript unit tests, this is the first time I've run them on Allegro. Everything works except for certain escape sequences in strings; I'll take a look why.

Vladimir

On Sat, Jan 7, 2012 at 2:59 PM, Vladimir Sedach vsedach@gmail.com wrote:

This looks like a named-readtables/allegro issue. I'll need to get a trial edition and see what's wrong.

Vladimir

2012/1/6 Anton Vodonosov avodonosov@yandex.ru:

...

-------- Forwarding the Robert's response  -------- 06.01.2012, 19:06, "Robert Goldman" rpgoldman@sift.info:

On 1/6/12 Jan 6 -8:51 AM, Anton Vodonosov wrote:

...

I don't know, the test results for Allegro are contributed by  Robert Goldman, lets ask him.

Robert, when you run tests do you use alisp or mlisp?

I use alisp (ANSI-compliant) lisp exclusively for these tests.

Cheers, r

P.S. You may need to forward this, since I am not a subscriber of the parenscript mailing list.

...

06.01.2012, 17:13, "Gary King" gwking@metabang.com:

...

Hi Anton,

Is this mlisp or alisp? If the former, it's almost surely a case-sensitivity issue.

thanks,

On Jan 6, 2012, at 2:57 AM, Anton Vodonosov wrote:

...

As you may see, parenscript fails on Allegro:

; While compiling (:TOP-LEVEL-FORM "package.lisp" 54) in /home/rpg/lisp/cl-test-grid/quicklisp/dists/quicklisp/software/parenscript-2.3/src/package.lisp:   Unhandled ERROR is signaled: There is no readtable named :PARENSCRIPT.

---

parenscript-devel mailing list parenscript-devel@common-lisp.net http://lists.common-lisp.net/cgi-bin/mailman/listinfo/parenscript-devel