On Tue, Nov 27, 2012 at 08:15:13AM -0800, Ted Dunning wrote: > > I can only say from my own experience that people make mistakes over time and > having the code warn them when that happens is a good thing. > > Your experience may be different but I have to admit that I have done some > pretty silly things along the lines of forgetting to follow some constraint.
That's exactly what I'm saying: We know that we can introduce bugs in code but we cannot accompany every statement with a check! Then, where you draw the line between "this must be checked" and "this does not need a check" is indeed a matter of choice. Gilles > On Nov 27, 2012, at 8:08 AM, Gilles Sadowski <gil...@harfang.homelinux.org> > wrote: > > > My point is that _if_ the methods can be made > > "private", then we can assume that they are used properly there (which is > > the only place where they can be called). It's the same that we wouldn't > > check whether, say, we wrote > > a + b > > instead of > > a - b > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org > For additional commands, e-mail: dev-h...@commons.apache.org > --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
