On Fri, 14 Jun 2002, Julian Buckley wrote: > however, what needs to be established is just what direction Circle > Admin wants coding.doc to take. coding.doc has a well-defined direction and I do not want to stray too far from the structure and purpose that Jeremy defined. By adding more work than what's already left to it, we risk turning it into a Sisyphean task. > A section on gdb (or your debugger of choice) also needs to be included > [...] I think there's already enough documentation available for this tool, much of which is better than what we could produce. Even if you don't agree, there, it begs the question why we would just document one tool that's useful for CircleMUD development. Why not also document GCC and Make? Why not the compilers and debuggers of other platforms? Why not library X and library Y? The list could go on, but, really, we shouldn't document any of the above. An abundance of serviceable documentation is just a web search away in many cases. -dak -- +---------------------------------------------------------------+ | FAQ: http://qsilver.queensu.ca/~fletchra/Circle/list-faq.html | | Archives: http://post.queensu.ca/listserv/wwwarch/circle.html | | Newbie List: http://groups.yahoo.com/group/circle-newbies/ | +---------------------------------------------------------------+
This archive was generated by hypermail 2b30 : 06/25/03 PDT