Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:26350 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 19886 invoked by uid 1010); 5 Nov 2006 17:09:50 -0000 Delivered-To: ezmlm-scan-internals@lists.php.net Delivered-To: ezmlm-internals@lists.php.net Received: (qmail 19871 invoked from network); 5 Nov 2006 17:09:50 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 5 Nov 2006 17:09:50 -0000 Authentication-Results: pb1.pair.com header.from=lester@lsces.co.uk; sender-id=unknown Authentication-Results: pb1.pair.com smtp.mail=lester@lsces.co.uk; spf=permerror; sender-id=unknown Received-SPF: error (pb1.pair.com: domain lsces.co.uk from 194.73.73.228 cause and error) X-PHP-List-Original-Sender: lester@lsces.co.uk X-Host-Fingerprint: 194.73.73.228 c2bthomr12.btconnect.com FreeBSD 4.7-5.2 (or MacOS X 10.2-10.3) (2) Received: from [194.73.73.228] ([194.73.73.228:23994] helo=c2bthomr12.btconnect.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 43/35-10980-BDA1E454 for ; Sun, 05 Nov 2006 12:09:48 -0500 Received: from [127.0.0.1] (host81-138-11-136.in-addr.btopenworld.com [81.138.11.136]) by c2bthomr12.btconnect.com (MOS 3.7.4b-GA) with ESMTP id BTY80176; Sun, 5 Nov 2006 17:04:20 GMT Message-ID: <454E1AE2.1050106@lsces.co.uk> Date: Sun, 05 Nov 2006 17:09:54 +0000 User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-GB; rv:1.8.0.7) Gecko/20060910 SeaMonkey/1.0.5 MIME-Version: 1.0 To: internals@lists.php.net References: <005e01c6ff82$e6092c30$ec01010a@intranet.db> <2FAA3BA3-283C-445D-9648-70C207FF2251@prohost.org> <454CBD65.5040205@cschneid.com> <454D66C4.2090708@cschneid.com> <1465A1B3-C0AE-48E0-9E3A-66BDC57D89F3@prohost.org> In-Reply-To: <1465A1B3-C0AE-48E0-9E3A-66BDC57D89F3@prohost.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: [PHP-DEV] New Datetime class problem From: lester@lsces.co.uk (Lester Caine) ( 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