Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:79416
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.213.174 as permitted sender)
MIME-Version: 1.0
Sender: yohgaki@gmail.com
In-Reply-To: <091A4805-7B61-4CBD-A5C5-EDFC068616CF@ajf.me>
References: <CAGa2bXaAqbV4OnJSnXNboaZXD7cROR+Ue8jCE33uKci7kNo-KA@mail.gmail.com>
 <091A4805-7B61-4CBD-A5C5-EDFC068616CF@ajf.me>
Date: Thu, 4 Dec 2014 17:48:07 +0900
Message-ID: <CAGa2bXa7YyojBu5D1NHcmJ1UUbH1QbNXV22TkKKuD3gPkcNWLw@mail.gmail.com>
To: Andrea Faulds <ajf@ajf.me>
Cc: "internals@lists.php.net" <internals@lists.php.net>
Content-Type: multipart/alternative; boundary=001a113ed0e25155d00509600704
Subject: Re: [PHP-DEV] Only variables can be passed by reference
From: yohgaki@ohgaki.net (Yasuo Ohgaki)

--001a113ed0e25155d00509600704
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

Hi Andrea,

On Thu, Dec 4, 2014 at 5:32 PM, Andrea Faulds <ajf@ajf.me> wrote:

> > I think we can get rid of this error now when literal is returned.
> > The reason we have E_STRICT error is that legacy PHP didn't
> > support this, I suppose.
> >
> > http://3v4l.org/8fISj
>
> Hmm, I think there=E2=80=99s some logic to having a warning anyway. If a =
parameter
> is taken by reference, then it=E2=80=99s presumably going to be modified.=
 So if you
> pass something that isn=E2=80=99t a variable (and therefore the modified =
result
> can=E2=80=99t be accessed) to a by-reference parameter, it doesn=E2=80=99=
t really make
> sense.


I agree. It might be a bug in user code simply. However, example code
illustrates that there is valid usage.
Static method may return literal, default for some config, etc.

http://3v4l.org/jKXpb

We may use @ or get rid of E_STRICT altogether. I wonder if we really need
E_STRICT error here.

--
Yasuo Ohgaki
yohgaki@ohgaki.net

--001a113ed0e25155d00509600704--