Differences

This shows you the differences between two versions of the page.

--- rfc:max_execution_wall_time [2020/12/13 00:21] – kocsismate
+++ rfc:max_execution_wall_time [2020/12/13 00:24] – kocsismate
@@ Line 39: / Line 39: @@
 HHVM solved the same problem by introducing the ''TimeoutsUseWallTime'' ini setting (https://github.com/facebook/hhvm/commit/9a9b42e3610cdf242f16ddb8936ce34adfa0be9e) in order to offer a way to change the meaning of ''max_execution_time'', while still (partially) remaining compatible with PHP. This made sense for a sister language, but in case of PHP itself, it seems to be an unnecessary complication which could result in weird issues.
-It would also be possible to directly change the behavior of ''max_execution_time'' to measure wall-clock time on all platforms. This approach is rejected by the current RFC mainly due to its vast BC break, and the fact that a CPU-time based execution timeout settings are useful as a sanity check of the code itself (e.g. for making sure there are no infinite loops).
+It would also be possible to directly change the behavior of ''max_execution_time'' to measure wall-clock time on all platforms. This approach is rejected by the current RFC mainly due to its vast BC break, and the fact that CPU-time based execution timeouts are useful as a sanity check of the code itself (e.g. for making sure there are no infinite loops).
 ===== Backward Incompatible Changes =====