> > The idea of exceptions as "unexpected" falls away once you are doing > anything like network access or even file access. > Java distinguish between this two situation with checked and unchecked (runtime) exception. Runtime exceptions should never be cached (unless you can propose some valid recovery path from InvalidMonitorStateException or NullPointerException).
> > >> , on the other hand if you checked exception handling is just catch and >> log you are also doing it wrong - >> > But it is a start. It doesn't hurt to log it even you think you are > already doing the "right thing" in response to it. > Well maybe that's why I said: "just catch and log" not "just catch, log and perform some appropriate fallback action". > > >> if exception occur some operation was prematurely terminated so usually >> it should be communicated to user (for example IOException when downloading >> something should at least end with some message shown). >> > > Assuming you are doing all that and giving the best user friendly message > to the user possible, you still might have a vested interest in the nitty > gritty details of those exceptions to fix the problem. Original poster's > query is very legitimate. > Why? How can you fix IOException? -- Bart -- -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/android-developers?hl=en --- You received this message because you are subscribed to the Google Groups "Android Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
