https://wiki.php.net/rfc/octal.overload-checking
Because having this expression evaluate to true makes me sad: ("\000"
=== "\400")
-Sara
https://wiki.php.net/rfc/octal.overload-checking
Because having this expression evaluate to true makes me sad: ("\000"
=== "\400")-Sara
+1 from my side right away. We all settled with the fact that "==" is
completely useless but at least "===" should be:
reflexive
symmetric
transitive
consistent
--
Richard "Fleshgrinder" Fussenegger
https://wiki.php.net/rfc/octal.overload-checking
Because having this expression evaluate to true makes me sad: ("\000"
=== "\400")
I haven't heard any responses on this and wanted to bump it back to
the top of your newsreaders.
For the record, my inclination is to raise a warning on octal
overflow, but not change behavior (at least, not for 7.1, perhaps
later).
Note that this warning would bubble up during the lexing phase, so an
opcache would prevent it from raising on every page load. That's
probably fine, the alternative is to signal the parser to bake it into
the ast output and that's way over-engineered.
-Sara
Hi Sara,
https://wiki.php.net/rfc/octal.overload-checking
Because having this expression evaluate to true makes me sad: ("\000"
=== "\400")I haven't heard any responses on this and wanted to bump it back to
the top of your newsreaders.For the record, my inclination is to raise a warning on octal
overflow, but not change behavior (at least, not for 7.1, perhaps
later).Note that this warning would bubble up during the lexing phase, so an
opcache would prevent it from raising on every page load. That's
probably fine, the alternative is to signal the parser to bake it into
the ast output and that's way over-engineered.
I guess everyone agrees to raise warning.
("\000" === "\400") === TRUE is wrong, simply.
Regards,
--
Yasuo Ohgaki
yohgaki@ohgaki.net
https://wiki.php.net/rfc/octal.overload-checking
Because having this expression evaluate to true makes me sad: ("\000"
=== "\400")I haven't heard any responses on this and wanted to bump it back to
the top of your newsreaders.For the record, my inclination is to raise a warning on octal
overflow, but not change behavior (at least, not for 7.1, perhaps
later).
ACK.
For now I have documented the issue
(https://svn.php.net/viewvc?view=revision&revision=339098).
--
Christoph M. Becker
Den 2016-04-19 kl. 01:24, skrev Sara Golemon:
https://wiki.php.net/rfc/octal.overload-checking
Because having this expression evaluate to true makes me sad: ("\000"
=== "\400")I haven't heard any responses on this and wanted to bump it back to
the top of your newsreaders.For the record, my inclination is to raise a warning on octal
overflow, but not change behavior (at least, not for 7.1, perhaps
later).Note that this warning would bubble up during the lexing phase, so an
opcache would prevent it from raising on every page load. That's
probably fine, the alternative is to signal the parser to bake it into
the ast output and that's way over-engineered.-Sara
This reminds me a bit about the RFC:
https://wiki.php.net/rfc/invalid_strings_in_arithmetic.
So an E_WARNING it should be and option 2. In my opinion
no deprecation is needed.
Cheers //Björn