> >These topics usually don't interest the average PHP developer - why > >keep it in the same manual, then? > > > >What do you think about this? > > > +1 - Maybe even consider adding to part 2 some documentation on > developing PHP itself. Right now, one must read the few files on the > Zend API, some coding standards, subscribe to this list, and use the > force (read the source) - not that this approach is all bad. > There are some musings to split the manual up, and make it more usefull, ie -- allow extension developers the opportunity to manage their own documentation, and have it built and integrated into the overall system... So I think modularizing the doc system is a good idea.
-- james -- PHP Development Mailing List <http://www.php.net/> To unsubscribe, visit: http://www.php.net/unsub.php
