Pah, we all know the future is psp (http://www.edwardbear.org/mod_psp-0.3.tar.gz ;-)
psp sucks badly :P
Just to be clear: I'd be happier without type hinting then type hinting throwing an E_ERROR (a E_WARNING would also make me happy).
The problem I have is the 1% of the time where a type mismatch doesn't get caught, running normal code on a production site, and it causes a bailout. I can imagine that's going to cause quite a few errors (display_errors off, hard to reproduce bug).
You mean that a function which is supposed to receive an object and calls methods on that objects/manipulates that object and etc. shouldn't lead to a fatal error? I think you're exaggerating big time. I think this is a case where you want your script to fail and you can use the error handler to create a more user friendly error page.
Andi
-- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
