Return-Path: Delivered-To: new-httpd-archive@hyperreal.org Received: (qmail 2823 invoked by uid 6000); 12 Mar 1998 18:46:03 -0000 Received: (qmail 2816 invoked from network); 12 Mar 1998 18:46:01 -0000 Received: from devsys.jagunet.com (206.156.208.6) by taz.hyperreal.org with SMTP; 12 Mar 1998 18:46:01 -0000 Received: (from jim@localhost) by devsys.jaguNET.com (8.8.8/jag-2.4) id NAA29570 for new-httpd@apache.org; Thu, 12 Mar 1998 13:45:57 -0500 (EST) From: Jim Jagielski Message-Id: <199803121845.NAA29570@devsys.jaguNET.com> Subject: Re: the C++ disaster (was Re: Source code - optimised assembler) To: new-httpd@apache.org Date: Thu, 12 Mar 1998 13:45:57 -0500 (EST) In-Reply-To: <35082BB2.86DEA6C8@algroup.co.uk> from "Ben Laurie" at Mar 12, 98 06:38:42 pm X-Mailer: ELM [version 2.4 PL25] Content-Type: text Sender: new-httpd-owner@apache.org Precedence: bulk Reply-To: new-httpd@apache.org Ben Laurie wrote: > > We seem to have made a large leap here. Now you are saying that _every_ > project done in C++ has gone wrong. I can demonstrate several that > haven't, and I'm sure I'm not alone. There are a lot of crap programmers > out there, and they write a lot of crap code. Many of them write crap > code in C++. This tells us nothing about C++. > I don't mind programming in C++, but to do it right I find I have to mentally "switch gears" or else I produce C++ that's no different from C. In other words, to program well in C++, you have to be in OOP mode. Otherwise, what comes out is crap. Both C and C++ give you enough rope to hang yourself. IMO C++ gives you a bit more rope to do the job, but dead is dead. And sometimes, you need the extra rope when NOT hanging yourself, at which point, C++ shines. -- =========================================================================== Jim Jagielski ||| jim@jaguNET.com ||| http://www.jaguNET.com/ "That's no ordinary rabbit... that's the most foul, cruel and bad-tempered rodent you ever laid eyes on"