Eh, how often are you going down to the bit representation of signed integers? Naturally I learned two's complement ages ago, but all of my bitwise manipulation seems to be on unsigned integers (and frankly I've only used bitwise operations at work once for implementing bloom filters. Normally I only get to do lower level stuff like that in side-projects). So internalizing two's complement has never seemed relevant.

> And a byte value of 128? What is that in hex?

0x80

▲ jibal 3 days ago | parent [-]

> 0x80

Which is of course has the sign bit set.

The comments here are educational ... I hadn't realized that the field of programming had become this degraded.

▲ jibal a day ago | parent | next [-]

> Such needless condescension, jibal.

THAT comment is condescending--talk about ideas, not people. I condescended to no one ... my issue is the state of computer science education.

> On the contrary, there is no sign bit. You asked for 128

I didn't ask for anything. The subject here was the value range of the i8 type.

	▲	craftkiller a day ago \| parent [-]
		> I didn't ask for anything. To quote you: "What is that in hex?"

▲ craftkiller 2 days ago | parent | prev | next [-]

On the contrary, there is no sign bit. You asked for 128 which is either:

  1. Unrepresentable in S8
  2. Representable in U8 as shown in my above comment.
  3. Representable in S16 as 0x0080 but then the sign bit is not set.

My comment accurately represents the hex encoding for #2.

▲ superblas 2 days ago | parent | prev [-]

Such needless condescension, jibal.