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: Jens Ayton <email@hidden>
- Date: Tue, 15 Aug 2006 21:39:41 +0200
- Openpgp: id=84FF254B
Steven Fisher:
>
> Granted, a new warning would be better. But I think the main mistake
> Microsoft made with Visual Studio (and the reason some people are
> passionately opposed to this) was defaulting the warnings to on. The
> people who care enough to fix them also probably care enough to turn
> them on.
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()).
--
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