[Openmcl-devel] Side effects when redefining dispatching reader macro?

[Ron Garret]

Looks like a CCL bug to me:

Welcome to Clozure Common Lisp Version 1.10-r16479M  (DarwinX8664)!
? (MAKE-DISPATCH-MACRO-CHARACTER #\# NIL *readtable*)
T
? #'foo
> Error: Reader error on #<CCL::RECORDING-CHARACTER-INPUT-STREAM #x302000E7D6CD>, near position 2:
>        Undefined character #\' in a #\# dispatch macro.


On Nov 12, 2015, at 9:05 AM, Mirko Vukovic <mirko.vukovic at gmail.com> wrote:

> After executing the following code (using named-readtables) reader macros such as #C(...), #(...), #|...|# don't work.
> 
> seems to delete prior reader macros:
> 
> CL-USER> (ql:quickload :named-readtables)
> CL-USER> 
> (named-readtables:defreadtable :test
>   (:merge :standard)
>   (:macro-char #\# :dispatch))
> CL-USER> (named-readtables:in-readtable :test)
> CL-USER> #C(1d0 1d0)
> 
> Error message: 
> Reader error on #<STRING-INPUT-STREAM  #x21010256CD>, near position 2, within "#C(1d0 1d0)
> ":
> Undefined character #\C in a #\# dispatch macro.
> 
> The same code on SBCL does not remove the prior definitions of the reader macro.
> 
> I don't know if that is a bug in CCL, named-readtables, or freedom allowed under the standard.
> 
> Maybe someone can make sense of it.
> 
> Mirko
> _______________________________________________
> Openmcl-devel mailing list
> Openmcl-devel at clozure.com
> https://lists.clozure.com/mailman/listinfo/openmcl-devel