[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: critical issues
From: |
David Kastrup |
Subject: |
Re: critical issues |
Date: |
Sat, 01 Jan 2011 10:38:59 +0100 |
User-agent: |
Gnus/5.13 (Gnus v5.13) Emacs/24.0.50 (gnu/linux) |
"Keith OHara" <address@hidden> writes:
> On Fri, 31 Dec 2010 16:31:23 -0800, Trevor Daniels
> <address@hidden> wrote:
>> ... the concern I had was this. Quite a lot of the
>> documentation was written, not by inspecting the code
>> to see what was intended, but by experimenting and
>> writing up what was found. I certainly worked that
>> way, and I think Mark and Keith did recently in
>> documenting the new spacing stuff.
>
> Pretty much. If it makes you feel better, I did read a fair bit of
> the code to help build up a mental model of how things worked.
The problem is that one is documenting the implementation, not the
designed interface. Which is fixating things at the wrong end of the
stick: the implementation should be free to gravitate towards its best
state without having to change the documentation and/or the interface.
--
David Kastrup
Re: critical issues, Jan WarchoĊ, 2011/01/01
Re: critical issues, Trevor Daniels, 2011/01/01
Re: critical issues, David Kastrup, 2011/01/01
Re: critical issues,
David Kastrup <=
Re: critical issues, Phil Holmes, 2011/01/02