• 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 09:46:54 +0200
  • Openpgp: id=84FF254B

John C. Daub:
>
> I was wondering if there's anything Xcode/gcc can currently do to help
> enforce secure coding?
>
> I grant there's a lot here the compiler can't do, but for example take the
> list of string functions to avoid:

Copy the declarations into a file, say BadStuff.h. Then add
__attribute__((deprecated)) or __attribute__((poison)) to each
declaration. Include BadStuff.h from a prefix header.


--
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

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

  • Prev by Date: Re: -Wshorten-64-to-32 and LL suffix
  • Next by Date: Re: FSRef_fopen alternative
  • 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