[Argh! Posted to google groups again!]
Bernhard Schmalhofer wrote:
Amir Karger schrieb:
I have a test script that runs 85 tests (and will run many more once I
write more opcodes.
So if all I want to do is, essentially, perl -e 'chdir languages/Z and
system(parrot z3.imc t/test.z3)'
On Thu, 2005-08-04 at 08:52 -0400, Amir Karger wrote:
I'm about to commit an updated version of leo's Z-code-to-PIR
translator. I'm wondering what I should do about t.
I hope to have a variant of Test::More written in pure PIR in the near
future (though it probably requires the new calling
I'm about to commit an updated version of leo's Z-code-to-PIR
translator. I'm wondering what I should do about t.
I have a test script that runs 85 tests (and will run many more once I
write more opcodes. Luckily, I developed it already when I was doing
plotz). I could easily modify it to output
Excellent questions. Perhaps I can whip up a languages.pod once 0.2.3
is out the door, based on partcl and the current state of a few other
languages out there.
Right now, the unified language testing harness, such as it is,
would rather you had a script called harness that took a --files
Amir Karger schrieb:
I have a test script that runs 85 tests (and will run many more once I
write more opcodes. Luckily, I developed it already when I was doing
plotz). I could easily modify it to output ok n and not ok with a
comment about what went wrong. However, because it's a big Z-code
