Follow Slashdot blog updates by subscribing to our blog RSS feed


Forgot your password?
Java Perl Programming

Developer Creates An Experimental Perl 5 To Java Compiler ( 94

An anonymous reader writes: Saturday night saw the announcement of an experimental Perl 5 to Java compiler. "This is the first release," posted developer FlÃvio S. Glock -- after 100 weeks of development. "Note that you don't need to compile a Java file. Perlito5 now compiles the Perl code to JVM bytecode in memory and executes it." He describes the compiler as "a work-in-progress" that "provides an impressive coverage of Perl features, but it will not run most existing Perl programs due to platform differences."
This discussion has been archived. No new comments can be posted.

Developer Creates An Experimental Perl 5 To Java Compiler

Comments Filter:
  • by KermodeBear ( 738243 ) on Sunday May 14, 2017 @01:01PM (#54414467) Homepage

    Well, that's one way to make Perl even more unreadable. :P

  • by 93 Escort Wagon ( 326346 ) on Sunday May 14, 2017 @01:13PM (#54414505)

    I'm not sure if there's a practical point to this. Perl is going to be at least as widely supported as Java, so it's not a question of availability. And the dev makes no claims regarding speed... actually the dev makes no claims whatsoever, other than "here it is" and "most perl scripts won't work". If speed were actually the goal, I don't think Java byte code would be the target.

    From the standpoint of being a cool nerd project, though - most definitely. This does seem like a throwback to the "news for nerds" catch phrase.

    • by angel'o'sphere ( 80593 ) on Sunday May 14, 2017 @09:09PM (#54416089) Journal

      Java Byte Code is JIT compiled.
      So chances are that it is much faster than the original perl byte code.

    • by Xest ( 935314 )

      I can speak for this type of application, I genuinely find these kind of projects useful, not for Java, but certainly for .NET.

      One of our products supports client scripting, and it used to just call out to native Lua, it was horrible doing this for many reasons, from performance due to unmanaged managed martialling, through to security issues in being difficult to sandbox.

      I replaced the scripting engine with one built ground up to resolve many of these issues, not least to make the damn thing more modular

  • oh goodie (Score:5, Funny)

    by ooloorie ( 4394035 ) on Sunday May 14, 2017 @01:16PM (#54414517)

    The unpalatable compiling to the unspeakable.

  • by JustNiz ( 692889 ) on Sunday May 14, 2017 @01:28PM (#54414553)

    Compiler for Bash Scripts to Visual Basic.

  • by Anonymous Coward

    Because it's the most used language! And does everything perfectly fine! And has tons of SDK support!

  • by alangmead ( 109702 ) on Sunday May 14, 2017 @02:46PM (#54414857)
    Larry Wall made Java Perl Lingo (JPL, named after Larry's previous employer) around the release of Perl 5. O'Reilly first tried to sell it as a commercial software in the Perl Resource Kit, but eventually made it open source [] in a "dumpware" sort of mode. It eventually became incompatible with newer Perl and Java releases and I want to say it was abandoned, but that is pretending people used it.
  • ... it wants its two hottest languages back.

  • That is what the world really needs.

  • "Saturday night saw the announcement of an experimental Perl 5 to Java compiler."

    Now you can go from incomprehensible shit to unmanageable drek with just a click! Yippee!

  • "FlÃvio"? His name is Flávio.

    2017. And people still have websites which can't process UTF-8 properly. Jesus.

  • And now you have two problems...
  • While it may work and all... why? Why translate Perl that will run, runs well, doesn't have any of the problems of Java... why move it into java?
    Someone after a rube goldberg award?

  • Personally, I'd find a Java-to-Perl converter more useful. Lots of good dev environments for Java, not so much for Perl.

No extensible language will be universal. -- T. Cheatham