Jeff> Oliver Xymoron wrote:
>> Some problems with documentation:
>>
>> - is a poor substitute for code - can never be complete, accurate,
>> or timely enough to match the source - <language> is much more
>> ambiguous than C
Jeff> If you want to know exactly what occurs, look at the code. If
Jeff> you want an overview, a summary, a quick scan of the logic
Jeff> contained within the code, and perhaps suggested best usage of
Jeff> the code, look at the docs (if they exist).
My primary worry here is that people tend to consider the
documentation as the truth. IMHO it is very important that on every
single page the will say something like this: "The Code is
Authoritative, read it!"
Jes
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/