On 16 December 2014 at 13:18, Andrea Faulds <a...@ajf.me> wrote: > Hmm, actually, a 2to3-esque tool and a formal extension of 5.6's support by a > year sounds like a better solution. If others agree, I might withdraw this > RFC.
I disagree. 2to3 wasn't a success in the Python world — in the end, the only migration solution that worked there was code bases that could run on both Python 2 and 3 (with the help of userland compatibility libraries like six and python-future), and I believe the same will be true for PHP 5 and 7. More generally, I don't believe a standalone CLI tool can be the whole answer even if that wasn't a problem: too many of our users only ever run their code in shared Web server environments and aren't proficient enough at the command line (on whatever OS they choose) for that kind of tooling. I'm sure someone will write a 2to3 type tool, and that some people will find it useful, but I don't think it's the right answer in terms of advertising a migration path. Adam -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
