Re: [boost] Re: circular_buffer?

From: Doug Gregor (gregod_at_[hidden])
Date: 2001-02-28 11:53:01

On Wednesday 28 February 2001 05:24, Moore, Paul wrote:
> From: Doug Gregor [mailto:gregod_at_[hidden]]
>
> > On Tuesday 27 February 2001 01:49, boost_at_[hidden] wrote:
> > > Actually, neither of these is what I'm looking for.
> >
> > Why not supply a traits class to determine what to do when
> > the buffer is full? Then the decision is left to the user.
> > Here's a rough outline supporting the three possibilities
> > (throw an exception, increase size, do nothing):
>
> The requested form isn't exactly "do nothing", it's "wrap and overwrite".
> If that's implicit in the (to my mind over-) general concept, then that's
> fine.

The overflow handling does nothing, in effect performing a "wrap and 
overwrite". 

> I have to admit that I still don't see the point of the resizing versions -
> if you want something that allows you to add entries indefinitely, why not
> use one of the existing library classes (say, deque)? As far as I can see,
> the ONLY POINT to circularity is the overwriting property (for all sorts of
> MRU-type lists).

Other applications may require different behavior, and there is no reason not 
to support this;

        Doug