
25 Apr
2012
25 Apr
'12
10:21 a.m.
Étienne wrote:
This is very convenient but there usage cases where the pool should not perform any dynamic memory allocation, i.e. the maximum number of simultaneously required buffers is known at initialization. I have hence defined a simple class 'static_pool' (see below), which (i) allocate all requested buffers at initialization; (ii) fails (returns null) if more buffers are being asked for at runtime.
Does such a class has its place within the Boost Pool library ?
Sounds much like singleton_pool. Chris