Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:16757 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 43194 invoked by uid 1010); 16 Jun 2005 17:39:16 -0000 Delivered-To: ezmlm-scan-internals@lists.php.net Delivered-To: ezmlm-internals@lists.php.net Received: (qmail 43179 invoked from network); 16 Jun 2005 17:39:16 -0000 Received: from unknown (HELO gmail.com) (127.0.0.1) by localhost with SMTP; 16 Jun 2005 17:39:16 -0000 X-Host-Fingerprint: 64.233.170.205 rproxy.gmail.com Linux 2.4/2.6 Received: from ([64.233.170.205:30394] helo=rproxy.gmail.com) by pb1.pair.com (ecelerity 1.2 r(5656M)) with SMTP id BD/71-20931-449B1B24 for ; Thu, 16 Jun 2005 13:39:16 -0400 Received: by rproxy.gmail.com with SMTP id c51so171230rne for ; Thu, 16 Jun 2005 10:39:14 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=qWCfaOqFZEl6jBmWqV53285iY4pD7fARhz50pVS4vwQzKrjG/9PURC62JJQXVb7bqumUpH0pH7dUDzJe00E77gqWE0n/ICNdyRAbWxx10bvPSbqJqJBXXyJMINdGMINPRMutf88+WvVkiEmOVjxbe/Wh1hIj+e25VuqKkAr8MSg= Received: by 10.38.181.14 with SMTP id d14mr679691rnf; Thu, 16 Jun 2005 10:39:14 -0700 (PDT) Received: by 10.38.65.11 with HTTP; Thu, 16 Jun 2005 10:39:14 -0700 (PDT) Message-ID: Date: Thu, 16 Jun 2005 13:39:14 -0400 Reply-To: Dan Scott To: Zeev Suraski Cc: boots , internals@lists.php.net In-Reply-To: <5.1.0.14.2.20050616195027.0366c130@localhost> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline References: <20050616163021.80366.qmail@web50807.mail.yahoo.com> <5.1.0.14.2.20050616195027.0366c130@localhost> Subject: Re: [PHP-DEV] In regards to E_STRICT and PHP5 From: denials@gmail.com (Dan Scott) On 6/16/05, Zeev Suraski wrote: > Why would you enable it then? You have to very explicitly enable it, as > it's off by default, and doesn't get enabled even if you switch to E_ALL. Well, that depends on your definition of "default"; php.ini-recommended in HEAD shows: ; - Show all errors, including coding standards warnings ; error_reporting =3D E_ALL | E_STRICT -- so the user who does 'cp php.ini-recommended /etc/php.ini' is, in fact, getting E_STRICT by default with the recommended configuration. Perhaps E_ALL should be the default in php.ini-recommended, with E_ALL | E_STRICT a documented (but commented) option. Dan