It will be easier (AFAIK Zend docs are in the way). But I strongly
disagree it belongs to PHP manual. It is huge even now. We might have
another book, called "Developer's reference guide" - that would be
logical. Maybe somebody knowing how those DSSL's work should start it now,
so that when the content arrives it could be put in...
why doesn´t these things get *published* to the list (at least),
there are many thing being very intransparently,
at least the php-dev list should know everything what´s going on
in my opinion, like compiler issues, developer reference guide and
so on...
Yes it would. It would become so huge that you won't be able to find
anything there without a search engine. Structuring information was not
invented just for fun. Imagine all your Perl or C or Java programming
books now became one book called "Java manual" or "Perl manual". And then
try to find there some tiny part.
Currently our manual is much to small! It´s not well structured
(escpecially the functions part) and it should contain much more
example code with some tutoring tendencies, because it´s the USER guide,
not the experts guide.
--
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 ° · ° . ¤ ·