James Keenan via RT wrote:
On Fri Feb 23 13:44:22 2007, [EMAIL PROTECTED] wrote:
I couldn't find any other tests that run pbc_output_is() (but
admittedly, I didnt' look for too long), so it might be this function is
never used.
[parrot] 577 $ find t -name '*.t' | xargs grep -n pbc_output_is
t/native_pbc/integer.t:58:pbc_output_is( undef, '270544960', "i386 32 bit opcode_t, 32 bit
intval" );
t/native_pbc/number.t:88:pbc_output_is( undef, $output, "i386 double float 32 bit opcode_t"
);
t/native_pbc/number.t:91:# pbc_output_is(undef, <<OUTPUT, "i386 long double float 32 bit
opcode_t");
t/native_pbc/number.t:92:# pbc_output_is(undef, <<OUTPUT, "PPC double float 32 bit BE
opcode_t");
t/native_pbc/number.t:93:# pbc_output_is(undef, <<OUTPUT, "little-endian 64-bit
tru64");
t/native_pbc/number.t:94:# pbc_output_is(undef, <<OUTPUT, "big-endian 64-bit
irix");
t/native_pbc/string.t:54: pbc_output_is( undef, $output, "i386 32 bit opcode_t, 32 bit
intval" );
t/perl/Parrot_Test.t:53: pbc_output_is pbc_output_like
pbc_output_isnt
How would these instances affect the problem?
it seems the .pbc files are stored in the repository.... is that
desirable? IMO, it would be enough to store the PIR only, and have that
compiled to PBC, and only *then* do the test. But if that is not
possible, then so be it. (of course, it might be a good thing to have
ALL test cases run twice: as PIR and as PBC)
kid51
kjs
