Microsoft To Banish Memcpy () 486. Posted by kdawson on Friday May 15, 2009 @11:26AM from the good-riddance dept. kyriacos notes that Microsoft will be adding memcpy () to its list of function calls banned under its secure development lifecycle. This reader asks, "I was wondering how advanced C/C++ programmers view this move.
You claim that memcpy/memmove is faster than std::copy, while in my experience the performance of memcpy/memmove is the same as for std::copy/std::copy_backward. Your string class is supposed to be faster than std::string. While this may be true for some operations, it is probably not true for the most important ones, and for situations where. memcpy() is intended for when you wish to copy one array into another, or something similar. dwk Seek and ye shall find. quaere et invenies. "Simplicity does not precede complexity, but follows it." -- Alan Perlis "Testing can only prove the presence of bugs, not their absence." -- Edsger Dijkstra.