I never liked those microsoft functions, and disable all the warnings in each new project. What are you supposed to use instead of memcpy? It's a bit of a rant but I find myself in agreement with this:
http://unspecified.wordpress.com/2009/05/16/microsoft-bans-m...
This header would be much more useful if it suggested safe alternatives for each of the functions it poisions
While there is probably no meaningful use for gets() (which is missing from that list and certainly is not Win32 specific) and maybe sprintf() and even more maybe strcat(), what is exactly so insecure about things like memcpy() or alloca()?
I am actually happy that gcc doesn't find it important to support a library that prevents its users from using functions that are clearly defined in the specification of the language it supports.
Iām currently doing a school project in C and we wrote a shell script to check every source file for these insecure functions. It displays a warning and suggest you a more secure alternative function.
this site is unusable on my phone.the sidebar dominates the screen.
It turns out there is a project - the safe C library - that implements strcpy_s and friends as an open source library (MIT license). so this header can be used with the Safe C library.
Good! I had never ignored that unsafe notices from visual studio console.
Somewhat off-topic, but I can't use my back-button to get off this page.
Can we please, please stop breaking shit that worked just fine in '95?
http://motherfuckingwebsite.com/