Mladen Turk wrote: > William A. Rowe, Jr. wrote: >> GOOD GOD you can't be serious :) >> >> strncat strncpy exist for a reason, C's been safe for decades if >> only the correct functions are chosen :) >> > > Didn't say it's wrong or something like that, > but beside constantly fighting with hacking > and suppressing newest MS compilers security presumptions, > I see nothing wrong of using provided SDK functions > for MS only related code.
My 2c - since MS doesn't want to play in C POSIX land and work with the appropriate spec bodies, but would rather invent their unique mindset (again) and work against the communities, I'm rather partial to ignoring their 'security overtures'. Fortunately I've seen some blog feedback to the effect that 'we made a mistake with this draconian change' or words to that effect, so hopefully VC 8.1 might see some course correction. FWIW there is some community source licensing and portable implementation around this MS Strings Lib, but that doesn't really change my opinion. The reason against this commit is that you break older ms clibs (which is precisely what they would like you to do.) Bill --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
