[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
- To: Moon@STONY-BROOK.SCRC.Symbolics.COM
- Subject: issue HASH-TABLE-PRINTED-REPRESENTATION
- From: Jon L White <firstname.lastname@example.org>
- Date: Mon, 17 Oct 88 17:13:49 PDT
- Cc: email@example.com, firstname.lastname@example.org
- In-reply-to: David A. Moon's message of Thu, 13 Oct 88 18:15 EDT <19881013221502.0.MOON@EUPHRATES.SCRC.Symbolics.COM>
re: Date: Thu, 13 Oct 88 15:25:59 MDT
From: email@example.com (Sandra J Loosemore)
I like the syntax suggested in what is described as "yet another proposal"
but the way it specifies the optional parts is broken. It should be
#[size]H([type [rehash-size [rehash-threshold]]] (ki vi)*)
It is very important that the syntax for expressing hash table options
be extensible, and therefore keyword-based. Any syntax like this that's
positional, and furthermore assumes that all option values are
non-lists, is simply not acceptable. Putting the size out there in
front is weird, too.
Is it really that important that the extensible part of the syntax look
exactly like that for the "Standard" components? Even in Sandra's format,
you still have room for implementation-specific keyword options.
-- JonL --