note 68797 rejected from function.assert by danbrown
| From: | danbrown@php.net | Date: | Sat, 19 Jul 2008 23:34:42 +0000 |
| Subject: | note 68797 rejected from function.assert by danbrown | ||
| References: | 1 | Groups: | php.notes |
| Request: | Send a blank email to php-notes+get-141794@lists.php.net to get a copy of this message | ||
Note Submitter: hodgman at ali dot com dot au
----
I dont agree with gk at proliberty dot com's statements below.
If you are constantly enabling assertions before each assertion, then you are removing the
functionality provided by being able to turn off assertions in the first place.
Assertions should only be enabled during testing/development, and then disabled once your code
reaches a production stage.
This means you should either leave disabling/enabling assertions up to the INI file, or let the
entry point of the script decide.
If you need an assertion to be there in the final copy of the code, then you are using the wrong
tool. Assertions are a tool for debugging only.