Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:26354
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: error (pb1.pair.com: domain php.net from 81.169.182.136 cause and error)
Date: Sun, 5 Nov 2006 18:57:19 +0100
Reply-To: Marcus Boerger <helly@php.net>
Message-ID: <745591637.20061105185719@marcus-boerger.de>
To: Lester Caine <lester@lsces.co.uk>
Cc: internals@lists.php.net
In-Reply-To: <454E1AE2.1050106@lsces.co.uk>
References: <005e01c6ff82$e6092c30$ec01010a@intranet.db> <2FAA3BA3-283C-445D-9648-70C207FF2251@prohost.org> <454CBD65.5040205@cschneid.com> <B990B08B-20E3-41FD-BA54-A8F78443B572@prohost.org> <454D66C4.2090708@cschneid.com> <1465A1B3-C0AE-48E0-9E3A-66BDC57D89F3@prohost.org> <454E1AE2.1050106@lsces.co.uk>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] New Datetime class problem
From: helly@php.net (Marcus Boerger)

Hello Lester,

  we have the same problem for functions since years, why is there suddenly
such a big problem with classes now? All new php/pecl classes will follow
one of the following rules:
- Prefix with the extension name
- Postfix with "Iterator"
- Postfix with "Exception"
that seems the same amount of protection as prefix functions with extension
name plus underscore. I don't see any problem since the above rule is in
place.

best regards
marcus

Sunday, November 5, 2006, 6:09:54 PM, you wrote:

> ( This should have been to the pigging list !!!! sorry Ilia )

> Ilia Alshanetsky wrote:

>>>> You can use old PHP too, or modify the source code, it is "open 
>>>> source" after-all.
>>>
>>> Come on, that can't be the solution. Think about hosting companies for 
>>> example.
>> 
>> They as a rule use old versions, in fact I bet you'd be hard pressed to 
>> find a big or even a medium size hosting company offering PHP 5.2 just 
>> now. So you have plenty of time to fix your code.

> The main problem here Ilia is that people HAVE to fix their code JUST IN
> CASE the host updates. Some people will not even know they have a
> problem because they are using a third party application and then they
> will not know how to fix it IF their host updates.

> Since it would seem that most hosts have not even switched to PHP5
> anyway, this is probably all academic anyway, but we have been here
> before, with versions of PHP released that broke a large number of
> applications and it got to the state that host WOULD NOT update in case
> it broke something.

> DateTime is just another example of the fact that PHP has no management
> of conventions and these get changed version to version. We NEED a
> mechanism to pinch back common function names that does not break
> existing applications simply because the vast number of users have no
> knowledge that there is a problem!

> -- 
> Lester Caine - G8HFL
> -----------------------------
> L.S.Caine Electronic Services - http://home.lsces.co.uk
> Model Engineers Digital Workshop -
> http://home.lsces.co.uk/ModelEngineersDigitalWorkshop/
> Treasurer - Firebird Foundation Inc. - http://www.firebirdsql.org/index.php




Best regards,
 Marcus