Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:116632
Message-ID: <6b6250dc-23be-78f3-f156-c7815cc7cb71@gmail.com>
Date: Sun, 12 Dec 2021 22:20:45 +0000
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:91.0) Gecko/20100101
 Thunderbird/91.3.2
Content-Language: en-GB
To: internals@lists.php.net
References: <CAMrTa2FB-EVGq29oLCU8fYkMYi+KsQiEAFv1xxMFO7vnm8e6=Q@mail.gmail.com>
 <CA+kxMuQqGpkuqwFLrW29G38aOUNbvXM6Dq=P8NXt=1zai_=zxA@mail.gmail.com>
 <7126a5cb-fdaf-4e50-b8af-7d95965d1125@www.fastmail.com>
 <CA+kxMuROkHkVVWd0AFDweQBBNqXCkPmGqJVggGduDF6=KyZEgg@mail.gmail.com>
 <96304dc4-7577-4d4e-a1b2-63e707ea30dd@www.fastmail.com>
In-Reply-To: <96304dc4-7577-4d4e-a1b2-63e707ea30dd@www.fastmail.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 12/12/2021 22:01, Larry Garfield wrote:
> If the list of operators is expanded by the engine, yes.  The point is that IF it were decided in the future to allow user-space defined operators, that would be considerably easier with a separate keyword.


A real-life example of this approach would be PostgreSQL, where a 
user-defined operator can be (almost) any combination of + - * / < > = ~ 
! @ # % ^ & | ` ?

It would be *possible* to have an open-ended naming scheme for these, 
such as "function __atSign_leftAngle" for the operator @> (which 
conventionally means "contains" in PostgreSQL) but it would be rather 
awkward compared to "operator &>" or "#[Operator('&>')]".


Regards,

-- 
Rowan Tommins
[IMSoP]