Markus Fischer <[EMAIL PROTECTED]> writes: > As long as the extension is marked EXPERIMENTAL so are the > docs and so they may be out of date for current version and > also up to date with current versions and not reflect the > behaviour of any of the older versions.
*sigh* I should have made this more clear. The sockets is but an *example* of why the documentation un-versioned is a bad idea. Yes, the sockets code is experimental, but the MySQL stuff (for example) is not. If someone changes the documentation in CVS and that gets put up on the website, then the poor unsuspecting user going to look up the spec for mysql_connect() is going to be scratching their head trying to figure out why the heck the code they're writing that conforms to the documentation doesn't work. The documentation needs to be treated just like the actual executable code. It should be released in conjunction with PHP and a new version put up when bugs are fixed and the old versions should be available just like the old versions of PHP are. I don't know what the stats are for how many people are using older versions of PHP versus those on the bleeding edge, but speaking from experience, it sure would be nice to have documentation on hand for the version I'm using without having to refer to caveats about which version the array commands were changed in (another real-world example). -- Brian Lalor [EMAIL PROTECTED] [EMAIL PROTECTED] -- PHP Development Mailing List <http://www.php.net/> To unsubscribe, visit: http://www.php.net/unsub.php
