---- you wrote: > I agree, however, the explicit null check will slow down the execution > speed of applets. Why? In case of a JIT or compiled Java for applets "if (sm != null)" will be branch predicted and cause no harm at all. Moreover, AFAIK try/catch in general produce more code and even if it is never executed it still can cause more processor cache misses. Regards, Igor ------------------------------------------------------ Get the Latest News at CNN Interactive: http://CNN.com
- Re: Why catch (NullPointerException e)? Ian Rogers
- Re: Why catch (NullPointerException e)? Etienne M. Gagnon
- Re: Why catch (NullPointerException e)? Tom Tromey
- Re: Why catch (NullPointerException e)? Ian Rogers
- Re: Why catch (NullPointerException e)? Etienne M. Gagnon
- Re: Why catch (NullPointerException e)? Ian Rogers
- Re: Why catch (NullPointerException e)? Etienne M. Gagnon
- Re: Why catch (NullPointerException e)? Ian Rogers
- Re: Why catch (NullPointerException e)? Etienne M. Gagnon
- RE: Why catch (NullPointerException e)? Cierniak, Michal
- Re: Why catch (NullPointerException e)? igor
- Re: Why catch (NullPointerException e)? Ian Rogers
- RE: Why catch (NullPointerException e)? Cierniak, Michal
- RE: Why catch (NullPointerException e)? igor
- RE: Why catch (NullPointerException e)? Cierniak, Michal

