Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:116695
Message-ID: <7285dd63-42f4-dcd1-6549-178157858abd@gmail.com>
Date: Tue, 21 Dec 2021 09:12:47 +0000
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:91.0) Gecko/20100101
 Thunderbird/91.4.0
Content-Language: en-GB
To: internals@lists.php.net
References: <CAMrTa2FB-EVGq29oLCU8fYkMYi+KsQiEAFv1xxMFO7vnm8e6=Q@mail.gmail.com>
 <44b3fb4b-4693-1639-c8c0-5e17296c196e@gmail.com>
 <CAMrTa2E9STK3G52mnQ9UsrUqi_bH4SMUzcE76PEGcxcLzGPVZA@mail.gmail.com>
 <4b58c011-ed87-ba87-201d-0cf8e4116c6f@processus.org>
 <CAB-BujbjgBBNdLjf+8SxWKJrv3J3CU8Mv51n4AkCwpsOt5WekA@mail.gmail.com>
 <CAMrTa2Fk2R8PB77Ws7dcfwRw-NWfmH4AzJkNgehA1WR4Nr1StQ@mail.gmail.com>
 <CAJF_ukUKYdwyQ8g2VScOxtpSfUR7R5VjeDWcxCXRTeqAGU1E5A@mail.gmail.com>
 <67431363-cd1e-9575-7d51-0f4d265d05b9@gmail.com>
 <CA+kxMuSehufPoGWSF-Wi_spk550O0Cm6DDQQBgYeaLGZbMZESA@mail.gmail.com>
 <CAB-BujZTaANvFQPYzAuc7ap9J8zpSk2Bu9oGGZexvr5rEqQy5Q@mail.gmail.com>
In-Reply-To: <CAB-BujZTaANvFQPYzAuc7ap9J8zpSk2Bu9oGGZexvr5rEqQy5Q@mail.gmail.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] [RFC] User Defined Operator Overloads (v0.6)
From: rowan.collins@gmail.com (Rowan Tommins)

On 21/12/2021 00:43, Andreas Hennings wrote:
> I think the example in the RFC is interesting, but not ideal to
> advertise the RFC.
> The example is with native scalar types and build-in operator implementations.
> (I don't know how GMP works internally, but for an average user of PHP
> it does not make sense to call this "overloaded")


I think you have misunderstood the example. GMP doesn't work with scalar 
types, it works with its own objects; the general approach is to call 
gmp_init() with a string describing a large number that cannot be 
represented by a PHP integer. This gives you an object which doesn't 
have any methods (it replaced a resource in older versions), but can be 
used with the gmp_* functions, and with mathematical operators 
overloaded in the engine.

So the questions you posed are not hypothetical:

> - Are those variables scalar values, or objects?
> - Are the operators using the built-in implementation or some custom
> overloaded implementation? (depends on the operand types)
> - Are the return values or intermediate values scalars or objects?

They are objects, using an overloaded implementation of the operators, 
and returning more objects.

The only difference is that right now, you can only overload operators 
in an extension, not in userland code.

Regards,

-- 
Rowan Tommins
[IMSoP]