If they don't know what they are looking for, splitting POSIX up into 10 modules doesn't make it any simpler. They will now have to search 10 manuals, and the number of lines of documentation won't decrease.
It might well help, if the sub-modules were well organized. If I was doing POSIX compliant file manipulations, for example, I wouldn't bother reading the manual for the date manipulation and timezone handling sub-module.
Sure the total amount of documentation is the same: but the number of lines of documentation that I need to read in order to solve my problems is decreased if the modules are better organized. It's really the same principle that leads us to we split our code into modules in the first place. If you split code (or documentation) up into logically ordered pieces, then you only have to read the code (or documentation) that applies to what you're working on; not the entire program (or manual page). If done right, it can save a lot of time and effort
--
Ytrew Q. Uiop | [reply] |
| [reply] |