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

[Dune]

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 - Martin Nolte (nolte)

----------
The idea looks great. The problem is just that you are using new / delete to allocate memory for the deleter. But the idea of using an allocator is exactly to avoid new / delete.

Moreover, in the case of the GenericGeometries, performance is of the utmost importance. Therefore, the solution should not involve an unnecessary function call just to avoid the use of a different interface. If we want to replace the PolyAllocator solution by an STL allocator solution, the latter one may not have _any_ impact on the performance. I am not trying to say there is no such solution, I just don't see it. Somehow, the STL allocators seem rather limited to me.
----------

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

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.