Arquivos
hhvm/hphp/test/quick/debugger/info1.php.expectf
T
Herman Venter b7ed094ed2 Use the same output formatting for = command as is used for the print command.
The = command uses formatting that is user customizable and subtly different, by default, from the formatting used by the print command and the variable command. This has historical roots. It seems that the debugger used to use print_r, which is brittle, and the customization hook was introduced to work around this brittleness. This work around is no longer necessary since the debugger now has its own, robust way of formatting values as strings. Also, the difference between = and print is a perennial source of confusion for debugger users.
2013-07-26 11:31:15 -07:00

46 linhas
938 B
Plaintext

Program %s/info1.php loaded. Type '[r]un' or '[c]ontinue' to go.
@
info array_key_exists
/**
* ( excerpt from http://php.net/manual/en/function.array_key_exists.php )
* array_key_exists() returns TRUE if the given key is set in the array. key can be any value possible for an array index.
*
* @key mixed Value to check.
* @search mixed An array with keys to check.
*
* @return bool Returns TRUE on success or FALSE on failure.
*/
function array_key_exists($key, $search);
info stdClass
// defined on line %d to %d of %s/systemlib.php
class stdClass {
}
run
Program %s/info1.php exited normally.
@
info myfunc
// defined on line 3 to 5 of %s/info1.php
function myfunc($a, $b);
info MyClass
// defined on line 7 to 11 of %s/info1.php
class MyClass {
// properties
public $pub;
protected $pro;
private $pri;
}
info MyClass::pub
public $pub;
info MyClass::pro
protected $pro;
info MyClass::pri
private $pri;
quit