Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:99782
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 74.125.83.48 as permitted sender)
To: internals@lists.php.net, Sebastian Bergmann <sebastian@php.net>
References: <827b77ce-f2b7-930a-34cb-ce11ebc2d531@php.net>
Message-ID: <4dc7b920-6f34-8f39-0fe8-8a289ae67f3f@gmail.com>
Date: Wed, 5 Jul 2017 21:46:56 -0700
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:52.0)
 Gecko/20100101 Thunderbird/52.2.1
MIME-Version: 1.0
In-Reply-To: <827b77ce-f2b7-930a-34cb-ce11ebc2d531@php.net>
Content-Type: text/plain; charset=utf-8
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] OBJECT_OPERATOR vs. DOUBLE_COLON
From: smalyshev@gmail.com (Stanislav Malyshev)

Hi!

> I think that using :: on a variable that contains an object should not
> "fall back" to a static access on the object's class. Instead the
> runtime should error out.

Why should it not do what it does now? What would it achieve? I don't
see any improvement in changing that - it may break code that is using
this facility, and it won't make anything better. True, this is an
exotic and non-obvious feature, but many languages have such features,
which are used only by people that need them. If we proposed to add such
feature, true, it may be too exotic to be added on its own merits, but
since it is already there (and, probably, used in some code somewhere) -
why bother messing with it? I don't see how just leaving it be hurts
anything.

-- 
Stas Malyshev
smalyshev@gmail.com