Balanced Parenthesis Token Splitter
Split a literal delimiter only outside balanced parentheses; parentheses are retained, quotes and escapes have no special meaning.
Description
Split a literal delimiter only outside balanced parentheses; parentheses are retained, quotes and escapes have no special meaning.
A top-level delimiter can be ignored inside balanced parentheses. This tokenizer tracks nesting without evaluating the enclosed text.
When to use this tool
Split a literal delimiter only outside balanced parentheses; parentheses are retained, quotes and escapes have no special meaning.
- Prepare the supplied text, delimiter 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, delimiter. 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.tokens. Interpret false, null and empty lists using the distinctions below; they can be valid outputs.
Require a one-character delimiter other than a parenthesis. Scan code points while updating parenthesis depth, reject negative or nonzero final depth and split only at depth zero, retaining parentheses in token text.1
| Input field | Meaning and representation | Accepted input |
|---|---|---|
| text | text. | Text; at most 8,192 UTF-16 code units, subject to the grammar above |
| delimiter | delimiter. | 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.tokens | The tokens list in the ordering and representation described above. |
{
"input": {
"text": "a,(b,c),d",
"delimiter": ","
},
"output": {
"result": {
"tokens": [
"a",
"(b,c)",
"d"
]
}
}
}Limitations and assumptions
- Quotes, escapes, comments and other bracket types have no special meaning. Empty fields remain, and at most 128 tokens are accepted.
- All declared input fields are required and unexpected top-level fields are rejected. Numbers must be finite; lists are limited to 128 entries and ordinary text fields to 8,192 UTF-16 code units, with tighter limits where stated.
- JSON text inputs must parse within bounded nesting and size limits. Numeric outputs outside the safe finite range are rejected; large exact integer results use decimal strings. Indexes and half-open spans are zero-based unless a rank is explicitly described as one-based.
Alternative or Complementary methods
Use a parser for the actual target format when the task requires CSV, shell, URL, calendar or filesystem semantics. These tools implement the specific small grammars stated here, without adding those surrounding conventions.
References
Similar or alternative tools
- Escaped Delimiter Token Splitter
Split or join an explicit backslash-escaped single-character delimiter dialect with control escapes; not CSV, shell or programming-language syntax.
- Escaped Delimiter Token Joiner
Split or join an explicit backslash-escaped single-character delimiter dialect with control escapes; not CSV, shell or programming-language syntax.