Gneale: Created page with "===== Return to: Chialisp ===== According to Matt Howard 20210816, there is a "peculiarity with how integers are encoded in bytes. It's signed integers. If you just return `run '(q . 0xd7)'` you get -41 because the most significant bit is set and that's telling the interpreter to read this as a negative number. If you add some leading zeroes `run '(q . 0x00d7)'`, it should pop out as you would expect". Returns 215.

Orig..."

2023-11-17T15:56:34Z

Created page with "===== Return to: Chialisp ===== According to Matt Howard 20210816, there is a "peculiarity with how integers are encoded in bytes. It's signed integers. If you just return <code>run '(q . 0xd7)'</code> you get -41 because the most significant bit is set and that's telling the interpreter to read this as a negative number. If you add some leading zeroes <code>run '(q . 0x00d7)'</code>, it should pop out as you would expect". Returns 215. <h1>Orig..."

New page

===== Return to: [[Chialisp|Chialisp]] =====

According to Matt Howard 20210816, there is a "peculiarity with how integers are encoded in bytes.

It's signed integers.

If you just return <code>run '(q . 0xd7)'</code> you get -41 because the most significant bit is set and that's telling the interpreter to read this as a negative number.

If you add some leading zeroes <code>run '(q . 0x00d7)'</code>, it should pop out as you would expect".

Returns 215.

<h1>Original concern</h1>

Q: I still have one question: why does <code>brun '(- (q . 0xd7) (q . 0x1))'</code> return -42?

A: <code>hex(-42 & 0xff) == '0xd6''</code> I see thanks!

Integer byte encoding peculiarity - Revision history

Orig..."