Display, graphic, or printable characters?
Lassi Kortela
(11 Nov 2019 13:34 UTC)
|
||
Re: Display, graphic, or printable characters?
John Cowan
(11 Nov 2019 21:57 UTC)
|
||
Re: Display, graphic, or printable characters?
Lassi Kortela
(11 Nov 2019 22:07 UTC)
|
||
(missing)
|
||
(missing)
|
||
(missing)
|
||
Re: Display, graphic, or printable characters?
Lassi Kortela
(12 Nov 2019 11:53 UTC)
|
||
Re: Display, graphic, or printable characters?
John Cowan
(12 Nov 2019 17:13 UTC)
|
||
Re: Display, graphic, or printable characters?
Lassi Kortela
(18 Nov 2019 19:46 UTC)
|
||
Re: Display, graphic, or printable characters? Lassi Kortela (22 Nov 2019 12:56 UTC)
|
||
Re: Display, graphic, or printable characters?
Lassi Kortela
(22 Nov 2019 13:18 UTC)
|
||
Re: Display, graphic, or printable characters?
Lassi Kortela
(22 Nov 2019 13:20 UTC)
|
||
Re: Display, graphic, or printable characters?
Lassi Kortela
(11 Nov 2019 23:34 UTC)
|
Even more trouble from a closer reading of SRFI 14: char-set:blank space and tab char-set:graphic letter + digit + punctuation + symbol char-set:printing graphic + whitespace char-set:whitespace space, newline, tab, FF, VT, CR So the "printing" characters include ALL whitespace characters, not just the space character. That means it would be misleading to use "ascii-printing?" to refer only to the space character + graphic characters in SRFI 175. I still believe an "only space + graphic" procedure is more useful/reliable than an "all whitespace + graphic" procedure. The C/Unix world would seem to agree. Common Lisp does too. ANSI CL does not define a tab character but CLISP, SBCL and CCL all say (graphic-char-p #\tab) is false.