> >>>Sorry If this has been bought up before. I was going through > >>>the man pages finding some stuff that needed documenting and came > across > >>>this http://au3.php.net/manual/en/function.substr-compare.php > >>> > >>>After some investigating found out that it only exists in php5.0b2, so > >>>my questions is how are we going around documenting php5 functions and > >>>there versions? > >> > >>I don't think this was discussed before, but there was a post on > >>internals@ talking about that : > >> > >>http://news.php.net/article.php?group=php.internals&article=%3C5.1.0.14. > 2. > >>20031113192909.06aef8b0%40127.0.0.1%3E > >> > >>I think that we should encourage internals to send us some (well|bad > >>formated) docs and work on this topic. > > > > Is it internals place to tell the docs team how to document? Kinda > pointless > > if you ask me just a thought, if there has been no set standard about > what > > to do, mabey this is the time? > > Flame at will > > There is probably "not enough" overlap between the internals and > documentation team... Some guys here can add documentation on most of > the functions is proper prototypes are in the source code, and it is > understandable what the function does. Otherwise it is common practice > that an extension writer documents the functions he added, and the doc > team refines it, fits it into the build system, adds interlinks, fixes > errors, mispelling, adds missing functions, etc. This was the case for > example lately with the tidy extension (or the mysqli extension). > > Goba
I agree with that 100%, however when it comes to the question I raised, how do we document the version for php as there is beta's and the such do we start documenting now etc, shouldn't this be a doc team problem? I'm pretty new to this list so I'm not sure how things work etc but that's just the way I view it, however if things are done differently please feel free to put me in my place Jared
