Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:23687 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 70199 invoked by uid 1010); 26 May 2006 06:38:38 -0000 Delivered-To: ezmlm-scan-internals@lists.php.net Delivered-To: ezmlm-internals@lists.php.net Received: (qmail 70183 invoked from network); 26 May 2006 06:38:38 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 26 May 2006 06:38:38 -0000 X-PHP-List-Original-Sender: derick@php.net X-Host-Fingerprint: 82.94.239.5 jdi.jdi-ict.nl Linux 2.5 (sometimes 2.4) (4) Received: from ([82.94.239.5:36313] helo=jdi.jdi-ict.nl) by pb1.pair.com (ecelerity 2.0 beta r(6323M)) with SMTP id 71/BF-17316-C62A6744 for ; Fri, 26 May 2006 02:38:36 -0400 Received: from localhost (localhost [127.0.0.1]) by jdi.jdi-ict.nl (8.13.6/8.12.11) with ESMTP id k4Q6cUt0019408; Fri, 26 May 2006 08:38:31 +0200 Date: Fri, 26 May 2006 08:38:21 +0200 (CEST) X-X-Sender: derick@localhost To: Marcus Boerger cc: Todd Ruth , Andi Gutmans , Edin Kadribasic , PHP Developers Mailing List In-Reply-To: <454303585.20060524213714@marcus-boerger.de> Message-ID: 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> X-Face: "L'&?Ah3MYF@FB4hU'XhNhLB]222(Lbr2Y@F:GE[OO;"F5p>qtFBl|yVVA&D{A(g3[C}mG:199P+5C'v.M/u@Z\![0b:Mv.[l6[uWl' MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Subject: Re: [PHP-DEV] fatal static call in php 6.0? From: derick@php.net (Derick Rethans) On Wed, 24 May 2006, Marcus Boerger wrote: > This situation is just like the one where we had to fix reference stuff > as we found out that it indeed was causing SEGVs in certain situations. > And i want to provide such situations and i want that at nearly all > costs because i do not want to have such a situation again. For one > reason it took me like a full week of work to help Derick with a tiny > piece in debugging and i don't know how much time Derick spend on > tracking the issue down and fixing it. In short i rather drop a feature > than risking SEGVs. A few weeks I would say :) > Now decide for your self what is more expensive/more dangerous for you? > An unstablel PHP or a tiny feature loss? > > Btw, right now you can have abstract static methods in interfaces. This > was a compromise I introduced when we found out the issue. Did I miss something here? I thought that a patch of yours made this a fatal error? Did you revert this? regards, Derick -- Derick Rethans http://derickrethans.nl | http://ez.no | http://xdebug.org