Stories
Slash Boxes
Comments
NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.

All the Perl that's Practical to Extract and Report

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
 Full
 Abbreviated
 Hidden
More | Login | Reply
Loading... please wait.
  • Wow. (Score:3, Insightful)

    by Matts (1087) on 2002.05.02 2:11 (#7853) Journal
    I think this is great. I'm picturing that we no longer need to write an XML parser for Perl 6 - just plug in XalanJ... Hmmm...

    Of course it's probably a huge job. I imagine it'll go the 80/20 way - the last 20% of those JVM ops will be a bitch to implement right. Are some of those ops GUI ops too?
    • The problem is less likely the GUI ops, as there aren't any (it's all method calls on library code), as stuff like exception schemes and external interfaces.

      I'd be happy if just the pure java library code stuff worked. I'm planning on being thrilled if the rest does. :)
    • FWIW, we'll be able to do most of the ops quite easily - the JVM is mostly quite low level [sun.com] (not GUI level at all). The main problem is converting the whole API as well. There has been some work on the GNU Classpath [gnu.org] project, which might be useful, but yes, the last 20% will be quite tricky ;-)