Current Status

[Jeff Sturm]

Per Bothner wrote:
> > methods inlined,
> 
> No.  It is very limited you can do in terms in inlining of reasonable
> Java code without violating the access specifiers and hence producing
> invalid bytecode.  It doesn't seem worth it to me.  Better to inline
> when compiling to native code, either using gjc or a JIT (i.e.
> *after* verification).

You can't inline across class boundaries to be sure... but private
methods are normally safe to inline.  They are common enough to be a
worthwhile optimization.

-- 
Jeff Sturm
jsturm@sigma6.com