Opened 7 years ago

Closed 5 years ago

Last modified 5 years ago

#1365 closed defect (wontfix)

bitwise-not returns wrong values on non-negative arguments

Reported by: johnwcowan Owned by:
Priority: minor Milestone: 5.1
Component: core libraries Version: 4.12.0
Keywords: Cc:
Estimated difficulty: trivial


The expression (bitwise-not 0) returns 4611686018427387903 (i.e. 0x3fffffffffffffff) instead of -1. The fxnot procedure does not have this problem, nor does the numbers-egg version of bitwise-not. However, (bitwise-not -1) correctly returns 0.

Change History (5)

comment:1 Changed 7 years ago by evhan

5.0 doesn't exhibit this behaviour, so any fix is going to be 4.x-specific.

comment:2 Changed 7 years ago by sjamaan

Looks like I haven't had my morning coffee yet ;)

Last edited 7 years ago by sjamaan (previous) (diff)

comment:3 Changed 6 years ago by sjamaan

Milestone: someday4.14.0

It's only a CHICKEN 4 issue. If we ever decide to make a 4.14.0, we should tackle this. Otherwise we can just close it as wontfix, because in CHICKEN 5 it works as it should.

comment:4 Changed 5 years ago by sjamaan

Resolution: wontfix
Status: newclosed

Who am I kidding, there won't be a 4.14

comment:5 Changed 5 years ago by sjamaan


Ticket retargeted after milestone deleted

Note: See TracTickets for help on using tickets.