Re: t/op/integer.t is IMHO wrong

2001-09-19 Thread Dan Sugalski
At 03:56 PM 9/18/2001 -0700, Damien Neil wrote: >On Wed, Sep 19, 2001 at 12:51:43AM +0200, Mattia Barbon wrote: > > I think that especting 4294967295 == -1 because they have the same > > bit pattern ( on two's complement 32 bit machines ) is wrong > >I was wondering how long it would take for some

Re: t/op/integer.t is IMHO wrong

2001-09-18 Thread Simon Cozens
On Wed, Sep 19, 2001 at 12:51:43AM +0200, Mattia Barbon wrote: > I think that especting 4294967295 == -1 because they have the same > bit pattern ( on two's complement 32 bit machines ) is wrong Oh shit, here we go again. Nick Clark, where are you? -- Thus spake the master programmer:

Re: t/op/integer.t is IMHO wrong

2001-09-18 Thread Damien Neil
On Wed, Sep 19, 2001 at 12:51:43AM +0200, Mattia Barbon wrote: > I think that especting 4294967295 == -1 because they have the same > bit pattern ( on two's complement 32 bit machines ) is wrong I was wondering how long it would take for someone to notice that. :> If anyone feels like defining

t/op/integer.t is IMHO wrong

2001-09-18 Thread Mattia Barbon
set I2, -2147483648 print I2 print "\\n" set I3, 4294967295 print I3 print "\\n" end CODE 305419896 -1698898191 2147483647 -2147483648 -1 OUTPUT I think that especting 4294967295 == -1 because they have the same bit pattern