rfc:zend-vm-pause-api
Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revisionNext revisionBoth sides next revision | ||
| rfc:zend-vm-pause-api [2017/11/01 01:22] – lvht | rfc:zend-vm-pause-api [2017/11/01 01:35] – lvht | ||
|---|---|---|---|
| Line 2: | Line 2: | ||
| * Version: 0.9 | * Version: 0.9 | ||
| * Date: 2017-11-01 | * Date: 2017-11-01 | ||
| - | * Author: Haitao Lv php@lvht.net | + | * Author: Haitao Lv, php@lvht.net |
| * Status: Draft | * Status: Draft | ||
| * First Published at: http:// | * First Published at: http:// | ||
| Line 11: | Line 11: | ||
| So it is impossible to change the Zend VM's execute flow in an zend extension. As a result, any feature, like Fiber, | So it is impossible to change the Zend VM's execute flow in an zend extension. As a result, any feature, like Fiber, | ||
| - | related to Zend VM's execute flow cannot be implemented by a standalone. | + | related to Zend VM's execute flow cannot be implemented by a standalone |
| ===== Proposal ===== | ===== Proposal ===== | ||
| - | This PRFC propose a new zend_vm_pause API and an new EG(pause_op), by which some zend extension could make the | + | This PRFC propose a new zend_vm_pause API, by which some zend extension could make the zend vm execution paused. |
| - | zend vm execution paused. | + | As a result, we can implement feature like Fiber in a standalone extension. |
| We need introduce a new vm global EG(pause_op) as zend_op and init it by the following code | We need introduce a new vm global EG(pause_op) as zend_op and init it by the following code | ||
rfc/zend-vm-pause-api.txt · Last modified: 2017/11/21 10:56 by lvht