Or perhaps we could make our documentation based on PHP version
like the
mysql manual does. So we have a "different" manual for PHP6, PHP 5(.
3), 5.2,
one for PHP 4, etc. Then we could include /domxml in the PHP4
manual, and
the dom in the PHP5 and 6 ones. You could add a small dropdown box
at the
top like we have with languages now to choose the PHP version
you're looking
into. You could also have that stored in a cookie via my php.net
functionality.
I'm pretty sure phD can be modified to output docs specific to
versions if
we properly assign versions and changelogs to all functionality.
Totally. I would really appreciate semi-version-specific manual, and I
think we've discussed it in the passed...
The actual markup change wouldn't have to be that dramatic, adding few
version attributes here and there would probably do the trick - and
then new options to PhD "--only-php5" "--all-versions"
"--php5-and-greater" or whatever..
Users of the manual should be aware of what happened in the past,
present, and future, so I personally am against the idea of version
specific manuals. Other reasons include maintenance, PECL madness,
linking/references to "now missing parts", and lack of much difference
between PHP versions. And, we have changelogs.
However, there are parts of the manual that should be rewritten/
restructured to reflect the current landscape. Like for example
instead of oop being for PHP 4 and oop5 for PHP 5, simply have oop be
the current with others for the past... but this is getting off topic.
Basically we need to prepare for the future better.
As for the dom versus domxml man page problem, in the short term how
about we just remove the domxml xinclude file from phpman.
Regards,
Philip
