3v4l.org

run code in 150+ php & hhvm versions
Bugs & Features
<?php $date = new DateTime('now'); $firstOfMonth = $date->modify('1st day of current month')->format(DATE_ISO8601); $lastOfMonth = $date->modify('end of month')->format(DATE_ISO8601); var_dump(array($firstOfMonth, $lastOfMonth));
Output for 7.0.0 - 7.1.0
Warning: DateTime::modify(): Failed to parse time string (1st day of current month) at position 0 (1): Unexpected character in /in/2PJVb on line 5 Fatal error: Uncaught Error: Call to a member function format() on boolean in /in/2PJVb:5 Stack trace: #0 {main} thrown in /in/2PJVb on line 5
Process exited with code 255.
Output for hhvm-3.12.0
Warning: DateTime::modify(): Failed to parse time string (1st day of current month) at position 0 (1): Unexpected character in /in/2PJVb on line 5 Fatal error: Uncaught exception 'BadMethodCallException' with message 'Call to a member function format() on a non-object (boolean)' in /in/2PJVb:5 Stack trace: #0 {main}
Process exited with code 255.
Output for hhvm-3.10.0
array(2) { [0]=> string(24) "2016-04-12T16:15:08+0200" [1]=> string(24) "2016-04-12T16:15:08+0200" }
Output for 5.6.0 - 5.6.28
Warning: DateTime::modify(): Failed to parse time string (1st day of current month) at position 0 (1): Unexpected character in /in/2PJVb on line 5 Fatal error: Call to a member function format() on boolean in /in/2PJVb on line 5
Process exited with code 255.
Output for 5.2.13 - 5.2.17, 5.5.0 - 5.5.35
Warning: DateTime::modify(): Failed to parse time string (1st day of current month) at position 0 (1): Unexpected character in /in/2PJVb on line 5 Fatal error: Call to a member function format() on a non-object in /in/2PJVb on line 5
Process exited with code 255.
Output for 5.4.0 - 5.4.45
Fatal error: Uncaught exception 'Exception' with message 'DateTime::__construct(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected the timezone 'UTC' for now, but please set date.timezone to select your timezone.' in /in/2PJVb:3 Stack trace: #0 /in/2PJVb(3): DateTime->__construct('now') #1 {main} thrown in /in/2PJVb on line 3
Process exited with code 255.
Output for 5.3.0 - 5.3.29
Fatal error: Uncaught exception 'Exception' with message 'DateTime::__construct(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead' in /in/2PJVb:3 Stack trace: #0 /in/2PJVb(3): DateTime->__construct('now') #1 {main} thrown in /in/2PJVb on line 3
Process exited with code 255.
Output for 5.2.3 - 5.2.12
Fatal error: Call to a member function format() on a non-object in /in/2PJVb on line 5
Process exited with code 255.
Output for 5.2.0 - 5.2.2
<br /> <b>Fatal error</b>: Call to a member function format() on a non-object in <b>/in/2PJVb</b> on line <b>5</b><br />
Process exited with code 255.
Output for 5.0.0 - 5.1.6
<br /> <b>Fatal error</b>: Class 'DateTime' not found in <b>/in/2PJVb</b> on line <b>3</b><br />
Process exited with code 255.
Output for 4.4.2 - 4.4.9
<br /> <b>Parse error</b>: syntax error, unexpected T_OBJECT_OPERATOR in <b>/in/2PJVb</b> on line <b>5</b><br />
Process exited with code 255.
Output for 4.3.0 - 4.3.1, 4.3.5 - 4.4.1
<br /> <b>Parse error</b>: parse error, unexpected T_OBJECT_OPERATOR in <b>/in/2PJVb</b> on line <b>5</b><br />
Process exited with code 255.
Output for 4.3.2 - 4.3.4
<br /> <b>Parse error</b>: parse error in <b>/in/2PJVb</b> on line <b>5</b><br />
Process exited with code 255.