Clean platform library guideline: Difference between revisions
From Clean
Jump to navigationJump to search
Bas 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'''... |
No edit summary |
||
| 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 08: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.
