PHP 5.2.6:

$ref->invoke($arr, 1);
Fatal error: Uncaught exception 'ReflectionException' with message 'Invocation of function array_unshift() failed' 

$ref->invokeArgs(array($arr, 0));
Fatal error: Uncaught exception 'ReflectionException' with message 'Invocation of function array_unshift() failed'

PHP 5.3.0:

$ref->invoke($arr, 1); and $ref->invokeArgs(array($arr, 0));
Warning: Parameter 1 to array_unshift() expected to be a reference, value given

Ops... 5_3 also issued 'Fatal error'.

Warning: Parameter 1 to array_unshift() expected to be a reference, value given in %s on line %d

Fatal error: Uncaught exception 'ReflectionException' with message 'Invocation of function array_unshift() failed' in %s:%d
Stack trace:
#0 %s(19): ReflectionFunction->invoke(Array, 1)
#1 {main}
  thrown in %s on line %d

Hi Felipe, I don't understand your messages.

I know that it generates a Fatal error as I know that send the array forcing reference works as expected but it generates a warning.

As I wrote on php.net manual too, to solve this strange behaviour I used a "non-sense" strategy (at least for me) ...

$arr = array(2, 3, 4);
$ref = new ReflectionFunction('array_unshift');
$ref->invokeArgs(array_merge(array(&$arr), array(1)));
$ref->invokeArgs(array_merge(array(&$arr), array(0)));
// $arr == [0,1,2,3,4]

I can't understand why one single value is accepted by reference inside an array while more than one is not accepted.

Since PHP 5 should manage by itself references I think that ReflectionFunction should do the same, without reference requirement but working as expected.

Do you think am I wrong?
Kind Regards

$ref->invoke(&$arr, 1);
$ref->invokeArgs(array(&$arr, 0));
var_dump($arr);	// correct and expected result

Doesn't show warning on 5.2.6 and 5.3. That was my message.

Felipe, I'm testing PHP Version 5.2.6-dev and I have the same problem.

<?php
$arr    = array(2, 3, 4);
$ref    = new ReflectionFunction('array_unshift');
$ref->invoke(&$arr, 1);
$ref->invokeArgs(array(&$arr, 1));
var_dump($arr);
exit;
?>

Warning: Call-time pass-by-reference has been deprecated; If you would like to pass it by reference, modify the declaration of [runtime function name](). If you would like to enable call-time pass-by-reference, you can set allow_call_time_pass_reference to true in your INI file in ...

I guess above warning should not exists. So, can you confirm that this is a bug?
Cheers

Sorry, this is what I would like to be able to do:

<?php
$arr    = array(2, 3, 4);
$ref    = new ReflectionFunction('array_unshift');
$ref->invoke($arr, 1);
$ref->invokeArgs(array($arr, 1));
var_dump($arr);
exit;
?>

Without fatal errors, simply because if send by reference is deprecated, ReflectionFunction (... and I didn't test ReflectionMethod ...) should be able to manage correctly variables by references.

This is another Fatal Error example:

<?php
function unshift(&$arr, $mix){
    return  array_unshift($arr, $mix);
}
$arr    = array(2, 3, 4);
$ref    = new ReflectionFunction('unshift');
$ref->invoke($arr, 1);
$ref->invokeArgs(array($arr, 1));
var_dump($arr);
exit;
?>

I hope these examples explain correctly where and what is the problem.
Kind Regards

As expected, this problem is present on ReflectionMethod too.

Basically, the summary of this bug is wrong and I guess that correct could be the changed one.

I tested both problems in PHP 5.2.5 and 5.2.6-dev.

This example shows the problem using methods as well.

<?php

class Test{
    public  function unshift(&$arr, $mix){
        return  array_unshift($arr, $mix);
    }
}

$instance   = new Test;
$arr        = array(2, 3, 4);
$ref        = new ReflectionMethod('Test', 'unshift');

// WARNING
$ref->invoke($instance, &$arr, 1);
$ref->invokeArgs($instance, array(&$arr, 0));
var_dump($arr); // [0,1,2,3,4]

// FATAL ERROR
$ref->invoke($instance, $arr, 1);
$ref->invokeArgs($instance, array($arr, 0));
var_dump($arr);
exit;

?>

Thanks for solving this problem.
Kind Regards.

Please try using this CVS snapshot:

  http://snaps.php.net/php5.2-latest.tar.gz
 
For Windows (zip):
 
  http://snaps.php.net/win32/php5.2-win32-latest.zip

For Windows (installer):

  http://snaps.php.net/win32/php5.2-win32-installer-latest.msi

No feedback was provided for this bug for over a week, so it is
being suspended automatically. If you are able to provide the
information that was originally requested, please do so and change
the status of the bug back to "Open".