30+ years ago, when I took Computer Science 100 in college, one of the important lessons was that you should *never* trust input, and we had to run our homework programs on maliciously designed data (especially useful for finding off-by-one errors.)
The main causes of stack overflow are input routines that don't check how much data you're handing them, and there's simply no excuse for allowing that in professional code. I'm guessing that the buggy programs were written in C - it's a beautiful efficient language, but it *will* let you shoot yourself in the foot - or else in some variant like C++ or C#, which offer you better-protected data structures but still let you use the old-fashioned ones.
|
Does Verizon's Voyager stack up to the iPhone? |
|
|
5 IT skills that won't boost your salary
[1,407]
Women 4 times more likely than men to cough up personal info
[589]
Japan's 10 funniest tech-related commercials [Videos]
[407]
Throwing away a promo CD is "unauthorized distribution"?
[1,265]
Adults too quick to dismiss educational video games
[682]
Attack of the iPhone clones [Slideshow]
[578]
10 things IT needs to know about AJAX
[1,258]
This Year's 25 Geekiest 25th Anniversaries [Slideshow]
[409]
|
|
Post new comment