Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:56693
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.213.170 as permitted sender)
Mime-Version: 1.0 (Apple Message framework v1251.1)
Content-Type: text/plain; charset=iso-8859-1
In-Reply-To: <4ED68940.3050502@ralphschindler.com>
Date: Wed, 30 Nov 2011 14:58:17 -0500
Cc: Nikita Popov <nikita.ppv@googlemail.com>,
 internals <internals@lists.php.net>
Content-Transfer-Encoding: quoted-printable
Message-ID: <90D867E2-E6FB-481D-B57C-911E5FE6A418@gmail.com>
References: <4ED6713D.2050009@ralphschindler.com> <CAF+90c8vKhvOO3qTPgN2TsV-=Vsw0G14B=-HQbD1YZw-Wt6bmg@mail.gmail.com> <4ED67DCB.5090102@ralphschindler.com> <CAF+90c8-MAxO-39iwAhpqgqkpbM5g5y7URd9_JJQFCa=+jw5zg@mail.gmail.com> <4ED68940.3050502@ralphschindler.com>
To: Ralph Schindler <ralph@ralphschindler.com>
Subject: Re: [PHP-DEV] 5.4's New De-referencing plus assignment
From: will.fitch@gmail.com (Will Fitch)

If that's the case, then why not just add whatever $options is as a =
parameter to your constructor.  I'm not totally against this concept, =
but this use is moot.

On Nov 30, 2011, at 2:51 PM, Ralph Schindler wrote:

> Ironically, quite the opposite is something I find useful:
>=20
> ($foo =3D new MyComponent($bar))->configure($options);
>=20
> In a single line, instantiate and configure (via an API call) an =
object.  The return of configure() is not important to me, but the =
brevity of that workflow, and the result of "new" is.
>=20
> -ralph
>=20
>=20
> On 11/30/11 1:13 PM, Nikita Popov wrote:
>> To me the main problem here is that $bar =3D ($foo =3D new =
Foo)->bar()
>> simply doesn't make much sense. It is equivalent to:
>> $foo =3D new Foo;
>> $bar =3D $foo->bar();
>> Which is much cleaner and easier to understand.
>>=20
>> The plain (new Foo)->bar() syntax *is* useful for cases like (new
>> ReflectionClass($class))->implementsInterface('Foo'), where you need
>> only one single bit of information from a class.
>>=20
>> Nikita
>>=20
>> On Wed, Nov 30, 2011 at 8:02 PM, Ralph Schindler
>> <ralph@ralphschindler.com>  wrote:
>>> Nikita,
>>>=20
>>> You're completely right about the expanded expressions, but I'm not =
sure its
>>> an edge-case per-se.
>>>=20
>>> The problem with the current syntax is that the resultant of the =
'new'
>>> operation is lost UNLESS your chained method returns $this - which =
IMO makes
>>> it about as 1/2 as useful as it really could be.
>>>=20
>>> In the case of "new" though, the resultant is always an object, it =
seems
>>> like it should be permissible to change the parser to allow for =
variable
>>> assignment of the target object.
>>>=20
>>> I think for people just trying out this new behavior (by seeing it =
in the
>>> release notes as (new Foo)->bar()), the next logical thing is to try =
this
>>> syntax:
>>>=20
>>>  ($foo =3D new Foo)->bar()
>>>=20
>>>  // OR in bison
>>>  '(' variable '=3D' new_expr ')'
>>>=20
>>> I did it, and I see other people doing it too. So I guess the =
question is...
>>> "how edge case is this edge case?" :)
>=20
>=20
> --=20
> PHP Internals - PHP Runtime Development Mailing List
> To unsubscribe, visit: http://www.php.net/unsub.php
>=20