On Dec 28, 2007 5:34 AM, Aaron Trevena <[EMAIL PROTECTED]> wrote: > Hi all, > > I was wondering about this - people keep on asking about "when it will > be finnished" - I'm more interested in "can I do X in it" where X is > something I'm interested in and/or something I can contribute to > and/or something that I consider important for production code I want > to migrate to perl 6 in the future. > > I'd be happy to host a page with a nice chart of what you can do and > what is needed to do it ( i.e. pugs, nqp, punie, low level stuff, > cp6an, etc). > > Obviously keeping it up to date will be some work, in fact keeping all > the websites for perl 6 up to date is a significant piece of work that > the core developers don't have time for. > thanks! it's nice to have the help. currently, every perl 6 implementation i know of is working towards passing the perl 6 test suite, located in the pugs repository (http://svn.pugscode.org/t/).
if we had a smoke machine (e.g. feather.perl6.nl) that frequently built the various implementations (pugs, kp6, perl6,) ran the perl 6 test suite against each implementation, and posted color-coded tabulated html results, it would offer a way for folks to compare implementations directly. we don't have this right now. smolder (http://sourceforge.net/projects/smolder) is what we have in mind to use. a summary page that describes the quality of the smoke results in word or chart form may also be helpful. this can also be extended to include mp6, nqp, etc. obviously i'm suggesting more work than you set out to do... but i'm not sure creating a summary page will be easy without this in place, unless you use qualitative results rather than quantitative. although it may not be easy, a summary page of qualitative results is better than what we have now, so if you have tuits to do that, please do. ~jerry
