Re: [MERGE] Split MemPool.cc into framework and allocators

From: Henrik Nordström <henrik_at_henriknordstrom.net>
Date: Sat, 29 May 2010 14:04:51 +0200

lör 2010-05-29 klockan 22:36 +1200 skrev Amos Jeffries:

> That single squid_curtime dependency is exactly the remaining problem
> with the non-squid binaries in AIX and Cygwin builds. Despite the
> binaries that are breaking making no use of this memory code.

That dependency never brings in the memory pool code. It makes it harder
to use the MemPools outside Squid however.

But MemPools.cc overloads the new & delete operators which means any
code bring in if it's in the link line.

> The ones which don't match the portability scope of libcompat are moving
> to src/ yes. The shell definitions of xmalloc/xcalloc/xfree with safety
> checks fall under portability, but the full pool allocator
> implementation does not.
>
> 'tis only relevant for 3.2 now though.

Ok.

Regards
Henrik
Received on Sat May 29 2010 - 12:04:56 MDT

This archive was generated by hypermail 2.2.0 : Sat May 29 2010 - 12:00:12 MDT