|
ascii-string? predicate
Lassi Kortela
(20 Sep 2019 09:51 UTC)
|
|
Re: ascii-string? predicate
John Cowan
(20 Sep 2019 18:25 UTC)
|
|
ascii-string/char/byte/bytevector predicates
Lassi Kortela
(20 Sep 2019 19:53 UTC)
|
|
Re: ascii-string/char/byte/bytevector predicates
John Cowan
(20 Sep 2019 20:20 UTC)
|
|
Re: ascii-string/char/byte/bytevector predicates Lassi Kortela (20 Sep 2019 20:26 UTC)
|
|
Re: ascii-string/char/byte/bytevector predicates
Shiro Kawai
(20 Sep 2019 22:22 UTC)
|
|
Re: ascii-string/char/byte/bytevector predicates
Lassi Kortela
(20 Sep 2019 22:52 UTC)
|
|
Re: ascii-string/char/byte/bytevector predicates
Shiro Kawai
(21 Sep 2019 03:48 UTC)
|
|
Re: ascii-string/char/byte/bytevector predicates
Lassi Kortela
(21 Sep 2019 09:24 UTC)
|
|
Re: ascii-string/char/byte/bytevector predicates
Lassi Kortela
(21 Sep 2019 09:28 UTC)
|
Re: ascii-string/char/byte/bytevector predicates Lassi Kortela 20 Sep 2019 20:26 UTC
> Part of my job is to keep terminology consistent. "Byte" is already > defined as 0-255 in R6/R7RS. A good principle, and a good definition for "byte". > I stll like "ASCII codepoint" in the text and "codepoint" in the procedure > name. I intended "ascii-byte?" to mean "a byte that is ASCII", as distinguished from a byte that is not ASCII (or an integer that is not a byte).