Return-Path: Delivered-To: new-httpd-archive@hyperreal.org Received: (qmail 24643 invoked by uid 6000); 6 Feb 1998 15:31:25 -0000 Received: (qmail 24637 invoked from network); 6 Feb 1998 15:31:24 -0000 Received: from unknown (HELO mail3.bellglobal.com) (198.235.216.132) by taz.hyperreal.org with SMTP; 6 Feb 1998 15:31:24 -0000 Received: from shell.lerdorf.on.ca ([207.164.141.19]) by mail3.bellglobal.com (Netscape Mail Server v2.02) with SMTP id AAA10933 for ; Fri, 6 Feb 1998 10:30:48 -0500 Date: Fri, 6 Feb 1998 10:33:39 -0500 (Eastern Standard Time) From: rasmus@lerdorf.on.ca (Rasmus Lerdorf) To: new-httpd@apache.org Subject: More function naming conflicts Message-ID: X-X-Sender: rasmus@imap3.bellglobal.com 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 Somebody somewhere is really out to get me. The latest Solid (an RDBMS) libs have no less than 5 function naming conflicts with Apache. I don't see why in the world they have a "send_http_header" function for example, but something like "process request" is way too generic a name for Apache to have as a non-static function. It would be nice if every single non-static Apache function was clearly labelled with whatever prefix it was we decided on for these things. http_request.o: Definition of symbol `process_request' (multiply defined) http_protocol.o: Definition of symbol `send_http_header' (multiply defined) util.o: Definition of symbol `ht_time' (multiply defined) util.o: Definition of symbol `gm_timestr_822' (multiply defined) util.o: Definition of symbol `unescape_url' (multiply defined) -Rasmus