Mailing-List: contact dev-help@apr.apache.org; run by ezmlm
Precedence: bulk
Received-SPF: pass (nike.apache.org: domain of jorton@redhat.com designates
 66.187.233.31 as permitted sender)
Date: Tue, 13 May 2008 10:14:50 +0100
From: Joe Orton <jorton@redhat.com>
To: dev@apr.apache.org
Subject: Re: apr_reslist semantics
Message-ID: <20080513091450.GA9992@redhat.com>
Mail-Followup-To: dev@apr.apache.org
References: <20080512202209.79187ffa@grimnir> <4828AE2F.9020101@apache.org>
 <4828B236.6040504@rowe-clan.net> <20080513080703.GA5406@redhat.com>
 <20080513095842.6b681493@grimnir>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
In-Reply-To: <20080513095842.6b681493@grimnir>
User-Agent: Mutt/1.5.17 (2007-11-01)
Organization: Red Hat UK Ltd, Amberley Place, 107-111 Peascod Street, Windsor,
 Berkshire, SL4 1TE, United Kingdom.
  Registered in UK and Wales under Company Registration No. 03798903
  Directors: Michael Cunningham (USA), Brendan Lane (Ireland),
 Matt Parson (USA), Charlie Peters (USA)

On Tue, May 13, 2008 at 09:58:42AM +0100, Nick Kew wrote:
> On Tue, 13 May 2008 09:07:03 +0100
> Joe Orton <jorton@redhat.com> wrote:
> >  changing each function call into
> > an indirected dynamic-symbol-lookup-and-function-call would be an 
> > unmaintainable hack.
> 
> But that's not the proposal on the table!  Noone is suggesting
> changing any function call, API or even ABI.  Merely how the
> code is loaded.

OK, great.  How will it work then?

> >	  Since downstream users must also continue to be 
> > linked against those LDAP libraries by virtue of linking against 
> > libaprutil, it would also be a redundant hack.
> 
> That is a misfeature of the current build procedure.

The code was explicitly designed to work like this, it's a feature which 
can't be removed without breaking backwards compat with existing 
downstream users.  (I'm not saying I like it)

joe