Display values in Decimal and/or Hexadecimal format

The syntax of the "?" command is:
?[,][=][-] ####|0x####
  where ',' inserts commas in decimal formatted output (i.e., #,###,###,###)
  "=" emits both decimal and hexadecimal formatted output with '=' between
  "-" omits the "0x" before hexadecimal formatted output
  #### is a numeric value, in decimal format
  0x#### is a numeric value, in hexadecimal format
Notes:
  No distinction is made between uppercase and lowercase.
  The order of any modifiers before the space is irrelevant.
  Only the first value parsed is displayed.
  The remainder of the line is discarded, or treated as a comment.
  Leading '0' digits (except "0x", of course) are suppressed.
  Overrange (more than 4,294,967,295 or 0xFFFFFFFF) values are not output.

In simplest usage, this command parses then displays the value entered in the "other" format, i.e., if a decimal value is entered, it is displayed in hexadecimal format, and if entered in hexadecimal format, it is output in decimal format. Immedate numeric conversions are often helpful when creating configurations from the command line or debugging new progam logic.

Consider these examples:

>? 0xFFFF
65535
>?, 0xfffe
65,534
>
>? 1234
0x4D2
>E 8 |= 8  ; Turn on hex only parsing
>? 1234
4660
>?, 1234
4,660
>E 8 ^= 8  ; Turn hex parsing off (back to default)
>?, 1234   ; Comma does not affect hex output
0x4D2
>
>? 12345
0x3039
>?- 12345
3039
>?= 12345
12345 = 0x3039
>?=- 12345
12345 = 3039
>?,-= 12345    ; All 3 options again; modifier order changed
12,345 = 3039
>
>? -16     ; Signed decimal conversion
0xFFFFFFF0
>? -1
0xFFFFFFFF
>?- -1
FFFFFFFF
>? 0xFFFFFFFF
4294967295
>?, 0xFFFFffff
4,294,967,295
>
>? = 0x12345
74565
>?= 0x12345
74565  = 0x12345
>?,-= 0x12345    ; All 3 options again
74565  = 12345
>
>?,-= 0x54321
344,865  = 54321
>                                                                               
See also:
  The default Command Extensions code which came with MIRTOS checks for "?" alone and displays a help sequence if it finds precisely that (i.e., even "? " is skipped!)