| From time to time on this list, the recommendation is made to never
| user C++ when given a choice (most recently by Crispin Cowan in the
| "re-writing college books" thread). This is a recommendation I do not
| understand. Now, I'm not an expert C++ programmer or Java or C#
| programmer and as y
The biggest problem with C++ is that, like C, it is not type safe. The memory
model is a disasterous sea of bits. Plus it is an arcane, hard to understand
language prone to misunderstandings.
If you can at all avoid C++, do so.
Use Java, C#, or some other type safe alternative.
gem
compa
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On Behalf Of Robert C. Seacord
> Sent: 01 November 2006 10:16
> To: Ben Corneau
> Cc: SC-L@securecoding.org
> Subject: Re: [SC-L] Why Shouldn't I use C++?
>
> Ben,
>
> I would not go so far as to say never use
At 9:08 PM -0500 10/31/06, Ben Corneau wrote:
> C and C++ are very different. Using C++ like C is arguable unsafe, but when
> it's used as it was intended can't C++ too be considered for secure
> programming?
What assurance does upper management have that C++ was used "as it was
intended" rather
Ben,
I would not go so far as to say never use C++. It is probably the most
powerful and expressive commercially successful programming language
available today and there are often good reasons to use the language.
Secure programming in C++ is possible, but C++ itself is exceptionally
complex, h