jerry gay wrote:
On 2/26/07, Leopold Toetsch <[EMAIL PROTECTED]> wrote:
Am Sonntag, 25. Februar 2007 12:28 schrieb Klaas-Jan Stol:
> Can you tell whether pbc_output_is() can take PIR code and compile it
> during running the test? Or does is always expect the pbc file to be
> present?
As said, it doesn't make sense to feed .pir code into these tests. So
no /
yes.
testing functions which accept pir as input, compile to pbc, and run
the pbc, do not exist. *however* the flags to parrot do exist
(--output-pbc in combination with --run-pbc should do it.)
ok, that's what I wanted to know, thanks! (I didn't know pbc_output_is()
was specifically for testing pbc files of different platforms)
therefore, the possibility exists to create these testing functions.
it can probably be bolted on fairly quickly, but Parrot::Test is such
a mess, it may be better to de a little refactoring first to make this
easier. i don't know which i'll get to first.
I can't help here, my knowledge of Perl is too minimal, sorry.
so, this is an opportunity for somebody to beat me to either of those
things--patches welcome.
~jerry
kjs
