nope, it checks both. How could you call it secure without checking both sizes? memcpy_s(dest,dmax,src,slen) and my implementation safeclib even at compile-tim

nope, it checks both. How could you call it secure without checking both sizes? memcpy_s(dest,dmax,src,slen) and my implementation safeclib even at compile-time, similar to glibc's FORTIFY.