The relationship is quite natural and clear. Imagine a Camel walking through the desert. Beside it is a Ponie riding on a Parrot's back. There is a single saddle that sits across both the Camel and the Ponie. The Ponie is pushing an oyster forward in the sand. The Parrot wears a bare chain that is clearly meant to eventually hold Perls from this oyster. | [reply] |
| [reply] |
Excellent reading.. Thanks!
| [reply] |
Perl6 will run on a virtual machine, which is called parrot.
Perl5 code will also run on the Perl6 virtual machine, through what is known as ponie.
Therefore, you will not need to run two versions of Perl (unless you really want to). A Perl6 installation should cover your Perl 5 code.
It's worth noting that Perl6 will not be the standard for a while, so personally I continue to develop my Perl5 skills. But I can't wait for Perl6!
--
bm | [reply] |
So then.... Does that mean we won't necessarily have to learn anything to implement perl 6? And ponie and parrot are "behind the scenes"?
| [reply] |
The operating rule of perl6 design is that today's code will run unchanged, but for your code to take advantage of perl6 syntax and capabilities, your code must specifically declare that it is perl6-ready.
The underlying technologies (the native vm or the parrot vm) are largely irrelevant to implementing perl applications.
How and when and why you might want to learn perl6 is completely at your own pace.
--
[ e d @ h a l l e y . c c ]
| [reply] |
