chromatic wrote:
Instead of printing "done" at the end of code, the *_output_*() test functions
now check that Parrot's exit code is zero. This prevents the test suite from
eating segfaults, as it used to.
If you want to test that Parrot exits with an error given buggy code, use the
*_err
On Sunday 20 May 2007 15:45:57 James Keenan wrote:
> The patch attached reflects the approach we've been taking over the
> last half-year or so in testing the Perl 5 components of Parrot.
> Feedback encouraged.
Instead of printing "done" at the end of code, the *_output
Applied in r18617.
On Mon May 21 18:58:45 2007, allison at perl.org wrote:
> Bernhard Schmalhofer via RT wrote:
> >
> > When hearing 'executables' I primarily think of compiled programs, e.g.
> > compiled C-programs. Personally I'd call the *.pl files simple scripts.
>
> Agreed, *.pl isn't an executable. Script wo
Bernhard Schmalhofer via RT wrote:
When hearing 'executables' I primarily think of compiled programs, e.g.
compiled C-programs. Personally I'd call the *.pl files simple scripts.
Agreed, *.pl isn't an executable. Script works, or program.
Allison
On So. 20. Mai 2007, 15:45:56, jkeen at verizon.net wrote:
> The patch attached reflects the approach we've been taking over the
> last half-year or so in testing the Perl 5 components of Parrot.
> Feedback encouraged.
Thanks, patch applied in r18608.
My $0.02:
When hearin
-year or so in testing the Perl 5 components of Parrot.
Feedback encouraged.
kid51
tests.pod
Description: Binary data
hat stuff is documented *somewhere* in the docs or
can be retrieved in the mailing list.
Now, my question is, are there any docs describing, or containing
pictures, of these main components of Parrot? (I'm talking about a
picture containing boxes, with lines of interaction between them). For
ex
