Opcode EXT_FCALL_BEGIN and EXT_FCALL_END?

15 years ago by Mathieu Suen — view source — reply

unread

Hi,

I am wondering what the opcode EXT_FCALL_BEGIN and EXT_FCALL_END is used
for?
Thanks

-- Mathieu Suen

15 years ago by Stanislav Malyshev — view source — reply

unread

Hi!

I am wondering what the opcode EXT_FCALL_BEGIN and EXT_FCALL_END is used
for?

When php is in "extended opcode" mode (usually used by debuggers) these
opcodes are generated by the compiler before entering and after exiting
function calls (so that the debugger could do "step into" and "step
over"). They are not used in non-debugging context.

Stanislav Malyshev, Zend Software Architect
stas@zend.com http://www.zend.com/
(408)253-8829 MSN: stas@zend.com

15 years ago by Derick Rethans — view source — reply

unread

I am wondering what the opcode EXT_FCALL_BEGIN and EXT_FCALL_END is used
for?

When php is in "extended opcode" mode (usually used by debuggers) these
opcodes are generated by the compiler before entering and after exiting
function calls (so that the debugger could do "step into" and "step over").
They are not used in non-debugging context.

Are you guys using those in Zend Debugger? Because in Xdebug I found
them utterly useless (not EXT_STMT, which I do use). Instead of using
EXT_FCALL_* I just do the triggers in the overloaded zend_execute.

Derick

--
http://derickrethans.nl | http://ezcomponents.org | http://xdebug.org
twitter: @derickr

15 years ago by Stanislav Malyshev — view source — reply

unread

Hi!

Are you guys using those in Zend Debugger? Because in Xdebug I found
them utterly useless (not EXT_STMT, which I do use). Instead of using
EXT_FCALL_* I just do the triggers in the overloaded zend_execute.

I think those appeared before execute() was overridable, so newer code
doesn't have to use it.

Stanislav Malyshev, Zend Software Architect
stas@zend.com http://www.zend.com/
(408)253-8829 MSN: stas@zend.com

15 years ago by Sebastian Bergmann — view source — reply

unread

Stanislav Malyshev wrote:

I think those appeared before execute() was overridable, so newer code
doesn't have to use it.

So, why not remove them? :)

--
Sebastian Bergmann Co-Founder and Principal Consultant
http://sebastian-bergmann.de/ http://thePHP.cc/

15 years ago by Stanislav Malyshev — view source — reply

unread

Hi!

So, why not remove them? :)

Why remove them? They don't hurt anyone. They might be also usable for
something like static analysis (to know when fcall begins and ends), or
maybe somebody out there is using them for something else.

Stanislav Malyshev, Zend Software Architect
stas@zend.com http://www.zend.com/
(408)253-8829 MSN: stas@zend.com

Opcode EXT_FCALL_BEGIN and EXT_FCALL_END?

When php is in "extended opcode" mode (usually used by debuggers) these opcodes are generated by the compiler before entering and after exiting function calls (so that the debugger could do "step into" and "step over"). They are not used in non-debugging context.

I think those appeared before execute() was overridable, so newer code doesn't have to use it.

Why remove them? They don't hurt anyone. They might be also usable for something like static analysis (to know when fcall begins and ends), or maybe somebody out there is using them for something else.

When php is in "extended opcode" mode (usually used by debuggers) these
opcodes are generated by the compiler before entering and after exiting
function calls (so that the debugger could do "step into" and "step
over"). They are not used in non-debugging context.

I think those appeared before execute() was overridable, so newer code
doesn't have to use it.

Why remove them? They don't hurt anyone. They might be also usable for
something like static analysis (to know when fcall begins and ends), or
maybe somebody out there is using them for something else.