[rwmj]

I just tried it on the ZX81 online emulator: http://www.zx81stuff.org.uk/zx81/jtyone.html

You have to type the following sequence of keys:

  P  [Shift]I  2  [Shift]H  3  2  [Shift]O  -
  [Shift]I  [Shift]I  2  [Shift]H  3  2  [Shift]O
  -  1  [Shift]O  Enter

which should appear as:

  PRINT (2**32)-((2**32)-1)

It prints 0 which is not the expected answer! (The 0/0 at the bottom of the screeen is an OK message, the answer is printed in the top left corner). I think this isn't necessarily a bug, it's because the computer used something similar to modern single precision floating point.

Also try this (SQR is entered as: [Shift]Enter H):

  PRINT SQR 0.25

On the emulator it looks like the bug has been fixed, but on early models of the real hardware it would give a completely bogus result.

I think what was interesting was it used a kind of bytecode to run maths routines (similar to the Apple II's SWEET16 code).

[zokier]

0 is actually what I'd expect as an answer. Even on very modern Python you get

    In [1]: 2.0**64 - (2.0**64-1.0)
    Out[1]: 0.0

Thats how floats behave like with operands that differ greatly in magnitude. Also this

    In [2]: 2.0**64 == (2.0**64 - 1.0)
    Out[2]: True

[trynton]

> 0 is actually what I'd expect as an answer. Even on very modern Python you get

Given a four byte mantissa, it should be 1 for anything under and equal to 2^32 and 0 for anything over 2^32. Instead it outputted some random number. A bug in checking the flags or some-such. Or maybe a bug in the float to string routine.

[zokier]

The sign takes one bit off the mantissa.

[anthk]

"1" in Scheme:

    >(- (expt 2 64) (- (expt 2 64) 1))
    1

http://people.csail.mit.edu/jaffer/SCM.html

[jhbadger]

Are you sure that isn't just doing integer math? I don't have a scheme implementation handy, but I tried it in sbcl Common Lisp and while (- (expt 2 64) (- (expt 2 64) 1)) does yield 1,

(- (expt 2.0 64) (- (expt 2.0 64) 1)) yields 0.

[anthk]

True, 0. But I think Guile had an exact->inexact function.

[trynton]

According to the link to ""ZX81 ROM Assembly Listing"", it used a "FORTH-like, stack-based language.". Amazing all the same how they managed to squeeze so much out of so little.