Comment Preferences

"B" is 11.

• Actually, no.(0+ / 0-)

10  = 2
11 = 3

A = 1010
B = 1011

and I just proved myself wrong.  1011 is B, not D.

My children are the joy of my life

[ Parent ]

• No. You are conflating ASCII with hex.(2+ / 0-)
Recommended by:
Mr Robert, bontemps2012

Hex is base 16, so it needs single-digit representations for 0 to 15. The number after 9 is A, with a value of ten. B is 11, C is 12, D is 13.

The number 10 in hex is sixteen, because the second from right digit is the number of sixteens.

bontemps2012 is 100% correct above.

Binary and hex are related in that every four buts (binary digits) can correspond to one hex digit.

1011 in binary equals eleven (8+3+1). In hex that would be B.

1011 in HEX Is much, much larger (4096+16+1).

101112 cannot be a binary number because of the two. There are only two digits in binary.

In capitalist America, bank robs you!

[ Parent ]

• Bits not buts damn you autocorrect(1+ / 0-)
Recommended by:
STEVEinMI

Also I see what you meant there, it wasn't ASCII but taking groups of four bits. The confusion is in marking hex vs decimal values clearly.  Sorry for my earlier misinterpretation of your comment, but you did munge hex with decimal with binary in wrongly correcting bt.

1011 = eleven = B.

In capitalist America, bank robs you!

[ Parent ]

• I should have said hexadecimal to begin with. (0+ / 0-)

In my profession we always shorten it to 'hex'.

My children are the joy of my life

[ Parent ]

• No, you should have not munged which system was(1+ / 0-)
Recommended by:
bontemps2012

Which in correcting bontemps2012. Bt was correct that B is eleven and B is 1011 from binary.

Calling it hex vs hexadecimal was not the issue.

In capitalist America, bank robs you!

[ Parent ]

• Which is why I've always had a weakness(1+ / 0-)
Recommended by:

for octal. (True, but chortleable.)

If they haven't worked with core dumps, today, there's next to no chance you will see people with "fluency" reading hex.

The top of it for hex was when we coded our own assembler routines -- mainly forced by limited memory. Even with mainframe systems, if you wanted to read data off disks at full speed then you had to write your own channel driver.

Then, for fun, there was the IBM 704 with LISP 1.5... and we had one 'cuz the card reader wouldn't die.

• I dunno, even the blue screen of death has(1+ / 0-)
Recommended by:
bontemps2012

been known to dump core.

But I had to write an assembler mumble mumble years ago, which si why I can read hex, octal, binary, and keep a translation of them all going.

So for yesterday, 1011 in decimal would be 111111001 in binary.  At least figuring out 1011 in hex to binary is relatively trivial.

In capitalist America, bank robs you!

[ Parent ]

Subscribe or Donate to support Daily Kos.