Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:70517
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 74.125.82.175 as permitted sender)
Message-ID: <52A1E615.40300@gmail.com>
Date: Fri, 06 Dec 2013 14:58:29 +0000
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.1.1
MIME-Version: 1.0
To: Leigh <leight@gmail.com>, PHP Internals <internals@lists.php.net>
References: <1386315591.31655.16.camel@smugmug> <CAPwsocGnq2rWW81FnPxu0=x=zT_eF0rPnc8wEpn2afYQE_hi0Q@mail.gmail.com>
In-Reply-To: <CAPwsocGnq2rWW81FnPxu0=x=zT_eF0rPnc8wEpn2afYQE_hi0Q@mail.gmail.com>
Content-Type: multipart/alternative;
 boundary="------------020504060901030009090004"
Subject: Re: [PHP-DEV] Obsolete SAPIs
From: ellison.terry@gmail.com (Terry Ellison)

--------------020504060901030009090004
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

On 06/12/13 12:04, Leigh wrote:
> On 6 December 2013 07:39, Mike <mike.php.net@gmail.com> wrote:
>> Just stumbled over this one:
>>
>> https://bugs.php.net/bug.php?id=60503
>>
>> Time to remove some things in master?
>>
>> --
>> Regards,
>> Mike
> Possibly relevant; in case you missed it there was a small discussion
> on removing obsolete SAPIs earlier this year.
>
> Thread was started by Terry Ellison on August 19th if you want to check it out.
>
> [PHP-DEV] Which OSs and SAPI should PHP 5.6 support?
>
Thanks Leigh,

Looking back at the thread, I made the mistake of wandering off topic, 
but the points in my O/P are still lying there unanswered:

* Obsolete SAPI list:
> Examples of what I am talking about are SAPIs with no clear evidence 
> of active support (I've listed the last non-bulk change in brackets to 
> give a measure of the level of support):
>     aolserver (2008), caudium (2005), continuity (2004), phttpd (2002),
>     pi3web (2003), roxon (2002), thttpd (2002), tux (2007), webjames 
> (2006) 
* Obsolete OS support:
> Likewise in the Zend, TSRM, ext/opcache ... sources, there is 
> conditional code dependent on BeOS, __sgi, __osf__,  __IRIX__, PI3WEB, 
> GNUPTH(*), OS_VXWORKS,  etc. as well as obsolete BSD versions -- OSs 
> that are no longer actively supported. 

We've had "make test" feedbacks for years.  Is this data ever mined to 
validate that SAPI and OS build variants are being actively carried out 
tracking currently supported OSes?  Do we have an active deprecation 
process so that we can cull dead code?

There's too much ifdef source and even some compiled logic -- mainly in 
the Zend Engine and in the SAPIs, but also extensions -- that has 
probably not been covered in testing since at least the 5.2 timescales.  
If we never exercise and validate code, then isn't time to at least 
actively deprecate it in 5.6 so that it can be removed in a future release?

Regards
Terry Ellison



--------------020504060901030009090004--