Re: Programming join documentation - is this imaginatioin ?

On 2006-06-22, Paul E. Black <> wrote:
One reason to have documentation is to explain whatever is not evident
from the source code. So by definition, we will always need
documentation whenever there is information which is explicitly in the

Apart from all other reasons, code might describe very well /what/ it is
doing, but it might not always be clear /why/ it is doing it. That
needs additional documentation.