On 10/1/14 10:36 AM, Bruno Medeiros wrote:
On 01/10/2014 14:55, Steven Schveighoffer wrote:
On 10/1/14 9:47 AM, Bruno Medeiros wrote:
On 29/09/2014 19:58, Steven Schveighoffer wrote:
Any uncaught exceptions are BY DEFINITION programming errors.
Not necessarily.
For some applications (for example simple console apps), you can
consider the D runtime's default exception handler to be an appropriate
way to respond to the exception.
No, this is lazy/incorrect coding. You don't want your user to see an
indecipherable stack trace on purpose.
-Steve
Well, at the very least it's bad UI design for sure (textual UI is still
UI).
But it's only a *bug* if it's not the behavior the programmer intended.
Sure, one could also halt a program by reading a null pointer on
purpose. This is a grey area that I think reasonable people can
correctly call a bug if they so wish, despite the intentions of the
developer.
-Steve
