Ok, now is much more clear to me.
What I understand, is that:
- A Framework statement is always required if you don't want to include the whole modules; so it's like to say:
'do not include the whole thing, but just the module specified in the Framework, and the ones specified in the include statements that follow'
- choosing the right framework depends on which statements are used in the code, and in this case, the Framework Assistant by jb is really handy;
- if I do not use the Framework key word, but only the include statements, this will not prevent the loading of the whole thing.
The Framework as an 'include container' - thanks James - is indeed a good example of how to mantain the code tiny.
Thanks all,
Sergio.
What I understand, is that:
- A Framework statement is always required if you don't want to include the whole modules; so it's like to say:
'do not include the whole thing, but just the module specified in the Framework, and the ones specified in the include statements that follow'
- choosing the right framework depends on which statements are used in the code, and in this case, the Framework Assistant by jb is really handy;
- if I do not use the Framework key word, but only the include statements, this will not prevent the loading of the whole thing.
The Framework as an 'include container' - thanks James - is indeed a good example of how to mantain the code tiny.
Thanks all,
Sergio.