thinking about proper implementation of tail calls

[Mark Roos]

I am looking to learn something here that I haven't seen in my code yet.

John mentioned
        Suppose you are compiling your favorite high-level language to the 
JVM, and you start 
        running into the various size limits in class files

To which there seemed to be some agreement that this was an issue. Running 
over my Smalltalk
code base my largest method is 12000 bytes with only about a dozen that 
are more than
10k bytes.  The corresponding class file is 16k bytes ( I only do one 
method + blocks per class file)

So my question is what is causing these mega methods.  Is it just an 
artifact of the language being
implemented or is it from some language side optimization (such as trace 
optimization)?  Perhaps
I am just lucky to not see it yet.

thanks
mark
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mail.openjdk.java.net/pipermail/mlvm-dev/attachments/20120901/497168c8/attachment.html