Unclear behavior of parameter 'max_size'

[edupuis]

When constructing a pool, a 'max_size' parameter can be given. If non zero, the documentation states that the pool will not allow more than 'max_chunks' at once.

However, this restriction is not taken into account in function ordered_malloc(n) :

boost::pool<> p(sizeof(int), 16, 16);

void *ptr = p.ordered_malloc(32);  // Succeeds

Either the documentation should be precised, either the illustrated allocation should fail.

[edupuis]

(In [78337]) Improved coherency between 'next_size' and 'max_size'; the first one is now always smaller or equal to the second one. No mallocs of more than 'max_size' chunks at once are allowed. Documentation will need update. This fixes #6867.

[edupuis]

​https://svn.boost.org/svn/boost/sandbox/pool at revision 79460 contains a solution for tickets #3789, #5902, #6561, #6610, #6701, #6718, #6865 and #6867. Related test cases are also present.

​https://svn.boost.org/svn/boost/sandbox/pool at revision 79460 does not contain any other new features or modifications other than those related to the above tickets.

Boost.Pool currently has no maintainer and is thus orphaned.