Return-Path: Delivered-To: apmail-httpd-dev-archive@httpd.apache.org Received: (qmail 54320 invoked by uid 500); 7 Nov 2001 15:19:42 -0000 Mailing-List: contact dev-help@httpd.apache.org; run by ezmlm Precedence: bulk Reply-To: dev@httpd.apache.org list-help: list-unsubscribe: list-post: Delivered-To: mailing list dev@httpd.apache.org Received: (qmail 54309 invoked from network); 7 Nov 2001 15:19:41 -0000 From: "Brian Havard" To: "dev@httpd.apache.org" Date: Thu, 08 Nov 2001 02:19:33 +1000 (EST) Reply-To: "Brian Havard" Priority: Normal X-Mailer: PMMail 2.10.1999 for OS/2 Warp 4.05 In-Reply-To: <01e601c16797$d47f7510$94c0b0d0@v505> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Subject: Re: cvs commit: httpd-2.0/server protocol.c Message-Id: X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N On Wed, 7 Nov 2001 08:18:55 -0600, William A. Rowe, Jr. wrote: >From: "Greg Stein" >Sent: Wednesday, November 07, 2001 3:56 AM > > >> Um. That doesn't look right. > >It doesn't but it is ;) > >> Those macros are based on *linkage*, not usage. If server/protocol.c occurs >> within the "core" DLL on Windows, then it must use the AP_CORE_DECLARE() >> macro. >> >> Those macros have nothing to do with visibility, and everything to do with >> linkage. >> >> OtherBill knows the most here, so let's hear his opinion here. I only >> /think/ something may be wrong here. > >Would be wrong, except that AP_DECLARE refers to the core module. The difference >is an abstract concept that goes back to early Apache 1.3 porting. In theory, we >could ignore all AP_CORE_DECLARES (leave them un-dllexported) and have very >private core module. In fact, everyone seems to dip their hands in there so >they are exported, I believe. > >So today, what Doug changed should be a noop - and CORE is not much more than >window dressing to tell folks the API is internal and subject to change. Not >that there is much difference in the 2.0 tree between core/non-core, or stable >APIs and fluid APIs :) Actually, build/make_exports.awk does NOT currently include AP_CORE_DECLAREd functions so platforms that depend on it to generate the list of core exports do not export core functions. This is actually a problem because mod_proxy uses several core functions so it fails to build correctly as a DSO. The offending symbols are: ap_set_config_vectors() ap_merge_per_dir_configs() ap_create_request_config() ap_create_per_dir_config() Should they get their CORE removed too? -- ______________________________________________________________________________ | Brian Havard | "He is not the messiah! | | brianh@kheldar.apana.org.au | He's a very naughty boy!" - Life of Brian | ------------------------------------------------------------------------------