Hi! > This gives quite a bit more info since we now know that it was an > argument and specifically which argument it was, what its type was and > what it should have been vs. having a fatal from somewhere deep in the > function itself. So I disagree with you on it not making life easier for > the caller in this specific case where there is no way for the type to > be coerced into something that makes sense.
You've traded bad error message for slightly better error message, but on the way you've lost the ability to actually handle this situation. Which exactly what bothers me - we're teaching people that the right way of handling any unexpected situation is to rely on post-mortem error logging after it blows up in runtime. I'm not sure it's such a good idea. -- Stanislav Malyshev, Software Architect SugarCRM: http://www.sugarcrm.com/ (408)454-6900 ext. 227 -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
