- 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
it would've been kinda usefull would there be breakpoints on the //shenanigans
Admin
Testing? It's much more cost-effective to just let your users do that after you deploy. If there are bugs in the code, the users will find them and let you know.
Admin
Admin
damn it, I have to report these guys they forgot to write
in every single empty catch!!!
http://gist.github.com/200075
Admin
Something horrible WILL happen if Foo = Null! ;-)
Let that be a lesson to you. Never let your foo be null!
;-)
Admin
Then you learned wrong! Much better not to handle an exception at all than to silently suppress it, because then it will propagate upwards and be caught by an error-handling mechanism elsewhere instead of resulting an untraceable bug.
The only mitigating circumstance for this is that we are told the code is for a GUI. You don't really want all your errors reaching the user. But still, best design would be to catch anyt hat haven't been caught elsewhere at the last possible moment, log the error, and present the user with a generic error message and some sensible choices.
Admin
WTF², that doest not look like an error or exception condition.
Admin
Admin
Hi, welcome to Walmart!
Admin
Oh snap!
Tis true.
Captcha = genitus /giggle
Admin
PrgmSHNANGNS:ClrHome:Disp "ERR:SHENANIGANS","1:QUIT","2:Goto ":Return:Disp "SECRET MESSAGE!","TI-BASIC 84+SE"
Admin
This just in:this is actually Lucy.