On 9/15/06, Leopold Toetsch <[EMAIL PROTECTED]> wrote:
Am Freitag, 15. September 2006 01:42 schrieb Karl Forner: > But by looking in other tests and in the Parrot::Test, it seems that the > canonical way > of running a PIR script is through the example_output_is() function. > BUT this function does not take any arguments for Parrot. I'd subclass Parrot::Test and create a function shootout_output_is(), which takes an extra commandline argument.
Hmmm but if I subclass Parrot::Test, I won't be able to reuse any code. So if by instance the multiplatform way of getting the path to the parrot interpreter changes, I will have to synchronyze the code in the subclass too. Isn't it evil ? By the way, I have implemented the test using the TEST_PROG_ARGS environment variable. It is not very elegant but at least it seems to work for now.
