Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:23363 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 779 invoked by uid 1010); 15 May 2006 10:51:28 -0000 Delivered-To: ezmlm-scan-internals@lists.php.net Delivered-To: ezmlm-internals@lists.php.net Received: (qmail 764 invoked from network); 15 May 2006 10:51:28 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 15 May 2006 10:51:28 -0000 X-PHP-List-Original-Sender: cellog@php.net X-Host-Fingerprint: 66.79.163.178 bluga.net Linux 2.5 (sometimes 2.4) (4) Received: from ([66.79.163.178:48223] helo=mail.bluga.net) by pb1.pair.com (ecelerity 2.0 beta r(6323M)) with SMTP id 55/32-19568-03D58644 for ; Mon, 15 May 2006 06:51:28 -0400 Received: from mail.bluga.net (mail.bluga.net [127.0.0.1]) by mail.bluga.net (Postfix) with ESMTP id 532012836D; Mon, 15 May 2006 03:57:36 -0700 (PDT) Received: from [211.48.66.248] (unknown [211.48.66.248]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.bluga.net (Postfix) with ESMTP id 212C128363; Mon, 15 May 2006 03:57:34 -0700 (PDT) Message-ID: <44685D24.2000801@php.net> Date: Mon, 15 May 2006 06:51:16 -0400 User-Agent: Mozilla Thunderbird 1.0.6 (Windows/20050716) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Steph Fox Cc: Marcus Boerger , Pierre-Alain Joye , internals@lists.php.net References: <138663365.20060514205903@marcus-boerger.de> <038d01c676f8$ab9b3380$6602a8c0@foxbox> In-Reply-To: <038d01c676f8$ab9b3380$6602a8c0@foxbox> Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit X-Virus-Scanned: ClamAV using ClamSMTP Subject: Re: [PHP-DEV] E_ALL changes in 5.2/6.0 From: cellog@php.net (Greg Beaver) Steph Fox wrote: > Marcus, > > FWIW I'm with you (unusually) over E_STRICT. Why would anyone have E_ALL > switched on anywhere but a dev box? - and when there is the option to > switch on E_ALL without E_STRICT, it makes it much easier to miss > useful information about the direction PHP is going in. > > Pierre: the biggest E_STRICT issues I'm aware of are the 'vars don't > live here any more' one (which was removed two months ago in PHP_5_1 > branch) and the 'only variables can be passed by reference' one (which > is in PHP 4.4.* anyway). Beyond those two, it ought to be pretty rare Side note: calling functions statically that do not have a static modifier causes E_STRICT. Hello PEAR::isError() This is of course going to be a fatal in PHP 6, but it is now the most common E_STRICT I see in PHP4-based code. I agree that it is appropriate to change something like this in a 5.X.0, but it will be a headache for anyone running legacy apps (not just PEAR). Until someone writes some killer apps in PHP5 to replace phpBB and company, changes of this nature will simply prevent moving to PHP5 but that's another story and not the concern of internals (I agree with this strongly). If you all are willing to deal with the fallout (think PHP 4.4) then that's that. Greg