Reading Maximum Address Of The HD In LBA48
Reading Maximum Address Of The HD In LBA48
...False alert!...
Last edited by Lprogster on Sat Sep 08, 2007 6:07 am, edited 1 time in total.
- AndrewAPrice
- Member
- Posts: 2309
- Joined: Mon Jun 05, 2006 11:00 pm
- Location: USA (and Australia)
I remember reading a comment in early Linux source about a function that said something like "I hope this works. I'd hate to have to debug this".
The my complex the code is, the more you want to write it once and never touch it again and assume your the perfect coder who does have bugs.
It'll appear to work, until 2 months later when you've built a whole lot of code dependent on that code and after a day of debugging you've uncovered around 20 bugs in your original code.
It's even scarier when you find major bugs in your code (especially errors in pointer arithmetic) yet it runs perfectly and produces no seen side effects.
The my complex the code is, the more you want to write it once and never touch it again and assume your the perfect coder who does have bugs.
It'll appear to work, until 2 months later when you've built a whole lot of code dependent on that code and after a day of debugging you've uncovered around 20 bugs in your original code.
It's even scarier when you find major bugs in your code (especially errors in pointer arithmetic) yet it runs perfectly and produces no seen side effects.
My OS is Perception.
Seen that a lot, sadly. Usually it's a function that makes a hash of everything but barely compiles, which is then never used.MessiahAndrw wrote:It's even scarier when you find major bugs in your code (especially errors in pointer arithmetic) yet it runs perfectly and produces no seen side effects.