Re: Making PHP 5 a first class citizen
| From: | Philip Olson | Date: | Sat, 09 Oct 2010 16:37:31 +0000 |
| Subject: | Re: Making PHP 5 a first class citizen | ||
| References: | 1 2 3 4 5 | Groups: | php.doc |
| Request: | Send a blank email to phpdoc+get-969382205@lists.php.net to get a copy of this message | ||
On Oct 8, 2010, at 10:30 AM, Julien Pauli wrote:
> I'm just putting back the subject here ;-)
>
> Actually translating French doc, I noticed that few days ago, a change to the original (en)
> source from PCRE had a huge diff deleting all the "available since PHP4.X.Y". Same inside
> other sources from En doc.
>
> So, what to do ?
>
> I'm +1 to put away all the references with "PHP4" inside. We all know PHP4 is
> not supported any more, it should just move to the museum.
> Actually, I'm reading and correcting typos in the Fr doc, should I go to remove everything
> talking about PHP4 (obviously except the specific chapter about PHP4 objects) ?
>
> Exemple from session : "PHP_INI_ALL in PHP <= 4.2.3. PHP_INI_PERDIR in PHP < 5.
> Available since PHP 4.0.3"
> That is something really boring to read, confusing, and completly out of date.
Greetings Julien,
Okay, let's do it. Creating changelog entries everywhere is one option but the work involved no
longer feels worth it. Let's consider the current manual as "The PHP 4/5 Manual" and
finally remove all PHP 4 specific references from SVN. Well, except for a few exceptions like the
dom page should mention the domxml vs dom issue.
The topic of version specific manuals comes up occasionally but I don't see it working. I
won't go into detail with my feelings now, but lean towards thinking it's a bad idea even
if it could be done with a magic wand.
As for which version of PHP 5 to go with, that's a tougher question. I forget most of the
proposed solutions but think there are several and will search the archives this week. Solutions
that limit the inline versioning text (e.g., "As of PHP 5.1.0, Foo and Bar...") are ideal.
I think version specific XML attributes was one thought, where PhD would handle it and output
something useful.
And lastly, the INI version information is/was generated by doc-base/scripts/iniupdate/* but in
reality, it no longer works and people have been editing the XML by hand. However, it's
something to keep in mind.
What do people think about all of this? :)
Regards,
Philip