Couple of points:

1. While morphing perl optrees is a pain, it's definitely doable--it's what B::Deparse does. If we can translate Python bytecode to run on Perl 5's engine, translating most perl 5 to run on Parrot isn't a big deal
2. There'll be a perl 5 compatible version of the regex engine, to make that transition easier.
3. You're not under any obligation to move anything to perl 6. Perl 5's not going to drop over dead just because we release perl 6

Larry's promised a translator from perl 5 to perl 6 that'll handle most things. I've promised it too, and you'll get it if I have to embed perl 5 inside a perl 6 extension somehow.

(I've also promised a perl 5 parser for parrot, but people seem to enjoy heaping scorn on that idea, the silly twits, so we'll leave that one off for now)

---

---

Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!

Titles consisting of a single word are discouraged, and in most cases are disallowed outright.

Read Where should I post X? if you're not absolutely sure you're posting in the right place.

Please read these before you post! —

• How do I compose an effective node title?
• How do I post a question effectively?
• Markup in the Monastery

Posts may use any of the Perl Monks Approved HTML tags:

a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr

You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)

	For:		Use:
	&		&
	<		&lt;
	>		&gt;
	[		&#91;
	]		&#93;

Link using PerlMonks shortcuts! What shortcuts can I use for linking?

See Writeup Formatting Tips and other pages linked from there for more info.