In any case: The idea of keeping documentation and code next to each other in the same file, makes it much easier to document changes as they occur. How that is done is argueably a matter of taste (doxygen, POD, cweb, etc.).
For sure, that works great if you're talking about technical (read programmer) documentation. What about end-user documentation (user manuals etc)?
Most of the embedded documentation tools I've seen seem to lean heavily towards the former; what about tools for the latter (which is arguably of at least similar importance in a commercial world)?
Is there anything out there that really works in practice at both ends of the spectrum?
Slashdot Mirror
For sure, that works great if you're talking about technical (read programmer) documentation. What about end-user documentation (user manuals etc)?
Most of the embedded documentation tools I've seen seem to lean heavily towards the former; what about tools for the latter (which is arguably of at least similar importance in a commercial world)?
Is there anything out there that really works in practice at both ends of the spectrum?