Christopher Jones wrote:
The best comment from that is
The solution is clear: build a full compatibility layer, not a conversion tool, into 3.x that makes 2.x code run without change and ABRUPTLY stop development on 2.x.
The simple fact that conversion of PY2 code so it will work in PY3 was the problem since there is a MUCH smaller pool of programmers who are capable of the work? It's not unlike PHP4 to 5 since there was little incentive to upgrade systems that were working fine already.
Basically as long as PHP6 runs at least the bulk of PHP5.? code then there will not be any major block. The only problem is should it run PHP5.2 code, or only PHP5.6? Little things like only supporting e_strict?
--
Lester Caine - G8HFL
-----------------------------
Contact - http://lsces.co.uk/wiki/?page=contact
L.S.Caine Electronic Services - http://lsces.co.uk
EnquirySolve - http://enquirysolve.com/
Model Engineers Digital Workshop - http://medw.co.uk
Rainbow Digital Media - http://rainbowdigitalmedia.co.uk