State of lambda forms stealing stack frames?

[Jochen Theodorou]

Am 22.12.2013 19:59, schrieb Remi Forax:
[...]
>> If I first call fib(44) and then fib(45) without memoization, then it
>> takes much to long to calculate all those BigIntegers.
>
> You can call fib with small values, the idea is to be sure that when you
> call fib(100),
> fib has already been compiled in assembly code.

in practice this means you will be screwed if your code is first called 
in a manner that will hit the reduced stack frame limit before the JIT 
had a chance to compile code.

[...]
> Some lambda forms are tailcalls but there is something more important,
> when a lambda form does a direct call at the end to a Java method,
> it is usually possible to compact the stack frame at that time.

well... that would be one of 5 or 6 frames... surely a gain, but not the 
big hit. So not sure why you say here "more important"

bye Jochen

-- 
Jochen "blackdrag" Theodorou - Groovy Project Tech Lead
blog: http://blackdragsview.blogspot.com/
german groovy discussion newsgroup: de.comp.lang.misc
For Groovy programming sources visit http://groovy-lang.org