|
|
php.net | support | documentation | report a bug | advanced search | search howto | statistics | random bug | login |
[2017-09-20 08:38 UTC] ben at redsnapper dot net
Description:
------------
Using print_r on a DateTime object creates a side-effect: the property 'date' is now set and publicly available.
Test script:
---------------
//Expected Behaviour
php > $d1 = DateTime::createFromFormat("Ymd\THis\Z", '20170920T091600Z');
php > echo $d1->date;
Notice: Undefined property: DateTime::$date
//Unexpected Behaviour / side effect.
php > $d2 = DateTime::createFromFormat("Ymd\THis\Z", '20170920T091600Z');
php > print_r($d2->date);
DateTime Object
(
[date] => 2017-09-20 09:16:00.000000
[timezone_type] => 3
[timezone] => UTC
)
php > echo $d2->date;
2017-09-20 09:16:00.000000
Expected result:
----------------
There should be no change (side-effect) made to an object when using print_r()
PatchesPull RequestsHistoryAllCommentsChangesGit/SVN commits
|
|||||||||||||||||||||||||||||||||||||
Copyright © 2001-2024 The PHP GroupAll rights reserved. |
Last updated: Tue Dec 03 17:01:29 2024 UTC |
For the sake of completeness, this also happens when var_dump'ing or ReflectionObject::export'ing: php > $dt = new DateTime; php > var_dump($dt); object(DateTime)#3 (3) { ["date"]=> string(26) "2017-09-20 10:57:54.000000" ["timezone_type"]=> int(3) ["timezone"]=> string(13) "Europe/Berlin" } php > echo $dt->date; 2017-09-20 10:57:54.000000 php > $dt = new DateTime; php > ReflectionObject::export($dt); Object of class [ <internal:date> class DateTime implements DateTimeInterface ] { // some lines omitted … - Dynamic properties [3] { Property [ <dynamic> public $date ] Property [ <dynamic> public $timezone_type ] Property [ <dynamic> public $timezone ] } // some lines omitted … } php > echo $dt->date; 2017-09-20 10:57:57.000000 So it adds three public properties.