[container] documentation
Hi Ion, I read over the documentation for Container. Looks like a neat library. I like the idea of a next gen STL in Boost. In the documentation, I think the recursive containers section could spell out what's going on here - I didn't catch it at first. It could just say "Recursive data structures contain elements of their own type." Perhaps with a link to http://en.wikipedia.org/wiki/Recursive_data_type. Pretty cool. Didn't this grow out of Interprocess? I'm wondering if it has somehow an improved contract with the allocator to support shared memory - or is that worth talking about? Cheers, Gordon
El 23/01/2011 19:43, Gordon Woodhull escribió:
Hi Ion,
I read over the documentation for Container. Looks like a neat library. I like the idea of a next gen STL in Boost.
In the documentation, I think the recursive containers section could spell out what's going on here - I didn't catch it at first. It could just say "Recursive data structures contain elements of their own type." Perhaps with a link to http://en.wikipedia.org/wiki/Recursive_data_type. Pretty cool.
Thanks, I'll add this.
Didn't this grow out of Interprocess? I'm wondering if it has somehow an improved contract with the allocator to support shared memory - or is that worth talking about?
Yes, it supports some special functions, also new allocation schemes like explained in: http://www.drivehq.com/web/igaztanaga/allocplus/ But those contracts are yet experimental. Best, Ion
I'm wondering if it has somehow an improved contract with the allocator to support shared memory - or is that worth talking about?
Yes, it supports some special functions, also new allocation schemes like explained in:
Oh cool, this is (a bit more than ;) what I was looking for in the Container documentation.
But those contracts are yet experimental.
Does this mean they are not documentable yet? Cheers, Gordon
El 24/01/2011 0:37, Gordon Woodhull escribió:
I'm wondering if it has somehow an improved contract with the allocator to support shared memory - or is that worth talking about?
Yes, it supports some special functions, also new allocation schemes like explained in:
Oh cool, this is (a bit more than ;) what I was looking for in the Container documentation.
But those contracts are yet experimental.
Does this mean they are not documentable yet?
No, I implemented those contracts to experiments a bit with allocplus (https://svn.boost.org/trac/boost/wiki/LibrariesUnderConstruction, see Allocplus) and Interprocess also uses them. I think those contracts need some more discussion to propose an extended, performance related allocator interface. Then Boost.Container could support such allocators. At the moment, Boost.Container aims to support shared memory containers and move semantics. In the short term, it should implement C++0x container requirements, including stateful allocator protocols. Best, Ion
participants (2)
-
Gordon Woodhull -
Ion Gaztañaga