Indeed -- well, the patch file is there in assembla if you need
keyword serializability right now. Otherwise, I can't imagine it'll
be long before it's brought into the github HEAD (though I'm certain
Rich has more pressing things to handle).
- Chas
On Aug 14, 2009, at 3:18 PM, bradford cr
the serializeability issues also come up with cascading/hadoop.
On Thu, Aug 13, 2009 at 7:58 PM, Chas Emerick wrote:
>
> On Jul 31, 1:47 pm, Chris Kent wrote:
> > Great. As far as my (possibly flawed) understanding goes it should be
> > pretty simple. Make it implementSerializableand add a re
On Jul 31, 1:47 pm, Chris Kent wrote:
> Great. As far as my (possibly flawed) understanding goes it should be
> pretty simple. Make it implementSerializableand add a readResolve
> method that returns intern(sym). sym will have already been interned
> by its own readResolve method.
No, you're
Great. As far as my (possibly flawed) understanding goes it should be
pretty simple. Make it implement Serializable and add a readResolve
method that returns intern(sym). sym will have already been interned
by its own readResolve method.
On Jul 31, 3:03 am, Chas Emerick wrote:
> It turns out
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,
spe
