On Mon, 2013-08-19 at 17:05 +0100, Terry Ellison wrote: > By way of a background. I've been doing a review of the exting code > base looking at how to establishing a roadmap extend OPcache > functionality across all supported OSes and SAPIs. And this raises a > supplementary Q: which OSs and SAPIs should we be supporting for PHP 5.6 > anyway? I would be interested in the views of the dev team on this. > > It would be good to agree a list of which OSs are to be supported at PHP
The short version is quite simple: PHP supports everything and nothing. Our aim is to be portable and have it running anywhere somebody has a C compiler and the required libs. On the other hand, in open source spirit, we promise nothing. In reality I expect that most developers use Linux and we have a active Windows fraction. If we promise support for any platform it has two direct consequences: - We have to test and verify it - We immediately disappoint people who run PHP successfully on "edge" platforms And then more longterm consequences: - Mind new platforms - Continuous discussions about adding support for new platforms The current model otoh works quite well. > 5.6, which SAPIs are supported, and a matrix of which SAPIs are > supported on non-threaded and build TSRM variants. I myself would kill TSRM, but others have reasons to disagree ;-) In general: There are features which are dependent on operating system, 3rd party library or TSRM. This is fine. Based on my statement from above I claim (again, there are people who disagree for reasons I follow less than the general case above) that nobody who cares about performance uses TSRM, as such an opcode cache is not needed in such environments. > 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), nsapi (2011), > phttpd (2002), pi3web (2003), roxon (2002), thttpd (2002), > tux (2007), webjames (2006) > I realise that some of these may still be actively used with a user > community out there wanting to track current versions, and this is just > a case of "if ain't broke..." However, I do wonder when some of these > were actively maintained and routinely tested against the current > versions at release -- and if not then perhaps PHP 5.6 is the correct > point to retire them from the source tarball and configure options? First thing to note is that the SAPI layer is one of the most stable ones. So old SAPIs most likely work. Secondly: Yes some of them almost certainly can go, when we discussed this last (~10 years ago) an issue was that we have no good place to put these. For extensions we have Siberia^H^H^H^H^HPECL where people can try if they get it working ... getting SAPIs work from out of tree is not as easy ... johannes -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
