• Anon (unregistered) in reply to Brian

    Everyone who whines about Visual Studio seems to just be of the kind what spells Microsoft with a $.

    It has problems, plenty of them, most of them related to responsiveness of the IDE, but it is leaps and bounds better than every single other IDE available.

  • Anon (unregistered) in reply to Ulysses

    "Exceptions give helpful information to humans".

    Really? like "Object reference not set to an instance of an object"?

    This is why I generally show a helpful message to users in situations where problems can be anticipated (opening a file). But otherwise just show a general "call tech support" message. Of course, I build mainly business applications, and our tech support knows how to properly check the logs for the full exception details including stack trace.

  • Ugh (unregistered)

    The people in .net land don't know how bad they have it. Checked exceptions in Java land are so much better. There are literally millions of lines of .net code floating around with nary an exception handler in place for NORMAL stuff like network hiccups and database connection pool timeouts. Yes, your application should DEFINITELY blow up if the network experiences some lag rather than catching the exception and re-trying a suitable number of times.

    And exception handling is FAR SUPERIOR to result codes for the reasons mentioned -- there's a reason .net and Java both have exception handling rather than HRESULT or some other nonsense.

  • Anon (unregistered)

    I had this before in VS 2008 and 2010, I think also 2012. By default it won't step into exception handlers. And pray tell, how do you actually find the source of the bug if you are going at it like a user and not at a developer?

    BTW the mindset that exception handling should be rare is what causes so many problems with software, causing pointless crashes and a huge amount of unnecessary data loss.

    It costs very little to avoid the software crashing and even if the user can't do anything due to the bug, at least he can reproduce the bug far more easily than if the program instantly crashes and thus greatly help the developers in actually fixing this.

    PS: Pretending that all your software is error free and thus exception handling is a bad idea is simply childish bragging.

  • experienced guy (unregistered) in reply to DocMonster

    30 years ago, we were all coding C, which had no exceptions. Fast forward 30 years & who needs this new-fangled stuphs?

  • Ulysses (unregistered) in reply to Appalled

    Do whatever the fuck you want that works. There's no right or wrong. There is only what works.

    Said every other WTF factory that ended up here. Scriptkids like you give the rest of us a bad name.

Leave a comment on “Exceptional Handling”

Log In or post as a guest

Replying to comment #:

Log Out

« Return to Article