Sun, 17 May 2009

Unsafe at any speed: Memcpy() banished in Redmond

Well, in my not so humble opinion as a long time C coder, this is pretty brain dead. Memcpy() already has a length parameter -

void *memcpy(void *dest, const void *src, size_t n)

what good will adding another do? If you're brain damaged enough to misuse it as it is, you're probably going to be brain damaged enough to misuse it no matter how many additional parameters are added. As with any technology, it's not the tools that are the problem here - it's the way the tools are used.

A more colorful take is provided at Perl.org.

Memcpy() and brethren, your days are numbered. At least in development shops that aspire to secure coding.

(link) [The Register]

/Technology | 0 writebacks | permanent link

comment...

 
Notes: If you put a <mailto:> link in the URL field your address will not be mangled: this could be a bad idea as your email address could be easily harvested by bots designed for SPAM. The comments field should now format correctly for line feeds and carriage returns: when you hit the 'Enter' or 'Return' keys in your comment it should break to a new line. The text should wrap cleanly. Please let me know if it doesn't. No HTML tags will pass through - entering links seems to be the main cause of comment SPAM. Also, please be sure that Javascript is enabled in your browser before attempting to post a writeback. Sorry for any inconvenience, but this really helps cut down on the amount of comment SPAM I have to deal with.
 
 Name:
 URL:(optional)
 Title: (optional)
 Comments:  
Save my Name and URL/Email for next time