> The alternative is to start removing catch clauses so that the app will, > in fact, crash and the developer can at least see something. This seems > like a silly approach, though. >
Quite the contrary: if you are catching runtime exceptions then you are doing it wrong (most of the runtime exception indicate bugs in code, so catching them just suppressing effect of bug), on the other hand if you checked exception handling is just catch and log you are also doing it wrong - 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). -- 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.
