Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:23646 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 87605 invoked by uid 1010); 25 May 2006 11:47:28 -0000 Delivered-To: ezmlm-scan-internals@lists.php.net Delivered-To: ezmlm-internals@lists.php.net Received: (qmail 87590 invoked from network); 25 May 2006 11:47:27 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 25 May 2006 11:47:27 -0000 X-Host-Fingerprint: 217.162.171.242 217-162-171-242.dclient.hispeed.ch Received: from ([217.162.171.242:22759] helo=localhost.localdomain) by pb1.pair.com (ecelerity 2.0 beta r(6323M)) with SMTP id B9/57-17316-F4995744 for ; Thu, 25 May 2006 07:47:27 -0400 Message-ID: To: internals@lists.php.net Date: Thu, 25 May 2006 13:47:24 +0200 User-Agent: Thunderbird 1.5.0.2 (Macintosh/20060308) MIME-Version: 1.0 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: <454303585.20060524213714@marcus-boerger.de> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Posted-By: 217.162.171.242 Subject: Re: [PHP-DEV] fatal static call in php 6.0? From: cschneid@cschneid.com (Christian Schneider) 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