$ prove t/library/past*.t
t/library/pastpattern.t ............. ok
t/library/pasttransformer.t ......... ok
t/library/pasttransformerdynamic.t .. ok
t/library/pastwalker.t .............. ok
t/library/pastwalkerdynamic.t ....... ok
All tests successful.
Files=5, Tests=2161, 18 wallclock secs ( 0.38 usr 0.05 sys + 16.40 cusr 0.66 csys = 17.49 CPU)
Result: PASS
2,161 as of right now. That number is probably about to go up significantly as I've recently re-factored the code in question a lot, and I haven't written new tests for some of the new functionality.
It's Not Quite a Perl project, although it is a Not Quite Perl 6 project. It's a optimization and analysis framework, originally for Parrot Abstract Syntax Trees(which Parrot's Compiler Tools framework uses), but now rather easy to extend to any tree-like data structure.
-
Are you posting in the right place? Check out Where do I post X? to know for sure.
-
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big>
<blockquote> <br /> <dd>
<dl> <dt> <em> <font>
<h1> <h2> <h3> <h4>
<h5> <h6> <hr /> <i>
<li> <nbsp> <ol> <p>
<small> <strike> <strong>
<sub> <sup> <table>
<td> <th> <tr> <tt>
<u> <ul>
-
Snippets of code should be wrapped in
<code> tags not
<pre> tags. In fact, <pre>
tags should generally be avoided. If they must
be used, extreme care should be
taken to ensure that their contents do not
have long lines (<70 chars), in order to prevent
horizontal scrolling (and possible janitor
intervention).
-
Want more info? How to link
or How to display code and escape characters
are good places to start.
|
