Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:6715 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 88639 invoked by uid 1010); 25 Dec 2003 17:32:56 -0000 Delivered-To: ezmlm-scan-internals@lists.php.net Delivered-To: ezmlm-internals@lists.php.net Received: (qmail 88614 invoked from network); 25 Dec 2003 17:32:55 -0000 Received: from unknown (HELO mail.zend.com) (192.117.235.230) by pb1.pair.com with SMTP; 25 Dec 2003 17:32:55 -0000 Received: (qmail 31281 invoked from network); 25 Dec 2003 17:32:54 -0000 Received: from localhost (HELO zeev-laptop.zend.com) (127.0.0.1) by localhost with SMTP; 25 Dec 2003 17:32:54 -0000 Reply-To: zeev@zend.com Message-ID: <5.1.0.14.2.20031225193237.07ec8e28@localhost> X-Sender: zeev@localhost X-Mailer: QUALCOMM Windows Eudora Version 5.1 Date: Thu, 25 Dec 2003 19:32:47 +0200 To: internals@lists.php.net Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Subject: Error reporting behavior with streams From: zeev@zend.com (Zeev Suraski) People, When streams were introduced, the format of error messages involving include/require changed significantly, and now emits two errors instead of one. Am I the only one being bugged by this? I think we can simply remove the REPORT_ERRORS option from php_fopen_wrapper_for_zend(). Possibly, if there are cases where php_stream_open_wrapper_as_file() can report something smarter than just the inability to create the stream, we can add an option such as REPORT_NONTRIVIAL_ERRORS, so that if the stream-level error has something smart to say, it won't go unnoticed. Thoughts? Zeev