Re: "waldschrotts guide to nifty references" - manualpage draft, version 0.9b

AL>> why doesn╢t these things get *published* to the list (at least), AL>> there are many thing being very intransparently, Which things? AL>> at least the php-dev list should know everything what╢s going on AL>> in my opinion, like compiler issues, developer reference guide and AL>> so on... These docs do not exist yet. We all have 24 hours per day exactly, you know :) AL>> Currently our manual is much to small! It╢s not well structured AL>> (escpecially the functions part) and it should contain much more AL>> example code with some tutoring tendencies, because it╢s the USER guide, AL>> not the experts guide. No it is *not* users guide. It is reference manual. If you want user's guide, fine, but it's not the same as reference manual. And they should be different, because they serve different purpose. In this case, we need two documents, and making existing reference manual into user's guide only to struggle afterwards to get reference manual back would be a clean waste of time and effort. -- Stanislav Malyshev stas@zend.com +972-3-6139665 ext.106