[Herbert == [EMAIL PROTECTED] on Wed, 8 Sep 2004 15:18:27 +0000] Herbert> And any way for an overeager newbie to help?
The classic answer is "write tests". There's thousands of code snippets that have been tossed out to the various perl6-* lists over the last few years. Many are bogus, but woven into most threads are examples of "this should work" real Perl6 code. Just by browsing lists archives, in a few days, you could probably write a few dozen placeholder tests. You couldn't be very confident of them, given you don't have a language implementation to test them with. But they would make great fodder for the team, and would either get morphed into final tests in the distribution, or morphed into conversations where the final syntax does get hashed out. Few things will get the syntax nailed down like throwing out erroneous test cases. Think very simple tests. Maybe 3 tests for each of the operators thus far defined. Tests to check that the unicode and plain ascii versions of operators both give the same results. Little object tests. Etc. If the first thing implemented is the grammar engine, Patrick/et al will need test code to parse. -- [EMAIL PROTECTED] "One cannot mark the point without marking the path."
