Mail Archives: cygwin/2001/10/08/23:55:41
Christopher C.,
This is a bit of a pet peeve for me, so I just have to chime in, even if
Christopher F.'s replies make it moot in this context.
Please, PLEASE don't use source code as an input to or as a specificational
/ definitional source of information for producing written documentation.
That is, by definition, putting the cart before the horse.
I won't go on, but that's such a pervasive misconception (that an
implementation defines a specification) and it happens to be one that
bothers me supremely, so I just had to say my piece.
Thank you for listening.
Randall Schulz
Mountain View, CA USA
At 19:40 2001-10-08, Christopher Currie wrote:
>There was supposedly a thread about docs recently, but I've had a hard time
>tracking it down...
>
>Therefore, I'd like to take a stab at writing the man pages for these calls.
>The best references are going to be the actual source code...
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Bug reporting: http://cygwin.com/bugs.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/
- Raw text -