Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:3406 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 76591 invoked from network); 14 Jul 2003 05:55:23 -0000 Received: from unknown (HELO a6s.sargasso.net) (198.77.14.39) by pb1.pair.com with SMTP; 14 Jul 2003 05:55:23 -0000 Received: (qmail 32263 invoked from network); 14 Jul 2003 05:55:22 -0000 Received: from a5s.sargasso.net (198.77.14.38) by pri1.mail.sargasso.net with SMTP; 14 Jul 2003 05:55:22 -0000 Date: Mon, 14 Jul 2003 01:55:22 -0400 (EDT) X-X-Sender: david@a5s.sargasso.net To: internals@lists.php.net Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Subject: Re: pfpro issuing E_ERROR when E_WARNING would be more appropriate From: david@php.net (David) These errors are thrown when the user is passing illegal variable types, please explain why you think they should be warnings. Even silently converting them to other types would make no sense in these cases. David (marc doesn't show e-mail addresses so I can't cc the submitter) Sara wrote: > ext/pfpro/pfpro.c has several php_error_docref() calls (particularly in > pfpro_process) which issue E_ERROR (Fatal Errors/Non-recoverable) in > situations where an E_WARNING would seem more appropriate (as it would allow > the calling script to recover and continue. > > Is there a particular reason a fatal error would be thrown in this case? > > -Sara -- |> /+\ \| | |> David Croft Infotrek