On Jan 2, 2017 6:32 AM, "Rob Tompkins" wrote:
Regarding Gilles’ last comment asking on why I think we should hold off on
putting this functionality in. It seems that we have a lively bit of
discourse here over the different varieties of offering the consumer the
best options as to how to provide
On 2 January 2017 at 14:32, Rob Tompkins wrote:
> Regarding Gilles’ last comment asking on why I think we should hold off on
> putting this functionality in. It seems that we have a lively bit of
> discourse here over the different varieties of offering the consumer the best
> options as to how
Regarding Gilles’ last comment asking on why I think we should hold off on
putting this functionality in. It seems that we have a lively bit of discourse
here over the different varieties of offering the consumer the best options as
to how to provide a uniform randomness generator to TEXT. Thus
The job of TEXT is to use the provided random source to generate the
text output.
TEXT should make it easy to use any implementation that provides the
range of input values it needs.
The choice of random source is up to the user; they are the only ones
who know what sort of randomness is needed.
T
On Sat, 31 Dec 2016 12:01:34 -0500, Rob Tompkins wrote:
Based on all the discussion and that RNG isn’t currently included in
the pom, this feels like a great 1.1 forward topic because .
[...] because ... ?
I’m going
to mark the Jira as 1.X as opposed to 1.0.
Wrt the issue of providing diffe
Based on all the discussion and that RNG isn’t currently included in the pom,
this feels like a great 1.1 forward topic because . I’m going to mark the Jira
as 1.X as opposed to 1.0.
Regarding getting this in, like I said before I’m indifferent. I think though
that this fits into the RERO area
On Sat, 31 Dec 2016 00:00:16 + (UTC), Bernd Eckenfels wrote:
The issues of the j.u.Random implementation are only for the default
implementation,
Not true, unfortunately (more than one example in the document).
if you provide a different algorithm (from
Securearandom or any distribution f
Gilles wrote:
> On Fri, 30 Dec 2016 23:05:25 +0100, Gilles wrote:
>> On Fri, 30 Dec 2016 20:00:50 +0100, Jörg Schaible wrote:
>>> Hi Gilles,
>>>
>>> Gilles wrote:
>>>
On Fri, 30 Dec 2016 17:03:56 +0100, Jörg Schaible wrote:
> Gilles wrote:
>
>> Hi.
>>
>> On Fri, 30 Dec 201
The issues of the j.u.Random implementation are only for the default
implementation, if you provide a different algorithm (from Securearandom or any
distribution from RNG) you can avoid it (if needed)
Gruss
Bernd
--
http://bernd.eckenfels.net
On Fri, Dec 30, 2016 at 10:50 PM +0100, "Gilles"
On Fri, 30 Dec 2016 23:05:25 +0100, Gilles wrote:
On Fri, 30 Dec 2016 20:00:50 +0100, Jörg Schaible wrote:
Hi Gilles,
Gilles wrote:
On Fri, 30 Dec 2016 17:03:56 +0100, Jörg Schaible wrote:
Gilles wrote:
Hi.
On Fri, 30 Dec 2016 09:40:20 -0500, Rob Tompkins wrote:
Hello all,
Personally, I
On Fri, 30 Dec 2016 20:00:50 +0100, Jörg Schaible wrote:
Hi Gilles,
Gilles wrote:
On Fri, 30 Dec 2016 17:03:56 +0100, Jörg Schaible wrote:
Gilles wrote:
Hi.
On Fri, 30 Dec 2016 09:40:20 -0500, Rob Tompkins wrote:
Hello all,
Personally, I would like to resolve the TEXT-36 and TEXT-42 Jira
On Fri, 30 Dec 2016 18:22:37 + (UTC), Bernd Eckenfels wrote:
Hello,
You suggested to use UniformRandomProvider in TEXT-36.
I suggest to use j.u.Random because it is a common (interface like)
I know that already.
To advance the discussion, could you please comment on the issues
in the docume
Hi Gilles,
Gilles wrote:
> On Fri, 30 Dec 2016 17:03:56 +0100, Jörg Schaible wrote:
>> Gilles wrote:
>>
>>> Hi.
>>>
>>> On Fri, 30 Dec 2016 09:40:20 -0500, Rob Tompkins wrote:
Hello all,
Personally, I would like to resolve the TEXT-36 and TEXT-42 Jira
tickets before proceeding
Hello,
You suggested to use UniformRandomProvider in TEXT-36.
I suggest to use j.u.Random because it is a common (interface like) type which
is easy to provide any alternative random provider you would want (on protected
method to implement) - just like InputStream is a commonly subtyped base cla
On Fri, 30 Dec 2016 17:30:17 + (UTC), Bernd Eckenfels wrote:
Sorry I meant *uniform* distribution
Gruss
Bernd
On Fri, Dec 30, 2016 at 5:58 PM +0100, "Bernd Eckenfels"
wrote:
Hello,
I am somewhat unclear, why would you require a random distribution
(Interface).
Who said?
I
On Fri, 30 Dec 2016 17:03:56 +0100, Jörg Schaible wrote:
Gilles wrote:
Hi.
On Fri, 30 Dec 2016 09:40:20 -0500, Rob Tompkins wrote:
Hello all,
Personally, I would like to resolve the TEXT-36 and TEXT-42 Jira
tickets before proceeding with the release, but I wanted to check
to
see if anyone
We could add the dep for a 1.1 or 2.0 release but removing the dep would be
more painful for users that end up depending on it. The question is: how
much benefit do we really get for TEXT from a dep on RNG.
Gary
On Dec 30, 2016 6:40 AM, "Rob Tompkins" wrote:
> Hello all,
>
> Personally, I would
Sorry I meant *uniform* distribution
Gruss
Bernd
On Fri, Dec 30, 2016 at 5:58 PM +0100, "Bernd Eckenfels"
wrote:
Hello,
I am somewhat unclear, why would you require a random distribution (Interface).
Is there no better more generic Interface in RNG-API? Having said that I still
Hello,
I am somewhat unclear, why would you require a random distribution (Interface).
Is there no better more generic Interface in RNG-API? Having said that I still
think j.u.Random is fine - but if not maybe a byte or int Provider would be
better than a specific interface for the random source
Gilles wrote:
> Hi.
>
> On Fri, 30 Dec 2016 09:40:20 -0500, Rob Tompkins wrote:
>> Hello all,
>>
>> Personally, I would like to resolve the TEXT-36 and TEXT-42 Jira
>> tickets before proceeding with the release, but I wanted to check to
>> see if anyone else has any opinions on what work needs to
Hi.
On Fri, 30 Dec 2016 09:40:20 -0500, Rob Tompkins wrote:
Hello all,
Personally, I would like to resolve the TEXT-36 and TEXT-42 Jira
tickets before proceeding with the release, but I wanted to check to
see if anyone else has any opinions on what work needs to be
completed
before the releas
Hello all,
Personally, I would like to resolve the TEXT-36 and TEXT-42 Jira tickets before
proceeding with the release, but I wanted to check to see if anyone else has
any opinions on what work needs to be completed before the release.
Regarding TEXT-36: 'Dependency on “Commons RNG” ‘, I’m rela
22 matches
Mail list logo
