Received: (from majordom@localhost) by hyperreal.com (8.8.4/8.8.4) id NAA10049; Tue, 8 Apr 1997 13:44:01 -0700 (PDT) Received: from bilge-gw.topsail.org (bilge-gw.topsail.org [207.8.162.150]) by hyperreal.com (8.8.4/8.8.4) with ESMTP id NAA09999 for ; Tue, 8 Apr 1997 13:43:50 -0700 (PDT) Received: from argo.topsail.org ([172.16.86.5]) by bilge-gw.topsail.org (8.8.5/8.7.3) with ESMTP id QAA29221 for ; Tue, 8 Apr 1997 16:43:45 -0400 (EDT) Message-ID: <334AAE00.969FE9D7@topsail.org> Date: Tue, 08 Apr 1997 16:43:44 -0400 From: Chuck Murcko Organization: The Topsail Group X-Mailer: Mozilla 4.0b3C (X11; I; FreeBSD 2.1.7-RELEASE i386) MIME-Version: 1.0 To: new-httpd@apache.org Subject: Re: conf.h and httpd.h and proxy module X-Priority: 3 (Normal) References: <199704082031.QAA05130@devsys.jaguNET.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: new-httpd-owner@apache.org Precedence: bulk Reply-To: new-httpd@apache.org Jim Jagielski wrote: > > Chuck Murcko wrote: > > > > Marc Slemko wrote: > > > > > > right now things can include conf.h or httpd.h, but things break if they > > > do both. > > > > > Why is it lame to assume that core .h files should be includable by > > other things? Especially conf.h? This sounds like some other side > > effect, somehow. That says to me that we're accumulating a list of > > gotchas for module writers and others. The regex stuff was an example of > > that. > > > > Scuuze me.... but httpd.h includes conf.h itself. > Which is why mod_proxy.h only includes httpd.h. I somehow don't understand the problem here. Wrapping headers in #ifdefs is a lame exercise for those who don't understand how headers work, who like to #include everything that looks relevant, you see it all over Sun code. -- chuck Chuck Murcko The Topsail Group, West Chester PA USA chuck@topsail.org