Re: Xcode/gcc help in enforcing secure coding?
Re: Xcode/gcc help in enforcing secure coding?
- Subject: Re: Xcode/gcc help in enforcing secure coding?
- From: Steven Fisher <email@hidden>
- Date: Tue, 15 Aug 2006 12:11:06 -0700
On 15-Aug-06, at 9:08 AM, Sean McBride wrote: Well, gcc gives plenty of other warnings for plenty of completely "acceptable" "standard" things, like unused variables, etc. We're talking about warnings, not errors. Still, you make a good point. Maybe instead of generating deprecated warnings, a new warning that gives secure coding advice could be created...
Granted, a new warning would be better. But I think the main mistake Microsoft made with Visual Studio (and the reason some people are passionately opposed to this) was defaulting the warnings to on. The people who care enough to fix them also probably care enough to turn them on.
I'll quite happily add a prefix with #define WARN_INSECURE, #define DEPRECATE_INSECURE or turn on a SECURITY_ADVISE compiler option. I'd love to see warning messages and don't especially care exactly what they are... :) |
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden