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 we shouldn't count on the current behaviour continuing.
Rob On Oct 18, 9:24 pm, Phil Hagelberg <p...@hagelb.org> wrote: > On Mon, Oct 18, 2010 at 3:02 PM, Rob Lachlan <robertlach...@gmail.com> 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 only one forward slash allowed, > > but no errors are thrown at something like this: > > I think the official stance is that there's a big difference between > what is officially supported and what you happen to be able to do in > the current version without things blowing up. > > > Using the keyword function, we seem to be able to make keywords out of > > any pair arbitrary strings, even including spaces. > > I submitted a patch for this over a year ago, but I gather there were > some concerns about the runtime cost of such behaviour. It's one of > the most long-standing tickets still open: > > https://www.assembla.com/spaces/clojure/tickets/17-gc-issue-13-%09val...) > > -Phil -- You received this message because you are subscribed to the Google Groups "Clojure" group. To post to this group, send email to clojure@googlegroups.com Note that posts from new members are moderated - please be patient with your first post. To unsubscribe from this group, send email to clojure+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/clojure?hl=en
