I admit to being unclear on why DateFormatter conflicts with Date. I'll have to read the manuals later. Seems rather limiting if all names beginning with "Date" are now verboten. That said:
A) Derick, Shifu, Can you (or anyone) demonstrate the name conflict? I think it should have been caught by testing if it exists. I'd like to reproduce the problem. B) Name change proposals: 1) DatetimeFormatter 2) IntlDateFormatter 3) TheOtherDateFormatter ;-) 4) ICUDateFormatter If possible, I would like to confirm that there is a conflict problem or not today, and if there is agree on the name change today. tex -----Original Message----- From: Derick Rethans [mailto:[EMAIL PROTECTED] Sent: Friday, March 21, 2008 9:35 AM To: Stanislav Malyshev Cc: sf.chen; Tex Texin; [EMAIL PROTECTED]; 'Ed Batutis'; 'Hong,Weilin'; PHP Developers Mailing List Subject: [PHP-DEV] Re: [php-icu] Graphemes and unicode vs intl extension On Fri, 21 Mar 2008, Stanislav Malyshev wrote: > > You can't actually use the class name "DateFormatter" when you want > > pecl/intl to be in core. "Date" is the prefix for the already > > existing Date extension. > > I think we still can name it DateFormatter, especially if we plan (and > we do, as I understand) to merge DateFormatter functions with ext/date > in PHP 6, and we don't have any conflict now and we do not have any > plans to have DateFormatter in ext/date (correct me if I'm wrong here). You're wrong. We can rename it later *if* it gets merged into ext/date, but you can't simply use a classname with a prefix that conflicts with something else. Merging it would most likely change API anyway. > But if you have a better name for it - please propose it. Something that does not start with Date. regards, Derick -- Derick Rethans http://derickrethans.nl | http://ezcomponents.org | http://xdebug.org -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
