It is generally recommended to explicitly declare the visibility for methods.
Adding explicit visibility (private, protected, or public) is generally
recommend to communicate to other developers how, and from where this method
is intended to be used.
It is generally recommended to explicitly declare the visibility for methods.
Adding explicit visibility (private, protected, or public) is generally
recommend to communicate to other developers how, and from where this method
is intended to be used.
It is generally recommended to explicitly declare the visibility for methods.
Adding explicit visibility (private, protected, or public) is generally
recommend to communicate to other developers how, and from where this method
is intended to be used.
It is generally recommended to explicitly declare the visibility for methods.
Adding explicit visibility (private, protected, or public) is generally
recommend to communicate to other developers how, and from where this method
is intended to be used.
It is generally recommended to explicitly declare the visibility for methods.
Adding explicit visibility (private, protected, or public) is generally
recommend to communicate to other developers how, and from where this method
is intended to be used.
Loading history...
35
{
36
return $this->patient;
37
}
38
39
/**
40
* Maps properities of an $obj to $patient by calling setter of each property.
41
*
42
* E.g. value of $obj->prop will become $patient->prop by calling $patient->setProp
43
*
44
* @param unknown $patient
45
* @param unknown $obj
46
* @return unknown
47
*/
48
public static function map($patient, $obj)
49
{
50
foreach (get_object_vars($obj) as $key => $value) {
51
if ($value instanceof \stdClass && property_exists($value, 'date')) {
Adding explicit visibility (
private,protected, orpublic) is generally recommend to communicate to other developers how, and from where this method is intended to be used.