Brian Wheeler writes:
> This diff adds jsr_ic and ret to the interpreter. I don't know if my
> way of returning is legal, and I know there's probably issues with 64
> bit machines, but it works...and that's the important part :)
Ok! We definitely need to get some tests into the Parrot tree. W
Zak Greant, working for the PHP QA team, sent me email telling me
about their setup:
> Please do - you may also want to take a peek at
> http://qa.php.net/build_tracker - the application is incomplete, however, I
> think that it is a good idea. If anyone is interested, then when I get it
> co
Michael G Schwern writes:
> "perl-benchmarks" good idea. Who's chairing? (not me, not now anyway)
I *strongly* recommend giving it a deadline and a specific goal. Also,
the mailing list name would be perl6-qa-benchmarks.
Nat
Barrie Slaymaker writes:
> > And it'll take a decent amount of time to build up a reasonably large
> > set of discrete benchmarks.
>
> Seems like the perl5 test scripts might be a good place to start.
I'd rather see someone write a program that involves file reading
and writing, regular expressi
Michael G Schwern writes:
> On Mon, Jul 31, 2000 at 05:45:41PM -0700, Tony Payne wrote:
> > It has been suggested on the bootstrap list that we tackle bug control as
> > well. Are we interested in this task, and, if so, what tools shall we use?
>
> I have 0 experience in this and no clever ideas
