Ian Rogers wrote: > 3) initialise sm to a default_sm object This is probably the best alternative, but you must be careful in the implementation of System.getSecurityManager(). This method should return null when your "default" object is in place. (Otherwise, it wouldn't conform to the API specification). The consequence of this is that, internally, the class library shouldn't use System.getSecurityManager() to get the security manager... Etienne -- ---------------------------------------------------------------------- Etienne M. Gagnon, M.Sc. e-mail: [EMAIL PROTECTED] Author of SableVM: http://www.sablevm.org/ ----------------------------------------------------------------------
- Re: Why catch (NullPointerException e)? Stuart Ballard
- 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)? 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

