Streams is/are a PHP API for use by extension authors, so as Markus said, we need some kind of C API section in the manual.
I think the Zend docs should be integrated into php docs, or at least "renamed" so that they apply to extending PHP rather than just Zend. Then the streams API can be documented within that doc tree. If the doc guys could prepare the way, I will fill in the docs - the last time I set about documenting some stuff, the whole doc tree was restructured in between the time I checked it out and the time I checked it in again. Since I'm not subscribed to php-doc (I get too much mail already!), I want to make sure that this stuff is set-up correctly, so I don't waste my efforts :-) Thanks, --Wez. On 12/06/02, "Markus Fischer" <[EMAIL PROTECTED]> wrote: > Hi, > > streams are mostly only visible internally right now. At > least, this is what Andi was talking about, documenting the C > API of streams because it should be used from now on but > documentation is limited. > > So, this would be a candidate in Zend API docs ... ? But > then, it's not Zend stuff, so it should be in the PHP manual, > some C API section. > > - Markus > > On Wed, Jun 12, 2002 at 12:09:04PM +0200, Gabor Hojtsy wrote : > > > Can someone please help out Wez? ;) > > > > I don't really know what streams are about [it's not documented ;)], > > so if it's a new extension, Wez can start with copy-pasting one > > extensions documentation (see phpdoc/en/reference/ANY_EXTENSION_NAME). > > The XML files are quite self descriptive, so the tags to be used speak > > for themselfs. > > > > But we would also be happy with a nicely formatted text file (like the > > one in the overload/README), and so we can build up an XML file based > > on it.
