Re: RFC: phpdbg
On 30/11/13 10:41, Nikita Popov wrote:
Independently from phpdbg, is there any particular (technical) reason that
prevents (zend?) extensions from registering SAPIs? Could we add something
for that to work?
Nikita, if you think about it the SAPI contains main() -- or the respective shared library master entry point, and acts as the calling / callback framework for the Zend environment. To make the SAPI an extension would require inverting this PHP Zend architecture so that there is some sort of general minimal wrapper which can then layer in an additional personality by loading in some shared library from some context. However, this wouldn't be a Zend or PHP extension as we know it. This would involve a lot of work.
Thinking off the top of my head, what we could possibly do would be to hook some of the standard entries in the CLI SAPI so that a SAPI-aware extension could insert itself into this chain and modify the behaviour of the standard CLI (or potentially other) SAPIs. This approach could allow phpdbg to be a Zend Extension "skin" on the standard CLI.
Regards Terry
Thread (21 messages)