AL>> reference for technical details IMHO, a manual should contain as much
AL>> useful information as possible
No. We could put there description of Zend API, details of Zend memory
manager, API of zend hashes and 1001 things - but they *do not belong
there*. It's a PHP manual, and this has nothing to do with PHP as a
language. There are 1000 other places (books, Zend.com, php.net,
phpwizard.com) where PHP articles and details are due. Manual is not only
place to put PHP/Zend material, and it should be kept clean. Not as much
information as possible, but exaclty as much information as needed for a
reference guide (as opposed to a tutorial, programmer's guide and user's
guide).
You´re right, instead of that you´re wrong in the point that
reference-counting does not affect the PHP programmers behaviour.
For example PHP devs would feel more free using copys of variables if they understood
that it doesn´t hurt them very much behind the scenes.
This script does not copy the object 3 times, it just increases ref-count by 3.
$copy1=$mega_mature_object;
$copy2=$mega_mature_object;
$copy3=$mega_mature_object;
But the user would expect that it copies and copying takes time and memory usually.
Perhaps it only affects <1% of the devs, but it´s a relevant issue while the zend api
is not (for the manual).
--
o----------0-¬---------O-·---¬----o---®-----o o O ° .
| http://www.kiffen.de | pRoteçt y0ur bRaín |0 O ° ¤ °
·
0°·³°²'²³-¹'³´³°^°³~³²³°'³²²¨³²^³¹³²°²³`³º³°Þ °
o © ° . ·
| psychedelic experience | gott@kiffen.de | O ° o °
o-¬--o--0-----©-·--O-----o-----0-¤----------o 0 ° · ° . ¤ ·