[Dune] [#1126] support PoolAllocator to allocate more than one object at a time
Dune
flyspray at dune-project.org
Sat Jun 9 00:22:33 CEST 2012
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.
The following task has a new comment added:
FS#1126 - support PoolAllocator to allocate more than one object at a time
User who did this - Markus Blatt (mblatt)
----------
Exactly! And that is consistent with the current behaviour.
First of all the pool is never filled (until the system runs out of memory). The pool is a linked list of memory chunks of static size. Whenever there is no memory left in th pool, a new chunk is allocated and added to the list.
Second of all your understanding of max_size is backed up by the standard.
max_size: The number of elements of type T that might be allocated as maximum by a call to member allocate. (Personally I would not expect this number to change between calls.)
----------
More information can be found at the following URL:
http://www.dune-project.org/flyspray/index.php?do=details&task_id=1126#comment3706
You are receiving this message because you have requested it from the Flyspray bugtracking system. If you did not expect this message or don't want to receive mails in future, you can change your notification settings at the URL shown above.
More information about the Dune
mailing list