Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:123036
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Precedence: bulk
Mime-Version: 1.0 (1.0)
Subject: Re: [PHP-DEV] Proposal: Arbitrary precision native scalar type
Date: Mon, 8 Apr 2024 19:16:12 +0900
Message-ID: <C14F2898-7012-4098-93BB-B79D9040AA8C@sakiot.com>
References: <AF9C71A0-71A8-4228-A16A-555F1CA9D444@rwec.co.uk>
Cc: internals@lists.php.net
In-Reply-To: <AF9C71A0-71A8-4228-A16A-555F1CA9D444@rwec.co.uk>
To: "Rowan Tommins [IMSoP]" <imsop.php@rwec.co.uk>
From: saki@sakiot.com (Saki Takamachi)

Hi Rowan,

> Again, I don't think "has more than one attribute" is the same as "feel al=
most like objects". But we're just getting further away from the current dis=
cussion, I think.

> The proposed class is called BCMath\Number, which implies that every insta=
nce of that class represents a number, just as every instance of a class cal=
led DateTime represents a date and time.
>=20
> In the end, a class is just a type definition. In pure OOP, it defines the=
 type by its behaviour (methods / messages); in practice, it also defines th=
e properties that each value of the type needs.
>=20
> So I am saying that if you were designing a class to represent numbers, yo=
u would start by saying "what properties does every number value have?" I do=
n't think "rounding mode" would be on that list, so I don't think it belongs=
 on a class called Number.

We should cool down for now. At the very least, this is the place to discuss=
 Alex's proposal, not to comment on my RFC.

If a deeper discussion is needed, we can do that in a new thread.

Regards.

Saki=