On Tuesday, June 25, 2013 10:10:44 AM UTC-7, a1 wrote:
>
>
> 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)
>

A Klingon warrior does not catch exceptions. Our software does not coddle 
the weak!

I can agree from a pure software engineering philosophical perspective, but 
I am not at all convinced that end users prefer this approach. 

The idea of exceptions as "unexpected" falls away once you are doing 
anything like network access or even file access. 
 

> , 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. 
 

> 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. 

Nathan
 

-- 
-- 
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.


Reply via email to