Hi. After some investigation and hacking it seems that there are two problems with JYaml. One: it's Java 5. You can get it in a 1.4-version, but this is a byte code-enhanced version using retrotranslator to exist in 1.4-world. This is a problem for a few reasons: first, it's problematic to recompile if we need to change JYaml. Second, retrotranslator does not seem to be a good solution for stable applications. The second problem with JYaml is more serious. There doesn't seem to be an easy way to register Ruby transfers for the basic operations. The system returns HashMaps and ArrayLists, and sure, we could use some automatic translation for these objects, but it still feels kindof icky. And we won't be able to register new types at runtime in a nice manner either. The other way out would be to hack JYaml to be JRuby-specific, but this seems to be quite an endeavour.
So, I'm going to sleep on the problem and get back tomorrow. /Ola ------------------------------------------------------- This SF.Net email is sponsored by xPML, a groundbreaking scripting language that extends applications into web and mobile media. Attend the live webcast and join the prime developer group breaking into this new coding territory! http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642 _______________________________________________ Jruby-devel mailing list Jruby-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jruby-devel
