Re: Proposal of removing PHP4 references from the manual

On Mon, Jul 14, 2014 at 10:49 AM, Maciej Sobaczewski <msobaczewski@gmail.com> wrote: > Hello Hannes, > > >> On Sat, Jul 12, 2014 at 11:44 PM, Maciej Sobaczewski <sobak@php.net> >> wrote: >> >>> *Dealing with removal* >>> - determine base version described in the manual - probably just 5.0.0 to >>> omit additional confusion >>> - remove all entries from changelogs for versions lower than PHP 5.0.0 >>> - remove functions not available in PHP5 >>> - remove extensions for PHP < 5.0.0 (if we have such) >>> - remove all inline references, notes etc. >>> >> >> I thought we did this already? (with the exception of removing PHP4 >> from versions.xml - which I don't really see a benefit - its imo is a >> fun history "fyi"?) > > > Respectfully, I don't think so. Right, most of the extensions not available > for PHP 5 has been removed, but there are still tons of references to PHP 4 > which are distracting users. Some examples: > > - "zlib: PHP 4.0.4 - PHP 4.2.3 (systems with fopencookie only)" > wrappers.compression.php > > - "Enable transparent session id propagation. Only valid for PHP 4.1.2 or > less. From PHP 4.2.0, trans-sid feature is always compiled." - > configure.about.php > > - "Available since PHP 4.3.0" - so many places > > - "These filters are <emphasis>not</emphasis> available for PHP 4." - > filters.php > > - many INI directives are not available in PHP 5.x > > - IMO directives available since PHP 4.x shouldn't have any additional > notes, like directives available as of PHP 3. If we assume that base version > for the manual is 5.0.0, it means that they are just available from reader's > point of view. That's all. > > - "Since PHP 4.0.2, <constant>__FILE__</constant> always contains an > absolute path with symlinks resolved whereas in older versions it contained > relative path under some circumstances." > > - "Prior to PHP 4.0.6, the behaviour of the <function>tempnam</function> > function was system dependent. [...]" - rather long note. > > - way more These should all, along with any other inline version information, go into changelogs. These changelogs are a goldmine when looking through a application that has been with us throughout time and received incremental upgrades as time goes. Lets not fuckover the people that has been with us this long. [...] > >> We could resurrect overload and domxml and export into .html page like >> php3.php? Is that what they are asking for? > > > I think that providing compressed/online snapshot of specified revision > somewhere on doc.php.net would be more convenient and even easier to prepare > for us. Opinion based on post written by Chris Wright in this topic. No. Thats a major annoying maintenance headache. We've got http://php.net/manual/php3.php (its thinner then I remembered?) Lets add the PHP4 specifics (oop4, dotnet, sw, domxml, ...) to php4.php there. -Hannes