Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:23583 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 9012 invoked by uid 1010); 19 May 2006 16:49:37 -0000 Delivered-To: ezmlm-scan-internals@lists.php.net Delivered-To: ezmlm-internals@lists.php.net Received: (qmail 8997 invoked from network); 19 May 2006 16:49:37 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 19 May 2006 16:49:37 -0000 X-PHP-List-Original-Sender: steph@zend.com X-Host-Fingerprint: 192.38.9.232 gw2.emini.dk Linux 2.4/2.6 Received: from ([192.38.9.232:2321] helo=gw2.emini.dk) by pb1.pair.com (ecelerity 2.0 beta r(6323M)) with SMTP id 2A/05-19568-F17FD644 for ; Fri, 19 May 2006 12:49:35 -0400 Received: from foxbox (unknown [84.228.79.24]) by gw2.emini.dk (Postfix) with ESMTP id E85EDB2842; Fri, 19 May 2006 18:49:29 +0200 (CEST) Message-ID: <09fc01c67b63$cc334a50$6602a8c0@foxbox> Reply-To: "Steph Fox" To: "Ilia Alshanetsky" Cc: "Brian Moon" , "PHP Internals List" References: <947BC60F-8D8C-46F9-822C-DCA6B3C900EB@prohost.org> <446DDD97.6080407@dealnews.com> <000F9763-40EE-4B33-B7BC-C9B8A704CC23@prohost.org> <097601c67b5e$b938d690$6602a8c0@foxbox> Date: Fri, 19 May 2006 18:46:35 +0200 MIME-Version: 1.0 Content-Type: text/plain; format=flowed; charset="Windows-1252"; reply-type=response Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2900.2180 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180 Subject: Re: [PHP-DEV] Flamewar Summary Conclusion From: steph@zend.com ("Steph Fox") Cool. I just had a horrible vision of hundreds of reports of 'strange crashes' :) > When E_RECOVERABLE_ERROR is triggers and not handled, it gets translated > to an E_ERROR "Catchable fatal error...". > > > On 19-May-06, at 12:10 PM, Steph Fox wrote: > >> Back to my original (off-list) question - what happens if people don't >> have E_RECOVERABLE_ERROR level error reporting switched on? Does it >> fall back to E_ERROR or does the code fail silently? >> >>> I'll add a note about it to the 5.2 README file. >>> >>> >>> On 19-May-06, at 11:00 AM, Brian Moon wrote: >>> >>>> Ilia Alshanetsky wrote: >>>>> So the only affect is that value numeric value of E_ALL is greater >>>>> then it was before. Marcus has already applied patch to this affect >>>>> a few days ago (Thanks!). >>>> >>>> This needs to be made obvious in the release notes or something. >>>> Users that set their error level in apache will use a numeric value >>>> and not the constants. That is the only way to change the value for >>>> an entire virthost. >>>> >>>> -- >>>> >>>> Brian Moon >>>> ------------- >>>> http://dealnews.com/ >>>> Its good to be cheap =) >>>> >>>> -- >>>> PHP Internals - PHP Runtime Development Mailing List >>>> To unsubscribe, visit: http://www.php.net/unsub.php >> >> > > Ilia Alshanetsky > Advanced Internet Designs Inc. > ilia@prohost.org > > >