Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:20503 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 81239 invoked by uid 1010); 26 Nov 2005 08:21:11 -0000 Delivered-To: ezmlm-scan-internals@lists.php.net Delivered-To: ezmlm-internals@lists.php.net Received: (qmail 81224 invoked from network); 26 Nov 2005 08:21:11 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 26 Nov 2005 08:21:11 -0000 X-Host-Fingerprint: 64.233.182.205 nproxy.gmail.com Linux 2.4/2.6 Received: from ([64.233.182.205:14177] helo=nproxy.gmail.com) by pb1.pair.com (ecelerity 2.0 beta r(6323M)) with SMTP id CB/3D-56276-6FA18834 for ; Sat, 26 Nov 2005 03:21:10 -0500 Received: by nproxy.gmail.com with SMTP id a4so374078nfc for ; Sat, 26 Nov 2005 00:21:07 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=iCngI+3/ndhfAC6FIaIHNwxSb1JaTJEd6XszgMgrQIQwvUy/7MRzYbgJnn8Zif6tVFuHeA3lgTUbYNSUrgddoRsB0kmg0WQSJzg0pRg55LV0s1jEYB4epNR4ZsaeQrxxdlCxgkRts2f0o0tH+G1NIeJEqled+r6o/147rNcO/PY= Received: by 10.48.221.5 with SMTP id t5mr270890nfg; Sat, 26 Nov 2005 00:21:07 -0800 (PST) Received: by 10.48.108.6 with HTTP; Sat, 26 Nov 2005 00:21:07 -0800 (PST) Message-ID: <4858f9d90511260021t5345b654m@mail.gmail.com> Date: Sat, 26 Nov 2005 09:21:07 +0100 To: Robert Cummings Cc: kennyt@php.net, Greg Beaver , internals@lists.php.net In-Reply-To: <1132966917.30011.6.camel@blobule.suds> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline References: <4387B552.8000806@php.net> <1132966917.30011.6.camel@blobule.suds> Subject: Re: [PHP-DEV] solution to the "Date" issue From: stefan.walk@gmail.com (Stefan Walk) 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... tha= t > > language... that has multiple implementations of the standard classes. > > It can't hurt to play to people's comfort when the change doesn't reall= y > > 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. Regards, Stefan