Hi folks,
I've often got the problem that a larger application behaves unclear
if some of the include()'d/require()'ed scripts has some syntax error.
It seems that the all the code is executed until this require-statement
where the parse fails. If its an include() then it seems execution
proceeds nevertheless.
In some situations this can be helpful, i.e. for larger frameworks
checking themselves (for example a module loader can simply try to
include() the module's code and properly handle the error when it fails).
But on the other hand there are many cases where this is problematic.
Is there any way to chance this behavour ?
regards,
Enrico Weigelt == metux IT services
phone: +49 36207 519931 www: http://www.metux.de/
fax: +49 36207 519932 email: contact@metux.de
cellphone: +49 174 7066481
-- DSL-Zugang ab 0 Euro. -- statische IP -- UUCP -- Hosting
I've often got the problem that a larger application behaves unclear
if some of the include()'d/require()'ed scripts has some syntax error.
It seems that the all the code is executed until this require-statement
where the parse fails. If its an include() then it seems execution
proceeds nevertheless.
This is correct and expected behavior, and also noted in the manual at:
http://nl3.php.net/include/
Derick