PMC Tools Test Failure

Hi there, I see one failure with the buildtools tests, run right after make realclean and a fresh Configure. t/tools/pmc2cutils/04-dump_pmc...ok 103/119 # Failed test (t/tools/pmc2cutils/04-dump_pmc.t at line 533) t/tools/pmc2cutils/04-dump_pmc...NOK 106

Re: PMC Tools Test Failure

chromatic wrote: Hi there, I see one failure with the buildtools tests, run right after make realclean and a fresh Configure. t/tools/pmc2cutils/04-dump_pmc...ok 103/119 # Failed test (t/tools/pmc2cutils/04-dump_pmc.t at line 533) t/tools/pmc2cutils/04-du

[svn:perl6-synopsis] r13559 - doc/trunk/design/syn

Author: larry Date: Thu Feb 1 10:52:27 2007 New Revision: 13559 Modified: doc/trunk/design/syn/S03.pod Log: Keeping exceptions exceptional and lazy to promote parallelism. Some random C<> cleanup. Modified: doc/trunk/design/syn/S03.pod ===

Re: PMC Tools Test Failure

On Thursday 01 February 2007 04:07, James E Keenan wrote: > IIRC, in order to be able to get full coverage on a branch, I > have to determine whether a file was overwritten or not, which I'm doing > with a comparison of mtimes. Hm, that's a tricky test to write. You have to dodge questions of pr

[svn:perl6-synopsis] r13560 - doc/trunk/design/syn

Author: larry Date: Thu Feb 1 13:33:59 2007 New Revision: 13560 Modified: doc/trunk/design/syn/S03.pod doc/trunk/design/syn/S12.pod Log: Killed filetest operators! (They were a pain to parse anyway.) A Pair pattern now queries back to object to ask if it thinks it matches. Str and IO use

[svn:perl6-synopsis] r13561 - doc/trunk/design/syn

Author: larry Date: Thu Feb 1 13:38:41 2007 New Revision: 13561 Modified: doc/trunk/design/syn/S03.pod Log: typos from [particle]++ and /me Modified: doc/trunk/design/syn/S03.pod == --- doc/trunk/design/syn/S03.pod

[svn:perl6-synopsis] r13562 - doc/trunk/design/syn

Author: larry Date: Thu Feb 1 13:43:24 2007 New Revision: 13562 Modified: doc/trunk/design/syn/S03.pod Log: More tweakage. Modified: doc/trunk/design/syn/S03.pod == --- doc/trunk/design/syn/S03.pod(original)

Re: On PASM and PIR registers

Am Mittwoch, 31. Januar 2007 12:00 schrieb Klaas-Jan Stol: > So, my question is now, why do we still need the PASM registers PASM registers are physically allocated within the Parrot virtual machine. PIR registers are virtual registers, like .local variable w/o a name. The register allocator assi

[svn:perl6-synopsis] r13563 - doc/trunk/design/syn

Author: larry Date: Thu Feb 1 21:22:29 2007 New Revision: 13563 Modified: doc/trunk/design/syn/S03.pod Log: Fixes from thom++. Modified: doc/trunk/design/syn/S03.pod == --- doc/trunk/design/syn/S03.pod(origi