On Tue, Jan 5, 2016 at 12:24 PM, Aaron Piotrowski <aa...@icicle.io> wrote: > Before anything can be done with the @ operator, changes will need to > be made to remove warnings for conditions that the code has no way of > checking prior to calling these functions. > I'd include pragmatism in that calculus. fopen() can technically be safely called, but only by adding a lot of boilerplate that makes code ugly. An @ suppression is perfectly reasonable provided the return value is sanity checked.
-Sara -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
