Front page | perl.perl5.porters |
Postings from December 2011
On Fri, 16 Dec 2011 21:32:51 +0100 Paul Johnson <paul@pjcj.net> wrote: > 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'm willing to mentor this task, but I should note I started adding more tests to the perl debugger, either as regression tests as part of bug fixes or as ones preventing future bugs here: https://github.com/shlomif/perl/tree/perl-d-add-tests-3 Nevertheless, more help would be appreciated. Regards, Shlomi Fish -- ----------------------------------------------------------------- Shlomi Fish http://www.shlomifish.org/ What Makes Software Apps High Quality - http://shlom.in/sw-quality Microsoft — making it all make sense. Ours. Please reply to list if it's a mailing list post - http://shlom.in/reply .Thread Previous | Thread Next