Return-Path: Delivered-To: new-httpd-archive@hyperreal.org Received: (qmail 5736 invoked by uid 6000); 24 Jun 1999 17:09:48 -0000 Received: (qmail 5370 invoked from network); 24 Jun 1999 17:09:40 -0000 Received: from twinlark.arctic.org (204.107.140.52) by taz.hyperreal.org with SMTP; 24 Jun 1999 17:09:40 -0000 Received: (qmail 24039 invoked by uid 500); 24 Jun 1999 17:09:39 -0000 Date: Thu, 24 Jun 1999 10:09:39 -0700 (PDT) From: Dean Gaudet To: new-httpd@apache.org Subject: Re: cvs commit: apache-2.0/mpm/src/os/unix iol_socket.c iol_socket.h Makefile.tmpl In-Reply-To: Message-ID: X-Comment: Visit http://www.arctic.org/~dgaudet/legal for information regarding copyright and disclaimer. MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: new-httpd-owner@apache.org Precedence: bulk Reply-To: new-httpd@apache.org Read the archives, I can't be bothered stating my position for the nth time. Dean On Thu, 24 Jun 1999, Alexei Kosut wrote: > On 24 Jun 1999 dgaudet@hyperreal.org wrote: > > > I think this is a better i/o layer interface. > > [...] > > > +/* it is expected that each io layer will extend this structure as they > > + require; they must only ensure that the methods pointer remains in > > + the indicated position. */ > > struct ap_iol { > > - void *iol_data; > > const ap_iol_methods *methods; > > }; > > 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. > > Oh, and hi again, folks! > > -- > Alexei Kosut > Stanford University, Class of 2001 * Apache * > >