3v4l.org

run code in 300+ PHP versions simultaneously
<?php $message = ":</p> <ul> <li>We could delay deleting the unit for a \"couple of frames\" until we have had time to report events about it to the script. However, this would create a new strange state for units to be in, an <em>(about-to-be-deleted)</em> state. This will severely increase code complexity and confusion since there would be a ton of places where you would have to check if you were dealing with a \"real\" unit or an \"about-to-be-deleted\" unit, both in the script and in the engine. Horrible.</li> ou perhaps want... instead you would get Enter/Destroy. And you wouldn't be able to tell which unit was destroyed.</li> "; $message = preg_replace("/<\/p>((.|\n)+?)(?=<\/p>)/", "\n$1", $message); echo strip_tags($message); ?>
Output for 4.3.0 - 4.3.11, 4.4.0 - 4.4.9, 5.0.0 - 5.0.5, 5.1.0 - 5.1.6, 5.2.0 - 5.2.17, 5.3.0 - 5.3.29, 5.4.0 - 5.4.45, 5.5.24 - 5.5.35, 5.6.7 - 5.6.28, 7.0.0 - 7.0.20, 7.1.0 - 7.1.7, 7.2.29 - 7.2.33, 7.3.16 - 7.3.33, 7.4.0 - 7.4.33, 8.0.0 - 8.0.30, 8.1.0 - 8.1.27, 8.2.0 - 8.2.17, 8.3.0 - 8.3.4
: We could delay deleting the unit for a "couple of frames" until we have had time to report events about it to the script. However, this would create a new strange state for units to be in, an (about-to-be-deleted) state. This will severely increase code complexity and confusion since there would be a ton of places where you would have to check if you were dealing with a "real" unit or an "about-to-be-deleted" unit, both in the script and in the engine. Horrible. ou perhaps want... instead you would get Enter/Destroy. And you wouldn't be able to tell which unit was destroyed.

preferences:
211.42 ms | 406 KiB | 305 Q