12.11.2013, 01:41
Don't use that method however, otherwise your main script will be dependent on your module's data and it can be mixed very easily.
Each module should be completely dependent upon themselves. In other words, if I were to run that module with another script (or by itself entirely with little boilerplate code) it should run. So, each module should contain hooked functions to handle triggers (callbacks). Every internal function and data (as should be with any include) should be declared as static. There should be an API to communicate between the module and your main script, i.e. functions. These functions should include means of getting the private (static) data from the file to the other (getter/setter functions).
I was debating writing a full mode taking use of modules to release so people better understood the design process. May do so now..
Each module should be completely dependent upon themselves. In other words, if I were to run that module with another script (or by itself entirely with little boilerplate code) it should run. So, each module should contain hooked functions to handle triggers (callbacks). Every internal function and data (as should be with any include) should be declared as static. There should be an API to communicate between the module and your main script, i.e. functions. These functions should include means of getting the private (static) data from the file to the other (getter/setter functions).
I was debating writing a full mode taking use of modules to release so people better understood the design process. May do so now..