Character Class Overlap Table
Return exact overlap codes between explicit ASCII character banks; no Unicode normalization or regex execution.
Description
Return exact overlap codes between explicit ASCII character banks; no Unicode normalization or regex execution.
Two explicit ASCII character sets overlap on the codes they share. Numeric sets avoid ambiguous class syntax.
When to use this tool
Return exact overlap codes between explicit ASCII character banks; no Unicode normalization or regex execution.
- Prepare the supplied left, right 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 left, right. 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.overlap. Interpret false, null and empty lists using the distinctions below; they can be valid outputs.
Require every input code from 0 to 127. Deduplicate the left list, retain codes also in right and sort overlap ascending.1
| Input field | Meaning and representation | Accepted input |
|---|---|---|
| left | left. | List of finite numbers; at most 128 entries |
| right | right. | List of finite numbers; at most 128 entries |
| Output field | Interpretation |
|---|---|
| result | Object containing the named outputs below. |
| result.overlap | The overlap list in the ordering and representation described above. |
{
"input": {
"left": [
1,
2,
2
],
"right": [
2,
3
]
},
"output": {
"result": {
"overlap": [
2
]
}
}
} Limitations and assumptions
- No regex source or Unicode properties are parsed. Input duplicates do not produce duplicate output codes.
- 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
Compile generated pattern sources with explicitly chosen flags and test them on bounded representative text. Pattern sources, replacement strings and JSON string spellings require different escaping conventions.
References
Similar or alternative tools
- ASCII Character Class Complement
Complement an explicit code set against ASCII 0–127 only, not Unicode or a regex engine’s complete character universe.
- ASCII Character Class Formatter
Format a positive ASCII character class using explicit two-digit hexadecimal escapes, avoiding metacharacter ambiguity.