Re: [PHP-I18N] intl 1.0.0RC1

Hi!

> What are the good reasons for not changing the names?

This was already discussed on the list, so reading the archives would 
help. But OK, here it goes again:

1. We want the extension to be in 5.2 to 6.x
2. We want PHP source code compatibility between 5.x and 6.x code
3. We want PHP 6 users use class Collator when they need collator, not 
some weird long name, same with Locale etc.
4. intl extension, unlike many others, do not have one functional 
module, but multiple ones, related only by underlying library. Thus 
prefixing all modules with extension name makes as much sense as 
prefixing all functions using libc or libm with common prefix. Each 
functional module, of course, does have its own prefix.
-- 
Stanislav Malyshev, Zend Software Architect
[email protected]   http://www.zend.com/
(408)253-8829   MSN: [email protected]