Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:45156 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 47657 invoked from network); 30 Jul 2009 21:17:38 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 30 Jul 2009 21:17:38 -0000 Authentication-Results: pb1.pair.com smtp.mail=markus@fischer.name; spf=permerror; sender-id=unknown Authentication-Results: pb1.pair.com header.from=markus@fischer.name; sender-id=unknown Received-SPF: error (pb1.pair.com: domain fischer.name from 62.179.121.32 cause and error) X-PHP-List-Original-Sender: markus@fischer.name X-Host-Fingerprint: 62.179.121.32 viefep12-int.chello.at Solaris 10 (beta) Received: from [62.179.121.32] ([62.179.121.32:5517] helo=viefep12-int.chello.at) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 39/D0-43040-FED027A4 for ; Thu, 30 Jul 2009 17:17:36 -0400 Received: from edge02.upc.biz ([192.168.13.237]) by viefep12-int.chello.at (InterMail vM.7.09.01.00 201-2219-108-20080618) with ESMTP id <20090730211732.DRWC6129.viefep12-int.chello.at@edge02.upc.biz>; Thu, 30 Jul 2009 23:17:32 +0200 Received: from genuine.home ([213.47.135.119]) by edge02.upc.biz with edge id NMHW1c04q2ak1Bp02MHX6E; Thu, 30 Jul 2009 23:17:32 +0200 X-SourceIP: 213.47.135.119 Received: from vserv01.home ([192.168.1.20] helo=[127.0.0.1]) by genuine.home with esmtpa (Exim 4.50) id 1MWd0E-0003SZ-EC; Thu, 30 Jul 2009 23:17:30 +0200 Message-ID: <4A720DED.9070701@fischer.name> Date: Thu, 30 Jul 2009 23:17:33 +0200 User-Agent: Thunderbird 2.0.0.22 (Windows/20090605) MIME-Version: 1.0 To: Hannes Magnusson CC: Joey Smith , internals@lists.php.net References: <7f3ed2c30907300148k246bb727qe60b888ddfe5523f@mail.gmail.com> <20090730182837.GA1605@joeysmith.com> <7f3ed2c30907301137u50952971i5edfd12e2187a198@mail.gmail.com> In-Reply-To: <7f3ed2c30907301137u50952971i5edfd12e2187a198@mail.gmail.com> X-Enigmail-Version: 0.95.7 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Spam-Score: -32 X-Spam-Level: --- X-Spam-Report: Spam detection software, running on the system "genuine.home", has identified this incoming email as possible spam. The original message has been attached to this so you can view it (if it isn't spam) or label similar future email. If you have any questions, see the administrator of that system for details. Content preview: Hannes Magnusson wrote: > On Thu, Jul 30, 2009 at 20:28, Joey Smith wrote: >> However, now that it's come up, I'm wondering what the costs/risks are >> of setting libxml_use_internal_errors() on by default? > > I don't think thats a good idea. > People are used to getting a warning when stuff fails, and suppressing > them all of the sudden is not cool and people will waste a good chunk > of time figuring out what is wrong with the script they are developing > and eventually find out libxml_use_internal_errors() is enabled by > default and they'll start flaming the list about how much we all suck. [...] Content analysis details: (-3.3 points, 5.0 required) pts rule name description ---- ---------------------- -------------------------------------------------- -3.3 ALL_TRUSTED Did not pass through any untrusted hosts 0.0 BAYES_50 BODY: Bayesian spam probability is 40 to 60% [score: 0.5000] Subject: Re: [PHP-DEV] Re: RFC: Replacing errors with Exceptions From: markus@fischer.name (Markus Fischer) Hannes Magnusson wrote: > On Thu, Jul 30, 2009 at 20:28, Joey Smith wrote: >> However, now that it's come up, I'm wondering what the costs/risks are >> of setting libxml_use_internal_errors() on by default? > > I don't think thats a good idea. > People are used to getting a warning when stuff fails, and suppressing > them all of the sudden is not cool and people will waste a good chunk > of time figuring out what is wrong with the script they are developing > and eventually find out libxml_use_internal_errors() is enabled by > default and they'll start flaming the list about how much we all suck. Observing the thread, I totally agree to that. In my case I've "been there, done that" and although I flamed at the beginning why I can't catch the error properly (until I found the said function :) ), you can bring the counter example too: give no libxml_use_internal_errors() and throwing an exception instead, you don't have to worry about some special function to flip error handling. You just know how to cope with Exceptions, not some esoteric function to be called to get some information out. - Markus