StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
text
Body
copied!<p>(Edit: sorry, misread your question; previous answer removed.)</p> <p>You can use any memory pool for your objects. Usually you group together same (or similar) sized objects in the same pool. Since you usually have to call a special <code>delete</code> function on the pool I suggest you use a <code>shared_ptr</code> with a custom deleter. You can then use this <code>shared_ptr</code> with any standard container you like.</p> <p>Edit: It seems like an example is needed. Warning: this is totally untested and from the top of my head. Don't expect it to compile.</p> <pre><code>#include <boost/pool.hpp> #include <memory> class A; class B; // B inherits from A int main() { // could be global boost::object_pool<A> a_pool; boost::object_pool<B> b_pool; std::vector<std::shared_ptr<A>> v; v.push_back(std::shared_ptr<A>(a_pool.construct(), [&](A*p) { a_pool.free(p); })); v.push_back(std::shared_ptr<A>(a_pool.construct(), [&](A*p) { a_pool.free(p); })); v.push_back(std::shared_ptr<A>(a_pool.construct(), [&](A*p) { a_pool.free(p); })); v[2] = std::shared_ptr<B>(b_pool.construct(), [&](B*p) { b_pool.free(p); }); return 0; } </code></pre> <p>This will work even is B is much larger than A. It also does not rely on the automatic freeing of the pool which is IMHO dangerous. The memory layout is not tight because the pool will always overallocate, but it will have no fragmentation and this is what you want if I understood your question.</p>

Querying!

Guidance

An individual column

Larger individual text columns get their own page to allow for proper reading.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload