#13616 [Sus->Csd]: Compiler complains about function declaration after return is called
| From: | sniper@php.net | Date: | Sat, 07 Dec 2002 01:55:34 +0000 |
| Subject: | #13616 [Sus->Csd]: Compiler complains about function declaration after return is called | ||
| References: | 1 | Groups: | php.bugs |
| Request: | Send a blank email to php-bugs+get-26920@lists.php.net to get a copy of this message | ||
ID: 13616
Updated by: sniper@php.net
Reported By: brianm@dealnews.com
-Status: Suspended
+Status: Closed
Bug Type: Scripting Engine problem
Operating System: Linux
PHP Version: 4.0CVS-2001-10-09
Assigned To: ssb
New Comment:
Seems to be fixed in PHP 4.3.0-dev.
Previous Comments:
------------------------------------------------------------------------
[2001-10-17 17:35:04] brianlmoon@php.net
I worded that poorly, It in fact does not do the zend_hash_add the
second time, thus keeping a function from ever being added twice.
------------------------------------------------------------------------
[2001-10-17 17:34:09] brianlmoon@php.net
I have a zend_compile.c that will allow the same function from the same
file too pass through with a NOTICE rather than a fatal ERROR. Is this
of interest to anyone? It is a good interim solution I think.
------------------------------------------------------------------------
[2001-10-17 11:53:43] ssb@php.net
This turns out to be due to another bug fix (9884), and will probably
end up being documented as a compatibility breaker in 4.1.0.
I recommend that you use include_once instead.
------------------------------------------------------------------------
[2001-10-11 20:20:06] ssb@php.net
Example can be reduced to:
test.php:
<?php
function foo() {}
include "test2.php";
?>
test2.php:
<?php
return;
function foo() {}
?>
------------------------------------------------------------------------
[2001-10-10 14:40:32] sander@php.net
Reproduced with latest dev from php4win.com (04-Oct-2001).
------------------------------------------------------------------------
The remainder of the comments for this report are too long. To view
the rest of the comments, please view the bug report online at
http://bugs.php.net/13616
--
Edit this bug report at http://bugs.php.net/?id=13616&edit=1