Re: Experimental "peer to peer" modular programming concept
- Posted by Shian_Lee May 06, 2015
- 1810 views
Part of the problem is the way include files work assumes that an included file is somehow lower in the hierarchy, and there is no clear way to make different parts of the program "peers" or independent "modules" without some other library to include them and control them.
Does anyone else have this problem?
Certainly.
Whenever too much code is in the same level in the hierarchy, the program is hard to maintain or understand.
A simple way to deal with it is by splitting the code into many include files and placing groups of files in different directories, and by adding documentation that explains what is going on; but it's fake and confusing.
It's hard to avoid some kind of pattern in this case, since the code must remain maintainable.
