Well, one thing that people can contribute that doesn't require much (if any) knowledge of the internals is tests (whether in PASM, PIR, or one of the other languages that run on top of Parrot). Tests that uncover bugs are particularly helpful!
Absolutely. I definitely don't want to underestimate the value of tests -- they're amazingly helpful. They also don't have to necessarily be dull "grab one op, make sure it works, move on" sorts of things, though those are good. More abusive tests of IMCC's allocators (using lots of .local or temp variables), or the garbage collector (allocating and freeing up masses of data) are also quite useful, as are tests designed specifically to make parrot fall down and die in as nasty a way as possible. Destruction testing is handy if you're trying to make sure you can't be destroyed... :)
--
Dan
--------------------------------------"it's like this"-------------------
Dan Sugalski even samurai
[EMAIL PROTECTED] have teddy bears and even
teddy bears get drunk
