php.net |  support |  documentation |  report a bug |  advanced search |  search howto |  statistics |  random bug |  login
Bug #77797 Array assignment
Submitted: 2019-03-26 12:27 UTC Modified: 2019-03-26 12:35 UTC
From: taco at procurios dot nl Assigned:
Status: Duplicate Package: Unknown/Other Function
PHP Version: 7.2.16 OS: linux
Private report: No CVE-ID: None
View Add Comment Developer Edit
Anyone can comment on a bug. Have a simpler test case? Does it work for you on a different platform? Let us know!
Just going to say 'Me too!'? Don't clutter the database with that please !
Your email address:
MUST BE VALID
Solve the problem:
48 - 37 = ?
Subscribe to this entry?

 
 [2019-03-26 12:27 UTC] taco at procurios dot nl
Description:
------------
When passing an array append assignment directly to a public or protected method with opcache enabled, the array itself is passed to the method instead of the assigned value. Calling private methods or functions will not trigger this behaviour.

This behaviour only occurs with opcache enabled (tested both in cli and as apache module), so you'll need to run it at least twice to see the faulty behaviour.

Test script:
---------------
<?php
class Foo
{
    public function baz($arg)
    {
        return $arg;
    }

    public function bar()
    {
        $a = [];
        return $this->baz($a[] = 'foo');
    }
}

$foo = new Foo();
var_dump($foo->bar());

Expected result:
----------------
string(3) "foo"

Actual result:
--------------
array(1) {
  [0] =>
  string(3) "foo"
}

Patches

Add a Patch

Pull Requests

Add a Pull Request

History

AllCommentsChangesGit/SVN commitsRelated reports
 [2019-03-26 12:35 UTC] nikic@php.net
-Status: Open +Status: Duplicate
 [2019-03-26 12:35 UTC] nikic@php.net
Duplicate of bug #77691, which has been fixed in 7.2.17.
 
PHP Copyright © 2001-2024 The PHP Group
All rights reserved.
Last updated: Tue Apr 23 12:01:31 2024 UTC