rfc:deprecate_ticks
Differences
This shows you the differences between two versions of the page.
| Next revision | Previous revision | ||
| rfc:deprecate_ticks [2021/05/11 08:49] – created nikic | rfc:deprecate_ticks [2025/04/03 13:08] (current) – external edit 127.0.0.1 | ||
|---|---|---|---|
| Line 2: | Line 2: | ||
| * Date: 2021-05-11 | * Date: 2021-05-11 | ||
| * Author: Nikita Popov < | * Author: Nikita Popov < | ||
| - | * Status: | + | * Status: |
| * Target Version: PHP 8.1 | * Target Version: PHP 8.1 | ||
| + | * Implementation: | ||
| + | * Discussion: https:// | ||
| ===== Introduction ===== | ===== Introduction ===== | ||
| Line 16: | Line 18: | ||
| Async signals work by setting a VM interrupt flag whenever a signal is received, which will be handled at the next VM interrupt check. This means that async signals do not impose any additional cost, beyond what is always paid to handle timeouts. | Async signals work by setting a VM interrupt flag whenever a signal is received, which will be handled at the next VM interrupt check. This means that async signals do not impose any additional cost, beyond what is always paid to handle timeouts. | ||
| - | |||
| - | Beyond signal handling, I'm not aware of other applications of the ticks mechanism that are still in use today. | ||
| ===== Proposal ===== | ===== Proposal ===== | ||
| Line 28: | Line 28: | ||
| The removal of the ticks mechanism is expected to have limited impact. The primary user of ticks were pcntl signals, and these are handled through [[https:// | The removal of the ticks mechanism is expected to have limited impact. The primary user of ticks were pcntl signals, and these are handled through [[https:// | ||
| + | |||
| + | It is possible to use ticks to instrument all code by overriding PHP's file stream wrapper and rewriting all included files to add the '' | ||
| ===== Vote ===== | ===== Vote ===== | ||
| Yes/No. | Yes/No. | ||
rfc/deprecate_ticks.1620722949.txt.gz · Last modified: 2025/04/03 13:08 (external edit)