Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:45152 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 18880 invoked from network); 30 Jul 2009 18:29:15 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 30 Jul 2009 18:29:15 -0000 Authentication-Results: pb1.pair.com header.from=joey@joeysmith.com; sender-id=pass Authentication-Results: pb1.pair.com smtp.mail=joey@joeysmith.com; spf=pass; sender-id=pass Received-SPF: pass (pb1.pair.com: domain joeysmith.com designates 209.90.98.146 as permitted sender) X-PHP-List-Original-Sender: joey@joeysmith.com X-Host-Fingerprint: 209.90.98.146 host-3.pl1071314.fiber.net Received: from [209.90.98.146] ([209.90.98.146:49586] helo=joeysmith.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id E3/A5-25953-976E17A4 for ; Thu, 30 Jul 2009 14:29:14 -0400 Received: from joey by joeysmith.com with local (Exim 4.69) (envelope-from ) id 1MWaMn-0006sg-Gd for internals@lists.php.net; Thu, 30 Jul 2009 12:28:37 -0600 Date: Thu, 30 Jul 2009 12:28:37 -0600 To: internals@lists.php.net Message-ID: <20090730182837.GA1605@joeysmith.com> References: <7f3ed2c30907300148k246bb727qe60b888ddfe5523f@mail.gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <7f3ed2c30907300148k246bb727qe60b888ddfe5523f@mail.gmail.com> User-Agent: Mutt/1.5.18 (2008-05-17) Subject: Re: [PHP-DEV] Re: RFC: Replacing errors with Exceptions From: joey@joeysmith.com (Joey Smith) On Thu, Jul 30, 2009 at 10:48:49AM +0200, Hannes Magnusson wrote: > No PHP warnings at all. > > > Again. The examples you are looking for are network issues with > fopen(), file_get_contents() and such things. > > -Hannes Hannes, these are actually the ones I had in mind when I sent my last email - unfortunately, it's been so long since I ran into one, I can't remember how to trigger it, which is why I suggested we get bugs filed. Conceptually, it doesn't seem like it should be that hard to fix them. However, now that it's come up, I'm wondering what the costs/risks are of setting libxml_use_internal_errors() on by default?