[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Precedence for reader extensions
From: |
Mikael Djurfeldt |
Subject: |
Re: Precedence for reader extensions |
Date: |
Mon, 18 Feb 2013 22:26:36 +0100 |
On Mon, Feb 18, 2013 at 10:05 PM, Mikael Djurfeldt <address@hidden> wrote:
> If anyone is afraid about the effect this would have on reader
> performance, it is possible to compile %read-hash-procedures to a
> table of flags indicating exceptions.
But, given the current interface to reader extensions in the form of
an alist in a fluid, such a table would have to be compiled at each
entry to "read"...
- Precedence for reader extensions, Mikael Djurfeldt, 2013/02/18
- Re: Precedence for reader extensions, Mikael Djurfeldt, 2013/02/18
- Re: Precedence for reader extensions,
Mikael Djurfeldt <=
- Re: Precedence for reader extensions, Mark H Weaver, 2013/02/18
- Re: Precedence for reader extensions, Mikael Djurfeldt, 2013/02/19
- Re: Precedence for reader extensions, Mark H Weaver, 2013/02/19
- Re: Precedence for reader extensions, Mikael Djurfeldt, 2013/02/19
- Re: Precedence for reader extensions, Mikael Djurfeldt, 2013/02/19
- Re: Precedence for reader extensions, Ludovic Courtès, 2013/02/20
- Re: Precedence for reader extensions, Mark H Weaver, 2013/02/21
- Re: Precedence for reader extensions, Mikael Djurfeldt, 2013/02/22
- Re: Precedence for reader extensions, Ludovic Courtès, 2013/02/22