On 06/12/13 12:04, Leigh wrote:
On 6 December 2013 07:39, Mike <mike.php.net@gmail.com> wrote:
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,
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