> I would say the real issue at hand here is that the return
> statement is
> not a fucntion, but rather a language construct, thus it
> cannot be used
> as a function unless explicitly stated as so. The reason a parse error
> is occurring is because this particular construct has no support for
> being used in the given context. It would be like dropping in
> any other
> language construct suddenly such as a { or @ where it is not
> understood.
> Given that die() and exit() works just means they have been given
> support for this context.
Sounds to me that if it looks like a function, quacks like a function, etc.,
only a broken language definition would treat it differently from a
function...
--
PHP General Mailing List (http://www.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php
