saray | longer mantained - 'Yet Another Rest API Stubber'.split | REST library

Well safe unsafe question is coming because of the buffer over run issue. strcpy is not aware of destinations characeter holding capability. That's why its unsafe.

Safer would be strcpy_s( stud.name, 20, "goktug" );. Here we are specifying that no matter what we should be in limit of 20 as destnation is capable of holding 20 characters including the NUL terminating character.

^{One can argue that here data is being truncated which is not better than a clear message that destination is too small to hold the copied thing, but surely better than a buffer overrun exploits. If we think along that line then well, we can reach the conclusion that we shouldn't call them unless we become sure that destination can hold the copied string.}