Hi,
thanks for your comment. Right, and similarly, it struck me that in case there are variable-names in the path, like in
require_once $my_lib_dir . "some_funcs.php";
the variable $my_lib_dir could only be known at run-time and not by any simple script just scanning the source.
True - and if you had a script that actually changed $my_lib_dir then this could be a real mess. But if in your function you actually include the file you're trying to parse then you can know the value at runtime. But consider this:
require_once dirname(__FILE__) . 'some_funcs.php';
Interpreting that one is a little tougher... still might get around to it...
-- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
