Comments by djmarcus (Top 1 by date)

Reason for my vote of 1 \n The throwing of an exception when detecting an error is simply good programming practices.

The article focuses on the throwing of the error but does not address the two critical issues:

1: What to do when trapping the error?

2: How to notify the programmer?

In '1:' the code sample simply traps the error and does nothing

In '2:' the article is silent. This issue ('2:') is critical. Imagine the code running on a customer's machine. How will the information that an error occurred get back to the programmer?