Nick Sieger wrote:
On 5/23/07, Thomas E Enebo <[EMAIL PROTECTED]> wrote:
A good question is anyone still using this in any way outside our
core? I know someone complained about this in some way when we were
working on load/require and accidentally disabled it.
One other positive benefit is this will reduce how many files we
search for during require/load if we remove it. I am a little
hesitant since we are so close to 1.0.
If there's a time to break it, it would be now. The solution is, we
tell anyone using it to simply include your source in the app, right?
The serialization stuff isn't documented anywhere, really. The one
guy using it has probably been using JRuby for a while.
I vote for removing it.
Ditto. The only person we knew of that was using it was David Corbin,
and he's been inactive on the list for some time. And I actually don't
propose removing serialization capabilities completely...just not
serializing any of our core libraries. There's only a very few of them
anyway, the parser is pretty fast, and eventually we'll just precompile
them to Java code anyway.
So, for the record, I think we should:
- leave serialization in the codebase for those that want it.
- don't use it for core files we ship with, so that step's not needed.
- Charlie
---------------------------------------------------------------------
To unsubscribe from this list please visit:
http://xircles.codehaus.org/manage_email
