feat: add Python and Java regex engines
This commit is contained in:
@@ -20,8 +20,16 @@ common capture forms. It does not infer branch-reset numbering or claim full
|
||||
nesting; authoritative compilation, capture counts, names and result ranges
|
||||
come from PCRE2 itself.
|
||||
|
||||
The Python and Java providers likewise emit deliberately partial lexical trees.
|
||||
They recognize their documented capture and replacement forms for navigation
|
||||
and display, but do not claim full grammar acceptance. CPython `re` and TeaVM
|
||||
`Pattern` remain authoritative for compilation. Java capture names displayed
|
||||
with native numbered spans come from the bounded lexical metadata; they are not
|
||||
invented as a TeaVM-reported name table.
|
||||
|
||||
The explanation tree is structural. It is never called an actual execution
|
||||
trace. Selecting a node selects and scrolls its exact editor range; selecting
|
||||
pattern text chooses the smallest enclosing node. PCRE2’s separate trace viewer
|
||||
contains actual bounded automatic callouts; its movement labels remain a
|
||||
distinct derived layer and are never copied into the structural explanation.
|
||||
Python and Java expose no actual execution trace.
|
||||
|
||||
Reference in New Issue
Block a user