Make CampyreException extend RuntimeException

[pforhan]

... this would probably clean up a lot of code. Though we'd still need to catch in some places, so I'm not sure what this would do to stability and consistency. Need to look closer at the code.

[konklone]

I am instinctively nervous about this - it might catch more errors, but fewer underlying issues would end up rolling into the Android market's bug reports list.

Happy to give you access to the reports list, if you want to look through the bug reports.

[pforhan]

Not sure quite what you mean... RuntimeExceptions are still caught by the UncaughtExceptionHandler, and uploaded if the user chooses.

But anyway, I'm not keen on getting this right at this moment. It's pretty low priority, generally.

[konklone]

...oh, I think I misunderstood what you were suggesting. What's the effect of extending RuntimeException?

[pforhan]

It means you don't have to catch (CampyreException) or declare throws CampyreException all over the place.

[konklone]

Right now, everywhere I catch CampyreException, I think I want to, so I can turn it into a toast or something. Is there anywhere I could get rid of the catch without affecting the app's behavior?

I'd love to get rid of the "throws" clauses...

[pforhan]

That'd be a quick change to make, I think, and safest for now. We'd just have to watch out that we don't forget to catch in similar situations with new code...

[konklone]

If it's just an aesthetic improvement, I think I'd feel better with the explicit catches that we have now...