The Parrot engine is sufficiently complete to implement a significant subset of Perl 6. (And Perl 5, for that matter) Because of that, we're looking for folks to pitch in and help write a perl 6 (or perl 5--that's fine too) parser. The parser itself can be written in Perl 5. You don't need any knowledge of the Parrot engine to start--we can fill you in and get you going with that quickly enough.

Requirements? You'll have to be working on a platform that Parrot builds on, with the tools you'll need to build Parrot, which includes perl, a C compiler, a make tool, and a CVS client. You'll also have to be willing to deal with a platform that's still a bit in flux. (Count this as your chance to influence the design of the real Perl 6 runtime engine)

Details? You'll be writing code that parses perl 6, and ultimately spits out bytecode for the parrot engine. Nothing fancy, and the first run may well be throwaway code, but that's just fine.

Interested? Subscribe to perl6-internals at perl.org (A link to the archives is at dev.perl.org) and we'll get you going.

---

---

• Are you posting in the right place? Check out Where do I post X? to know for sure.
• Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:

  <code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>

• Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
• Want more info? How to link or How to display code and escape characters are good places to start.