use Perl

• s/Parrot/JVM/; (Score:1)

  by nothingmuch (5848)

  This is already being done, compiling for a VM that is a little more widely deployed than Parrot ;-)
  • Re: (Score:2)

    by Ovid (2709)

    It's possible you've seen something different, but what I've seen is COBOL to Java translators which then run on the JVM. I have not seen native COBOL running on the JVM. Nor have I seen an ability to migrate the code in place by embedding a modern language in it. If you've an example of either of those, I'd love to see it!
    • s/JVM/CLR/ (Score:1)

      by Stevan (6065)

      They have had production quality COBOLs on the .NET platform for a little while now. Given how the CLR works it becomes really easy to either have your COBOL call other libraries or your other libraries call COBOL.
      • Re: (Score:2)

        by Ovid (2709)

        Ah, the CLR is definitely a different story. I suspect that this would be a more attractive choice for COBOL developers as modern COBOL runs very fast and performance is often extremely important. I don't think Parrot would fare well if that's important. If easy of implementation and flexibility are important, though, then Parrot, I suspect, would crush the CLR.
        • Re:s/JVM/CLR/ (Score:1)

          by Stevan (6065) <reversethis-{moc ... {elttil.navets}> on 2009.11.24 10:57 (#71233) Journal

          Actually the CLR is pretty flexible, it used to be that ILASM was very much just C# written in Assembler, but recent efforts to make the CLR more dynamic (IronPython, etc) seem to have really pushed it forward. While I am not a fan of their OS, Microsoft Research has some really *really* smart people working there who are doing a lot of very cool stuff.

          Reply to This

          Parent