On Sat, 26 Nov 2005, Greg Beaver wrote:
> Taking the class out of PHP 5 will solve the problem for now (and I
> absolutely agree that this is necessary - so does *everyone* else save
> Derick, who is now on vacation and can't defend himself), but any time
> in the future it is introduced as "Date"
On Sat, 26 Nov 2005 14:37:39 -0600
[EMAIL PROTECTED] (Greg Beaver) wrote:
> Taking the class out of PHP 5 will solve the problem for now (and I
> absolutely agree that this is necessary - so does *everyone* else save
> Derick, who is now on vacation and can't defend himself), but any time
> in the
Pierre wrote:
> On Sat, 26 Nov 2005 00:50:04 -0600
> [EMAIL PROTECTED] (Greg Beaver) wrote:
>
>
>
>>Pierre, you can do all the #ifdefs you want, this idea does not
>>prevent this :). In addition, the #ifdef has no effect on this idea.
>
>
>
> You do not get the main problem.
>
> - The ifdef
On Sat, 26 Nov 2005 00:50:04 -0600
[EMAIL PROTECTED] (Greg Beaver) wrote:
> Pierre, you can do all the #ifdefs you want, this idea does not
> prevent this :). In addition, the #ifdef has no effect on this idea.
You do not get the main problem.
- The ifdef makes it disappear from a user point
Pierre wrote:
> On Fri, 25 Nov 2005 18:32:14 -0600
> [EMAIL PROTECTED] (Greg Beaver) wrote:
>
>
>>Hi,
>>
>>I would like to propose these simple steps be taken:
>>
>>1) rename "date" to "PHP_Date"
>>2) reserve the "PHP_" prefix for all future core classes in PHP 5 (if
>>any) 3) when namespaces bec
On Fri, 25 Nov 2005 18:32:14 -0600
[EMAIL PROTECTED] (Greg Beaver) wrote:
> Hi,
>
> I would like to propose these simple steps be taken:
>
> 1) rename "date" to "PHP_Date"
> 2) reserve the "PHP_" prefix for all future core classes in PHP 5 (if
> any) 3) when namespaces become available, reserve
