Quote:
Originally Posted by Thomas Richter
That is not very practical for any reasonably sized program.
|
We're talking about meynaf's OS framework. I actually have a version of that which he uses in his image viewer. This is framework just under 5000 lines, including empty lines and comment lines. Not exactly large. This code contains all the OS related code. We're not talking about a complete program with OS code spread all over the place. If that was the case it would be awful indeed.
Quote:
Originally Posted by Thomas Richter
it is still a problem with modularization
|
Not in this case. 5000 lines of code you can easily include anywhere is quite convenient and easy to use.
Quote:
Originally Posted by Thomas Richter
Generally, the include file should define the interface of the corresponding source file, and whenever this interface is needed, this file should be included. Combine that with a build environment such as "make", and you get automatic dependency resolution, and automatic re-assembling/re-compilation whenever you change the interface.
|
And with this framework you include two files that have no external dependencies at all and you're done. It doesn't get any easier than that.