On Mon, Dec 12, 2011 at 04:25:02PM +0000, Nicholas Clark wrote: > On Mon, Dec 12, 2011 at 05:17:53PM +0100, Johan Vromans wrote: > > Dave Mitchell <davem@iabyn.com> writes: > > > > > It's these sorts of exceedingly non-obvious gotchas that makes me very > > > wary of messing with the debugger. > > > > ... or that make it painfully clear that this piece of software requires > > good documentation and/or redesign. > > Good documentation alone won't save it. It (also) needs tests, and some idea > of coverage of those tests. I believe that investigating how to do this is > in the list of Google Code In tasks. Hopefully someone will take it up. I have added this as a task in the second batch of GCI tasks: http://www.google-melange.com/gci/task/view/google/gci2011/7241242 If anyone would be willing to mentor this, please make yourself known. Mentoring such a task is probably not particularly onerous to anyone familiar with the debugger and fame, fortune and a Google tee-shirt(*) await. I've also added tasks for testing a2p: http://www.google-melange.com/gci/task/view/google/gci2011/7235230 http://www.google-melange.com/gci/task/view/google/gci2011/7236229 So I'm also looking for mentors for these tasks. For the first one we would love to find someone who knows Awk as well as Perl. Such people seem to be in short supply nowadays. The second task merely requires someone who is able to help the student add tests to the core. We're also still grateful for anyone willing to offer their services for mentoring a particular task or just helping out in general, especially over the holiday season when many mentors will be unavailable for some of the time. Contact me or join #gci if you can volunteer. N.B. Mentoring by proxy is available to those with an aversion to creating a Google account. (*) Only one out of three is guaranteed. > But yes, I'm agreeing with "or" (in the inclusive sense). And I'm using "and" in the exclusive sense. -- Paul Johnson - paul@pjcj.net http://www.pjcj.netThread Previous | Thread Next