Microsoft Bans Memcopy()
This seems smart:
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.
Here’s the list of banned function calls. This doesn’t help secure legacy code, of course, but you have to start somewhere.
Clive Robinson • May 20, 2009 9:15 AM
As discussed a few days ago on this blog there are better ways to go these days than with C/C++.
Unfortunatly after something like 40years the assumptions about the resources are the other way around these days (ie Hardware=cheep Humans=expensive).
We need to think of a suitable high level language without the faults but still retaining the power and compactness.
Oh and please please thing up a better way to delcare variables (it’s a night mare hence so many pointers to void, and the risks ascociated).
I think both K&R have said they would change the precedence and ascociative behaviour in C…
Oh and perhaps we should stop thinking of “files” being the basic data/comms model I’m sure there are better ways to do it.
But hey Rome was not built in a day 8)