Paired Delimiter Depth Trace
Trace one literal delimiter pair outside any language grammar; quotes, escapes and comments are not interpreted.
Description
Trace one literal delimiter pair outside any language grammar; quotes, escapes and comments are not interpreted.
A delimiter-depth trace records how nesting changes at each chosen delimiter. Unmatched closing characters are reported without letting depth become negative.
When to use this tool
Trace one literal delimiter pair outside any language grammar; quotes, escapes and comments are not interpreted.
- Prepare the supplied text, opener, closer fields for this operation.
- Compare the complete example with the representation used by your own input before carrying the result into another step.
How to use the tool and how it works
- Enter text, opener, closer. Use the exact text syntax, units and index conventions explained below.
- Run the tool. If input validation fails, correct the supplied fields before interpreting any result.
- Read result.trace, result.unclosedOpeners. Interpret false, null and empty lists using the distinctions below; they can be valid outputs.
Require distinct one-unit opener/closer characters. Increment depth at openers, decrement at closers when possible, and emit each delimiter's offset, post-event depth and unmatchedClose flag. Return the final unclosed opener count.1
| Input field | Meaning and representation | Accepted input |
|---|---|---|
| text | text. | Text; at most 8,192 UTF-16 code units, subject to the grammar above |
| opener | opener. | Text; at most 8,192 UTF-16 code units, subject to the grammar above |
| closer | closer. | Text; at most 8,192 UTF-16 code units, subject to the grammar above |
| Output field | Interpretation |
|---|---|
| result | Object containing the named outputs below. |
| result.trace | The trace list in the ordering and representation described above. |
| result.unclosedOpeners | The unclosed openers value under the stated formula or text convention. |
{
"input": {
"text": "(a)",
"opener": "(",
"closer": ")"
},
"output": {
"result": {
"trace": [
{
"offset": 0,
"delimiter": "(",
"depth": 1,
"unmatchedClose": false
},
{
"offset": 2,
"delimiter": ")",
"depth": 0,
"unmatchedClose": false
}
],
"unclosedOpeners": 0
}
}
}Limitations and assumptions
- Only one delimiter pair is recognized. Quoting, escaping and language syntax are ignored; the final count does not list every unmatched opener's location.
- Text offsets and lengths use UTF-16 code units unless explicitly described as bytes or code points. CRLF, CR and LF are recognized as line endings; a terminal newline creates a final empty line in the shared line model.
- Every declared top-level field is required and unexpected fields are rejected. Numeric inputs must be finite; ordinary text fields are bounded to 8,192 UTF-16 code units, with tighter operation-specific limits where stated.
- Ordinary string lists have at most 128 entries of at most 128 code units each; numeric lists and matrices have separate bounded size checks. Nonfinite results and excessively large serialized outputs are rejected.
- Indexes are zero-based and spans have an exclusive end unless explicitly stated otherwise. A valid false, null or empty-list result is distinct from malformed input.
Alternative or Complementary methods
Use a parser or language-aware editor when quoting, syntax or nested constructs matter. For plain text transforms, keep UTF-16 offsets, Unicode code points, grapheme clusters and UTF-8 byte offsets distinct; apply changes to the same source version used to calculate spans.
References
Similar or alternative tools
- Single Pair Delimiter Repair Hints
Provide literal single-pair delimiter insertion hints with unmatched offsets; quotes, escapes and cross-type nesting are outside scope.
- acronym
Build an acronym from the uppercase first letter of each whitespace-separated word.