Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:23672 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 52898 invoked by uid 1010); 26 May 2006 00:54:27 -0000 Delivered-To: ezmlm-scan-internals@lists.php.net Delivered-To: ezmlm-internals@lists.php.net Received: (qmail 52882 invoked from network); 26 May 2006 00:54:27 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 26 May 2006 00:54:27 -0000 X-PHP-List-Original-Sender: alan@akbkhome.com X-Host-Fingerprint: 202.81.246.113 246-113.netfront.net Received: from ([202.81.246.113:49633] helo=akbkhome.com) by pb1.pair.com (ecelerity 2.0 beta r(6323M)) with SMTP id 35/81-17316-3C156744 for ; Thu, 25 May 2006 20:54:27 -0400 Received: from [192.168.0.184] by akbkhome.com with esmtp (Exim 4.62) (envelope-from ) id 1FjQjP-0004NX-Cm; Fri, 26 May 2006 09:03:12 +0800 Message-ID: <44765279.8000601@akbkhome.com> Date: Fri, 26 May 2006 08:57:29 +0800 User-Agent: Mozilla Thunderbird 0.8 (X11/20040926) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Christian Schneider CC: internals@lists.php.net References: <138663365.20060514205903@marcus-boerger.de> <038d01c676f8$ab9b3380$6602a8c0@foxbox> <44685D24.2000801@php.net> <1147708994.14148.23.camel@notebook.local> <16710545416.20060515202714@marcus-boerger.de> <1147721541.14148.47.camel@notebook.local> <4468DB43.1020005@emini.dk> <7.0.1.0.2.20060515194051.02b32ef8@zend.com> <1148496966.19173.79.camel@notebook.local> <454303585.20060524213714@marcus-boerger.de> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-ACL-Warn: "cleared badlog" Subject: planning future BC Breaks - was Re: [PHP-DEV] fatal static call in php 6.0? From: alan@akbkhome.com (Alan Knowles) Can we start concentrating on finding a real solution to BC breaks rather than throwing them out there and everyone complaining? define(php5) { stuff that breaks in php6 } define(php6) { stuff that doesnt work in PHP5 } It would be nice to back port this to PHP4, but at least make the future BC Breaks more bareable... Regards Alan Christian Schneider wrote: > One caveat with making a static call to a non-static function a fatal > error is that it will make use of static calls impossible for code > which wants to be PHP4 and PHP6 compatible, no? You probably don't > care but I still wanted to mention it. > > E_STRICT is nice for people who are able to move their code base to > pure PHP5 but not everybody can do that. Which means that converting > E_STRICT to E_FATAL should be done with care. But it's obviously up to > you guys to decide when the grace period is over... > > Oh, one thing which would help would be if certain E_STRICT errors > could be (optionally) reported at compile time to not have to depend > on code coverage tests. E.g. A::foo() could (optionally) report an > E_STRICT if class A with a non-static method foo is already defined > when encountering the call. Maybe the lint-mode could be used for that. > > PS: There are no plans to make non-static calls to static methods > illegal, right? > > - Chris >