> - I still think IntlDateFormatter vs the rest w/o Intl prefix is > inconsistent. Can't we just prefix it with "Intl" across the board? > Saves trouble down the road
I'd like to second this proposal. Consistency and far-less-likely-to-clash-with-existing-code are more important (IMHO) than slightly longer, slightly uglier names. It also makes it easier to identify which code is coming from which library (*). Namespaces were supposed to be in php5 but got pulled at the last minute (IIRC), but I see they will be in php6. Perhaps the Intl prefix could be used consistently on the php5 version, and not used at all (i.e. IntlDateFormatter becomes DateFormatter) in php6? On the other hand, having to rename functions to move from php5 to php6 would be unpopular? Are any other php6 libraries planning to drop prefixes? Darren *: This is why I often use full names in C++, such as std::cout, instead of "using namespace std;" -- Darren Cook, Software Developer/Researcher http://dcook.org/mlsn/ (English-Japanese-German-Chinese-Arabic open source dictionary/semantic network) http://dcook.org/work/ (About me and my work) http://dcook.org/work/charts/ (My flash charting demos) -- PHP Unicode & I18N Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
