On Sat, Jan 1, 2022 at 9:20 PM Michael Morris <tendo...@gmail.com> wrote:
> I leave the decision making to the maintainers and contribs who do the > actual work. Hell, I personally don't even use PHP that much these days > having gotten a job where I focus on writing Cucumber tests in JavaScript > that run on node.js. I keep up with PHP and this list though cause one > never knows what the next job will entail. I just dropped out of lurk mode > to underscore along with others up thread the massive ramifications of what > is being proposed. As someone who wrote stupid code I can see this > breaking, tread lightly. And hell, I don't even know how much of that code > is still in use since I've changed employers many times since it was > written. This situation is not unique and can create huge headaches for > companies running projects on legacy code bases. > I think a question worth asking is how much of that code is likely to actually run on PHP X.X if this were done. I don't have an answer to that, but the kind of code that you're talking about is likely to encounter other more fundamental problems. For instance, prior to 8.0, doing `$var = $obj + 2` would result in `$var = (int)3;` In PHP 7 this also produced a notice. In PHP 8, the same line results in a fatal error. I don't think that the impact would be limited to code that is written poorly however. There may be code which almost accidentally depends on this behavior that is in fact well maintained, since it is such a nuanced problem. To me, this seems like something worth doing, but it might be something that should wait for a major version. Jordan
