Re: Remove Classes and Objects (PHP 4)
| From: | Philip Olson | Date: | Mon, 14 Nov 2016 20:27:54 +0000 |
| Subject: | Re: Remove Classes and Objects (PHP 4) | ||
| References: | 1 2 3 4 5 6 7 8 9 10 11 12 13 14 | Groups: | php.doc |
| Request: | Send a blank email to phpdoc+get-969386344@lists.php.net to get a copy of this message | ||
Hello all,
If adding a separate PHP 4 document (like PHP 3 has) feels like
a wasted effort due to limited human resources (I agree), then
an alternative solution might be necessary.
Maciej added the following on Aug 17, 2014:
http://php.net/manual/php4.php
Which points to the old doc snapshots, and migration guide:
http://php.net/manual/en/migration5.php
That might be enough but in certain places that PHP 4->5 migration
guide assumes the online documentation contains PHP 4 information
so it lacks details. For example, regarding the PHP 4 OOP topic:
http://php.net/manual/en/migration5.oop.php
Not much there. So, two ideas:
1. Make the PHP 4->5 migration guide the PHP 4 manual
This means updating the guide to include relevant PHP 4 related
information. In this case, it would mean adding details about
how PHP 5 changed OOP. It does not mean throwing all PHP 4 docs
into the migration guide.
2. Add "See Also" for the biggest changes
This idea is less thought out and potentially overkill. But
some sections in the documentation might point to the PHP 4
migration guide if something major changed.
I can’t think of a good example so maybe this point should be
ignored :)
Just a random thought/idea, maybe a TODO folks can attack at their
leisure. I just fear living in the php.net bubble might not take
into account all the users out their maintaining old code.
Regards,
Philip
> On Nov 13, 2016, at 12:08 PM, James Titcumb <james@asgrim.com> wrote:
>
> I think as they're stored in SVN and the archive exists, that should be sufficient imo :)
>