Re: Assertion tripped in boost::uniform_int

From: matts_temp_id (mvogt_at_[hidden])
Date: 2003-07-14 19:12:08

I'm not quite following here, I'm sorry.

I believe David was asking whether I called my own function with
parameters min == max, which would have resulted in a call to
boost::random_number_generator<RNG, T>(1).

Which min == max condition are you referring to?  Is that the internal
effect of invoking random_number_generator(1)?

Matt.

--- In Boost-Users_at_[hidden], Jens Maurer <Jens.Maurer_at_g...>
wrote:
> matts_temp_id wrote:
> > > I presume that you sometimes call random with min = max ?
> > 
> > Well, that's not my intention, but I can't assert that it didn't
> > happen in this case - there are some data-dependent invocations
of the
> >  random number generator.
> 
> The current code does not handle the case min == max.
> There have been other people who requested that this should work
> and do the obvious thing (i.e. always return min).
> 
> I've checked in to the current CVS a fix that allows min == max
> for uniform_int.
> 
> Jens Maurer