Re: solution to the "Date" issue
| From: | Stefan Walk | Date: | Sat, 26 Nov 2005 08:21:07 +0000 |
| Subject: | Re: solution to the "Date" issue | ||
| References: | 1 2 3 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-20503@lists.php.net to get a copy of this message | ||
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.
Regards,
Stefan