Re: ext/intl
| From: | Lukas Kahwe Smith | Date: | Sun, 10 May 2009 13:57:53 +0000 |
| Subject: | Re: ext/intl | ||
| References: | 1 2 | Groups: | php.qa |
| Request: | Send a blank email to php-qa+get-64931@lists.php.net to get a copy of this message | ||
On 10.05.2009, at 15:49, Hannes Magnusson wrote:
On Sun, May 10, 2009 at 15:31, till <till@php.net> wrote:Wow, thats not very nice at all. I guess we really need to beef up our review process for new extensions if this is indeed the case. Any chance at getting this cleaned up within 2 weeks time? regards, Lukas Kahwe Smith mls@pooteeweet.orgHey Pierre, wondering -- and I hate to bring it up again -- but since ext/intl in php 5.3 basically mimics the behaviour of pecl/idn sans error codes. Could this be "adjusted"? I understand the code is seperate but since they share the function names it would be super convenient for people. We've noticed that ext/intl basically says 'no' in case of an error where pecl/idn returned a more verbose error stating why it failed. I know this is not a bug in ext/intl but never the less, it would be an improvement and make it easier for people to move code from pecl/idn to ext/intl.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. 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.