Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:7417 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 33355 invoked by uid 1010); 30 Jan 2004 10:43:11 -0000 Delivered-To: ezmlm-scan-internals@lists.php.net Delivered-To: ezmlm-internals@lists.php.net Received: (qmail 33322 invoked from network); 30 Jan 2004 10:43:10 -0000 Received: from unknown (HELO colo.lerdorf.com) (66.198.51.121) by pb1.pair.com with SMTP; 30 Jan 2004 10:43:10 -0000 Received: from DELL (c-24-6-108-60.client.comcast.net [24.6.108.60]) by colo.lerdorf.com (8.12.11/8.12.11/Debian-1) with ESMTP id i0UAh93i014411; Fri, 30 Jan 2004 02:43:10 -0800 Date: Fri, 30 Jan 2004 02:41:13 -0800 (Pacific Standard Time) To: Derick Rethans cc: internals@lists.php.net In-Reply-To: Message-ID: References: X-X-Sender: rasmus@lerdorf.com MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Spam-Status: No, hits=-4.8 required=5.0 tests=AWL,BAYES_00 autolearn=ham version=2.63 X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on colo Subject: Re: [PHP-DEV] Warnings in include files suddenly treated as fatal From: rasmus@php.net (Rasmus Lerdorf) 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. -Rasmus