Re: [boost] [circular_buffer] why is there no reserve(size_type)?
because: 1) it's behaviour is slightly different from the standard - you can increase but also decrease the capaciry of the container; decreasing of the capacity is not supported by reserve() 2) the word capacity is used all over the documentation of the circular buffer. I think set_capacity expresses better what the method does. Jan ----- Original Message ---- From: Steven Watanabe <watanabesj@gmail.com> To: boost@lists.boost.org Sent: Wednesday, 11 June, 2008 3:49:21 PM Subject: Re: [boost] [circular_buffer] why is there no reserve(size_type)? AMDG Jan Gaspar wrote:
it is called set_capacity(capacity_type)
Why is this different from the standard library name? In Christ, Steven Watanabe _______________________________________________ Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost __________________________________________________________ Sent from Yahoo! Mail. A Smarter Email http://uk.docs.yahoo.com/nowyoucan.html
Jan Gaspar skrev:
because: 1) it's behaviour is slightly different from the standard - you can increase but also decrease the capaciry of the container; decreasing of the capacity is not supported by reserve() 2) the word capacity is used all over the documentation of the circular buffer. I think set_capacity expresses better what the method does.
So the function is slightly different from the one in std::vector :-) Having a reserve() won't hurt ... in fact, it will make it easier to write code that works for both vector and circular_buffer. -Thorsten
participants (2)
-
Jan Gaspar -
Thorsten Ottosen