Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:115958
MIME-Version: 1.0
References: <CABTDVhBRpD=nWBk2xGLEmdcWwOzCeqGeqH5vLSugPFOeEN9Mog@mail.gmail.com>
 <61339ad1.1c69fb81.b518e.8644SMTPIN_ADDED_MISSING@mx.google.com>
 <CABTDVhC9d7R0czB5mUhfcUOc--E4xe+9V2W9dWLS7oYe_5fpNA@mail.gmail.com> <6135010c.1c69fb81.c3c9e.b3a1SMTPIN_ADDED_MISSING@mx.google.com>
In-Reply-To: <6135010c.1c69fb81.c3c9e.b3a1SMTPIN_ADDED_MISSING@mx.google.com>
Date: Mon, 6 Sep 2021 09:11:30 +0700
Message-ID: <CAEZPtU4yW92GJPf56Rr5W5nYSyx9=cLz8TKp9dOic2FyWSCXug@mail.gmail.com>
To: Ben Ramsey <ramsey@php.net>
Cc: PHP internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary="0000000000008b59d505cb4a2b18"
Subject: Re: [PHP-DEV] Re: [RFC] Random Extension 3.0
From: pierre.php@gmail.com (Pierre Joye)

--0000000000008b59d505cb4a2b18
Content-Type: text/plain; charset="UTF-8"

Hi Ben,

On Mon, Sep 6, 2021, 12:40 AM Ben Ramsey <ramsey@php.net> wrote:

> Go Kudo wrote on 9/4/21 23:00:
> > Indeed, it may be true that these suggestions should not be made all at
> > once. If necessary, I would like to propose to organize the RNG
> > implementation first.
> >
>
>
> The OOP API appears to be a wrapper around the RNG functions. The only
> thing it gains by being in the core is widespread use, but it loses a
> lot of flexibility and maintainability, since the API will be tied to
> PHP release cycles.
>
> By doing this as an OOP wrapper in userland code, you're not restricting
> yourself to release only when PHP releases, and you can work with the
> community (e.g., the PHP-FIG) to develop interfaces that other projects
> might use so they can make use of their own RNGs, etc.



I tend to agree with you. However, the same logic applies to any non binary
bytes RNG, all of them derivate from there with constraints.

I suppose this is choice PHP has to take. I don't see such APIs changing
too much over time but maybe in the beginning.  It could be done in two
phases.

best,
Pierre

--0000000000008b59d505cb4a2b18--