Description
Locate ASCII camel-case word boundaries.
Build and configuration formats have dialect-specific quoting, whitespace and escaping rules. A local prefix or character transformation handles only the declared fragment, leaving full parsing, evaluation and precedence to the consuming implementation.
Locate ASCII camel-case word boundaries.
When to use this tool
Use Identifier Case Boundary when inspecting the stated text or configuration fragment.
How to use the tool and how it works
- Enter identifier. Use the units and conventions below.
- Run the tool. Correct any format, range, or cross-field input error before interpreting the output.
- Read boundaries. Use the output convention below.
Locate ASCII camel-case word boundaries. Scan UTF-16 indexes for lowercase/digit-to-uppercase transitions and acronym-to-capitalized-word transitions; return zero-based boundary indexes.1
| Input field | Meaning and units | Accepted input |
|---|---|---|
| identifier | Identifier | Required. Text; maximum UTF-16 length 8192. |
| Output field | Interpretation | Returned shape |
|---|---|---|
| boundaries | ASCII case-transition boundaries as UTF-16 string indices; not grapheme positions. | Required. Array of safe integer; maximum items 256. |
{
"input": {
"identifier": "parseHTTPValue"
},
"output": {
"boundaries": [
5,
9
]
}
}Limitations and assumptions
- Non-ASCII case behavior, grapheme clusters and identifier validity are not inferred.
- Inputs must satisfy both the field types and the cross-field conditions above. Invalid input causes an error; a successful false flag or documented placeholder is a different result.
Alternative or Complementary methods
Use the appropriate full parser and actual configuration context for reliable interpretation or application.
References
Similar or alternative tools
- Code Point Identifier Escape Budget
Budget literal Unicode identifier escapes from supplied scalar values.
- Ini Section Leading Trailing Space Rule
Parse a single INI section header under an explicit trim rule.