Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:20361 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 16657 invoked by uid 1010); 25 Nov 2005 10:47:02 -0000 Delivered-To: ezmlm-scan-internals@lists.php.net Delivered-To: ezmlm-internals@lists.php.net Received: (qmail 16641 invoked from network); 25 Nov 2005 10:47:02 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 25 Nov 2005 10:47:02 -0000 X-Host-Fingerprint: 195.227.108.51 wfserver02.wf-ppr.de Windows 2000 SP2+, XP SP1 (seldom 98 4.10.2222) Received: from ([195.227.108.51:54629] helo=wfserver02.wf-ppr.de) by pb1.pair.com (ecelerity 2.0 beta r(6323M)) with SMTP id F7/A5-56276-5ABE6834 for ; Fri, 25 Nov 2005 05:47:02 -0500 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable X-MimeOLE: Produced By Microsoft Exchange V6.5.6944.0 Date: Fri, 25 Nov 2005 11:46:57 +0100 Message-ID: <00A2E2156BEE8446A81C8881AE117F192C1CFD@companyweb> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: [PHP-DEV] Re: PHP 5.1 (Or How to break tousands of apps out there) Thread-Index: AcXxq8R39hySBHzVTl6L+rdXAu0yCQAABhkw To: "PHP Developers Mailing List" Subject: AW: [PHP-DEV] Re: PHP 5.1 (Or How to break tousands of apps out there) From: mp@webfactory.de ("Matthias Pigulla") > Or > a) am I missing something > b) is it the core developers' opinion that core classes have=20 > the right of way? If things behave like that at least there should be a list of "reserved class names" just like with other keywords. And of course that list must not be changed as it is considered practical. I don't think PEAR has done anything wrong here; it was never disallowed to have a class named Date. And it's not only a PEAR problem but affects pretty much everyone out there with more than a few hundred lines of OO code. If it was a failure of QA, clearly one of the "language core" QA itself. Maybe namespaces are a solution, but until there is a good solution for the basic problem, stop adding classes to the core that way. Often it's hard enough to find short yet precise class names; and there is also a set of commonly used or agreed-on class names (just think of the common patterns). In no case anything done in the core must inflict with or otherwise touch that set - or forget about that "enterprise ready" stuff altogether. -mp.