On Wed, Jan 6, 2016 at 6:48 PM, Gilles wrote:
> On Wed, 6 Jan 2016 18:42:06 +0100, Luc Maisonobe wrote:
>
>> Le 06/01/2016 15:56, Gilles a écrit :
>>
>>> Hi.
>>>
>>> I've reread this article (which IIRC was advertised on this list some
>>> time ago):
>>> http://nvie.com/posts/a-successful-git-b
On Wed, Jan 6, 2016 at 10:32 AM, Luc Maisonobe wrote:
> Le 06/01/2016 15:19, Gilles a écrit :
> > Hi.
>
> Hi Gilles,
>
> >
> > On Tue, 05 Jan 2016 21:47:52 -, l...@apache.org wrote:
> >> Putting MATH_3_X branch to post-release state.
> >>
> >> This change is only done in case a new release sh
On Sat, Jan 9, 2016 at 9:09 PM, Gilles wrote:
> Hi.
>
> Relevant excerpt of previous posts:
>
> [...]
>>>
>>> Something implicit in "BitStreamGenerator": the maximum number of
>>> bits is 32 (cf. return type of "next(int)" and the ubiquitous use
>>> of hard-coded "32".
>>>
>>> What about the poss
Hi.
This post is related to:
https://issues.apache.org/jira/browse/MATH-1314
Problem:
Different RNGs have different ways to manage their internal state
(which is updated at each call to the "next()" function).
Some use one, or two, "int" (or "long") values, or arrays (of
varying sizes).
This
On 01/10/2016 05:09 AM, Gilles wrote:
> Hi.
>
> Relevant excerpt of previous posts:
>
>>> [...]
>>>
>>> Something implicit in "BitStreamGenerator": the maximum number of
>>> bits is 32 (cf. return type of "next(int)" and the ubiquitous use
>>> of hard-coded "32".
>>>
>>> What about the possibilit