2010年12月3日 · Because gets does not take a length parameter, it doesn't know how large your input buffer is. If you pass in a 10-character buffer and the user enters 100 characters -- well, …

2012年10月15日 · fgets() and gets_s() are the recommended replacements. Never use gets(). Given that gets_s is defined in an extension to the standard, only optionally implemented, you …

2015年7月10日 · Never use gets. It offers no protections against a buffer overflow vulnerability (that is, you cannot tell it how big the buffer you pass to it is, so it cannot prevent a user from …

Unlike fgets, gets_s maintains a one-to-one relationship between input lines and successful calls to gets_s. Programs that use gets expect such a relationship. The Microsoft Visual Studio …

2015年12月2日 · However, the function gets() has been removed from C11 standard. That means there's no longer a prototype for gets() in <stdio.h>. gets() used to be in <stdio.h>. The reason …

2009年10月1日 · When, later, you do gets() that ENTER is still in the input buffer and that's what gets() gets. You have two options: clear the input buffer after each scanf() clear the input …

2014年10月28日 · So in gets you enter charecters, strings, numbers and spaces. In case of scanf, you input ends as soon as a white-space is encountered. But then in your example you are …

I would heed the warning and replace gets.This is clear enough for me: BUGS. Never use gets(). Because it is impossible to tell without knowing the data in advance how many characters …

2013年6月5日 · The gets() function is defined to read input into a buffer provided by the caller, up to and including the first newline (or EOF). It does not provide any mechanism for limiting input …

2017年3月15日 · Also, regarding the warning with -Wdeprecated-declarations, gets() is no longer a part of C standard [C11 onwards]. So, C libraries compilers are not bound to support that …