It seems to me that the only usable method of "ring fencing" core
classes for the long term is to use namespaces. However, the namespaces
feature is a fairly large one and obviously will not be in 5.1. We can
discuss its inclusion in 5.2, should it happen to come out, or in PHP
6, but we need
On 11/26/05, Jani Taskinen <[EMAIL PROTECTED]> wrote:
>
> So you're also for letting PEAR dictate what PHP has and not the other
> way around? Somehow this doesn't sound right.
This is not about PEAR dictating, and the PEAR developers are not
those who would suffer from this PHP date cla
On Sat, 26 Nov 2005 15:07:15 +0200 (EET)
[EMAIL PROTECTED] (Jani Taskinen) wrote:
> On Sat, 26 Nov 2005, Pierre Joye wrote:
>
> > This ext/date problem is something I will hate to see happen again.
>
> Well, it's totally your own fault. I remember the couple of times
> you were asked t
On Sat, 26 Nov 2005, Pierre Joye wrote:
This ext/date problem is something I will hate to see happen again.
Well, it's totally your own fault. I remember the couple of times
you were asked to commit your stuff but you had some other things
to do. Now that someone did the work, you
On 11/26/05, Jani Taskinen <[EMAIL PROTECTED]> wrote:
>
> So you're also for letting PEAR dictate what PHP has and not the other
> way around? Somehow this doesn't sound right.
No, I do not let Derick decided on his own what should be commited in
a last RC. I do not let Derick decides wh
So you're also for letting PEAR dictate what PHP has and not the other
way around? Somehow this doesn't sound right.
--Jani
On Fri, 25 Nov 2005, Andrei Zmievski wrote:
I have to ask: what does renaming really buy us? The only purpose of
introducing this class in RC6, as far as I
Rasmus Lerdorf wrote:
Ilia Alshanetsky wrote:
The attached patch is a possible solution to the date *crisis*, it
renames the class to PhpDate to avoid any namespace conflicts with pear
or custom user classes called date.
If there are no strong objection 5.1.1 (5.1.0 + this patch and nothing
e
Ilia Alshanetsky wrote:
The attached patch is a possible solution to the date *crisis*, it
renames the class to PhpDate to avoid any namespace conflicts with pear
or custom user classes called date.
If there are no strong objection 5.1.1 (5.1.0 + this patch and nothing
else) goes out on Monday.
I object your honor!
This will set the stage for any other core objects to follow the same
convention. If namespaces are in PHPs future, design wise it would make more
sense to have them in a namespace ("PHP" seems to be popular), but if this
is released now as PhpDate, moving it to a namespace wo
I have to ask: what does renaming really buy us? The only purpose of
introducing this class in RC6, as far as I can tell, was to reserve the
'Date' name for future use. Since this goal is clearly unachievable,
what is the point of keeping a barely functional class around (as
PhpDate)? In my op
10 matches
Mail list logo
