It turns out that a framework we've been using is able to serialize *any* Java class, whether it implements Serializable or not -- so, we've been happily serializing keywords without them explicitly supporting it for some time.
However, making Keyword formally Serializable has other benefits, specifically that a proper patch would ensure that deserialized Keywords are interned as one would expect out. So, I may make a run at this sooner rather than later... - Chas On Jul 24, 7:06 pm, Chris Kent <cjk...@gmail.com> wrote: > Hi > > Are there any fundamental reasons why the Keyword class shouldn't be > serializable? I've been playing around with Clojure and Wicket and > it's not possible to use maps containingKeywordsin Wicket page > classes. Wicket pages are serialized and stored in the session > between requests and this fails if the page refers to anyKeywords. > UsingKeywordsin maps is common in Clojure (and in clj-record in > particular) and it would be a really useful change. > > I'd be happy to supply a (very small) patch if people think it's a > good idea. > > Thanks > Chris --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
