in reply to Perl 5 Optimizing Compiler, Part 4: LLVM Backend?
The fundamental problem with your dream is that Perl is not standardized. Perl has no immutable compliance suite. The definition of Perl is what P5P wants it to be. There are no exceptions to this. There is no industry body that sets the standard. P5P does not work for you and will not cooperate with you or anyone else. The same way that C# is owned by Microsoft, Perl's corporate overlord is booking.com. In former years, Perl's corporate overload was ActiveState, but their toy got old and they threw it away, then booking.com purchased it. Your creation will be a fork of Perl, and the history of Perl is littered with non-compatible offshoots such as PHP, Ruby, and Kurila.
Creating any sort of compiler, besides what passes for a compiler in Larry's Perl, enables closed source software to be written in Perl. Inasmuch as this is a great unforgivable sin in the open source world; you have made great enemies with P5P. P5P will subtly ensure that you will never be 100% compliant with P5P's Perl implementation. If your improved VM becomes a successful threat to the goals of P5P and its owner, TPF will litigate you for trademark infringement and prevent you from claiming compatibility with Perl 5. Take a lesson from Larry Wall who is the creator of Perl 5, and its stack-based architecture. He abandoned it because it was fatally flawed and the cabal behind it was resistant to change. You should follow his example.
|
|---|
| Replies are listed 'Best First'. | |
|---|---|
|
Re^2: Perl 5 Optimizing Compiler, Part 4: LLVM Backend?
by chromatic (Archbishop) on Aug 28, 2012 at 05:30 UTC | |
|
Re^2: Perl 5 Optimizing Compiler, Part 4: LLVM Backend?
by Will_the_Chill (Pilgrim) on Aug 28, 2012 at 05:34 UTC |