> De : Anthony Ferrara [mailto:ircmax...@gmail.com] > Saying that turning on an optional and previously unavailable option inside > code causing code breaks is any way a " BC" break is pure FUD.
Who talked of BC break for this ? I probably missed something because there's no BC break here, just an extremely probable disaster scenario. If people massively turn strict-type on because they see on twitter/google/fantasm that it is detecting more errors (and history shows it *will* happen), we have a big problem, because can only be massive casting. Nothing exaggerated here and history again shows that 'people know what they're doing' is not serious. "Strict types are sexy. I want to use them on my old codebase. It will help me finding bugs". Human. Basic. Don't think that's FUD. Regards François -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
