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: glenn andreas <email@hidden>
- Date: Tue, 15 Aug 2006 10:55:29 -0500
On Aug 15, 2006, at 10:32 AM, John C. Daub wrote:
on 8/15/06 9:49 AM, Jens Ayton at email@hidden wrote:
Well, I thought the option of not messing with your system headers
was
worth highlighting. :-)
Oh indeed it is. :-)
Pun though it may be, perhaps "highlighting" might be an answer -
assuming some future version of XCode includes the ability to specify
custom keyword coloring, perhaps some annoyingly bright orange color
could be set for these functions, so if you you see a bright orange
"strcat" in your source, it will stand out enough for you to inspect
it to make sure it is used safely...
Such a feature would allow custom policy and be adaptable for things
like in house libraries with insecure routine. It's not the same as
the compiler warning about it, but you'll notice it sooner in new
code you're writing, and no modification for headers is required (and
would compliment well the source control level of checking).
Glenn Andreas email@hidden
<http://www.gandreas.com/> wicked fun!
Widgetarium | the quickest path to widgets
_______________________________________________
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