On 15/12/14 20:08, Ferenc Kovacs wrote: > there are two advantages for having 5.7 and having those deprecated > messages in 5.7: > 1, if we introduce the deprecated message in 5.6.x, some people will miss > it (for example debian jessie has 5.6.2) > 2, would allow us to stabilize 5.6 instead of keep adding stuff to it > continuously . And LTS versions can be ring fenced at 5.6 ... with just functional fixes.
Perhaps what is needed is a tool which does identify the problems in 5.X code that need to be addressed in order to run clean in PHP7. Rather than encumbering PHP7 with E_STRICT type warning/error code, PHP5.7 would be a test environment to replace that functionality. Once code runs clean then one knows that it can be moved over? Style changes like the 'incorrect ternary '?' associativity' function would be highlighted so that BC problems are not silently changed. A properly documented migration tool rather than a production release as I would not expect to use PHP5.7 in a production environment! -- 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 -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
