Mailing-List: contact dev-help@apr.apache.org; run by ezmlm
Precedence: bulk
Received-SPF: pass (athena.apache.org: domain of jorton@redhat.com designates
 66.187.233.31 as permitted sender)
Date: Mon, 14 Apr 2008 20:33:47 +0100
From: Joe Orton <jorton@redhat.com>
To: dev@apr.apache.org
Subject: Re: svn commit: r647384 - in /apr/apr/trunk: CHANGES
	include/apr_pools.h memory/unix/apr_pools.c
Message-ID: <20080414193347.GA16091@redhat.com>
Mail-Followup-To: dev@apr.apache.org
References: <20080412063616.D87721A9832@eris.apache.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
In-Reply-To: <20080412063616.D87721A9832@eris.apache.org>
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 Sat, Apr 12, 2008 at 06:36:15AM -0000, Mladen Turk wrote:
> Author: mturk
> Date: Fri Apr 11 23:36:14 2008
> New Revision: 647384
> 
> URL: http://svn.apache.org/viewvc?rev=647384&view=rev
> Log:
> Introduce apr_pool_create_core_ex

What problem is this solving?

"This function should be used for short living pools, usually ones that 
are created and destroyed either in a loop or inside function call."

I don't understand that at all.  Needing to use an unparented pool 
sounds like an application bug/design issue.  Can you explain the 
context for this?

joe