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

[Mirko Vukovic]

On Thu, Nov 12, 2015 at 1:45 PM, Gary Byers <gb at clozure.com> wrote:

> How  d
>
> On 11/12/2015 10:05 AM, Mirko Vukovic 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.
>
>

> Knowing what versions of CCL and of the named-readtables library are
> involved might help.
> The implementation of readtables changed in the CCL trunk early last
> summer.  Soon after it did,
> the named-readtables library - which depends on knowing implementation
> details - changed as
> well
>
>
> From the slime interactive buffer:

Welcome to Clozure Common Lisp Version 1.11-r16635  (WindowsX8664)!



> Mirko
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.clozure.com/pipermail/openmcl-devel/attachments/20151112/a3aa016f/attachment.htm>