Dan, I am gonna turn off -debug in the interp test below, since the
test harness is picking up stderr as well as stdout and the test
below is failing. (-d causes Parrot to be talkative, no pun intended)
It just showed up when I fixed in interpreter local IO stuff (will commit
later).
Can the test harness ignore stderr?
-Melvin
output_is(<<'CODE', <<'OUTPUT', "runinterp");
-- newinterp P0, 1
++ newinterp P0, 0
print "calling\n"
runinterp P0, foo
print "ending\n"
end
print "bad things!\n"
foo:
print "In 2\n"
end
CODE
calling
In 2
ending
OUTPUT
