On Oct 19, 8:18 am, Rob Lachlan wrote:
> I see, thank you for linking to the ticket, Phil that really clarifies
> things. I suppose that I would tend more to Chas Emerick's view in
> his sept 28 comment (on the ticket), questioning whether there is a
> need to validate Keywords (and possibly symb
I see, thank you for linking to the ticket, Phil that really clarifies
things. I suppose that I would tend more to Chas Emerick's view in
his sept 28 comment (on the ticket), questioning whether there is a
need to validate Keywords (and possibly symbols) stringently. But
I'll take your point that
On Mon, Oct 18, 2010 at 3:02 PM, Rob Lachlan wrote:
> There seems to be a discrepancy between what keyword names are
> supposed to be allowed, according to the reader documentation, and
> which the reader actually allows. For instance, periods are supposed
> to be disallowed in keyword names, and
Hi,
The reader (LispReader) and the interning functions (symbol and keyword) are
separate. The reader tries to enforce some constraints, but overlooks some
edge cases, before eventually interning. The interning functions do not
validate input.
Besides the problems you raised, there are some con
There seems to be a discrepancy between what keyword names are
supposed to be allowed, according to the reader documentation, and
which the reader actually allows. For instance, periods are supposed
to be disallowed in keyword names, and only one forward slash allowed,
but no errors are thrown at
