BANNED: memcpy(), CopyMemory(), and RtlCopyMemory()

revolution wrote:

http://www.theregister.co.uk/2009/05/15/microsoft_banishes_memcpy/ 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.
And here is a list of other banned function calls:

http://msdn.microsoft.com/en-us/library/bb288454.aspx

In other words;

"Hey, look, people are making bad code with this function, and as a result their code sucks.. so let's remove it and make a new function! They're code will STILL suck just as much when they use this one wrong to, but who cares, change for the sake of change is the Windoz mantra, right??"

This isn't going to stop morons from riddling their code with buffer overruns. Just watch, they'll set numberOfElements to -1 out of pure laziness, or something.

revolution wrote:

comrade wrote:
Take a look at Apple kicking their ass.
Apple is kicking who's ass? At what? Do you mean Apple is "kick-ass" at making their users dumb? Hehe, some would say the users were already dumb if they bought an Apple. Not me of course, I wouldn't say that.

Some would say that at least Mac isn't made by idiots, like Windoz is. I wouldn't say such a thing, of course.