Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:115324
MIME-Version: 1.0
References: <CABTDVhD9SKNVFrt8NMj4BqdHmsMpSt0DH=SMmb-9C905rgc7PA@mail.gmail.com>
 <CAF+90c9LNqgF9JJgXY_cNbX4hY9hU2QaCNViNpy25YFLeKgzLQ@mail.gmail.com>
 <CABTDVhCJge1sodik-xqdGqJ1seU6xHWjwXhUSQK_-+h5Lqyqdg@mail.gmail.com> <03e301d76f76$8e2f7d60$aa8e7820$@jhdxr.com>
In-Reply-To: <03e301d76f76$8e2f7d60$aa8e7820$@jhdxr.com>
Date: Tue, 6 Jul 2021 23:30:49 +0900
Message-ID: <CABTDVhAi-AGpFPRLS2hurpaJ20f3cgu2bjNuDmg-3qdcJLT=kg@mail.gmail.com>
To: CHU Zhaowei <me@jhdxr.com>, PHP internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary="0000000000005399a205c6754512"
Subject: Re: [PHP-DEV] [RFC] Add Random Extension (before: Add Random class)
From: zeriyoshi@gmail.com (Go Kudo)

--0000000000005399a205c6754512
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

I was late in noticing the email. I'm sorry.

>  I still feel we should find a better name for them.

This is based on Java's Random.nextInt(), which may indeed be confusing.
How about generateInt()?

>  What's the range of its return? It's not clear in the RFC.

Currently, there is no way to check this, but we believe that since the RNG
implementation is now class-based, there is no need to check this anymore.
The size of the RNG to be generated is clear at the time of implementation,
and implementing a way to check this would override the method and break
consistency.

Regards,
Go Kudo

2021=E5=B9=B47=E6=9C=883=E6=97=A5(=E5=9C=9F) 4:15 CHU Zhaowei <me@jhdxr.com=
>:

> >> "Why does this method exist at all? When would you use it instead of
> >> getInt()?"
> >>
> > The case for this would be if you want to get a raw unrounded random
> number sequence as a number. The situations where this is required would
> certainly be limited, but it would be nice to have. (At least, I know of
> several production codes that use the result of mt_rand() with no
> arguments.)
>
> These two methods confused me at first as well, but I think it's ok with
> me after I check the documentation of mt_rand(), which also supports
> calling without range. So, compatibility is one of the reasons why this
> method exists, although I still feel we should find a better name for the=
m.
> They are too similar now, you won't be able to tell the difference withou=
t
> looking into the documentation or source code.
>
> Besides the name issue, I have another question for nextInt(). What's the
> range of its return? It's not clear in the RFC. The range of mt_rand()
> (without min and max) is 0 to mt_getrandmax(), so how about nextInt()? is
> there any equivalent method/constant for it?
>
> Regards,
> CHU Zhaowei
>
>
>
>

--0000000000005399a205c6754512--