Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:6716
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
In-Reply-To: <5.1.0.14.2.20031225193237.07ec8e28@localhost>
References: <5.1.0.14.2.20031225193237.07ec8e28@localhost>
Mime-Version: 1.0 (Apple Message framework v609)
Content-Type: text/plain; charset=US-ASCII; format=flowed
Message-ID: <F0A9DAFB-3700-11D8-8B31-000393B2B3C0@omniti.com>
Content-Transfer-Encoding: 7bit
Cc: internals@lists.php.net
Date: Thu, 25 Dec 2003 12:36:58 -0500
To: zeev@zend.com
Subject: Re: [PHP-DEV] Error reporting behavior with streams
From: george@omniti.com (George Schlossnagle)


On Dec 25, 2003, at 12:32 PM, Zeev Suraski wrote:

> 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?

I agree with you.  Not only are their two errors, but the error for 
include/require specifically is not as clear as it once was.

George