Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:119220
MIME-Version: 1.0
References: <CAFPFaMJFQOzHmvAM9_fWRQvK64GBBjeZkBEM34LqnjNSuov_pg@mail.gmail.com>
 <97df3b41-316e-0f83-09ce-d1d416eb7616@bastelstu.be>
In-Reply-To: <97df3b41-316e-0f83-09ce-d1d416eb7616@bastelstu.be>
Date: Sat, 31 Dec 2022 00:50:44 +0100
Message-ID: <CAJmy8YGYouus+-9FEhXa5+Td5R_CVdrsj_DdKseYAUdb6Q4sUg@mail.gmail.com>
To: =?UTF-8?Q?Tim_D=C3=BCsterhus?= <tim@bastelstu.be>
Cc: "G. P. B." <george.banyard@gmail.com>, PHP internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary="000000000000cc2a4b05f11445af"
Subject: Re: [PHP-DEV] What to do with opaque GMP objects which allows instantiation
From: divinity76@gmail.com (Hans Henrik Bergan)

--000000000000cc2a4b05f11445af
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

Why isn't that generating an ArgumentCountError?

On Fri, Dec 30, 2022, 21:36 Tim D=C3=BCsterhus <tim@bastelstu.be> wrote:

> Hi
>
> On 12/30/22 18:36, G. P. B. wrote:
> >   - Add a proper constructor that does the same as gmp_init() in
> master/8.2.1
>
> My preference would be this (without any target branch preference):
>
> If there is no technical reason to disallow creating new GMP objects via
> 'new', then I believe that making those objects behave more like
> "regular" / "userland" objects is a good thing.
>
> Best regards
> Tim D=C3=BCsterhus
>
> --
> PHP Internals - PHP Runtime Development Mailing List
> To unsubscribe, visit: https://www.php.net/unsub.php
>
>

--000000000000cc2a4b05f11445af--