On 02.09.2019 13:21, Dimitry Sibiryakov wrote:
02.09.2019 12:15, Alex Peshkoff via Firebird-devel wrote:
Don't gorget - 'classic' smart pointers, containers, etc. do NOT work
when object is deleted by pool.
That's why object in pool must never use non-pooled child object.
Adriano must use pooled Allocator in his SimilarMatcher for std
containers.
When first pool-enabled classes were added to firebird ~15 years ago
allocators were absolutely unable to peresent firebird pools. I doubt
basic rules of using them have changed - that can break applications
using allocators in _that_ way. But if yes - that would be great. The
first problem was object assignment - src allocator was also assigned to
target. How is it doing now?
Firebird-Devel mailing list, web interface at
https://lists.sourceforge.net/lists/listinfo/firebird-devel