From: Jim Jagielski <jim@devsys.jaguNET.com>
Message-Id: <199906241733.NAA03528@devsys.jaguNET.com>
Subject: Re: cvs commit: apache-2.0/mpm/src/os/unix iol_socket.c iol_socket.h
  Makefile.tmpl
To: new-httpd@apache.org
Date: Thu, 24 Jun 1999 13:33:16 -0400 (EDT)
In-Reply-To: <Pine.LNX.3.96dg4.990624102453.23427R-100000@twinlark.arctic.org>
 from "Dean Gaudet" at Jun 24, 99 10:25:03 am
Content-Type: text
Sender: new-httpd-owner@apache.org
Precedence: bulk
Reply-To: new-httpd@apache.org

Dean Gaudet wrote:
> 
> On Thu, 24 Jun 1999, Bill Stoddard wrote:
> 
> > Chris Costello wrote:
> > > 
> > > On Thu, Jun 24, 1999, Alexei Kosut wrote:
> > > > You know, I really don't mean to troll, but aren't there are other C-like
> > > > languages that are really much better at this sort of thing? Perhaps this
> > > > is a good time to at least seriously think about C++ (or a small subset of
> > > > it), one more time. So much of the Apache API, past, present and future,
> > > > would benefit from having easily available inheritance and polymorphism
> > > > that I think it may very well be worth the hassle. Maybe.
> > > 
> > >    With the overhead that comes with using C++, it would not be
> > > practical for something like the Apache HTTPd.
> > > 
> > What overhead are you referring to? It is possible to write very
> > efficient (in term of space and execution time) C++ programs. You need
> > to have a good understanding of how some of the nifty C++ features are
> > translated into the executable code. C++ is not an easy language to grok
> > to the fullest.
> 
> What nifty features are you referring to?
> 

Can I start up the autoconf religious war now too???

:) :) :)

-- 
===========================================================================
   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"