Hi! > Given that the *engine itself* now throws exceptions, and we have > bundled extensions which throw exceptions, the blanket ban on exceptions > "in core functions" seems increasingly out-dated. This particular
I agree. I think once we agreed we want to convert from fatals to exceptions, we need to recognize exceptions as a first-class citizen. Which means using it in internal functions is OK. Now, there is a big gap between E_WARNING on one side and E_ERROR/exception on the other side. Whether particular function crosses this gap or not is a case-by-case discussion, but "we can not use exceptions in core" should no longer be a part of it. > too quickly. I'm also a big fan of proper exception hierarchies - I've > seen so many times that you should never *catch* the base Exception > class, so *throwing* a base Exception seems very wrong to me. Agreed. Maybe we should have something like RuntimeException or Java? That is pretty generic too, but at least not Exception. -- Stas Malyshev smalys...@gmail.com -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
