Changes between Version 2 and Version 3 of VerifyExamples

Show
Ignore:
Timestamp:
05/18/09 14:52:42 (13 years ago)
Author:
coke
Comment:

--

Legend:

Unmodified
Added
Removed
Modified

  • VerifyExamples

    v2 v3  
    11 
    2 All the example PIR/PASM code that appears in Pod comments through the app should be tested, as should all the code in the top level examples directory. 
     2All the example {{{PIR}}} and {{{PASM}}} 
     3code that appears in {{{POD}}} comments through the app should be tested, as should all the code in the top level examples directory. 
    34 
    45While not run by default, you can verify these with: 
    … …  
    89}}} 
    910 
    10 To see how to markup POD so the examples are testable, see: 
     11To see how to markup {{{POD}}} so the examples are testable, see: 
    1112 
    1213{{{ 
    … …  
    1415}}} 
    1516 
    16 The goal should be to eventually have no _INVALID targets, and to have a small (tending to none) number of _TODO targets. 
     17The goal should be to eventually have no {{{_INVALID}}} targets, and to have a small (tending to none) number of {{{_TODO}}} targets. 
    1718 
    18 There shouldn't be any sample PIR that isn't testing (syntax changes, and we don't want to ship broken sample code.) 
     19There shouldn't be any sample code that isn't tested (syntax changes, and we don't want to ship any broken sample code) 
     20 
     21We should also eventually be able to test code written in other compilers shipped with parrot, like {{{NQP}}}}.