Emit EXT_STMT for each 'elseif' clause #8574
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This tiny change emits an extra EXT_STMT opcode for each
elseif
child in an AST_IF list.The reason why I am proposing this, is as follows:
A user reported a bug #2095 with Xdebug's code coverage, which complains that lines with
elseif
on them do not get "counted" as being it, whereelse if
lines do.The generated opcodes are for the
elseif
version:And for the
else if
version:In the
elseif
variant, theEXT_STMT
(opcode 7) is indeed missing.Xdebug uses this opcode for both code coverage analysis, as well as single stepping. The step debugger would also not have stopped at the
elseif
line.The reason here is that with
else if
it is really seen as two different things, with theif
being a new statement (and hence creating its ownEXT_STMT
), where withelseif
it is a continuation of the originalif
, which does not emit anEXT_STMT
for each separate condition. This patch equalizes the behaviour.