Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:44360 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 26560 invoked from network); 18 Jun 2009 16:36:08 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 18 Jun 2009 16:36:08 -0000 Authentication-Results: pb1.pair.com header.from=jani.taskinen@sci.fi; sender-id=unknown Authentication-Results: pb1.pair.com smtp.mail=jani.taskinen@sci.fi; spf=permerror; sender-id=unknown Received-SPF: error (pb1.pair.com: domain sci.fi from 204.13.248.71 cause and error) X-PHP-List-Original-Sender: jani.taskinen@sci.fi X-Host-Fingerprint: 204.13.248.71 mho-01-ewr.mailhop.org Received: from [204.13.248.71] ([204.13.248.71:51179] helo=mho-01-ewr.mailhop.org) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 54/5B-08167-4FC6A3A4 for ; Thu, 18 Jun 2009 12:36:06 -0400 Received: from cs181029147.pp.htv.fi ([82.181.29.147] helo=[127.0.0.1]) by mho-01-ewr.mailhop.org with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.68) (envelope-from ) id 1MHKan-000JTK-H6; Thu, 18 Jun 2009 16:36:01 +0000 X-Mail-Handler: MailHop Outbound by DynDNS X-Originating-IP: 82.181.29.147 X-Report-Abuse-To: abuse@dyndns.com (see http://www.dyndns.com/services/mailhop/outbound_abuse.html for abuse reporting information) X-MHO-User: U2FsdGVkX18OIV5MF7ixGje5SF12MpUeIO+yEO59sSc= Message-ID: <4A3A6CEE.30407@sci.fi> Date: Thu, 18 Jun 2009 19:35:58 +0300 Reply-To: jani.taskinen@iki.fi User-Agent: Thunderbird 2.0.0.21 (Windows/20090302) MIME-Version: 1.0 To: jvlad CC: internals@lists.php.net References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: [PHP-DEV] bug #48583 or display_errors saga From: jani.taskinen@sci.fi (Jani Taskinen) jvlad kirjoitti: > If the bug #48583 can't be accepted through bugs.php.net, I think it makes > sense to discuss it here. It's not a bug but "chicken'n'egg'" issue. Errors are displayed by default (IIRC) so if the ini file does not get parsed an error is outputted which IS really good thing. Just fix that damn ini file. :) --Jani