Re: safe strcpy()?
From: Crispin Cowan (crispin@wirex.com)
Date: 01/30/03
- Previous message: Ed Carp: "Re: safe strcpy()?"
- In reply to: mlh@zip.com.au: "Re: safe strcpy()?"
- Next in thread: Brandon Erhart: "Re: safe strcpy()?"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Date: Wed, 29 Jan 2003 22:19:47 -0800 From: Crispin Cowan <crispin@wirex.com> To: mlh@zip.com.au
mlh@zip.com.au wrote:
>Indeed. What we want is a language compatible with
>C but with string handling as a standard part -- luckily
>there is such a beast -- C++ !
>
C++ is unmitigated evil. The safety of C, and the performance of
Smalltalk :-(
People who need the safety and OOP abstractions of C++ should use Java
(or C# if you prefer): they have no business using a dangerous weapon
like C or C++. Even people skilled at writing C code should use a safer
language unless they *need* the speed and agility of C.
People who need greater performance than Java should use C, because C++
imposes such bloat. The abstraction of object oriented design and object
oriented programming can be done just fine without C++'s bloat: in Ye
Olde Dayes, it was called "abstract data structures."
There is no middle ground for C++. Everyone should just stop using it.
IMNSFHO, of course :-)
Crispin
-- Crispin Cowan, Ph.D. Chief Scientist, WireX http://wirex.com/~crispin/ Security Hardened Linux Distribution: http://immunix.org Available for purchase: http://wirex.com/Products/Immunix/purchase.html Just say ".Nyet"
- application/pgp-signature attachment: stored
- Next message: Timo Sirainen: "Re: safe strcpy()?"
- Previous message: Ed Carp: "Re: safe strcpy()?"
- In reply to: mlh@zip.com.au: "Re: safe strcpy()?"
- Next in thread: Brandon Erhart: "Re: safe strcpy()?"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]