Hi guys,
I have tried running this code.
However, I get this output.Code:#include <stdio.h> #include <conio.h> int main(){ char name[20]; printf("Enter name: "); scanf_s("%s", name); printf("Your name is %s.", name); _getch(); return 0; }
Enter name: abcd
Your name is .
Why is the output blank space?
Because you didn't read the manual page for scanf_s before using it.
scanf_s, _scanf_s_l, wscanf_s, _wscanf_s_l
You will note that you need another parameter - one telling the function the size of the buffer being passed.
Since you didn't say anything (and your compiler didn't warn you either), you're left scratching your head and posting on forums.
If you dance barefoot on the broken glass of undefined behaviour, you've got to expect the occasional cut.
If at first you don't succeed, try writing your phone number on the exam paper.
You may also want to check out the less 'Windows Centric' sscanf and fgets.
It is true that sscanf_s() and similar functions were introduced by Microsoft, but they are also now defined in Annex K of the 2011 C standard. So characterising them as "windows centric" is both unfair and outdated.Originally Posted by FloridaJo
(Admittedly, it is not mandatory that an C11 implementation support Annex K. However, it is not difficult to do so, so most hosted C11 implementations probably will.)
Okay, on a Mac then under what library do they reside?
In the draft standard, these are listed in <stdio.h> (see Annex B.20: http://www.open-std.org/jtc1/sc22/wg...docs/n1570.pdf)
My compiler doesn't recognize scanf_s.
Last edited by FloridaJo; 10-11-2014 at 04:23 PM.
Neither does mine.My compiler doesn't recognize scanf_s.
Though as grumpy pointed out, it's both C11 and not mandatory, so it's not surprising that our compilers don't support it.
I think the point was that it has been recognized by recent standards, and as such is technically fair game with regard to the standard (i.e. no longer strictly OS specific), though not necessarily widely adopted in implementation.
Okay, gotcha. Thanks.
