Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:7418 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 95964 invoked by uid 1010); 30 Jan 2004 11:05:57 -0000 Delivered-To: ezmlm-scan-internals@lists.php.net Delivered-To: ezmlm-internals@lists.php.net Received: (qmail 95920 invoked from network); 30 Jan 2004 11:05:57 -0000 Received: from unknown (HELO jdi.jdimedia.nl) (212.204.192.51) by pb1.pair.com with SMTP; 30 Jan 2004 11:05:57 -0000 Received: from localhost (localhost [127.0.0.1]) by jdi.jdimedia.nl (8.12.10/8.12.10) with ESMTP id i0UB5uvs025258; Fri, 30 Jan 2004 12:05:56 +0100 Date: Fri, 30 Jan 2004 12:05:14 +0100 (CET) X-X-Sender: derick@localhost To: Rasmus Lerdorf 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] Warnings in include files suddenly treated as fatal From: derick@php.net (Derick Rethans) On Fri, 30 Jan 2004, Rasmus Lerdorf wrote: > On Fri, 30 Jan 2004, Derick Rethans wrote: > > > On Fri, 30 Jan 2004, Rasmus Lerdorf wrote: > > > > > Remember that it is ok for an include to not find the file. We issue a > > > warning and move on. It should in no way be treated as a fatal error. > > > > But it should on a parse error in an include file, not? > > Yes, but a failed include is not a parse error. I know, I was just making sure while fixing it :) Derick