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

> What for? Refcounting is not visible from userspace in no way, why do you
> need it in the manual?

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

> Calling existing PHP manual "few" is a huge underestimate, IMO.
> But let's not bring there everything and the kitchen sink. Manual should
> be just reference, not all-about-the-subject tutorial.

You just said. It´s reference ;)
reference for technical details IMHO, a manual should contain as much
useful information as possible

like lars says...

> I agree--there are lots of things about the language that don't really
> need to be explained right in the manual itself. Although an appendix
> may not be a bad place for this sort of thing, along with the
> extension programming notes and other things that 99.7% of users won't
> ever need to know. 

-- 
o----------0-¬---------O-·---¬----o---®-----o o    O   °       .
| http://www.kiffen.de | pRoteçt y0ur bRaín |0  O °     ¤  °        ·
0°·³°²'²³-¹'³´³°^°³~³²³°'³²²¨³²^³¹³²°²³`³º³°Þ ° o © °   .  ·
| psychedelic experience |  gott <email protected>  | O   ° o           °
o-¬--o--0-----©-·--O-----o-----0-¤----------o  0 °  · °  .  ¤ ·

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