Jon Harrop wrote: > You generated code that turned out to be less efficient on the CLR in this > particular case but you cannot validly generalize that to all "non-standard > code".
right, I can't generalize to all non-standard code, but it's surely true for the kind of non standard code pypy generates :-). The exception inlining was only an example, there are other areas where the CLR jit was worse, like code that makes an heavy use of temp variables instead of leaving the values on the stack. [cut] > Why didn't you use tail calls instead? I honestly don't see how tail calls could help here; could you show me an example please? ciao, Anto --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "JVM Languages" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/jvm-languages?hl=en -~----------~----~----~----~------~----~------~--~---
