[PHP-DOC] Re: [PHP-DEV] "waldschrotts guide to nifty references" - manualpage draft, version 0.9b From: Stanislav Malyshev (stas <email protected>)
Date: 08/19/00

HH(>> 1) finding information about internals, esp. extension interface to
HH(>> both php core and Zend is not easy (yet), even if you have access
HH(>> to all the books around and i would welcome a manual part dedicated
HH(>> to this special topic

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...

HH(>> 2) as long as we do not have seperate tutorial and programmers and
HH(>> users guide and reference but only the one and only manual it
HH(>> should contain as much information as possible as looking through
HH(>> the 1000 other places will almost always end up in looking at
HH(>> 999 of them and missing the one you really needed

So we need to start that users guide and reference guide and whatever, not
bloat the manual.

HH(>> putting as much as possible into the manual won't harm as long
HH(>> as we manage to keep it devided in clear parts and sections

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. 

-- 
Stanislav Malyshev   stas <email protected>          
+972-3-6139665 ext.106