Byte Array Escaping Inverse
Explicit byte-stuffing inverse with escape followed by reserved byte XOR 0x20; escape and sentinel must differ.
Description
Explicit byte-stuffing inverse with escape followed by reserved byte XOR 0x20; escape and sentinel must differ.
A reserved-byte escape stream can be decoded only when every escape pair follows the same convention.
When to use this tool
Explicit byte-stuffing inverse with escape followed by reserved byte XOR 0x20; escape and sentinel must differ.
- Prepare the supplied bytes, escape, sentinel 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 bytes, escape, sentinel. 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.bytes. Interpret false, null and empty lists using the distinctions below; they can be valid outputs.
Require distinct escape and sentinel bytes. On escape, consume the next byte, XOR with 32 and require the result to equal escape or sentinel. Reject raw sentinel and return decoded bytes.1
| Input field | Meaning and representation | Accepted input |
|---|---|---|
| bytes | bytes. | List of finite numbers; at most 128 entries |
| escape | escape. | Safe integer |
| sentinel | sentinel. | Safe integer |
| Output field | Interpretation |
|---|---|
| result | Object containing the named outputs below. |
| result.bytes | The bytes list in the ordering and representation described above. |
{
"input": {
"bytes": [
1,
27,
32,
27,
59
],
"escape": 27,
"sentinel": 0
},
"output": {
"result": {
"bytes": [
1,
0,
27
]
}
}
}Limitations and assumptions
- Dangling or unknown escape pairs fail. No frame boundary, checksum, encryption or network protocol is inferred.
- 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.
- Lists are limited to 128 entries. JSON text must meet bounded size and depth checks, and numeric outputs beyond the safe finite magnitude are rejected. Exact large integers use decimal strings.
- 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
Retain the field-width, bit-index and byte-order conventions when combining operations. Slicing, escaping, permutation and alignment are separate transforms; none supplies a complete framing or cryptographic protocol.
References
Similar or alternative tools
- Byte Array Escaping Transform
Explicit byte-stuffing transform with escape followed by reserved byte XOR 0x20; escape and sentinel must differ.
- Byte Array Field Slice Table
Slice explicitly bounded half-open byte field spans; overlaps remain allowed and observable.