Benjamin Goldberg wrote:
> I would expect a large majority of parrot subroutines to
> *not* use all four register types.
>
> How difficult would it be to make imcc detect when less than 4
> register types were used in a subroutine, and replace a call to
> "saveall" with an appropriate combination
ow
to set an exit code.
Thanks,
Flaviu
Leopold Toetsch wrote:
Flaviu Turean/P6 <[EMAIL PROTECTED]> wrote:
Hello!
[ t/syn/clash_4.imc ]
1. $I0 (PIR) is set to `defined $P1`;
2. I0 (parrot) is set to `defined P1`. If there is a bug in lifetime
analysis, in step 1 above $P1 may mapped
Hello!
The code below is lifted from /languages/imcc/t/clash.t. I'm trying to
understand test writer's intent. Bear with me, please, while I
embarass myself:
> ##
> output_is(<<'CODE', <<'OUT', "defined");
> .sub _test
> $P1 = new PerlHash
> $I0 = def
> If we wrote a GUI library in parrot, a sort of Tkinter, and our
> widgets compiled down to parrot then we would have a consistent GUI
> library where widgets could be shared across languages and across
> platforms. Unlike the present situation where Tk widgets from Perl
> have to be rewritten f
