chicken-hackers
[
Top
][
All Lists
]
Advanced
[
Date Prev
][
Date Next
][
Thread Prev
][
Thread Next
][
Date Index
][
Thread Index
]
[Chicken-hackers] Possible bug in buffer-ports egg?
From
:
Simon Haines
Subject
:
[Chicken-hackers] Possible bug in buffer-ports egg?
Date
:
Sun, 15 Apr 2018 05:23:35 +0000
I think the buffer-ports egg incorrectly sign-extends bytes read from byte vectors that are greater than 127 and have the high bit set.
To reproduce:
(use buffer-ports)
(read-byte (open-input-port #u8(#x80))) ; => #x1FFF80
If this is not the expected behaviour, the attached patch changes this according to the included test case.
Regards,
Simon.
buffer-ports.patch
Description:
Text Data
reply via email to
[Prev in Thread]
Current Thread
[
Next in Thread
]
[Chicken-hackers] Possible bug in buffer-ports egg?
,
Simon Haines
<=
Re: [Chicken-hackers] Possible bug in buffer-ports egg?
,
Evan Hanson
,
2018/04/26
Prev by Date:
Re: [Chicken-hackers] [PATCH] Make result of empty "else" clause undefined in `cond' and `case' forms
Next by Date:
Re: [Chicken-hackers] [PATCH] Make result of empty "else" clause undefined in `cond' and `case' forms
Previous by thread:
[Chicken-hackers] Feature request: make cond more resilient against misuse
Next by thread:
Re: [Chicken-hackers] Possible bug in buffer-ports egg?
Index(es):
Date
Thread