New draft (#4) of SRFI 207: String-notated bytevectors Arthur A. Gleckler (05 Oct 2020 15:56 UTC)
Re: New draft (#4) of SRFI 207: String-notated bytevectors Wolfgang Corcoran-Mathe (05 Oct 2020 17:29 UTC)
Re: New draft (#4) of SRFI 207: String-notated bytevectors Daphne Preston-Kendal (05 Oct 2020 18:05 UTC)
Re: New draft (#4) of SRFI 207: String-notated bytevectors Wolfgang Corcoran-Mathe (05 Oct 2020 19:18 UTC)
Re: New draft (#4) of SRFI 207: String-notated bytevectors Marc Nieper-Wißkirchen (05 Oct 2020 20:19 UTC)
Re: New draft (#4) of SRFI 207: String-notated bytevectors Wolfgang Corcoran-Mathe (06 Oct 2020 05:44 UTC)
Re: New draft (#4) of SRFI 207: String-notated bytevectors Wolfgang Corcoran-Mathe (06 Oct 2020 16:14 UTC)
Re: New draft (#4) of SRFI 207: String-notated bytevectors Marc Nieper-Wißkirchen (06 Oct 2020 17:16 UTC)
Re: New draft (#4) of SRFI 207: String-notated bytevectors Daphne Preston-Kendal (07 Oct 2020 09:07 UTC)
Re: New draft (#4) of SRFI 207: String-notated bytevectors Marc Nieper-Wißkirchen (07 Oct 2020 09:24 UTC)
Re: New draft (#4) of SRFI 207: String-notated bytevectors Daphne Preston-Kendal (07 Oct 2020 09:49 UTC)
Re: New draft (#4) of SRFI 207: String-notated bytevectors Arthur A. Gleckler (07 Oct 2020 15:08 UTC)
Re: New draft (#4) of SRFI 207: String-notated bytevectors Marc Nieper-Wißkirchen (07 Oct 2020 15:22 UTC)
Re: New draft (#4) of SRFI 207: String-notated bytevectors Wolfgang Corcoran-Mathe (07 Oct 2020 15:57 UTC)
Re: New draft (#4) of SRFI 207: String-notated bytevectors Marc Nieper-Wißkirchen (07 Oct 2020 16:06 UTC)
Re: New draft (#4) of SRFI 207: String-notated bytevectors Wolfgang Corcoran-Mathe (07 Oct 2020 16:22 UTC)
Re: New draft (#4) of SRFI 207: String-notated bytevectors Wolfgang Corcoran-Mathe (06 Oct 2020 18:14 UTC)
Re: New draft (#4) of SRFI 207: String-notated bytevectors Daphne Preston-Kendal (07 Oct 2020 10:01 UTC)

Re: New draft (#4) of SRFI 207: String-notated bytevectors Wolfgang Corcoran-Mathe 07 Oct 2020 16:22 UTC

On 2020-10-07 18:06 +0200, Marc Nieper-Wißkirchen wrote:
> Speaking of this procedure: Isn't a similar procedure that returns a
> generator (instead of directly writing the bytes to a port) more
> general and useful?

e.g. make-bytestring-generator?  So that the following are
operationally equivalent:

    (generator-for-each (lambda (b) (write-u8 b out))
                        (make-bytestring-generator arg ...))

    (write-binary-bytestring out arg ...)

If this is correct, the verbosity of the first version is leading me
to believe that write-binary-bytestring should stay.  But yes, a
bytestring generator would be a useful thing to have in general.

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

"Some folks think Postmodernism means little more than the Empowerment
of the Vulgar.  Some folks think the same about Perl." --Larry Wall