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: Steve Checkoway <email@hidden>
- Date: Tue, 15 Aug 2006 01:44:54 -0700
On Aug 14, 2006, at 5:42 PM, Sean McBride wrote:
John C. Daub (email@hidden) on 2006-08-14 17:36 said:
Anyway, I'm just wondering if there's anything we can do with
Xcode 2.x to
help enforce the guidelines Apple set down about Secure Coding.
And if not,
hopefully what can be done could be done in Xcode 3.x.
No that I know of. I believe MS has marked some of those functions as
deprecated in its newest tools, I'd like to see Apple do that. You
could probably do the same by hacking your headers and using the
DEPRECATED_ATTRIBUTE #define from AvailabilityMacros.h. Then fix all
your warnings.
Apple, if you're listening, please, PLEASE do not mark standard
library functions deprecated that really aren't. I'm understand the
desire for some of the more dangerous functions but strlen is _not_
deprecated and microsoft pretending that it is is simply stupid. It's
very annoying to use a standard function only to find that other
people on the project using Windows cannot build because MS has
decided to remove/rename/deprecate the function.
--
Steve Checkoway
_______________________________________________
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