Critical errors that state "There is no error" and then kill a program are just not useful at all. I have experienced the actual "There is no error" critical exception first hand. It is a critical exception that stops an application from working. Yet the message is informing us that there is no error. Well, if there is no error, then why has a critical exception warning appeared on the screen? And why am I unable to continue using the application? Obviously, for the critical exception to be raised, there must be a critical exception somewhere that occurred. But where and why?
What makes such exceptions even more annoying is when they are deep-rooted in the framework or library that you are using (which you have no control over), and where you have no access to the source code. Such exceptions have caused programmers to say negative things out of frustration. I've been guilty of this and I've...
