The document discusses different approaches to modularizing a project including copy/paste, static libraries, and dynamically loaded libraries. Copy/paste and reusing files is discouraged as it prevents changing the project structure. Static libraries make applications larger and require rebuilding the whole project if the library changes. Dynamically loaded libraries allow changing the library without rebuilding the application and loading only needed functionality through explicit linking. The document recommends dynamically loaded libraries for modularization and provides a URL for additional information.

1. Split project to modules

2. Copy&Paste and reusing files
• Obviously copy&paste is bad
• Reusing files is bad also because we cannot
change structure of project

3. Static libraries
• This is compiled unlinked code
• Using static libraries makes your application
bigger
• If you change static library, you must rebuild
the whole project
• With static library you cannot load only
needed functionality
• Public interface

4. Dynamically loaded libraries
• This is compiled and linked code
• Dll Export/Import
• Export library
• Dll can be changed without rebuilding the
application
• Implicit/Explicit linking

5. Information to think on
• http://accu.org/index.php/journals/1718