On Wed, 10 Aug 2005, Zeev Suraski wrote:
> Calling to a function with the wrong arguments is something that should be
> dealt with when developing the application, not at runtime. I think that
> throwing exceptions in all sorts of places encourages people to write
> 'exception-oriented' apps, which is very messy. Type hinting is also not
> exactly an OO thing, it's an object thing, and there's a difference. PHP is
> filling up with a lot of builtin classes, as well as infrastructure classes,
> that actually simplify the lives of users, without them having to have a clue
> about object orientation. Some examples that come to mind are SimpleXML, the
> SOAP classes and PDO. On a long enough timescale - everybody using PHP will
> be using objects, and many (if not most) of them will be using them in
> procedural apps. I see a big negative point in forcibly introducing these
> people to the concept of exceptions.
I agree a 100% here.
> I believe we mentioned once the possibility of adding another error level,
> which is fatal - but still catchable by set_error_handler(). That is a good
> idea (which we should be doing either way).
That would work well. I just want the type hints to be catchable.
regards,
Derick