Skip to content

Main content

Bitwise: Adjacent Bit Pair Exchange Tool

Exchange adjacent low/high bit pairs across an explicitly even-width word, preserving all bits without JavaScript 32-bit coercion.

Loading tool…

Description

Exchange each adjacent bit pair in a word.

Bit positions are usually counted from the least-significant bit, while a displayed binary string has its own left-to-right indexing convention. Masks, fields and parity predicates describe a selected region or pattern; local agreement does not validate a complete encoded record.

Exchange each adjacent bit pair in a word.

When to use this tool

Use Bitwise: Adjacent Bit Pair Exchange when checking the stated mask, field, parity or bit-index convention.

How to use the tool and how it works

  1. Enter word, width. Use the units and conventions below.
  2. Run the tool. Correct any format, range, or cross-field input error before interpreting the output.
  3. Read result. Expand result to inspect the returned fields.

Exchange each adjacent bit pair in a word. Validate bounded word and even width; swap positions (0,1),(2,3),... and return exact decimal text.1

Input fieldMeaning and unitsAccepted input
wordWordRequired. Text. Integer syntax: optional + or - and 1-128 decimal digits; leading zeros accepted. Apply the sign restriction above. Implementation limit: 8192 Unicode code points and 16384 UTF-16 code units. Word value must satisfy 0 <= value < 2^width.
widthWidth under the stated bit, interval or geometry convention; apply the field-specific units and bounds.Required. Safe integer. Fixed-word implementation domain: whole width 1-128 bits.
Output fieldInterpretationReturned shape
resultReturned calculated value or nested object under the stated output convention.Required. Object.
result.exchangedExchangedCalculated result member: string.
json
{
  "input": {
    "word": "9",
    "width": 4
  },
  "output": {
    "result": {
      "exchanged": "6"
    }
  }
}

Limitations and assumptions

  • This is not full bit reversal, byte reversal or a machine instruction invocation.
  • Outputs are nested inside result. 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.
  • Numeric calculations use binary floating point unless exact decimal-integer arithmetic is explicitly stated. No hidden measurement tolerance or decimal rounding is added; nonfinite or out-of-contract results are rejected. Numeric signed-zero results are exported as zero.

Alternative or Complementary methods

Choose an explicit bit order, word width and missing-position policy; use the complete record format and appropriate parsing or checksum methods for full validation.

References

  1. Calculation and input contract: bitwise/adjacent-bit-pair-exchange — tool.io

Similar or alternative tools