From dev-return-9163-apmail-apr-dev-archive=apr.apache.org@apr.apache.org Sat Feb 08 10:00:05 2003 Return-Path: Delivered-To: apmail-apr-dev-archive@apr.apache.org Received: (qmail 70363 invoked by uid 500); 8 Feb 2003 10:00:04 -0000 Mailing-List: contact dev-help@apr.apache.org; run by ezmlm Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: Delivered-To: mailing list dev@apr.apache.org Received: (qmail 70340 invoked from network); 8 Feb 2003 10:00:03 -0000 Date: Sat, 8 Feb 2003 10:00:42 +0000 From: Joe Orton To: dev@apr.apache.org, dev@httpd.apache.org Subject: Re: [PATCH] HPUX static's and Mixing C with C++ modules Message-ID: <20030208100042.GB26551@manyfish.co.uk> Mail-Followup-To: dev@apr.apache.org, dev@httpd.apache.org References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4i X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N Hi, On Fri, Feb 07, 2003 at 12:23:09PM -0500, Arliss, Noah wrote: > I'll try to clarify things as best I can. First off, BIND_VERBOSE would be > fantastic. I had to add it in order to get my module to load at all with > shl_load, even though it still would not function. If there was a good > reason to remove BIND_VERBOSE that history would be nice to have. The > shl_load call would look better as: BIND_VERBOSE means the library writes error message to whatever file you happen to have open as fd 2 - which is unacceptable for a library. (the app may have closed stderr and be using fd 2 for something completely different). You get exactly the same error string back via apr_dso_error() anyway, which is the defined interface for retrieving the error string. Changing the call to: > + shl_t os_handle = shl_load(path, BIND_IMMEDIATE, 0L); seems fine to me, FWIW, but as Will says, the BIND_NOSTART has been there since the code was first checked into Apache 1.3, so there may be some subtle reason why it's needed. Regards, joe