On Aug 31, 11:44 am, sherod <[EMAIL PROTECTED]> wrote: > *Start quote*
> the runtime of the method. A whole-method compiler, however, has to > always analyze and translate the entire method, even if parts of it > are not particularly “compilation-worthy”. So, a little more code has been compiled than strictly needs to be. Who gives a toss? Do you really want to add extra complication to an already complicated system for so little benefit? (HotSpot does stub out most sad-paths.) I'm not sure that it makes much difference in recent years, but client HotSpot used to have problems when inner loops were embedded in large methods. That was only a problem with really badly written code, such as microbenchmarks and Swing. Tom Hawtin --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "The Java Posse" 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/javaposse?hl=en -~----------~----~----~----~------~----~------~--~---
