Re: ext/intl

Hi!

And even more annoying is the fact ext/intl invents its own error reporting completely. It silently fails and error message retrieval is left as exercise for the user, exactly the opposite of what _all_ other extensions do.

Isn't that what is described here? http://us.php.net/mysql_error Errors coming back from the MySQL database backend no longer issue warnings. Instead, use mysql_error() to retrieve the error text. Note that this function only returns the error text from the most recently executed MySQL function (not including mysql_error() and mysql_errno()), so if you want to use it, make sure you check the value before calling another MySQL function. If you think it should also produce warnings on each such instance, though as you'd need to handle the errors separately anyway, I'm not sure how useful that'd be. But it can be done.

Furthermore many of these messages are wrong, as they hardcode the function name to the message (see php_intl_idn_to() f.e.), rather then using the normal way of populating error messages.

They report where the error happened, what harm is in that? -- Stanislav Malyshev, Zend Software Architect stas@zend.com http://www.zend.com/ (408)253-8829 MSN: stas@zend.com