> Could you also provide a patch (or at least comments in the code) that > describe the limiations?
This satisfactory? (I didn't mention it in the README because that's supposed to be simpler instructions sans caveats, imo) Mike Lambert Index: docs/running.pod =================================================================== RCS file: /cvs/public/parrot/docs/running.pod,v retrieving revision 1.6 diff -u -r1.6 running.pod --- docs/running.pod 19 Mar 2002 23:29:17 -0000 1.6 +++ docs/running.pod 25 Mar 2002 00:47:13 -0000 @@ -84,4 +84,26 @@ and then use any of the above methods for running tests. +=item B<make quicktest> + +C<make quicktest> is similar to make test, except that it skips some steps +that are unnecessary most of the time, allowing for a significant speed gain. +It's intended to be used as a quick check during development, lowering the +barrier to checking tests. A C<make test> should be performed before +submitting patches, just in case it is affected. + +Instead of recompiling the .pasm files to .pbc files each time +the test is run, C<make quicktest> checks to see if the .pasm file is +identical to the test, and if so, it uses the previously-generated .pbc file. + +C<make quicktest> can fail under the following circumstances: + +- it is cancelled before the generation of the .pbc file can be completed +- the .pbc file format changes +- the numbering of opcodes used in the tests is changed +- the assembler changes in a manner that would affect its output on tests + +If C<make quicktest> fails to work properly, C<make test> is always +available as a fallback. + =back
