Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:20519 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 80214 invoked by uid 1010); 26 Nov 2005 12:29:25 -0000 Delivered-To: ezmlm-scan-internals@lists.php.net Delivered-To: ezmlm-internals@lists.php.net Received: (qmail 80198 invoked from network); 26 Nov 2005 12:29:25 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 26 Nov 2005 12:29:25 -0000 X-Host-Fingerprint: 81.169.182.136 ajaxatwork.net Linux 2.4/2.6 Received: from ([81.169.182.136:51514] helo=strato.aixcept.de) by pb1.pair.com (ecelerity 2.0 beta r(6323M)) with SMTP id 2F/D8-56276-52558834 for ; Sat, 26 Nov 2005 07:29:25 -0500 Received: from [192.168.1.3] (dslb-084-063-047-015.pools.arcor-ip.net [84.63.47.15]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (No client certificate requested) by strato.aixcept.de (Postfix) with ESMTP id 63625610282; Sat, 26 Nov 2005 13:35:38 +0100 (CET) Date: Sat, 26 Nov 2005 13:27:26 +0100 Reply-To: Marcus Boerger X-Priority: 3 (Normal) Message-ID: <6110167365.20051126132726@marcus-boerger.de> To: Stefan Walk Cc: Robert Cummings , kennyt@php.net, Greg Beaver , In-Reply-To: <4858f9d90511260021t5345b654m@mail.gmail.com> References: <4387B552.8000806@php.net> <1132966917.30011.6.camel@blobule.suds> <4858f9d90511260021t5345b654m@mail.gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Subject: Re: [PHP-DEV] solution to the "Date" issue From: helly@php.net (Marcus Boerger) Hello Stefan, Saturday, November 26, 2005, 9:21:07 AM, you wrote: > On 26/11/05, Robert Cummings 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