[EMAIL PROTECTED] wrote:
>
> > Not a cast:
> >
> > try {
> > ...
> > } catch(Exception e) {
> > throw new TurbineException(e.getMessage()); //or whatever
> > }
>
> Kevin, the problem with this is that JIT's can't optimize the code in the
> try/catch blocks. I'm willing to sacrifice a bit of debugging ability
> (which really isn't that big of a loss considering printStackTrace() still
> correctly tells you where the error is and you can figure it out from the
> class pacakge names that it is in Turbine) for the ability to JIT compile
> Turbine since it is a core framework and should be as optimized as
> possible.
URL? Has this been factored into Hotspot? I don't think sacrificing OO
design is worth it for performance issues. It is like ECS, we have a
lot of object creation here but correct OO design wasn't sacrificed just
because you have a hot GC.
--
Kevin A Burton ([EMAIL PROTECTED])
http://relativity.yi.org
Message to SUN: "Open Source Java!"
"For evil to win is for good men to do nothing."
------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Problems?: [EMAIL PROTECTED]
