Den 16-01-2011 16:13, Domagoj Saric skrev:
"Thorsten Ottosen" <nesotto@cs.aau.dk> wrote in message news:4D2AB8C0.7070700@cs.aau.dk...
I expect to finnish pre-review work in february.
Could you possibly add a policy that would 'produce' a strictly static buffer, i.e. that does not use/expand into the heap (to avoid the overhead described in the response to David Bergman)...
Maybe. I guess it takes some measurement to see if it is actually needed. For one, the container will allow you to do boost:.auto_buffer<T,N> buffer( n, boost::dont_initialize ); to make it avoid initialization. Futhermore, you may use buffer.unchecked_push_back( x ); to avoid code that checks for a full buffer and subsequent expansion. If that is not good enough, then why not just use boost::array<T,N>? (that is, if you really never will need the heap for any n) -Thorsten