« A tale of two PMCs. | Main | Intermission again... »



Feed You can follow this conversation by subscribing to the comment feed for this post.

i'm almost starting to get confused here. once again, great posts audrey. BUT i am starting to get a little dizzy and can't fully grok:

- what current perl6 syntax pugs supports
- what current perl6 syntax itself is frozen
- how far we need to go with pugs
- the who/what/where about cutting over to parrot
- how exactly the perl5 filter fits in

in other words, i need to be de-idiotized with a state of the onion (but a real state of the onion, not the usual comedy routines larry puts on), and i suspect lots of other people do too.

I belive, nothing is really 'frozen'? but some parts (flow control, function definition/call syntax, rules, OO) are less likely to change than the others (marcos). Some things are underspecced/unspecced (threads, builtins, embedding, distro/libraries).

Most work is now concentrated on bridging the gap between Pugs/lrep (parsers/interpreters, 'high level' implementations of P6) and Parrot 'the VM'; and bootstrapping (by moving Pugs/lrep infrastructures gradually from Haskell/p5 to p6).

That's what I gather from blogs here and lurking on perl6-* lists.

Verify your Comment

Previewing your Comment

This is only a preview. Your comment has not yet been posted.

Your comment could not be posted. Error type:
Your comment has been saved. Comments are moderated and will not appear until approved by the author. Post another comment

The letters and numbers you entered did not match the image. Please try again.

As a final step before posting your comment, enter the letters and numbers you see in the image below. This prevents automated programs from posting comments.

Having trouble reading this image? View an alternate.


Post a comment

Comments are moderated, and will not appear until the author has approved them.

Your Information

(Name is required. Email address will not be displayed with the comment.)