• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: Xcode/gcc help in enforcing secure coding?
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Xcode/gcc help in enforcing secure coding?


  • Subject: Re: Xcode/gcc help in enforcing secure coding?
  • From: Jens Ayton <email@hidden>
  • Date: Tue, 15 Aug 2006 21:41:44 +0200
  • Openpgp: id=84FF254B

glenn andreas:
>
> 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...

That's not much use when you've got a heap of legacy code, though. :-/


--
Jens Ayton
 _______________________________________________
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

References: 
 >Re: Xcode/gcc help in enforcing secure coding? (From: "John C. Daub" <email@hidden>)
 >Re: Xcode/gcc help in enforcing secure coding? (From: glenn andreas <email@hidden>)

  • Prev by Date: Re: Xcode/gcc help in enforcing secure coding?
  • Next by Date: NSDirectoryEnumerator
  • Previous by thread: Re: Xcode/gcc help in enforcing secure coding?
  • Next by thread: Re: Xcode/gcc help in enforcing secure coding?
  • Index(es):
    • Date
    • Thread