Return-Path: Delivered-To: new-httpd-archive@hyperreal.org Received: (qmail 580 invoked by uid 6000); 23 Jan 2000 19:30:19 -0000 Received: (qmail 553 invoked from network); 23 Jan 2000 19:30:17 -0000 Received: from twinlark.arctic.org (204.107.140.52) by taz.hyperreal.org with SMTP; 23 Jan 2000 19:30:17 -0000 Received: (qmail 8264 invoked by uid 500); 23 Jan 2000 19:30:16 -0000 Received: from localhost (sendmail-bs@127.0.0.1) by localhost with SMTP; 23 Jan 2000 19:30:16 -0000 Date: Sun, 23 Jan 2000 11:30:16 -0800 (PST) From: Dean Gaudet To: new-httpd@apache.org Subject: Re: cvs commit: apache-2.0/src/include http_core.h In-Reply-To: <388B4391.5D745820@algroup.co.uk> 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 On Sun, 23 Jan 2000, Ben Laurie wrote: > Ah, gotcha. It still niggles at me that it always seems to come down to > void *s, though. hrm... which aspect of void * is troublesome? the typelessness bothers me a bit. the array of void *'s for module per_dir and per_server configs bothers me in that it wastes memory. an array of atoms wouldn't bother me so much -- because an atom is allocated for each module/group of modules that wish to attach data to the structure. (whereas right now we allocate a void * for each module regardless of whether they use it or not) but none of those bother me as much as #ifdefs :) i'm not an OO person. how would you do this sort of dynamic extension in an OO language? Dean