Closed User4martin closed 1 year ago
@andgineer Pls apply.
could you resolve the conflicts?
Will do...
Can you check https://github.com/User4martin/TRegExpr/commit/more-references Can that be added? https://regex101.com/r/7qgquy/1
(and one other fix coming up)
Can that be added? https://regex101.com/r/7qgquy/1
It must be discussed in a new topic. with detailed description: what was not ok, what you propose...
Added #326 Added fix for "literal {" mode
Write to history block ending: "by Martin Friebe." Better increase version to 1.167.
Added another fix. Checking fixed length of a look-behind would fail if the look-behind had certain reference or sub-calls. (Because the HasFixedLength would increment the pointer to the next OP, but not skip the index stored after the command.)
docs:
``\k`name```
Did you make mistake - backtick instead of single quote?
@Alexey-T
GrpSubCalled
is only needed in execution loop, and therefore should only be cleared for a new Exec callGood, tkx.
(GrpBounds[0].GrpEnd[Idx] > GrpBounds[0].GrpStart[Idx])
maybe better >=
?
Good, tkx.
(GrpBounds[0].GrpEnd[Idx] > GrpBounds[0].GrpStart[Idx])
maybe better
>=
?
That is in TRegExpr.GetMatch
?
If it is equal, then the result is an empty string. And it has already been set to empty.
Ok, indeed.
@andgineer Please apply?
Fix #324 comment 1. Subsequent (side-by-side) recursive calls did see data captured in previous calls. Improve speed.
Include existing PR #323 and #322
@Alexey-T
All tests work for the old and new recursion behaviour. Except
Which are specially crafted to exploit the issue in the old behaviour