Zitat von "Stanislav Malyshev" <[EMAIL PROTECTED]>:
Hi!
Then do the right thing and make it PHP 5.3+ and namespace it right
from the beginning.
I'd be glad to, but it has to work with 5.2. I would like to make it
"ideal" way, but there are real world problems that needs to solve
which intervene :)
The inconsistency is that one class, IntlDateFormatter, has a
prefix. And the others do not.
I have to wholeheartedly agree with David. You are calling for
problems if *not* prefixing everything. See below.
Think of it as part of the name, not prefix. I'd like to keep it
DateFormatter, but Derick wants "Date" word for himself :)
Yes, and he wants it for a good reason, namely because he's gone
through all the trouble with the date extension already. Stas, you've
been around at that time already, so you know the "date" disaster back
then. And after many few-hundred-messages threads it was decided that
the new classes introduced with PHP 5.1.0 have to be prefixed with
Date, and that this has to happen for all new classes.
You also know pretty well that inconsistency is one of the most
frequent criticisms on PHP. You are making this worth with introducing
more inconsistencies in such a central piece of PHP.
Finally, I would like to point you to
http://www.php.net/manual/en/userlandnaming.rules.php:
"PHP will prefix any global symbols of an extension with the name of
the extension."
Jan.
--
Do you need professional PHP or Horde consulting?
http://horde.org/consulting/
--
PHP Unicode & I18N Mailing List (http://www.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php
