Re: solution to the "Date" issue

Hello Stefan, Saturday, November 26, 2005, 9:21:07 AM, you wrote: > On 26/11/05, Robert Cummings <robert@interjinn.com> wrote: >> On Fri, 2005-11-25 at 20:07, Ken Tossell wrote: >> > Not to start a flame war, but... >> > >> > How about STD, Std, or something similar? It certainly works for... that >> > language... that has multiple implementations of the standard classes. >> > It can't hurt to play to people's comfort when the change doesn't >> > really >> > affect PHP in any major way. :) >> > >> > But yes, a standard class prefix (to be migrated to a namespace) sounds >> > more practical than either asking everyone to use prefixes or hoping >> > that the minimal user base is affected by a conflict. >> > >> > And getting everyone into a habit of importing standard php classes -- >> > >> > class Date extends PHP_Date {} >> >> Maybe go with proper CamelCase: >> >> class Date extends PhpDate{} >> >> :) > This violates the coding standards for class names. Words have to be > separated by underscores. Mhhh noone updated the coding standards once we changed then before 5 was released. Right now only the __PHP_Incomplete_Class and php_user_filter plus ext MysqlI is ignoring them. The former could not be changed since there is valid code out and MysqlI not adhering to the standards caused an endless discussion...: marcus@zaphod /usr/src/php-cvs $ php -r 'print_r(get_declared_classes());'|grep _ [8] => __PHP_Incomplete_Class [9] => php_user_filter [72] => mysqli_sql_exception [73] => mysqli_driver [75] => mysqli_warning [76] => mysqli_result [77] => mysqli_stmt > -- > PHP Internals - PHP Runtime Development Mailing List > To unsubscribe, visit: http://www.php.net/unsub.php Best regards, Marcus