> can you please explain a bit more how you would achieve this in 3m loc?
AssertionExceptions are not intended to be caught, they are intended to be seen, in a specific environment. It doesn't really make sense to commit/deploy code that catches AssertionExceptions knowing that the code is actually dead in production. So you just don't deploy catch blocks for AssertionException, you might write one while debugging locally, but deploying them doesn't make sense. Cheers Joe On Fri, Feb 20, 2015 at 1:05 PM, Crypto Compress < cryptocompr...@googlemail.com> wrote: > > The alternatives are not nice, in my opinion. >> > > What are this alternatives? What are the drawbacks of "warning" in > production code? > > > -- > PHP Internals - PHP Runtime Development Mailing List > To unsubscribe, visit: http://www.php.net/unsub.php > >
