|
|
|
| Authored by: Anonymous on Friday, May 11 2012 @ 12:39 PM EDT |
C has no range check. My several millions of lines of C code have no buffer
overflows or memory leaks. I use debug and memcheck / valgrind to ensure this,
along with unit testing. When I am satisfied that the code functions as
designed, why would I enforce useless range checking code (code that is proven
not to be executable -- Dead Code)?
Rangecheck can be done away with. It is essentially merely comparing the list's
item number with the length of the list...
"I have ten grocery items in my list."
... later ...
"What is item number 32?"
Rangecheck: ERROR! You only have 10 items in the list!
That is how fundamental it is. You can actually look at the list before you
even ask.
if ( the_item_number_wanted < list.length() ) return
list[the_item_number_wanted];
^ This! This RIGHT HERE is what range check does. Utilizing rangecheck while
using this code would be superfluous, and the function itself is extremely
worthless.
It's like the air cap on your tires' valve stems. They serve a purpose, but for
the most part they don't really do anything useful at all, and It's NOT a big
deal if your tires are missing the little screw on caps for the air inlets.[ Reply to This | Parent | # ]
|
|
|
|
|
