Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:50625
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.214.42 as permitted sender)
DomainKey-Status: bad
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:in-reply-to:references:from:date:message-id:subject:to
         :cc:content-type;
        b=cf8Oiw8hpxar2ZK6M+KAqNW8/+IDNEpTSl2YfKBGTDxFdHUupD3zn5gWE/dqJVt2Fj
         aQXtYvQjAJnwssiuu8tr6AlEoifW5MZD13WCDAj/80sWzLAyGAdYb55WIN3bhstc1YX/
         Kk7yzhQGIg0fJSBik3PaGFV1ilCCFJTx1stLg=
MIME-Version: 1.0
In-Reply-To: <AANLkTintZ=1Zhk=HsAiEBOKbKMF=A=1K9Qgn8-KKYkzm@mail.gmail.com>
References: <AANLkTimaAqhn8oG-zjh7VfSh6Y_=1xKUGV224MKXzKwG@mail.gmail.com>
 <1290802903.7033.772.camel@guybrush> <AANLkTintZ=1Zhk=HsAiEBOKbKMF=A=1K9Qgn8-KKYkzm@mail.gmail.com>
Date: Sat, 27 Nov 2010 15:08:30 -0200
Message-ID: <AANLkTim1c1qdLvWa+z6-XuELrajKs0X=wzAQErLcaHMB@mail.gmail.com>
To: =?UTF-8?Q?Johannes_Schl=C3=BCter?= <johannes@schlueters.de>
Cc: internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary=001636c5c272b10b0c04960be4ba
Subject: Re: [PHP-DEV] [RFC] new foo()->bar()
From: felipensp@gmail.com (Felipe Pena)

--001636c5c272b10b0c04960be4ba
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

Hi,

2010/11/26 Felipe Pena <felipensp@gmail.com>

> 2010/11/26 Johannes Schl=C3=BCter <johannes@schlueters.de>
>
> On Fri, 2010-11-26 at 17:36 -0200, Felipe Pena wrote:
>> > var_dump(new foo()->bar()->x); // string(3) "PHP"
>>
>> It has some readability issues. One might assume it is
>>
>>    new (foo()->bar()->x)
>>
>> not
>>
>>    (new foo())->bar()->x
>>
>> As there is a mandatory space between "new" and its operand and no space
>> in front of the object operator and we allow non-constant operands to
>> "new".
>>
>> So what is
>>
>>    new $bar->foo();
>>
>> ? If I read the patch correctly this is valid and evaluated as
>>
>>   (new $bar)->foo();
>>
>> johannes
>>
>>
>
> new foo()->bar() should be read as: (new foo())->bar().
>
> And using variable:
>
> new $bar->y()->x should be read as: (new ($bar->y)())->x.
>
> <?php
>
> class foo {
> public $x =3D 1;
> }
>
> class bar {
> public $y =3D 'foo';
> }
>
> $bar =3D new bar;
>
> var_dump(new $bar->y()->x); // 1
>
>  ?>
>
> I.e. just as it is nowdays.
>


Well, if this feature is going to be accept, we could to decide what syntax
to use.
I have created another patch which is the bracketed version of this
presented here.

<?php

class foo {
public $x =3D 1;
}

class bar {
public $y =3D 'foo';
}

$x =3D 'bar';

$bar =3D new bar;

var_dump((new bar)->y); // foo
var_dump((new $x)->y); // foo
var_dump((new $bar->y)->x); // 1

?>

Thus we do not have the readability issues, as pointed by Johannes.

http://wiki.php.net/rfc/instance-method-call (updated!)


Thanks for the comments.

--=20
Regards,
Felipe Pena

--001636c5c272b10b0c04960be4ba--