Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:20471
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
To: kennyt@php.net
Cc: Greg Beaver <cellog@php.net>, internals@lists.php.net
In-Reply-To: <4387B552.8000806@php.net>
References: <CD.1E.56276.21DA7834@pb1.pair.com>  <4387B552.8000806@php.net>
Content-Type: text/plain
Organization: InterJinn
Message-ID: <1132966917.30011.6.camel@blobule.suds>
Mime-Version: 1.0
Date: Fri, 25 Nov 2005 20:01:57 -0500
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] solution to the "Date" issue
From: robert@interjinn.com (Robert Cummings)

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{}

:)

Cheers,
Rob.
-- 
.------------------------------------------------------------.
| InterJinn Application Framework - http://www.interjinn.com |
:------------------------------------------------------------:
| An application and templating framework for PHP. Boasting  |
| a powerful, scalable system for accessing system services  |
| such as forms, properties, sessions, and caches. InterJinn |
| also provides an extremely flexible architecture for       |
| creating re-usable components quickly and easily.          |
`------------------------------------------------------------'