[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: plists, alists, and hashtables
From: |
Ted Zlatanov |
Subject: |
Re: plists, alists, and hashtables |
Date: |
Wed, 05 Aug 2015 21:36:00 -0400 |
User-agent: |
Gnus/5.130012 (Ma Gnus v0.12) Emacs/25.0.50 (gnu/linux) |
On Wed, 5 Aug 2015 14:36:50 -0700 (PDT) Drew Adams <drew.adams@oracle.com>
wrote:
>> So as a first cut, maybe <(k1 . v1) (k2 . v2)> and
>> <<(k1 . v1) (k2 . v2)>> would be a good syntax
...
DA> Unfortunately, in Emacs Lisp we do not (yet) have reader macros.
DA> But that is all the *more* (not less) reason not to hard-code
DA> such syntax restrictions into the definition of Lisp itself.
DA> Working on adding reader macros to Emacs Lisp would be (very!)
DA> helpful. Hard-coding < and << syntax is not helpful (IMHO).
OK, I agree, except that it should be globally enabled, so whatever the
syntax, it can become a standard way to express a map. That's the
point; I can already use hashtables just fine. It needs to be accessible.
Can anyone explain to me what's missing in order to implement the reader
macro that translates «xyz» to some version of #s(hash-table ...)?
Ted
- Re: plists, alists, and hashtables, Ted Zlatanov, 2015/08/05
- Re: plists, alists, and hashtables, Stefan Monnier, 2015/08/05
- RE: plists, alists, and hashtables, Drew Adams, 2015/08/05
- Re: plists, alists, and hashtables, Pascal J. Bourguignon, 2015/08/05
- Message not available
- Message not available
- Re: plists, alists, and hashtables,
Ted Zlatanov <=