5 ms·

> Programmers respond by attempting to stamp out the gets() function in working code, but they refuse to remove it from the C programming language's standard in

• rlongstaff 11y ago
  ... but what percentage of current C code is C11. More importantly, how much new code is written according to C11?
• rgbrenner 11y ago
  C11 is about 6 years newer than the article. So the article was accurate at the time it was written.
• Gibbon1 11y ago
  But gets() isn't just one unsafe function all of the classic string functions are totally unsafe, and most of their safer replacements are similarly bad. They do things like take buffer size and then will truncate strings and leave off the terminating zero. So then the next string function will blow up. I think really when people manipulate strings in c/c++ they use the safe functions that come with frameworks.