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

AL>> It´s an interesting fact for switchers and experts,
AL>> I don´t think it´s a good idea to hide all technical details,
AL>> we´re open source so why we´re closed technology

It's not closed. But not everything belongs to the manual. We should not
bloat it with unnecessary details. Manual should serve it's purpose,
not try to be jack-of-all-trades.

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

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

-- 
PHP Development Mailing List <http://www.php.net/>
To unsubscribe, e-mail: php-dev-unsubscribe <email protected>
For additional commands, e-mail: php-dev-help <email protected>
To contact the list administrators, e-mail: php-list-admin <email protected>