#26759 [Bgs]: some less-than-desirable coding practices
| From: | kennyt@php.net | Date: | Fri, 16 Jan 2004 01:06:20 +0000 |
| Subject: | #26759 [Bgs]: some less-than-desirable coding practices | ||
| References: | 1 | Groups: | php.doc |
| Request: | Send a blank email to phpdoc+get-969358237@lists.php.net to get a copy of this message | ||
ID: 26759
Updated by: kennyt@php.net
-Summary: php documentation examples contain slow code
Reported By: kennyt@php.net
Status: Bogus
Bug Type: Documentation problem
PHP Version: Irrelevant
Assigned To: kennyt
New Comment:
it's a documentation "feature request" :-)
Previous Comments:
------------------------------------------------------------------------
[2004-01-01 17:43:24] derick@php.net
leave it at bogus
------------------------------------------------------------------------
[2004-01-01 14:24:28] vrana@php.net
If there are slow examples in the documentation, point to them. Bad
algorithms make scripts slow, not using double quotes where can single
quotes be.
------------------------------------------------------------------------
[2004-01-01 13:37:43] et@php.net
If you write less readable code in PHP because you are counting CPU
cycles which most of the time don't even add up to a noticeable amount
of time, you are doing something wrong IMHO.
------------------------------------------------------------------------
[2004-01-01 13:26:57] amaranth at phphacking dot com
I agree that the code examples in the manual teach bad habits. People
use them and don't realize there is a better solution, so they write
everything with this slower code. Once a script gets large enough these
do add up but by then its too late because so many lines would have to
be changed. If the manual showed better examples or at least told
people about the faster solutions it would fix a lot of headaches.
------------------------------------------------------------------------
[2004-01-01 05:55:31] derick@php.net
Don't smoke too much in the new year please.
------------------------------------------------------------------------
The remainder of the comments for this report are too long. To view
the rest of the comments, please view the bug report online at
http://bugs.php.net/26759
--
Edit this bug report at http://bugs.php.net/?id=26759&edit=1