User: Password:
|
|
Subscribe / Log in / New account

Python moratorium and the future of 2.x

Python moratorium and the future of 2.x

Posted Nov 12, 2009 20:34 UTC (Thu) by chromatic (guest, #26207)
In reply to: Python moratorium and the future of 2.x by drag
Parent article: Python moratorium and the future of 2.x

That's a work in progress; a project called Blizkost allows some interoperability with Perl 5 at the Parrot level. (XS modules complicate things somewhat, as you might expect... but the Blizkost approach is clever.)


(Log in to post comments)

Python moratorium and the future of 2.x

Posted Nov 12, 2009 22:17 UTC (Thu) by lysse (guest, #3190) [Link]

I believe "no" was the word for which you were reaching? (Possibly "not yet"?)

Python moratorium and the future of 2.x

Posted Nov 13, 2009 19:58 UTC (Fri) by chromatic (guest, #26207) [Link]

I haven't tried it, so I can't comment authoritatively on what works and doesn't work.

Python moratorium and the future of 2.x

Posted Nov 15, 2009 12:12 UTC (Sun) by IkeTo (subscriber, #2122) [Link]

> I believe "no" was the word for which you were reaching? (Possibly "not
> yet"?)

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.

Python moratorium and the future of 2.x

Posted Nov 18, 2009 17:37 UTC (Wed) by cptskippy (guest, #62050) [Link]

So if I understand all of this correctly, the Python 3 implementation that I can download and use today sucks because it lacks a feature that Perl 6 supported since it's inception 10 years ago and I should disregard the fact that I can't actually use this feature in Perl 6 because no one has ever been able to create a complete implementation of Peal 6?

Python moratorium and the future of 2.x

Posted Nov 19, 2009 6:42 UTC (Thu) by lysse (guest, #3190) [Link]

I believe designs for time machines also exist.


Copyright © 2017, Eklektix, Inc.
Comments and public postings are copyrighted by their creators.
Linux is a registered trademark of Linus Torvalds