You are quite right! But is this a situation you've meant in your code? Isn't it extremely rare <code>try</code>ing a new statement in order to catch OutOfMemoryError, is it? If we implement these checkings in inspector it would lead one became useless as it would report a lot of possible error reports. So we do not take throwing possible RuntimeException's and Error's at least for now.
Best regards, Maxim Shafirov JetBrains, Inc / IntelliJ Software http://www.intellij.com "Develop with pleasure!" ----- Original Message ----- From: "Jonas Kvarnstr�m" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Friday, March 15, 2002 8:40 PM Subject: Re: [Eap-list] Wrong "Condition is always false" detection > Maxim Shafirov wrote: > > >Uff, finally I've noticed that neither BufferedReader nor InputStreamReader > >throw any exception. So reader != null is really always true... > > > They could throw some RuntimeException or Error, couldn't they? > OutOfMemoryError, for example. And then the finally clause is executed. > > > > _______________________________________________ > Eap-list mailing list > [EMAIL PROTECTED] > http://www.intellij.com/mailman/listinfo/eap-list _______________________________________________ Eap-list mailing list [EMAIL PROTECTED] http://www.intellij.com/mailman/listinfo/eap-list
