Numeric Triple Token Parser
Parse an exact 3-component comma-separated finite numeric token with strict decimal/exponent grammar; no missing components or whitespace.
Description
Parse an exact 3-component comma-separated finite numeric token with strict decimal/exponent grammar; no missing components or whitespace.
A numeric triple token contains exactly three comma-separated values. Parsing is independent of any spatial interpretation.
When to use this tool
Parse an exact 3-component comma-separated finite numeric token with strict decimal/exponent grammar; no missing components or whitespace.
- Prepare the supplied token 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 token. 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.values. Interpret false, null and empty lists using the distinctions below; they can be valid outputs.
Require token at most 256 UTF-16 code units, split on commas, require three pieces and parse each with the strict finite decimal/exponent grammar.1
| Input field | Meaning and representation | Accepted input |
|---|---|---|
| token | token. | 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.values | The values list in the ordering and representation described above. |
{
"input": {
"token": "1,-2,3.5"
},
"output": {
"result": {
"values": [
1,
-2,
3.5
]
}
}
}Limitations and assumptions
- Whitespace is not trimmed and no axis labels, units, latitude limits or coordinate system are inferred.
- 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
- Numeric Pair Token Parser
Parse an exact 2-component comma-separated finite numeric token with strict decimal/exponent grammar; no missing components or whitespace.
- Numeric Range Token Parser
Parse one inclusive-shape numeric start..end token under strict decimal grammar; rejects backwards endpoints and does not enumerate the range.