Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:116240
MIME-Version: 1.0
References: <CABTDVhBRpD=nWBk2xGLEmdcWwOzCeqGeqH5vLSugPFOeEN9Mog@mail.gmail.com>
 <CAF+90c-kLHe-M4jcMRa=_8Lhakcyrtam109WKga6XLQqmJYp0Q@mail.gmail.com>
 <CABTDVhBYB1-TkxTNPCkedE0k0UBWv0eUNfmSr+KDWkpgcw12JA@mail.gmail.com>
 <CA+kxMuR21VF3Ax-N7ensrNAhs1O9kVQn=BuEBqoMV4FmDHpF0g@mail.gmail.com>
 <CABTDVhA_zAfRPx+9AtFUzVWySOaU6kG0H1Dxhsg2Gn3M0fTkQw@mail.gmail.com> <CA+kxMuSMmjB2fc=KDfi8SZch6378RDaY4enbV_w1YYecptN-aA@mail.gmail.com>
In-Reply-To: <CA+kxMuSMmjB2fc=KDfi8SZch6378RDaY4enbV_w1YYecptN-aA@mail.gmail.com>
Date: Thu, 7 Oct 2021 22:00:07 +0900
Message-ID: <CABTDVhA+byGMoKGiuqHttySJjp3BL=ywxwyom0b0yGvNsQWUVA@mail.gmail.com>
To: Dan Ackroyd <Danack@basereality.com>, PHP internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary="0000000000003deec805cdc2d837"
Subject: Re: [PHP-DEV] [RFC] Random Extension 3.0
From: zeriyoshi@gmail.com (Go Kudo)

--0000000000003deec805cdc2d837
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

2021=E5=B9=B49=E6=9C=8823=E6=97=A5(=E6=9C=A8) 2:05 Dan Ackroyd <Danack@base=
reality.com>:

> Go Kudo wrote:
> > Dan Ackroyd wrote:
> >> you can _simply_ include ext/random/random.h." sounds pretty
> >> dismissive of causing possibly unneeded work for downstream projects.
> >
> > The point I was trying to make was that while BC Breaks do occur, they
> are very easy to solve.
>
>
> I've found it useful to think about "value =3D benefit minus cost".
>
> I was calling out that it seems to be that this is a change you want
> to do for aesthetic reasons and are justifying it by trivialising the
> work involved. i.e. it has a tiny benefit that only has a positive
> value if the cost is also tiny.
>
> Although the change is simple:
>
> * Any code base that includes standard/php_rand.h won't compile, and
> people will have to find out what changed. Even though the fix may be
> easy to implement, each of those people will have to figure it out for
> themselves.
>
> * quite a few people will have to learn (or relearn) how to use #if to
> compare PHP version to include either standard/php_rand.h or
> random/php_random.h if they want their code to work on more than 1 PHP
> version.
>
> * it makes more work for downstream distributors of PHP, as their
> patches (including security patches) will need to be moved around.
>
> If there's a good reason to move stuff around, then fine, but avoiding
> creating extra work downstream is worth doing. And possibly is a hot
> topic right now.
>
> You could probably avoid a lot of downstream work by leaving a stub
> file at standard/php_rand.h that includes random/php_random.h.
>
> cheers
> Dan
> Ack
>
> btw, if you could please avoid top-posting, that would be appreciated:
> https://github.com/php/php-src/blob/master/docs/mailinglist-rules.md
>
> "Do not top post. Place your answer underneath anyone you wish to
> quote and remove any previous comment that is not relevant to your
> post."
>

I apologize for not knowing the rules of ML.
Is this correct?

It is true that it is better to maintain compatibility that can be
maintained.
However, I think this should be sorted out sometime. Perhaps it will be in
PHP 9.0.

First of all, I would like to change these RFC and implementations.

https://wiki.php.net/rfc/random_ext
https://wiki.php.net/rfc/rng_extension

Thank you.

--0000000000003deec805cdc2d837--