3v4l.org

run code in 300+ PHP versions simultaneously
<?php trait DataCollector { private static $CollectionData; public static function setData( $data ) { if (!isset(self::$CollectionData)) self::$CollectionData = array(); self::$CollectionData[] = $data; var_dump(self::$CollectionData); } public static function getCollectedData() { return self::$CollectionData; } } trait dataHandler { use DataCollector { getCollectedData as public; } } class Form { use DataCollector {} } class Field extends Form { public function __construct( $type, $text = NULL ) { self::setData( $type ); } } $Field1 = new Field( 'text' ); $Field2 = new Field( 'html' ); var_dump( 'Collected Data (Data Collector)', DataCollector::getCollectedData() ); var_dump( 'Collected Data (Data Handler)', dataHandler::getCollectedData() ); var_dump( 'Collected Data (Form)', Form::getCollectedData() );
Output for git.master, git.master_jit, rfc.property-hooks
array(1) { [0]=> string(4) "text" } array(2) { [0]=> string(4) "text" [1]=> string(4) "html" } Deprecated: Calling static trait method DataCollector::getCollectedData is deprecated, it should only be called on a class using the trait in /in/giFql on line 30 Deprecated: Accessing static trait property DataCollector::$CollectionData is deprecated, it should only be accessed on a class using the trait in /in/giFql on line 13 string(31) "Collected Data (Data Collector)" NULL Deprecated: Calling static trait method dataHandler::getCollectedData is deprecated, it should only be called on a class using the trait in /in/giFql on line 31 Deprecated: Accessing static trait property dataHandler::$CollectionData is deprecated, it should only be accessed on a class using the trait in /in/giFql on line 13 string(29) "Collected Data (Data Handler)" NULL string(21) "Collected Data (Form)" array(2) { [0]=> string(4) "text" [1]=> string(4) "html" }

This tab shows result from various feature-branches currently under review by the php developers. Contact me to have additional branches featured.

Active branches

Archived branches

Once feature-branches are merged or declined, they are no longer available. Their functionality (when merged) can be viewed from the main output page


preferences:
56.47 ms | 403 KiB | 8 Q