On 16/03/2015 11:49, Pavel Kouřil wrote:
it's similiar to the safe_mode though. Sure, it's not as bad as INI setting, but the "intent" is the same - a switch changing how code behaves.
ini_set('memory_limit', 10); also changes how your code behave, but it's global so that can be problematic.
die; changes how your code behave, but you can fix it if it doesn't do what you want in your file.
Code has meaning and therefore code changes what the program does. I don't think that's really a problem.
When I talked about the Dual Mode with some friends who are userland PHP devs (either current or former, because they switched to other stuff), none of them called the Dual Mode a great idea. The responses I got were mostly along the lines of "wow, this seems really weird" to "WTF are those developers smoking". Everyone of them (sure, ~10 people isn't really representative number) said that they think PHP needs STH, but not this Dual Mode stuff. Seriously, think about it for a while - when some setting that changes how code behaves was a good idea?
All your friends can happily ignore strict mode and no sysadmin can enable it as it is per-file. Those of us that do understand it and might want to use it can do so, and if your friends eventually go beyond the "this seems really weird" phase (it *is* weird because it's an uncommon approach to have both strict and non-strict in one language, but that doesn't necessarily mean it's bad) maybe they'll want to use it too some day. Or perhaps they'll need to start smoking.
Cheers, Jordi -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
