Nick Hibma <hi...@skylink.it> wrote: >> Programmers need documentation too. > >And they are going to scream like mad if there isn't any. But in the end >they start reading the code anyway, even if there is docu, because they >don't trust anything but their own eyes and brain. > >It's all documented in C anyway.
Not really. The C code defines what a piece of code is doing and how it does it. It does not explain why it is doing what it is doing, and most importantly, why it is doing it the way that it is. In many cases, the code might be written the way it is because that's the first thing that popped into the author's head. In this case, it might not matter if the code is substantially re-arranged. In some cases, the code is written in a particular way because the `more obvious' ways of writing the code didn't meet the author's requirements. Whilst it possible that the particular requirement was `this code must be unintelligible', it's more likely to be a subtle interaction with some other subsystem. Peter To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-hackers" in the body of the message
