John Wells wrote:
Thanks for the great replies...I'm pondering your answers, but would like a
little clarity on this:
After the core team, JRuby classes would be VERY VERY tricky to
un-obfuscate so JRuby could be a very good way to achieve Ruby
obfuscation even if nobody should do closed source anymore (well at
least that would be cool).
I'd say impossible. It can't be decompiled into Java code, because it
does a lot of VM-level things that don't have equivalents in Java. You
could dump the bytecode, but then you'd just have a bunch of bytecode
doing all the tricks necessary to make Ruby work. Algorithms would be
really possible to pull out of that mess. Plus most people can't read
bytecode.
Perhaps my email got snipped, but I'm not certain what "After the core team"
means. Are you saying after the core team gets full compilation working? Is full
compilation to bytecode an accomplish-able goal? And how soon do you feel it will be
accomplished?
Yes, I believe he meant "after the core team gets full compilation
working".
By 1.1, around the end of October, JRuby will be able to compile all
Ruby code completely to Java bytecode. This doesn't mean we'll be
producing normal Java types, however. Ruby's type system is much more
fluid as you know, so the completion of the compiler won't mean that
Ruby classes are callable and instantiable as Java classes; it will just
mean that all Ruby code executing has been compiled to bytecode and will
run faster. Additional enhancements to allow tighter Groovy-style Java
integration will take some deliberation, design, and time.
- Charlie
---------------------------------------------------------------------
To unsubscribe from this list please visit:
http://xircles.codehaus.org/manage_email
