As I was sipping my morning cup of coffee and sifting through today's issue of "CodeProject," I stumbled upon a pretty interesting article:
Full article: http://www.theregister.co.uk/2009/05/15 ... es_memcpy/Unsafe at any speed: Memcpy() banished in Redmond wrote:Microsoft plans to formally banish the popular programming function that's been responsible for an untold number of security vulnerabilities over the years, not just in Windows but in countless other applications based on the C language. Effective later this year, Microsoft will add memcpy(), CopyMemory(), and RtlCopyMemory() to its list of function calls banned under its secure development lifecycle. [...]
I totally think that it's a good idea, but gcc can't exactly get RID of memcpy(). Think of all of the embedded processors and old C applications that rely on that and other, similar functions.
