apr-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Mladen Turk <mt...@apache.org>
Subject Re: apr_pool_create_core_ex, WAS: Re: svn commit: r647384 - in /apr/apr/trunk: CHANGES include/apr_pools.h memory/unix/apr_pools.c
Date Tue, 08 Jul 2008 14:03:41 GMT
Sander Striker wrote:
> On Tue, Jul 8, 2008 at 3:26 PM, William A. Rowe, Jr.
> <wrowe@rowe-clan.net> wrote:
>> Mladen Turk wrote:
>>> Again, the global allocator might get destroyed before the
>>> child pool since for it the owner is global pool.
>> Interesting observation, hinging on being a bug itself.
> 
> All pools are guaranteed to live as long as the global pool, at least
> under the previous implementation.  That ensures that the global
> allocator lives as long as any pool.  The global pool will destroy it
> once it goes away on apr_pool_terminate(), which is called by
> apr_terminate().

Of course. I wasn't talking about that.
Everything about that is clear and it works like it should.

However in some use cases this behavior requires syncing the
pool and use case object model making things very complex.
So it's just one of the pool usages where the user is responsible
for maintaining the pool's life cycle, and that's it.


Regards
-- 
^(TM)

Mime
View raw message