[Dune] [#766] Separate GenericGeometries and the SmallObjectPool

Dune flyspray at dune-project.org
Fri Nov 5 00:12:35 CET 2010


THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.

The following task has a new comment added:

FS#766 - Separate GenericGeometries and the SmallObjectPool
User who did this - Carsten Gräser (Carsten)

----------
How could you do this with virtual methods?

Regarding the issue with different instances: The fact that you can allocate and deallocate is not part of the general requirement. BUT as exception all std containers are allowed to assume this. This is e.g. true for the boost pool allocator.

I still can't see the problem with the suggested approach. If we simply destroy objects the same way they are created (using the TMP) everything should work and we can use efficient and established threadsafe allocators like the one in boost.
----------

More information can be found at the following URL:
http://www.dune-project.org/flyspray/index.php?do=details&task_id=766#comment2260

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