Changes between Version 5 and Version 6 of HeaderModularization

Timestamp:

May 27, 2009, 4:59:09 PM (13 years ago)

Author:

Beman Dawes

Comment:

Refine wording

HeaderModularization

@@ -4 +4 @@
 
  1. Single include path (-I...). Without a single include path, builds, IDE's, and other tools become unmanageable.
- 2. Easy checkout, commit, merge, switch, and other source control operations.
+ 2. Easy checkout, commit, merge, switch, and other source control operations. Implies no separate checkout, update, commit, switch, etc. post-processing step.)
  3. Works well regardless of build engine, not just with bjam or CMake. 
  4. Doesn't break users existing scripts, IDE setups, etc. OK to break developers and release managers scripts.
@@ -11 +11 @@
  7. All maintenance occurs withing the library's libs/... directory. (Subset of (6), but important enough to list separately.)
  8. Easy scripting (inspect, unmerged changes, release management, etc.) ((7) goes a long way to achieve this.)
- 9. Works well with installers.
+ 9. Works well with out-of-the box subversion, bjam, CMake, installers, and other tools we are likely to use.
  10. Supports test-on-demand and test-library-against-different-branch.
+ 11. Doesn't waste disk space excessively.
 
 == Possible Approaches ==