unofficial mirror of guile-user@gnu.org 
 help / color / mirror / Atom feed
From: Wolf <wolf@wolfsden.cz>
To: Matt Wette <matt.wette@gmail.com>
Cc: guile-user@gnu.org
Subject: Re: bytevector seems to be missing in Guile
Date: Sat, 7 Jan 2023 22:12:01 +0100	[thread overview]
Message-ID: <Y7ngIROvaK3R2tF/@ws> (raw)
In-Reply-To: <2dba29d6-8976-fa93-80df-37f32977d486@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 715 bytes --]

On 2023-01-07 12:07:31 -0800, Matt Wette wrote:
> On 1/7/23 8:34 AM, Sascha Ziemann wrote:
> > Is the procedure "bytevector" missing in Guile?
> > 
> > I tried this:
> > guile --r7rs -c '(write (bytevector 1 2 3))'
> > 
> > R7RS defines it on page 49.
> > 
> 
> maybe you need (import (rnrs bytevectors))

I'm far from expert, but it looks to me like (bytevector) in particular is not
provided by guile.

I think the way in guile is

    #vu8(1 2 3)

Or you could make it from list of integers:

    (use-modules (rnrs bytevectors))
    (u8-list->bytevector '(1 2 3))

W.

-- 
There are only two hard things in Computer Science:
cache invalidation, naming things and off-by-one errors.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  reply	other threads:[~2023-01-07 21:12 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-07 16:34 bytevector seems to be missing in Guile Sascha Ziemann
2023-01-07 20:07 ` Matt Wette
2023-01-07 21:12   ` Wolf [this message]
2023-01-07 21:56     ` Taylan Kammer
2023-01-08  0:20       ` Robby Zambito
2023-01-08 12:19         ` Sascha Ziemann
2023-01-08 20:35           ` Robby Zambito

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.gnu.org/software/guile/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=Y7ngIROvaK3R2tF/@ws \
    --to=wolf@wolfsden.cz \
    --cc=guile-user@gnu.org \
    --cc=matt.wette@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).