Not logged in
Log in now
Create an account
Subscribe to LWN
LWN.net Weekly Edition for December 5, 2013
Deadline scheduling: coming soon?
LWN.net Weekly Edition for November 27, 2013
ACPI for ARM?
LWN.net Weekly Edition for November 21, 2013
Python moratorium and the future of 2.x
Posted Nov 12, 2009 20:34 UTC (Thu) by chromatic (guest, #26207)
Posted Nov 12, 2009 22:17 UTC (Thu) by lysse (guest, #3190)
Posted Nov 13, 2009 19:58 UTC (Fri) by chromatic (guest, #26207)
Posted Nov 15, 2009 12:12 UTC (Sun) by IkeTo (subscriber, #2122)
That depends on what the OP want. The design of Perl 6 definitely have backward compatibility addressed, at least so long as Perl extension module is not involved (i.e., there is no C code involved). The Perl 6 is designed to be based on a virtual machine (Parrot) that can interpret many different languages, Perl 5 is one of them. Then the Parrot engine can run many back-end languages at the same time, with objects of different languages cooperating in a fashion similar to Java dynamic language interface. Finally, the Perl 6 language is designed so that modules are distinguishable from Perl 5 modules by just looking at the first few tokens, so that the eventual VM can load a module and decide whether to use Perl 5 or Perl 6 back-end automatically. So the design is there, it's just an issue about when it actually enters implementation.
Posted Nov 18, 2009 17:37 UTC (Wed) by cptskippy (guest, #62050)
Posted Nov 19, 2009 6:42 UTC (Thu) by lysse (guest, #3190)
Copyright © 2013, Eklektix, Inc.
Comments and public postings are copyrighted by their creators.
Linux is a registered trademark of Linus Torvalds