note 68797 added to function.assert
| From: | hodgman at ali dot com dot au | Date: | Thu, 10 Aug 2006 23:45:18 +0000 |
| Subject: | note 68797 added to function.assert | ||
| Groups: | php.notes | ||
| Request: | Send a blank email to php-notes+get-115780@lists.php.net to get a copy of this message | ||
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.
----
Server IP: 203.220.0.234
Probable Submitter: 203.2.182.254 (proxied: 1.1 AURB-PROXY-03)
----
X-Spam-Status: No, hits=3.1 required=5.0 tests=DATE_MISSING,FROM_NO_LOWER
autolearn=no version=2.64
----
Manual Page -- http://www.php.net/manual/en/function.assert.php
Edit -- https://master.php.net/note/edit/68797
Del: integrated -- https://master.php.net/note/delete/68797/integrated
Del: useless -- https://master.php.net/note/delete/68797/useless
Del: bad code -- https://master.php.net/note/delete/68797/bad+code
Del: spam -- https://master.php.net/note/delete/68797/spam
Del: non-english -- https://master.php.net/note/delete/68797/non-english
Del: in docs -- https://master.php.net/note/delete/68797/in+docs
Del: other reasons-- https://master.php.net/note/delete/68797
Reject -- https://master.php.net/note/reject/68797
Search -- https://master.php.net/manage/user-notes.php