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: "John C. Daub" <email@hidden>
- Date: Mon, 14 Aug 2006 20:28:35 -0500
- Thread-topic: Xcode/gcc help in enforcing secure coding?
on 8/14/06 7:42 PM, Sean McBride at email@hidden 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.
Yeah, I didn't think there was anything in particular Xcode was doing now...
I couldn't find anything, and thus why I filed the RADAR.
But I wanted to ask, in case I was overlooking something. :-)
I'd prefer not to hack my headers, but that is a thought on how to work with
it.
--
John C. Daub }:-)>=
<mailto:email@hidden> <http://www.hsoi.com/>
"Crazy, but that's how it goes. Millions of people living a foes.
Maybe it's not too late to learn how to love and forget how to hate." - Ozzy
_______________________________________________
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