Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:26374 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 89115 invoked by uid 1010); 6 Nov 2006 07:14:04 -0000 Delivered-To: ezmlm-scan-internals@lists.php.net Delivered-To: ezmlm-internals@lists.php.net Received: (qmail 89099 invoked from network); 6 Nov 2006 07:14:04 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 6 Nov 2006 07:14:04 -0000 Authentication-Results: pb1.pair.com smtp.mail=lester@lsces.co.uk; spf=permerror; sender-id=unknown Authentication-Results: pb1.pair.com header.from=lester@lsces.co.uk; sender-id=unknown Received-SPF: error (pb1.pair.com: domain lsces.co.uk from 194.73.73.220 cause and error) X-PHP-List-Original-Sender: lester@lsces.co.uk X-Host-Fingerprint: 194.73.73.220 c2bthomr05.btconnect.com FreeBSD 4.7-5.2 (or MacOS X 10.2-10.3) (2) Received: from [194.73.73.220] ([194.73.73.220:11831] helo=C2bthomr05.btconnect.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 64/71-13078-3B0EE454 for ; Mon, 06 Nov 2006 02:13:59 -0500 Received: from [127.0.0.1] (host81-138-11-136.in-addr.btopenworld.com [81.138.11.136]) by C2bthomr05.btconnect.com (MOS 3.7.4b-GA) with ESMTP id FGM67354; Mon, 6 Nov 2006 07:08:27 GMT Message-ID: <454EE0BB.20606@lsces.co.uk> Date: Mon, 06 Nov 2006 07:14:03 +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> <454E23DA.8000705@cschneid.com> <63EDBC2B-D89A-41EE-B4AD-CDDB28A50AB4@prohost.org> <454E7433.3030303@lsces.co.uk> <7B3EDDC6-69C8-4E2E-892A-F776AA9C04F6@prohost.org> In-Reply-To: <7B3EDDC6-69C8-4E2E-892A-F776AA9C04F6@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) Ilia Alshanetsky wrote: > > On 5-Nov-06, at 6:30 PM, Lester Caine wrote: > >> Ilia Alshanetsky wrote: >> >>> The language always has the best pick of namespaces, this is not just >>> PHP, but ANY language. The fact we've made a compromise and allows >>> PEAR to retain the date class IMO has been a horrible mistake, one >>> hopefully not to be repeated in the future. >> >> I never used the PEAR Date - it was crap - but all my applications >> failed with your new one BECAUSE Date was the obvious name for that >> package. I STILL can not see why we can't just select these things as >> I do in C++ and include your new function if I want or keep with my >> own established version - what ever the name. This new stuff does not >> HAVE to be hard coded into the core - simply loadable like any other >> good extensible language? If we don't want it we don't load it! I >> don't need any database stuff other than Firebird - therefore I want a >> DATE and TIME package that follows Firebird rules end of story. > > You seem to be under the assumption that people care about what it is > that you want, reality is that most people could care less. That said > this is an open source project, so rather then pointless whining on the > list you can always tweak the source code to your needs, such is the > beauty of the open source software. Then perhaps it is about time that we cut a version of PHP that does what users want rather than a few developers :) The whole point here is that ISP's install this stuff so we have to work with the version that ISP's install. We have had a number of major crap-up's caused by making non-compatible changes and most of the time all that was needed was a simple switch to enable that new code *IF* it was needed. *YOU* should care that people want to use PHP or perhaps you are more of a mind to take the Microsoft attitude - sod the 'cuctomers' we will do what we want! But then Microsoft are now getting involved so perhaps that's to be expected ;) Personally I'm more than happy with PHP 5.0.4 and that is what is in MY customer sites, but other suppliers are upgrading when THEY want to, and so I then have to go round and make sure all MY code still works. *I* was lead to believe that the next BC break would come with PHP6 - but then you can't trust people no to change the rules when they feel like it :( -- 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