Hi Kalle,
Thank you for the list. It's very helpful!
On Fri, Dec 5, 2014 at 4:58 AM, Kalle Sommer Nielsen ka...@php.net wrote:
2014-12-04 9:28 GMT+01:00 Yasuo Ohgaki yohg...@ohgaki.net:
Any comments?
Regards,
--
Yasuo Ohgaki
yohg...@ohgaki.net
I think we should solve these on a
Hi all,
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
Is it possible to allow literal as referenced parameter for PHP7?
It's better to remove needless restrictions
On 4 Dec 2014, at 08:28, Yasuo Ohgaki yohg...@ohgaki.net wrote:
Hi all,
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’s some logic to
From: Andrea Faulds [mailto:a...@ajf.me], Thursday, December 04, 2014 9:33 AM
On 4 Dec 2014, at 08:28, Yasuo Ohgaki yohg...@ohgaki.net wrote:
Hi all,
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
Hi Andrea,
On Thu, Dec 4, 2014 at 5:32 PM, Andrea Faulds a...@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’s some logic to
Hi Yasuo
2014-12-04 9:28 GMT+01:00 Yasuo Ohgaki yohg...@ohgaki.net:
Any comments?
Regards,
--
Yasuo Ohgaki
yohg...@ohgaki.net
I think we should solve these on a case-by-case basis, I can think of
one reason why the warning exists, and that is because it modifies the
array pointer and the
Thoughts?
The only reason to take a parameter by reference is because you modify
the variable that the caller is passing in. Passing in constants is
*almost certainly* an error. I would rather have the warnings than
remove them.
--
PHP Internals - PHP Runtime Development Mailing List
To
On 4 Dec 2014, at 19:58, Kalle Sommer Nielsen ka...@php.net wrote:
I think we should solve these on a case-by-case basis, I can think of
one reason why the warning exists, and that is because it modifies the
array pointer and the argument is sent by reference. But I think we
can safely
