Would it be possible to implement CG(zend_linecol) in addition to
CG(zend_lineno)? As far I can see, this is a missing prerequisite for
Xdebug to report more fine-grained code coverage, for instance.
--
Sebastian Bergmann http://sebastian-bergmann.de/
GnuPG Key: 0xB85B5D69 / 27A7 2B14 09E4 98CD 6277 0E5B 6867 C514 B85B 5D69
Sebastian Bergmann wrote:
Would it be possible to implement CG(zend_linecol) in addition to
CG(zend_lineno)? As far I can see, this is a missing prerequisite for
Xdebug to report more fine-grained code coverage, for instance.
I've been thinking about this also, and would find this useful for some profiler/visualization purposes and perhaps for inclusion in errors.
-shire
Hi!
Would it be possible to implement CG(zend_linecol) in addition to
CG(zend_lineno)? As far I can see, this is a missing prerequisite for
Xdebug to report more fine-grained code coverage, for instance.
Unless we put this inside each opcode, I'm not sure it'd help xdebug too
much. And I'm not sure it is worth inflating the opcodes.
Also, I'm not sure scanner now knows enough to do it - though maybe it
can be made to know it.
Stanislav Malyshev, Zend Software Architect
stas@zend.com http://www.zend.com/
(408)253-8829 MSN: stas@zend.com
Stanislav Malyshev wrote:
Would it be possible to implement CG(zend_linecol) in addition to
CG(zend_lineno)? As far I can see, this is a missing prerequisite for
Xdebug to report more fine-grained code coverage, for instance.Unless we put this inside each opcode, I'm not sure it'd help xdebug too
much. And I'm not sure it is worth inflating the opcodes.
Also, I'm not sure scanner now knows enough to do it - though maybe it
can be made to know it.
Did anyone look into this yet? I still think that it would be beneficial
to have this information.
--
Sebastian Bergmann Co-Founder and Principal Consultant
http://sebastian-bergmann.de/ http://thePHP.cc/