Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:50597
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.213.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:content-transfer-encoding;
        b=b4hJxWvneIwHbxo6H1PHlslBE5zpMOlF2rUPz32RGbAgWuN7rpdutJPdvl83Y46j/2
         Aa2FB35aPzzu1KRbnEMRJ0zxgq1ZgmqfS5Ltu4q98kiC6gvAf6zGfI5vxmu3qfgPmISK
         Nz3cipn/XrsnQW+8UAn5OkdzEmf5PLop7yYmM=
MIME-Version: 1.0
In-Reply-To: <AANLkTimaAqhn8oG-zjh7VfSh6Y_=1xKUGV224MKXzKwG@mail.gmail.com>
References: <AANLkTimaAqhn8oG-zjh7VfSh6Y_=1xKUGV224MKXzKwG@mail.gmail.com>
Date: Fri, 26 Nov 2010 21:25:32 +0100
Message-ID: <AANLkTimeLX-aOARbJEOC-stjqCT_PAaMT7Dt0K+Eh0Jr@mail.gmail.com>
To: Felipe Pena <felipensp@gmail.com>
Cc: internals <internals@lists.php.net>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Subject: Re: [PHP-DEV] [RFC] new foo()->bar()
From: peter.e.lind@gmail.com (Peter Lind)

On 26 November 2010 20:36, Felipe Pena <felipensp@gmail.com> wrote:
> Hi all,
> I'm here again to presents another proposal, which adds support for
> instantiating a class and calling its methods and accessing its propertie=
s
> on same command.
>
> Example:
>
> <?php
>
> class bar {
> =C2=A0public $x =3D 'PHP';
> }
>
> class foo extends bar {
> =C2=A0public function bar() {
> =C2=A0 =C2=A0return $this;
> =C2=A0}
> }
>
> var_dump(new foo()->bar()->x); // string(3) "PHP"
>
> ?>
>
> Other examples which describes the feature at
> http://wiki.php.net/rfc/instance-method-call
>
> Thoughts?

It seems fairly handy and I've been in situations where I wanted to do
something like that - in fact, I use factories to achieve something
similar.
 However, the more I use it, the more it feels like introducing code
smells into my code. You're essentially instantiating an object only
to immediately throw it away. That means you don't actually need the
object at all, you should probably be looking for static methods or
class properties. Trying to avoid statics by introducing a way to
instantiate and throw away objects in the same statement feels a lot
like reinventing OOP while adding overhead.

Anyway, just a personal observation. I generally favour the way that
PHP allows you to dig your own grave (i.e. I love the freedom of the
language), so as a developer I would probably favour this as well,
though I find it mainly a way to introduce hacks.

Regards
Peter

--=20
<hype>
WWW: plphp.dk / plind.dk
LinkedIn: plind
BeWelcome/Couchsurfing: Fake51
Twitter: kafe15
</hype>