GitHub - arstrube/Strncpy: Testing behavior of various strncpy_s() implementations compared to strncpy().

arstrube / Strncpy Public

Notifications You must be signed in to change notification settings
Fork 0
Star 2

Testing behavior of various strncpy_s() implementations compared to strncpy().

Notifications

Name		Name	Last commit message	Last commit date
Latest commit History 12 Commits
libsafec		libsafec
.gitignore		.gitignore
README		README
RunAllTests.cpp		RunAllTests.cpp
strncpy.sln		strncpy.sln
strncpy.vcproj		strncpy.vcproj
strncpy_libc.c		strncpy_libc.c
strncpy_s_custom.h		strncpy_s_custom.h
strncpy_s_safe.c		strncpy_s_safe.c
strncpy_s_v8.c		strncpy_s_v8.c
strncpy_s_wine.c		strncpy_s_wine.c

Repository files navigation

TESTS TO COMPARE BEHAVIOR OF STRNCPY VS. STRNCPY_S

These tests were written to determine whether it would be
preferable to use strncpy_s() in the CppUTest project,
even though the destination size parameter would be ignored,
or to continue using strncpy().

Also, for non-Microsoft targets, whether there is a
suitable implementation of strncpy_s() for GNU-based
systems.

Because of this, macros are employed, and each test
tests all implementations, so it is easy to see where
they differ.

(c) 2014 Arnd R. Strube