On Thu, Feb 26, 2015 at 3:57 PM, Zeev Suraski <z...@zend.com> wrote: > Drupal homepage: One new E_DEPRECATED warning, which seems to catch a > real bug, or at least faulty looking code: > $path = trim($path, '/'); // raises E_DEPRECATED, as $path is boolean > false. > return $path;
So far nobody answered this question but Francois (tried). You keep using this E_DEPRECATED message as a safety net to catch possible bad things. What's about other changes that may not match the current casting rules (or lack of) and will be different with this RFC? Those considered as "Yes". This is what I worry about, even if minimal these cases are pains to track down and fix. Also I would really like a clear table describing in details what will be changed, to compare how it works now and how it work later. This is something that is crystal clear with the dual mode RFC, nothing changes by defaullt, and strict rules if strict mode is enabled for a file. As you would expect, I will vote no as it is proposed now. -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
