|
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 22:52 UTC
> I second for ascii-codepoint. > > ascii-byte? suggests there are different kind of "byte"s, which isn't the > case. > > On the same ground I'm not inclined to ascii-bytevector?, but > ascii-codepoint-bytevector? is too long so I accept it. They could also be: * byte-ascii? * char-ascii? * bytevector-ascii? * string-ascii? Or ascii-byte? could be ascii-integer?