26 lines
1.2 KiB
Markdown
26 lines
1.2 KiB
Markdown
# Syntax provider profile
|
|
|
|
Regex Tools has one public profile:
|
|
|
|
```text
|
|
community
|
|
```
|
|
|
|
It uses only reviewed open-source dependencies and builds without private
|
|
registry credentials. ECMAScript uses regexpp 4.12.2. PCRE2 uses an
|
|
application-owned lexical provider for partial explanations and the actual
|
|
bundled PCRE2 compiler for authoritative acceptance. Python and Java use
|
|
application-owned lexical providers for partial explanations and
|
|
flavour-native replacement tokens; bundled CPython `re` and TeaVM
|
|
`java.util.regex` respectively remain authoritative for compilation.
|
|
The Java provider follows the bundled TeaVM 0.15.0 replacement subset:
|
|
single-digit `$n` is executable, `$12` is `$1` followed by literal `2`, and
|
|
Java SE `${name}` references are surfaced as a compatibility limitation.
|
|
|
|
The product deliberately does not implement or reference an `@r101/parser`
|
|
profile. No commercial package alias, import, tarball, credential, licence key
|
|
or private CI path exists. Additional flavour syntax is implemented
|
|
incrementally as open-source providers behind the same application-owned
|
|
interface. Partial coverage is exposed as metadata and never presented as a
|
|
complete parser.
|