
4 Nov
2011
4 Nov
'11
4:35 p.m.
On Fri, Nov 4, 2011 at 5:02 PM, Andrey Semashev <andrey.semashev@gmail.com> wrote:
That sounds like a good idea.
Great. Does anyone else have comments / concerns about a (size_t) constructor?
I still don't like the idea. If you really want to add this feature, please
Why not?
retain the current interface intact. You could add a special manipulator to make the allpcation request explicit, like this:
What *exactly* is the interface you'd like to retain?
boost::scoped_array< int > p(boost::allocate_count(10));
Here allocate_count is a simple class that holds the size of the array to be allocated. Alternatively, Boost.Parameter could be used, but it is quite heavy for such basic tools like smart pointers.
-- Olaf