Piers Cawley <[EMAIL PROTECTED]> wrote:
> Okay, I'm confused, I thought that the whole point of a caller saves,
> continuation passing regime was that the caller only saves what it's
> interested in using after the function returns.
We don't have a problem WRT register preservation, the problem ar
The image is wonderful. Wrong, but funny.
I just got finished reading all of the recently posted and updated synopses
and found them remarkably coherent. I can see it as nothing but getting rid
of all of the old fluff in the language and replacing it with well thought
out, concrete and purpos
Okay, I'm confused, I thought that the whole point of a caller saves,
continuation passing regime was that the caller only saves what it's
interested in using after the function returns. Exactly *where* that
return happens, and whether it happens more than once, is completely
irrelevant from the po
Transcendental (and some other) ops that have a FLOATVAL out argument
and INTVAL source argument(s) are deprecated.
E.g.
acos Nx, Iy
atan Nx, Iy, Iz
Actually these opcodes aren't emitted any more, you'll get
set $N0, Iy
acos Nx, $N0
for registers or a floatval constant for constants.
1) the new sequence to install an exception handler now is:
push_eh catch_label
2) Please replace code using set_eh, e.g.:
newsub Px, .Exception_Handler, catch_label
set_eh Px
with the new one-liner.
3) The set_eh opcode will remain valid until the next opcode cleanup.
Thanks,
leo
Leopold Toetsch <[EMAIL PROTECTED]> wrote:
> 3) Function-like opcodes
> Stat, gmtime, seek, tell, send, poll, recv, gcd, lcm, pack, rand,
> split, sleep, and what not are all functions in C or perl and any
> other language I know. These are *not* opcodes in any hardware CPU I
> know (maybe VAXens
I've checked in intial support for anonymous subroutines.
.sub foo @ANON
creates an anonymous subroutine. It's available with the normal call syntax:
x = foo(y)
in the same module[1], as this syntax translates roughly to:
set_p_pc P0, foo
invoke
where "foo" is a visible clue for the inde
