- Feature Articles
- CodeSOD
- Error'd
- Forums
-
Other Articles
- Random Article
- Other Series
- Alex's Soapbox
- Announcements
- Best of…
- Best of Email
- Best of the Sidebar
- Bring Your Own Code
- Coded Smorgasbord
- Mandatory Fun Day
- Off Topic
- Representative Line
- News Roundup
- Editor's Soapbox
- Software on the Rocks
- Souvenir Potpourri
- Sponsor Post
- Tales from the Interview
- The Daily WTF: Live
- Virtudyne
Admin
Nope - not even for mobile apps - it's still wrong to suppress errors. Never grab a tiger by the tail.
Never catch an error that you don't have a mechanism to deal with - throw it upwards and let the parent deal with it. At least at the top, if no one knows how to deal with it, the end user can deal with it by buying someone else's software.
Admin
Yup, this "pattern" is very common in my office from a certain individual. Drives me nuts.
--captcha = eros
Admin
Do you think that special arrangements were made that day -- the Sun arrested in its orbit, the Earth's rotation stopped for a day, whichever way you look at it -- since the Sun didn't have to rise for you to see? Or do you trust it rose that day too, as every other day?
If you believe the first, you're obviously a solipsistic lunatic. If you believe the second: Why would trees behave differently from the sun; i'e, why would they behave differently just because you weren't there to observe them? That idea is cut to shreds by Occam's razor in pretty much no time at all.
Admin
Man, if this is the first time you've seen someone eat an exception... let me be the first to welcome you to software development.
Admin
A blog like yours should be earning much money from adsense.’~::-group buy seo
Admin
I've had the argument from the person I develop for that most software doesn't throw up an error listing where the crash occurred (ie. class and line number). But if it does fail it and it doesn't show where it failed it makes it harder for me to locate the source.