Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:66252
Return-Path: <felipensp@gmail.com>
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Delivered-To: mailing list internals@lists.php.net
Received: (qmail 26184 invoked from network); 26 Feb 2013 17:44:27 -0000
Received: from unknown (HELO lists.php.net) (127.0.0.1)
  by localhost with SMTP; 26 Feb 2013 17:44:27 -0000
Authentication-Results: pb1.pair.com smtp.mail=felipensp@gmail.com; spf=pass; sender-id=pass
Authentication-Results: pb1.pair.com header.from=felipensp@gmail.com; sender-id=pass
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.215.41 as permitted sender)
X-PHP-List-Original-Sender: felipensp@gmail.com
X-Host-Fingerprint: 209.85.215.41 mail-la0-f41.google.com  
Received: from [209.85.215.41] ([209.85.215.41:38587] helo=mail-la0-f41.google.com)
	by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP
	id F6/46-16132-A74FC215 for <internals@lists.php.net>; Tue, 26 Feb 2013 12:44:27 -0500
Received: by mail-la0-f41.google.com with SMTP id fo12so4191325lab.28
        for <internals@lists.php.net>; Tue, 26 Feb 2013 09:44:24 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=gmail.com; s=20120113;
        h=x-received:mime-version:in-reply-to:references:from:date:message-id
         :subject:to:cc:content-type;
        bh=NuivHarmwrgyrLmt3V5sL+ZzovhjE9dnzRpXTZVBHCo=;
        b=WbJ6llEM4q50onCK8fxThr2PJz+hcgYvyVv+XirMjcj+14auRs1u8pgo/H4ZHWOTDB
         vn1dqmaoRO7WhgV9LWBQs/txYhRPvKKIOmvdShJAX83lYBe9F1jeeAq6w048nXDfiOiz
         y9HdnJnKvS0bQpMw5rSKuLzzLGq9ZCCjctrF3Kq2s3cwyrfLtmpBajRat3uqZg+P4ere
         +vtW8+WmHDlommWBhQpJWhmnUafC2/w9/oYcE5O1T5o1MlzyezMhMyHc6Vmx2v3f8rRZ
         cEC05vf03h5unstJtuXSsc7sb2N7184LBhiSfp12twWOyZbgoKxrVWoDHgVXbltxRzGp
         aE6w==
X-Received: by 10.152.148.133 with SMTP id ts5mr14497461lab.2.1361900664061;
 Tue, 26 Feb 2013 09:44:24 -0800 (PST)
MIME-Version: 1.0
Received: by 10.112.19.39 with HTTP; Tue, 26 Feb 2013 09:44:04 -0800 (PST)
In-Reply-To: <CA+9eiLvh6GaS3GwRcqcyCHoy5F7ddOOG-82KCF6EH7B_VRyBuw@mail.gmail.com>
References: <CAF+90c8o=0u3deM6LA6TW9GjDeNrZA_16TAPBmHJQ7mN_P4v+A@mail.gmail.com>
 <CA+9eiLugMVzK+9Cj+z__GW8y_F5D_L0SFRNazmDOMQyPJy2c5w@mail.gmail.com>
 <CAF+90c-Kmx5=qqY3VpEDY+oPfDZ5acCSe_o0LcM6cA=FLMpauQ@mail.gmail.com> <CA+9eiLvh6GaS3GwRcqcyCHoy5F7ddOOG-82KCF6EH7B_VRyBuw@mail.gmail.com>
Date: Tue, 26 Feb 2013 14:44:04 -0300
Message-ID: <CA+5g0SKxZRW3R=27bX1L9HJMW4uaR5KB6NO4xT5ZFJKN9rOUjQ@mail.gmail.com>
To: Dmitry Stogov <dmitry@zend.com>
Cc: Nikita Popov <nikita.ppv@gmail.com>, PHP internals <internals@lists.php.net>
Content-Type: text/plain; charset=UTF-8
Subject: Re: [PHP-DEV] Allow (...)->foo() expressions not only for `new`
From: felipensp@gmail.com (Felipe Pena)

Hi,

>
> Yeah. It's not a simple patch. In the past, we had a lot of problems after
> introducing foo()[$i] syntax, because some edge cases were not taken in
> account.
>
> Thanks. Dmitry.

From what I remember, the same problem that I spotted by foo()[$i] is
the one that we already had with foo()->prop. So it actually was a bug
fix.

-- 
Regards,
Felipe Pena