Mailing-List: contact dev-help@apr.apache.org; run by ezmlm
Precedence: bulk
Sender: trawick@rdu163-40-092.nc.rr.com
To: Ian Holsman <ianh@cnet.com>
Cc: dev@apr.apache.org
Subject: Re: Mutli-DBM patch
References: <1006904850.11657.54.camel@griffon.cnet.com>
From: Jeff Trawick <trawick@attglobal.net>
Date: 28 Nov 2001 08:32:14 -0500
In-Reply-To: <1006904850.11657.54.camel@griffon.cnet.com>
Message-ID: <m33d2z81i9.fsf@rdu163-40-092.nc.rr.com>
Lines: 27
User-Agent: Gnus/5.0808 (Gnus v5.8.8) Emacs/20.7
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii

Ian Holsman <ianh@cnet.com> writes:

> (inline as well as attached)
> This is my first foray into AutoConf.. so this is why I'm posting the patch
> it defines there new #defines APU_HAVE_XDBM.
> there is also a new dbm open function _open_ex(...) to specify the DBM
> later all also add a specific open call for each DBM 
> 
> So .. please comment..

As far as autoconf usage, it looks reasonable to me...

Any reason why the type parameter passed to the new open function is
char * instead of an enum?

Is there a way for apps to be aware of the APU_HAVE_foo capabilities?
(I don't think this has to be solved immediately.)  Some will want to
know what choices they should offer their users.  

I guess having a char * type lets the app pass it straight from a
configuration directive to apr-util with no knowledge on the part of
the app.

-- 
Jeff Trawick | trawick@attglobal.net | PGP public key at web site:
       http://www.geocities.com/SiliconValley/Park/9289/
             Born in Roswell... married an alien...