Re: No more return in file-body (was: Re: [PHP-DEV] 4.0.7 when?)
| From: | Zeev Suraski | Date: | Wed, 17 Oct 2001 18:20:14 +0000 |
| Subject: | Re: No more return in file-body (was: Re: [PHP-DEV] 4.0.7 when?) | ||
| References: | 1 2 3 4 5 6 | Groups: | php.dev |
| Request: | Send a blank email to php-dev+get-68157@lists.php.net to get a copy of this message | ||
At 17:51 17-10-01, Jeroen van Wolffelaar wrote:
I strongly disagree. Using return in a script in order to stop executing that file is used a lot by myself, and I suppose by a lot of others too. Currently, include()'d files behave more or less like executing a argument-less function (in parent scope, that is). But the main reason is that now returning a certain value from a file is now broken too. (i.e., let include/require return a certain value).Uhm, nobody is talking about discontinuing return, and it should work just fine, w/ or w/o values. There's a specific issue with function/class redefinitions past the return statement. Zeev