|
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 21 Sep 2019 09:28 UTC
> * ascii-integer? > * ascii-char? > * ascii-bytevector? > * ascii-string? Having the "ascii-" prefix first is also clearer in that these should accept any object. For example, (ascii-integer? "foo") => #f should be perfectly valid, as should (ascii-bytevector? 123.45) => #f. I guess we could have (bytevector-ascii? ...) that raises an exception if the argument is not a bytevector, but that seems more complex than just returning #f for non-bytevectors.