No (bytevector n ...) ? Christian Stigen Larsen (01 Sep 2012 06:54 UTC)
Re: [Scheme-reports] No (bytevector n ...) ? Alex Shinn (01 Sep 2012 15:43 UTC)
[scheme-reports-wg1] Re: [Scheme-reports] No (bytevector n ...) ? John Cowan (01 Sep 2012 17:46 UTC)

[scheme-reports-wg1] Re: [Scheme-reports] No (bytevector n ...) ? John Cowan 01 Sep 2012 17:46 UTC

Alex Shinn scripsit:

On Sat, Sep 1, 2012 at 3:54 PM, Christian Stigen Larsen
<csl@sublevel3.org> wrote:
>
> is there no procedure to create bytevectors beyond using the reader syntax
> #u8(n ...).  Will there be a (bytevector n ...) constructor in the final
> R7RS?

> This seems to be a oversight - we actually use `bytevector'
> in a number of the examples.  I'll bring this up with the
> members.

The oversight was using it in the examples.  Version 4 of BlobAPI, which
is what we voted for in the first and second ballots, contained this
wording:

    Because there is no preferred way to interpret the data in a blob,
    there is no `blob` function analogous to `list` or `vector` and no
    second argument to `make-blob`.

However, when we overrode the second part in the third ballot (ticket #215)
and added a second optional argument to `make-blob` (now `make-bytevector`),
we didn't reconsider the first part.

I have added ticket #471 and copied the WG1 list on this reply.
--
John Cowan <cowan@ccil.org>             http://www.ccil.org/~cowan
Pour moi, les villes du Silmarillion ont plus de r�alit� que Babylone.
		--Christopher Tolkien, as interviewed by Le Monde