On 08/03/2010 01:35 AM, Richard Kenner wrote:
That is true, but very often the documentation is needed in two
places: in the code and in the manual. Especially for things like
machine constraints, flags and options.
Yes, but the audiences are different between users who read the manual and
developers who read the code. For the best quality, the two descriptions
may well be quite different, in emphasis, tone and other areas. If the
emphasis is on finding text that's acceptable for BOTH purposes, you create
documentation that's not ideal for EITHER.
The amount of comments copied tout-court from gccint to the target files
(especially with respect to target macro definitions) seems to
contradict this.
Paolo
