Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:7436 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 79381 invoked by uid 1010); 30 Jan 2004 19:16:58 -0000 Delivered-To: ezmlm-scan-internals@lists.php.net Delivered-To: ezmlm-internals@lists.php.net Received: (qmail 79352 invoked from network); 30 Jan 2004 19:16:58 -0000 Received: from unknown (HELO asuka.nerv) (24.100.195.79) by pb1.pair.com with SMTP; 30 Jan 2004 19:16:58 -0000 Received: (qmail 1670 invoked from network); 30 Jan 2004 19:16:57 -0000 Received: from rei.nerv (HELO dummy.com) (rei@192.168.1.1) by asuka.nerv with SMTP; 30 Jan 2004 19:16:57 -0000 Reply-To: ilia@prohost.org Organization: Prohost.org To: Martin Jansen , internals@lists.php.net Date: Fri, 30 Jan 2004 14:17:02 -0500 User-Agent: KMail/1.5.94 References: <200401301337.52932.ilia@prohost.org> <20040130191402.GC20996@divbyzero.net> In-Reply-To: <20040130191402.GC20996@divbyzero.net> MIME-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-ID: <200401301417.02198.ilia@prohost.org> Subject: Re: [PHP-DEV] Warnings in include files suddenly treated as fatal From: ilia@prohost.org (Ilia Alshanetsky) The oirignal parse error messages not only tells you the filename but also the line where the parse error occurs. The 2nd error (the one you referring to) will tell you on which line the 'broken' file is being included. Ex: Parse error: parse error in /home/rei/PHP_CVS/php4/BUILD/inc2.inc on line 3 Fatal error: Parse error inside included file. in /home/rei/PHP_CVS/php4/BUILD/inc1.php on line 2 Ilia On January 30, 2004 02:14 pm, Martin Jansen wrote: > On Fri Jan 30, 2004 at 01:3752PM -0500, Ilia Alshanetsky wrote: > > + zend_error(E_ERROR, "Parse error inside included file."); > > Is there any chance to include the name of the included file here?