Difference between revisions of "Clean platform library guideline"
From Clean
Jump to navigationJump to searchBas Lijnse (talk | contribs) (New page: The complexity of libraries for Clean ranges, from single pure Clean modules to large collections of Clean and C modules with dependencies on external shared libraries. While you '''can'''...) |
|||
| Line 1: | Line 1: | ||
| − | The complexity of libraries for Clean ranges, from single pure Clean modules to large collections of Clean and C modules with dependencies on external shared libraries. While you '''can''' organize the files of a library in an arbitrary way, it greatly helps if you follow a guideline when organizing a library. This will improve the maintainability of your libraries, and ease | + | The complexity of libraries for Clean ranges, from single pure Clean modules to large collections of Clean and C modules with dependencies on external shared libraries. While you '''can''' organize the files of a library in an arbitrary way, it greatly helps if you follow a guideline when organizing a library. This will improve the maintainability of your libraries, and ease its configuration, installation and distribution. |
Latest revision as of 09:36, 15 July 2008
The complexity of libraries for Clean ranges, from single pure Clean modules to large collections of Clean and C modules with dependencies on external shared libraries. While you can organize the files of a library in an arbitrary way, it greatly helps if you follow a guideline when organizing a library. This will improve the maintainability of your libraries, and ease its configuration, installation and distribution.
