chris# wrote:
Something just occurred to me that might satisfy both sides of the issue. What about the way Apache handles their versions of Apache (1.x and 2.x). That is to say; they haven't abandoned 1.3 (no surprise, as I think it still has the biggest install base). They simply maintain security related issues. ppl still continue to build modules for 1.3. ppl still continue to run/install it. Apache doesn't hide it in some back corner. Everybody's happy. Would this approach not be an acceptable "EOL" for PHP4? Just a thought.
But it does not get round the situation where people 'expect' PHP applications to RUN on PHP4 because PHP4 is available. Apache is a reasonable analogy, but there is a well defined divide between 1.x and 2.x installations and people developing for 2.x don't worry about 1.x. This division is not present in PHP so that even though PHP4 and PHP5 are different animals, the fact that a PHP5 application CAN be fixed to run on PHP4 means that there is an expectation by some that it WILL. We need some final break with PHP4 so that this perception is broken and new development does not have to hark back to past history?
-- Lester Caine - G8HFL ----------------------------- Contact - http://home.lsces.co.uk/lsces/wiki/?page=contact L.S.Caine Electronic Services - http://home.lsces.co.uk MEDW - http://home.lsces.co.uk/ModelEngineersDigitalWorkshop/ Firebird - http://www.firebirdsql.org/index.php -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
