Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:3407 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 14884 invoked from network); 14 Jul 2003 07:12:23 -0000 Received: from unknown (HELO jdi.jdimedia.nl) (212.204.192.51) by pb1.pair.com with SMTP; 14 Jul 2003 07:12:23 -0000 Received: from jdi.jdimedia.nl (jdi.jdimedia.nl [212.204.192.51]) by jdi.jdimedia.nl (8.12.4/8.12.4) with ESMTP id h6E7CMn4021274; Mon, 14 Jul 2003 09:12:22 +0200 Date: Mon, 14 Jul 2003 09:12:22 +0200 (CEST) X-X-Sender: derick@jdi.jdimedia.nl To: David cc: internals@lists.php.net In-Reply-To: Message-ID: References: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Subject: Re: [PHP-DEV] Re: pfpro issuing E_ERROR when E_WARNING would be more appropriate From: derick@php.net (Derick Rethans) On Mon, 14 Jul 2003, David wrote: > > 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. It still shouldn't throw a fatal error. E_ERROR is only meant for critical errors that will destabalize the Engine, in all other cases E_WARNING should be used, which is almost always the case in extensions. regards, Derick -- "Interpreting what the GPL actually means is a job best left to those that read the future by examining animal entrails." ------------------------------------------------------------------------- Derick Rethans http://derickrethans.nl/ International PHP Magazine http://php-mag.net/ -------------------------------------------------------------------------