Timeline for Why are off by one errors so common and what can we do to prevent them?
Current License: CC BY-SA 2.5
5 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Aug 12, 2016 at 1:48 | comment | added | Company Laser | I'd love to learn more about the science of this if anyone has more info. I also think this is why programatic styling, like CSS, is so frustrating where everything is edges... | |
| Jun 15, 2016 at 17:20 | review | Suggested edits | |||
| Jun 15, 2016 at 17:35 | |||||
| Feb 4, 2011 at 15:22 | vote | accept | Malfist | ||
| Feb 2, 2011 at 19:26 | comment | added | Karl Bielefeldt | +1 for encapsulation. The worst off-by-one bugs I have ever seen are when part of the program is 1-based and part is 0-based, and every single function it is used, you have to remember which one it was and whether you have to do the conversion or not and which direction to go. A couple months ago I had to track down a difficult off-by-2 error because poor encapsulation meant someone made off-by-1 errors in two separate compounding places. There were conversions all over the place that were impossible to follow and I was able to get it down to one conversion in one method. | |
| Feb 2, 2011 at 18:10 | history | answered | Mason Wheeler | CC BY-SA 2.5 |