3v4l.org

run code in 150+ php & hhvm versions
Bugs & Features
<?php var_dump( (new DateTime('now', new DateTimeZone('Europe\Vilnius')) )->getTimestamp() );
based on gEecS
Output for 7.0.0 - 7.1.0
Fatal error: Uncaught Exception: DateTimeZone::__construct(): Unknown or bad timezone (Europe\Vilnius) in /in/0YPv9:2 Stack trace: #0 /in/0YPv9(2): DateTimeZone->__construct('Europe\\Vilnius') #1 {main} thrown in /in/0YPv9 on line 2
Process exited with code 255.
Output for hhvm-3.12.0
Fatal error: Uncaught exception 'Exception' with message 'DateTimeZone::__construct(): Unknown or bad timezone (Europe\Vilnius)' in /in/0YPv9:2 Stack trace: #0 /in/0YPv9(2): DateTimeZone->__construct() #1 {main}
Process exited with code 255.
Output for hhvm-3.10.0

Process exited with code 153.
Output for 5.4.29 - 5.6.28
Fatal error: Uncaught exception 'Exception' with message 'DateTimeZone::__construct(): Unknown or bad timezone (Europe\Vilnius)' in /in/0YPv9:2 Stack trace: #0 /in/0YPv9(2): DateTimeZone->__construct('Europe\\Vilnius') #1 {main} thrown in /in/0YPv9 on line 2
Process exited with code 255.
Output for 5.4.27 - 5.4.28
Fatal error: Uncaught exception 'Exception' with message 'DateTimeZone::__construct(): Unknown or bad timezone (Europe\Vilnius)' in /in/0YPv9:2 Stack trace: #0 /in/0YPv9(2): DateTimeZone->__construct('Europe\\Villnius) #1 {main} thrown in /in/0YPv9 on line 2
Process exited with code 255.
Output for 5.4.0 - 5.4.26
Fatal error: Uncaught exception 'Exception' with message 'DateTimeZone::__construct(): Unknown or bad timezone (Europe\Vilnius)' in /in/0YPv9:2 Stack trace: #0 /in/0YPv9(2): DateTimeZone->__construct('Europe\Vilnius') #1 {main} thrown in /in/0YPv9 on line 2
Process exited with code 255.
Output for 4.4.2 - 4.4.9, 5.1.0 - 5.3.29
Parse error: syntax error, unexpected T_OBJECT_OPERATOR in /in/0YPv9 on line 2
Process exited with code 255.
Output for 4.3.0 - 4.3.1, 4.3.5 - 4.4.1, 5.0.0 - 5.0.5
Parse error: parse error, unexpected T_OBJECT_OPERATOR in /in/0YPv9 on line 2
Process exited with code 255.
Output for 4.3.2 - 4.3.4
Parse error: parse error in /in/0YPv9 on line 2
Process exited with code 255.