Hey Duke, Thanks a lot.
I'll have to brush up on my Perl (I learned it from a 90's textbook on the Perl/CGI web revolution ;) I will look in to that, thank you, it does seem to be a little dead over there at this hour though, off to another mailing list I suppose. Cheers, - Joe -- Public Key: [0xF8462E1593141C16]<http://pgp.mit.edu:11371/pks/lookup?op=get&search=0xF8462E1593141C16> Man is the lowest-cost, 150-pound, nonlinear, all-purpose computer system which can be mass-produced by unskilled labor. - NASA On Fri, Mar 25, 2011 at 5:11 PM, Jonathan "Duke" Leto <[email protected]>wrote: > Howdy Joseph, > > Welcome to the Parrot community! > > I would think that the preferred languages to implement this in would > be PIR/NQP/Rakudo/Winxed or Lua. > > I would recommend against PIR, because it is too low-level. If you > write a Perl 6 POD parser in any other of the above-mentioned Parrot > languages, we can generate PIR and Parrot bytecode for it. > > It seems natural to implement a Perl 6 POD parser in Rakudo Perl 6, so > you should probably ask them what their plans are. It could be that > the spec is still in flux and that is why they haven't written one > yet. You can go into #perl6 on irc.freenode.net and ask questions, > they are very friendly :) You should tell them you are a prospective > GSoC student and that I sent you. > > Duke > > On Thu, Mar 24, 2011 at 1:42 PM, Joseph Lewis <[email protected]> wrote: > > Hello, > > > > If you aren't tired of these yet, you will be soon :) > > > > I'm interested in creating a Perl 6 POD parser/output engine as described > in > > the wiki: > > > > POD parser > > > > Difficulty: 1/5 > > Links of Interest: <NONE, please add some> > > Possible Mentors: <UNKNOWN, please volunteer!> > > Details: Implement a library or tool to parse POD documentation from > > standalone .pod files and code files containing intermittent POD. The > > successful project should be able to translate POD documentation into > other > > formats such as LaTeX, HTML, man pages, raw text, or others. Special > focus > > should be on both compliance with the Perl 6 POD specification (Synopsis > 26 > > - Documentation) and interoperability with other HLLs besides Perl 6. The > > successful project will have a system with pluggable backends for > outputting > > documentation in the formats listed above and others. > > Expected Deliverables: <UNKNOWN, Please list what the deliverables will > be> > > > > I have some experience with implementing web specifications through > Python > > (DNS / HTTP / SMTP), that should lend itself a tad to the task at hand. > It > > doesn't seem that there is a HIL that is preferred for this work > (personally > > I'd like to use Python 3) probably because they can all be eventually > > compiled in to Parrot, or am I completely wrong in this? > > > > Is there anything else I should know? > > > > Thanks, > > Joe > > > > > > -- > > Public Key: [0xF8462E1593141C16] > > > > Man is the lowest-cost, 150-pound, nonlinear, all-purpose computer system > > which can be mass-produced by unskilled labor. > > - NASA > > > > > > _______________________________________________ > > http://lists.parrot.org/mailman/listinfo/parrot-dev > > > > > > > > -- > Jonathan "Duke" Leto > [email protected] > http://leto.net >
_______________________________________________ http://lists.parrot.org/mailman/listinfo/parrot-dev
