Talk:Pugs

From Wikipedia, the free encyclopedia

[edit] Accuracy unclear

From the article:

Originally there was hope that the huge Pugs test suite would form the basis of the actual Perl 6 test suite, but now it looks more like Pugs itself will form the basis of the actual Perl 6, so the point is a bit moot.

Is this really true? I was under the impression that Perl6 is intended to be written in Perl6, with Pugs being intended by its own developers to do no more than bootstrap the first build of the final Perl6 Perl6. If that's what the statement in the article means, it needs clarifying; if it means that Pugs will actually replace the Perl6 Perl6, then I'd say a reference would be in order, since there's no mention of any such intention on any of the linked sites. — Haeleth Talk 11:59, 28 October 2005 (UTC)

Hi, I think I wrote the above sentence, when this article was but a young thing. I can't give any definitive reference unfortunately. I'm certainly not saying anyone expects Perl 6 to be written in anything other than Perl 6; however the impression I've got is that Pugs is going places in its own right, and will gradually be converted from Haskell to Perl 6 rather than just acting as a bootstrap for some other implementation of Perl 6. Feel free to delete it if you think such speculation is out of place - you're probably right!

Adetaylor 20:47, 27 January 2006 (UTC)

The final milestone of Pugs is self-hosting, that is, translating all the compiler components into Perl 6. At that point of time, if there is no other Perl 6 implementations around, it might be possible that Pugs is simply renamed to Perl 6 (see EGCS); if there is already another self-hosting Perl 6 implementation, then Pugs would retain its name, but would still be a self-hosting compiler. audreyt 16:23, 30 January 2006 (UTC)

Where does Parrot fit into this? Will Pugs/Perl6 be producing Parrot bytecode? Aaron McDaid (talk - contribs) 14:13, 17 August 2006 (UTC)