|
The principle behind the suggestion is that for robust code you need to keep all warnings and errors enabled and turned up full volume, so to speak. That helps catch the inevitable bugs you will have in your code. When you go to production, you suppress/reroute by catching the errors and either logging them or emailing them to yourself, but keep them from sight of the user. Any fatal errors, of course, should be made known to the user in general terms. Do not give specific details of an error to the user -- he/she might be malicious and able to intuit a weak point of penetration if you do so.
|