Dan Sugalski <[EMAIL PROTECTED]> wrote:
Tail calls should be explicit, compile-time things. Otherwise we're going to run afoul of traceback requirements and suchlike things,
Yep. So is it implemented: * tailcall / tailcallmethod opcodes * the former is currently created by imcc with "parrot -Oc" only
Patch is probably ready tomorrow.
Cool. I think I'd like to skip having to specify the -Oc flag, though, and add explicit syntax to PIR.
For the long form sub call, .pcc_tail_call instead of .pcc_call. For the short form... I dunno, something explicit. Double-colons before the opening parenthesis or something. Foo::(). Or something else. Whatever works OK in the grammar. (Leaving out short-form tail calling is fine too)
Method calls should look about the same. Foo.methodname::() or something like that.
--
Dan
--------------------------------------it's like this-------------------
Dan Sugalski even samurai
[EMAIL PROTECTED] have teddy bears and even
teddy bears get drunk
