Compilers

[gunnar at arctecgroup.net (Gunnar Peterson)]

Sure it should be built into the language, and I assume it will be
eventually. Heck it only took 30 or 40 years for people to force developers
to use Try...Catch blocks.

-gp


On 12/21/06 9:30 AM, "McGovern, James F (HTSC, IT)"
<James.McGovern at thehartford.com> wrote:

> I have been noodling the problem space of secure coding after attending a
> wonderful class taught by Ken Van Wyk. I have been casually checking out
> Fortify, Ounce Labs, etc and have a thought that this stuff should really be
> part of the compiler and not a standalone product. Understanding that folks do
> start companies to make up deficiencies in what large vendors ignore, how far
> off base in my thinking am I?
>
>
> *************************************************************************
> This communication, including attachments, is
> for the exclusive use of addressee and may contain proprietary,
> confidential and/or privileged information.  If you are not the intended
> recipient, any use, copying, disclosure, dissemination or distribution is
> strictly prohibited.  If you are not the intended recipient, please notify
> the sender immediately by return e-mail, delete this communication and
> destroy all copies.
> *************************************************************************
>
>
> _______________________________________________
> Secure Coding mailing list (SC-L) SC-L at securecoding.org
> List information, subscriptions, etc - http://krvw.com/mailman/listinfo/sc-l
> List charter available at - http://www.securecoding.org/list/charter.php
> SC-L is hosted and moderated by KRvW Associates, LLC (http://www.KRvW.com)
> as a free, non-commercial service to the software security community.
> _______________________________________________


-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://krvw.com/pipermail/sc-l/attachments/20061221/a756b883/attachment.html