On Thu, Aug 29, 2019 at 2:29 PM Stanislav Malyshev <smalys...@gmail.com> wrote:
> >> I knew it worked, but I always considered this to basically be > >> the PHP equivalent of undefined behavior in C. And I don't think anyone > > It's not. It's very well defined behavior, that is not going to break - > unless it is broken intentionally in a zeal for adding more strictness > for the sake of strictness. So, another thing to learn. I love learning > new things, and love helping others do so! > > It is well defined. It's also, in my PERSONAL opinion, gross AF. That doesn't make me right or better or anything other than opinionated. Other opinions: * I'd quite like PHP to be a little less gross in places like this. * I think Nikita's hitlist here is a step in the right direction, however... * I DON'T think the cost to BC is justified in all cases. For example, an exception for read of undefined vars is traumatic BC. * I think declare(strict_types=1); already solved a very similar problem and could easily be applied to future issue like this. So how about we suck it up, put on our big girl panties, and just embrace declares (including namespace scoped declares and/or a modern version of .htaccess) -Sara
