From: ludo@gnu.org (Ludovic Courtès)
To: guile-devel@gnu.org
Subject: Re: review/merge request: wip-array-refactor
Date: Thu, 13 Aug 2009 11:16:09 +0200 [thread overview]
Message-ID: <87k5185b1i.fsf@gnu.org> (raw)
In-Reply-To: m3tz0clmfk.fsf@pobox.com
Hi Andy!
Andy Wingo <wingo@pobox.com> writes:
> On Sun 09 Aug 2009 18:41, ludo@gnu.org (Ludovic Courtès) writes:
>
>> Andy Wingo <wingo@pobox.com> writes:
[...]
>>> I've written lots of code that deals with srfi-4 vectors. I have three
>>> kinds of use cases. First is data being shoved around in a
>>> dynamically-typed system: dbus messages, gconf values, a system we
>>> at work, etc. Second, but related, is dealing with chunks of data that
>>> come from elsewhere, like GDK pixbufs, or GStreamer buffers. Third is
>>> hacking compilers, as in Guile itself, or emitting machine code for
>>> other machines.
[...]
>> SRFI-4 is a good fit for the 2nd use case as you're dealing with
>> fixed-width native-endianness numbers coming from C code.
>
> Agreed, modulo the possibility for this data to be embedded within some
> other stream.
>
>> But in this case, I don't think bytevectors are needed at all.
>
> I think they are needed whenever you want to *do* something with this
> data -- i/o for example.
In the 2nd use case (GDK pixbufs, GStreamer buffers), I suppose you
don't do I/O with the data; it just travels back and forth between C and
Scheme code. Is this correct?
Thanks,
Ludo'.
next prev parent reply other threads:[~2009-08-13 9:16 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-19 13:59 review/merge request: wip-array-refactor Andy Wingo
2009-07-22 21:48 ` Neil Jerram
2009-07-28 22:41 ` Andy Wingo
2009-07-30 21:10 ` Neil Jerram
2009-08-04 12:21 ` Andy Wingo
2009-08-09 16:41 ` Ludovic Courtès
2009-08-12 22:03 ` Andy Wingo
2009-08-13 9:16 ` Ludovic Courtès [this message]
2009-07-23 21:08 ` Ludovic Courtès
2009-07-24 22:01 ` Neil Jerram
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=87k5185b1i.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=guile-devel@gnu.org \
/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).