Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:114548
To: internals@lists.php.net
References: <CAF+90c_iYjsDWoqPaDtavVgj2WFdpiuBmGeQZFAqokVoVZTxoA@mail.gmail.com>
 <CAAwdEzC7ELqrGE0PMZ7ParYEN0CrHNVP1rnSvwW=Smcvdp41-Q@mail.gmail.com>
 <1a024ec2-60c0-4a48-5f1e-4a4369a6a642@gmail.com>
 <CAGBsUrfX=oQSgD42hC5xgTWKBpWXatWFVAdbi31sBThSH=b2mA@mail.gmail.com>
Message-ID: <052eada8-dd1d-059f-6ce5-4870174b1c1f@gmail.com>
Date: Thu, 20 May 2021 22:31:50 +0100
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:78.0) Gecko/20100101
 Thunderbird/78.10.1
MIME-Version: 1.0
In-Reply-To: <CAGBsUrfX=oQSgD42hC5xgTWKBpWXatWFVAdbi31sBThSH=b2mA@mail.gmail.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
Content-Language: en-GB
Subject: Re: [PHP-DEV] [RFC] First-class callable syntax
From: rowan.collins@gmail.com (Rowan Tommins)

On 20/05/2021 21:54, Kamil Tekiela wrote:
> This would be less confusing than the (...) syntax IMHO. Of course this
> still has the same ambiguity as Rowan points out. Is ::$objA->methA a
> property or a method? We could solve this problem by specifying the syntax
> to always refer to methods/functions. Parentheses could be used to enforce
> access to property, e.g. ::($objA->methA) would evaluate the value stored
> in the public property of the object $objA


This is precisely the kind of "solution" that I referred to as easy for 
the parser but confusing for humans.

::$objA->methA // method
(::$objA->methA) // method
::($objA->methA) // property
::($objA)->methA // method?
(::$objA)->methA // attempt to access a property of a Closure object?

It's just a mess, IMHO


Regards,

-- 
Rowan Tommins
[IMSoP]