It sounds like it’s just a compiler warning. Usage of scanf_s prevents possible buffer overflow. See: http://code.wikia.com/wiki/Scanf_s Good explanation as to why scanf can be dangerous: Disadvantages of scanf So as suggested, you can try replacing scanf with scanf_s or disable the compiler warning.
The _s functions are optional (Annex K of the C11 standard). They’re widely regarded as ‘not very beneficial’. In the answers to my question Do you use the TR-24731 “safe” functions?, you can find information about where there are problems with the standard specification — such as crucial differences between the standard and Microsoft’s implementation. … Read more
You are misusing scanf_s(). Microsoft compilers may warn you to use their secure extensions (aka c11 annex k). But, be careful if you do so. scanf_s() is not a direct replacement for scanf(). In this case you have to pass the size of the output buffer as an extra argument. char c; scanf_s(“%c”, &c, 1); … Read more
It is a function that belongs specifically to the Microsoft compiler. scanf originally just reads whatever console input you type and assign it to a type of variable. If you have an array called first_name[5] and you use scanf for “Alex”, there is no problem. If you have the same array and assign “Alexander”, you … Read more
I have been a vocal critic of these TRs since their inception (when it was a single TR) and would never use them in any of my software. They mask symptoms instead of addressing causes and it is my opinion that if anything they will have a negative impact on software design as they provide … Read more