Hi Derick,
This patch breaks PEAR::Date (because it reserves class "Date") and all
applications those use it.
Was this break discussed?
Do we really like it in 5.2?
Thanks. Dmitry.
> -Original Message-
> From: Derick Rethans [mailto:[EMAIL PROTECTED]
> Sent: Tuesday, July 18, 2006 4:38
I think we need to rename it. php_date or _date or something. I don't
really care what the name is, but I think we are too late in the game to
get the 'date' identifier. The other functions enabled are fine and
quite necessary actually. Both timezone_abbreviations_list() and
timezone_identi
Didn't we actually have a Date class for five days in a release once and not
a single bug report out of it?
I think we need to rename it. php_date or _date or something. I don't
really care what the name is, but I think we are too late in the game to
get the 'date' identifier. The other fu
On Tue, 18 Jul 2006 07:23:41 -0700
[EMAIL PROTECTED] (Rasmus Lerdorf) wrote:
> I think we need to rename it. php_date or _date or something. I
> don't really care what the name is, but I think we are too late in
> the game to get the 'date' identifier. The other functions enabled
> are fine and
On 18.07.2006 17:23, Rasmus Lerdorf wrote:
I think we need to rename it. php_date or _date or something. I don't
really care what the name is, but I think we are too late in the game to
get the 'date' identifier. The other functions enabled are fine and
quite necessary actually. Both timezo
Rasmus Lerdorf wrote:
I think we need to rename it. php_date or _date or something. I don't
really care what the name is, but I think we are too late in the game to
get the 'date' identifier. The other functions enabled are fine and
quite necessary actually. Both timezone_abbreviations_list
Lukas Smith wrote:
Rasmus Lerdorf wrote:
I think we need to rename it. php_date or _date or something. I
don't really care what the name is, but I think we are too late in the
game to get the 'date' identifier. The other functions enabled are
fine and quite necessary actually. Both timezon
On Tue, 18 Jul 2006, Rasmus Lerdorf wrote:
> I think we need to rename it. php_date or _date or something. I don't really
> care what the name is, but I think we are too late in the game to get the
> 'date' identifier.
I think this might be one of the bigger mistakes that we can do now. And
I
Lukas,
Ideally all libraries, be it PEAR or otherwise should always prefix
their class and function names, the one obvious prefix would be the
name of the library itself. For example when it comes to PEAR having
a pear_ (for functions) and PEAR (for classes) prefix would be perfect.
When
Hello,
On 7/18/06, Derick Rethans <[EMAIL PROTECTED]> wrote:
On Tue, 18 Jul 2006, Rasmus Lerdorf wrote:
This might also be something that might pop up more in the future so I
think we should figure that out first what we want,
What we should figure out is how to prevent you to pop in with y
No kidding, Derick. Go back and read all those discussions. If we want
to enable the ext/date classes, they need to be prefixed.
-Andrei
On Jul 18, 2006, at 7:16 AM, Dmitry Stogov wrote:
Hi Derick,
This patch breaks PEAR::Date (because it reserves class "Date") and all
applications those us
Steph, we discussed it to death already. Please be realistic.
-Andrei
On Jul 18, 2006, at 10:25 AM, Steph Fox wrote:
No kidding, Derick. Go back and read all those discussions. If we
want to enable the ext/date classes, they need to be prefixed.
Go back and read Ilia's blog entry on the sub
Steph, we discussed it to death already. Please be realistic.
'Discussed to death', I'd say. There wasn't a decision made, either way, and
I for one don't see why PEAR should dictate terms to PHP.
- Steph
-Andrei
On Jul 18, 2006, at 10:25 AM, Steph Fox wrote:
No kidding, Derick. Go back a
No kidding, Derick. Go back and read all those discussions. If we want to
enable the ext/date classes, they need to be prefixed.
Go back and read Ilia's blog entry on the subject. There were NO bug reports
about it, in the 5 days the Date class was 'out there'. Does that sound to
you like gaz
Hello Pierre,
please just hold breath and keep that *** for yourself.
best regards
marcus
Tuesday, July 18, 2006, 6:17:09 PM, you wrote:
> Hello,
> On 7/18/06, Derick Rethans <[EMAIL PROTECTED]> wrote:
>> On Tue, 18 Jul 2006, Rasmus Lerdorf wrote:
>> This might also be something that might p
Hello Dmitry,
well PEAR broke it's own rules here and somehow i feel PEAR needs to be
punished because PEAR never respected any PHP decision at all. Well you
might see that i am not a fan of PEAR. Actually i only use the minimum set
that allows me to run horde. Anyway the stone already fell into
I know I only lurk here usually, and this may be a daft idea but if I
don't throw it in the water I'll never know if it can float.
Why not allow classes and functions be overridden? For example, if I
define a function named mysql_query it replaces the existing function
and raises an E_STRICT error
Hello Lukas,
in a dreamworld everyone would prefix all obvious/easy names as they
are by their nature likely to cause clashes.
[Marcus falling a sleep and hitting the send key]
best regards
marcus
Tuesday, July 18, 2006, 4:31:11 PM, you wrote:
> Rasmus Lerdorf wrote:
>> I think we need to ren
18 matches
Mail list logo
