note 84589 added to function.assert

tom russo at gmail dot com said: "If your production code fails an assert, YOU WANT TO KNOW ABOUT IT. Asserts are a debugging tool, but you should not stop debugging your code just because it has gone into production." I agree that you want to know if your code breaks, however, in a production system, assertions are still the wrong tool for this. Assertions give this valuable debugging information to THE END USER, not to THE DEVELOPER. In production, switch over to a logging system and just display a "technical difficulties" page to the user - don't go handing out the internal workings of your system to your users! ---- Server IP: 209.41.74.194 Probable Submitter: 203.2.182.248 ---- Manual Page -- http://www.php.net/manual/en/function.assert.php Edit -- https://master.php.net/note/edit/84589 Del: integrated -- https://master.php.net/note/delete/84589/integrated Del: useless -- https://master.php.net/note/delete/84589/useless Del: bad code -- https://master.php.net/note/delete/84589/bad+code Del: spam -- https://master.php.net/note/delete/84589/spam Del: non-english -- https://master.php.net/note/delete/84589/non-english Del: in docs -- https://master.php.net/note/delete/84589/in+docs Del: other reasons-- https://master.php.net/note/delete/84589 Reject -- https://master.php.net/note/reject/84589 Search -- https://master.php.net/manage/user-notes.php