I have a fairly large project I'm working on...within the top level demon source, there's a directive to load a single file (common.inc) that boot-straps my class autoloader and third-party libs, sets-up my constants and functions files, etc.
Working within the top-level demon .php file, all is green and I have a happy...however, to make the source manageable, I decided to modularize sections of code specific to processing functionality into a sub-directory and just load these modules at run time with a simple require() function call: (require('subdir/module1.php'));
....../ ... etc ...
Functionally, everything still works, but my OCD is getting nose-flicked because the module files went yellow with warnings on classes that are defined and instantiated in the parent (demon.php) file.
I can use @var comments for a few of my class variables in the headers and that knocks out some of the warnings within the module source...but I'm having problems doing the same with the 3P library class variables... so I was thinking there has to be an easier way to do this...
Is there a simple(r) way to mark the module file as a child-file to it's parent so that the parser can resolve unknowns to that level and eliminate the banana-fest I'm seeing along the right-side of my screen within the module files?