Hi, chiming in from the side, On Tue, Jan 5, 2016 at 12:45 AM, Sara Golemon <poll...@php.net> wrote: > Forwarding a suggestion twitter/@Beryllium9: > > How about a global "disable error suppression" setting? That way a > project lead could enforce it for their codebase (and guarantee that > devs "aren't lazy"), but PHP doesn't lose its pragmatism? >
I think this is an excellent compromise worth discussion and can vouch for usage of this suggestion in our environment, today. I maintain a shared hosting environment of sorts and have many different developer groups working in that environment. This is the sort of configuration we would take advantage of immediately. Thanks twitter/@Beryllium9 (wherever you are!) + Sara, -- Dustin Wheeler | Software Developer NC State University m: mdwhe...@ncsu.edu | w: 5-9786 "If you don't know where you're going, it's easy to iteratively not get there." -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
