[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Chicken-janitors] #1576: Keywords get encoded with leading NUL byte, br
From: |
Chicken Trac |
Subject: |
[Chicken-janitors] #1576: Keywords get encoded with leading NUL byte, breaking read-write invariance of symbols starting with a NUL byte |
Date: |
Sat, 12 Jan 2019 15:29:55 -0000 |
#1576: Keywords get encoded with leading NUL byte, breaking read-write
invariance
of symbols starting with a NUL byte
-------------------------------------+-------------------------------------
Reporter: sjamaan | Owner:
Type: defect | Status: new
Priority: minor | Milestone: 5.1
Component: core libraries | Version: 5.0.0
Keywords: keywords, symbols, | Estimated difficulty: medium
read-write invariance |
-------------------------------------+-------------------------------------
Similar to #1077, the string belonging to keywords still get interned by
prefixing it with a NUL byte. This means {{{(string->symbol "\000foo")}}}
gets read as a keyword and printed back as `#:foo`.
This is of course not really correct.
Fixing it means we'll need to get rid of the in-bound signaling of the
keyword information. A potential fix could involve storing keywords in a
different symbol table than regular symbols.
--
Ticket URL: <https://bugs.call-cc.org/ticket/1576>
CHICKEN Scheme <https://www.call-cc.org/>
CHICKEN Scheme is a compiler for the Scheme programming language.
[Prev in Thread] |
Current Thread |
[Next in Thread] |
- [Chicken-janitors] #1576: Keywords get encoded with leading NUL byte, breaking read-write invariance of symbols starting with a NUL byte,
Chicken Trac <=