#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 |
Description
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 8 years ago by
comment:3 Changed 6 years ago by
| Milestone: | someday → 4.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 6 years ago by
| Resolution: | → wontfix |
|---|---|
| Status: | new → closed |
Who am I kidding, there won't be a 4.14
Note: See
TracTickets for help on using
tickets.
5.0 doesn't exhibit this behaviour, so any fix is going to be 4.x-specific.