David Brown wrote:
I don't think it is possible to write meaningful documentation for
non-trivial and non-redundant code before the code has been written.
I'm not sure you can get it 100% correct, no. But I don't think you can
dive into a project without knowing what you're trying to accomplish,
either. If you develop a library without writing down the API first, you
tend to get really crappy libraries, because you didn't sit down and
think out the interactions between the parts first.
--
Darren New / San Diego, CA, USA (PST)
"That's pretty. Where's that?"
"It's the Age of Channelwood."
"We should go there on vacation some time."
--
[email protected]
http://www.kernel-panic.org/cgi-bin/mailman/listinfo/kplug-lpsg
