Developer Creates An Experimental Perl 5 To Java Compiler (perl.org)
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."
Well, that's one way to make Perl even more unreadable. :P
Love sees no species.
Perl 5 must be godawful if you need to compile it to Java.
It isn't compiled to Java. It is compiled to JVM bytecode. Perl compilers have been done before, so the only new thing here is the backend target ... and that he claims to support "eval" without an embedded interpreter. I don't see how that is possible, and he should get a Turing award if he actually accomplished that.
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.
#DeleteChrome
The unpalatable compiling to the unspeakable.
Compiler for Bash Scripts to Visual Basic.
Because you need 'enterprise' and 'synergy' to win at Corporate Buzzword Bingo.
This is my signature. There are many like it, but this one is mine.
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 http://www.oreilly.com/pub/pr/... 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.
Probably merging projects in different laguages on the JVM. Also if you are sandboxed to just the JVM, running Perl5 without hitting metal is neat. I dunno for sure, but this could conceivably play a part in helping Perl6's Inline::Perl5 perform on rakudo-jvm.
Someone had to do it.
Considering how long Perl 5 existed before this happened, I'm fairly sure you don't need to do anything of the sort.
I wasn't aware that Perl still existed until last year. I thought it disappeared in the aftermath of the dot com bust.
/. is written in perl ...
That would explain why /. haven't been updated in 20 years.
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?