[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: APR is inconsistent about pool behavior

From: Greg Stein <gstein_at_lyra.org>
Date: 2000-10-10 02:09:47 CEST

On Mon, Oct 09, 2000 at 06:58:29PM -0500, Jim Blandy wrote:
>...
> > As you point out: APR is not built to use any behavior other than "abort on
> > alloc failure" (which I believe I pointed out back then, too). As a result,
> > we pretty much *have* to use the abort design. However, that isn't bad at
> > all... it works very well for us, too.
>
> No, that's fine. But if all APR users want that behavior, wouldn't it
> be nicer for it to be the default in APR? At the moment, you have to
> take special pains to get that behavior; I'd think one would rather
> have an abort function set in new pools by default, and provide a call
> to override it, if the caller is willing to take the responsibility.

The argument went something like "a library should never abort() a program,
that is up to the application to define."

*shrug*

I'm in the process of changing our svn_pool_create() function and its
callers. We'll have The Right Behavior(tm).

Cheers,
-g

-- 
Greg Stein, http://www.lyra.org/
Received on Sat Oct 21 14:36:10 2006

This is an archived mail posted to the Subversion Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.