read-textual-bytestring Shiro Kawai (14 Oct 2020 08:38 UTC)
Re: read-textual-bytestring John Cowan (14 Oct 2020 14:23 UTC)
Re: read-textual-bytestring Wolfgang Corcoran-Mathe (14 Oct 2020 18:43 UTC)
Re: read-textual-bytestring Wolfgang Corcoran-Mathe (14 Oct 2020 18:59 UTC)
Re: read-textual-bytestring Shiro Kawai (14 Oct 2020 19:19 UTC)
Re: read-textual-bytestring Wolfgang Corcoran-Mathe (14 Oct 2020 20:52 UTC)
Re: read-textual-bytestring Shiro Kawai (14 Oct 2020 21:20 UTC)
Re: read-textual-bytestring Wolfgang Corcoran-Mathe (14 Oct 2020 21:50 UTC)

Re: read-textual-bytestring Wolfgang Corcoran-Mathe 14 Oct 2020 21:50 UTC

On 2020-10-14 11:20 -1000, Shiro Kawai wrote:
> No, what I mean is that, when you're writing a generic parser, you read
> #u8, and then you can do...
>   (case (peek-char port)
>      ((#\")  (read-textual-bytestring port))  ;; read #u8"..."
>      ((#\()  (list->bytevector (read port)))   ;; read #u8(...)
>      (else (error ...)))

OK, that makes perfect sense now.  I was thinking of the
read-textual-bytestring parser, which of course doesn't have to deal
with the #u8() form.

--
Wolfgang Corcoran-Mathe  <xxxxxx@sigwinch.xyz>

"Prolonged contact with the computer turns mathematicians into
clerks and vice-versa." --Alan J. Perlis