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: Steven Fisher <email@hidden>
- Date: Tue, 15 Aug 2006 14:06:57 -0700
On 15-Aug-06, at 12:39 PM, Jens Ayton wrote: On the other hand, the people who need it most are those who are completely unaware of the issues. It seems people are still learning C from books/web tutorials whose sample code happily uses unsafe functions without mentioning the ramifications (and, like a book I used at uni, use malloc() a lot but never mention the existence of free()).
I really can't argue with that, only point out that a balance needs to be struck between educating, providing feedback to those who already understand and want it, and not annoying those who don't care to be educated or don't care for other reasons.
I do not believe that the status quo -- not providing warnings AT ALL, even optionally -- is the right balance.
PS: What's free()? ;) |
_______________________________________________
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