Le 06/07/2017 16:46, Stanislav Malyshev a écrit :
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 an
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 co
Hi Zeev,
Zeev Suraski wrote:
On 5 Jul 2017, at 19:09, Lauri Kenttä wrote:
I'm just wondering if T_PAAMAYIM_NEKUDOTAYIM could finally be changed to
T_DOUBLE_COLON in, say, PHP 8?
I for one would love not repeating that discussion once over... I realize some
people aren't fond of this toke
2017-07-05 18:47 GMT+02:00 Zeev Suraski :
> I for one would love not repeating that discussion once over... I realize
> some people aren't fond of this token, but it's at the level of harmlessness
> - and at least to some a part of the PHP folklore - that we should find
> better things to do th
On 05.07.2017 at 18:47, Zeev Suraski wrote:
>> On 5 Jul 2017, at 19:09, Lauri Kenttä wrote:
>> I'm just wondering if T_PAAMAYIM_NEKUDOTAYIM could finally be
changed to T_DOUBLE_COLON in, say, PHP 8?> > I for one would love not
repeating that discussion once over... I realize some people are
On 05.07.2017 at 18:47, Zeev Suraski wrote:
>> On 5 Jul 2017, at 19:09, Lauri Kenttä wrote:
>> I'm just wondering if T_PAAMAYIM_NEKUDOTAYIM could finally be
changed to T_DOUBLE_COLON in, say, PHP 8?> > I for one would love not
repeating that discussion once over... I realize some people are
> On 5 Jul 2017, at 19:09, Lauri Kenttä wrote:
>
>> On 2017-07-05 18:24, Rowan Collins wrote:
>>> On 5 July 2017 13:28:29 BST, "Johannes Schlüter"
>>> wrote:
On Mi, 2017-07-05 at 11:24 +0100, Rowan Collins wrote:
Firstly, I'm not sure where you got the names you've put in
ALL_CA
On 2017-07-05 18:24, Rowan Collins wrote:
On 5 July 2017 13:28:29 BST, "Johannes Schlüter"
wrote:
On Mi, 2017-07-05 at 11:24 +0100, Rowan Collins wrote:
Firstly, I'm not sure where you got the names you've put in
ALL_CAPS from, but they're not the official names of the operators
anywhere I've
On 5 July 2017 13:28:29 BST, "Johannes Schlüter" wrote:
>On Mi, 2017-07-05 at 11:24 +0100, Rowan Collins wrote:
>> Firstly, I'm not sure where you got the names you've put in
>> ALL_CAPS from, but they're not the official names of the operators
>> anywhere I've seen. The double-colon is technical
On Mi, 2017-07-05 at 11:24 +0100, Rowan Collins wrote:
> Firstly, I'm not sure where you got the names you've put in
> ALL_CAPS from, but they're not the official names of the operators
> anywhere I've seen. The double-colon is technically the "Scope
> Resolution Operator", or internally T_PAAMAYI
On 5 July 2017 at 08:08, Sebastian Bergmann wrote:
> As the deprecation / strict standards notices suggest,
>
> What do you think?
It's been deprecated for years.
An RFC to remove it would be appropriate to target PHP 8. I think
nobody remembered to propose it for PHP 7.
cheers
Dan
--
PHP Int
On 5 July 2017 08:08:48 BST, Sebastian Bergmann wrote:
>Is it intentional that the DOUBLE_COLON operator can be used on a
>variable that contains a reference to an object?
>
>class C
>{
> public function m()
> {
> print '*';
> }
>}
>
>$c = new C;
>$c::m();
>
>Until yesterday I
12 matches
Mail list logo
