Skip to content

Add 16-bit byte-swapped number output - #2

Open
CtrlLogicDev wants to merge 1 commit into
jiripolasek:masterfrom
CtrlLogicDev:feature/byte-swapped-16-bit
Open

Add 16-bit byte-swapped number output#2
CtrlLogicDev wants to merge 1 commit into
jiripolasek:masterfrom
CtrlLogicDev:feature/byte-swapped-16-bit

Conversation

@CtrlLogicDev

Copy link
Copy Markdown

Summary

  • Add a 16-bit byte-swapped result for signed INT and unsigned WORD/register values.
  • Preserve the existing parsing, explicit bit-length, input-base formatting, and copy conventions.
  • Add focused tests and a brief README feature-list entry.

Details

The conversion swaps the two bytes of the resulting 16-bit pattern:

((value & 0x00FF) << 8) | ((value & 0xFF00) >> 8)

Negative values use the application's existing two's-complement semantics. Values outside the signed/unsigned 16-bit range do not receive this result. This intentionally excludes 32-bit word swapping, full byte reversal, and floating-point reinterpretation.

Validation

  • dotnet format JPSoftworks.DevNumbers.slnx --no-restore --include src\DevNumbers.Engine\ByteOrderHelper.cs tests\DevNumbers.Test\ByteOrderHelperTest.cs --verbosity minimal
  • dotnet build JPSoftworks.DevNumbers.slnx --configuration Debug -p:Platform=x64 --no-restore — succeeded with 0 errors (3 existing nullable warnings)
  • dotnet test JPSoftworks.DevNumbers.slnx --configuration Debug -p:Platform=x64 --no-build — 168 passed, 0 failed, 0 skipped
  • Manually validated decimal and hexadecimal results in PowerToys Command Palette.

@CtrlLogicDev
CtrlLogicDev marked this pull request as ready for review July 31, 2026 23:27
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant