unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: Andy Wingo <wingo@pobox.com>
To: ludo@gnu.org (Ludovic Courtès)
Cc: guile-devel@gnu.org
Subject: Re: [Guile-commits] GNU Guile branch, master, updated. 782a82eed13abb64393f7acad92758ae191ce509
Date: Fri, 19 Jun 2009 09:50:54 +0200	[thread overview]
Message-ID: <m3skhw8xwh.fsf@pobox.com> (raw)
In-Reply-To: <861vph1e3o.fsf@gnu.org> ("Ludovic Courtès"'s message of "Thu, 18 Jun 2009 22:28:11 +0200")

Howdy,

On Thu 18 Jun 2009 22:28, ludo@gnu.org (Ludovic Courtès) writes:

> Andy Wingo <wingo@pobox.com> writes:
>
>>>> +           uniform-array->bytevector
>>>
>>> I would not export it from `(rnrs bytevector)' given that it has nothing
>>> to do with RnRS.
>>
>> No, but it does have to with bytevectors... Where would you put it?
>
> Dunno, maybe not anywhere public?

Er, I wrote it so I could use it in my code... Not being able to get at
the bits of uniform arrays from Scheme has been a sorely missing feature
for a long time now...

>>> Also, I would make the new C functions private, given that they are not
>>> intended for general use AIUI.
>>
>> Dunno. I could imagine calling both of them from C. Would there be a
>> problem with leaving them to be public?
>
> Yes, while we're not more confident wrt. shared arrays and similar.

What do you mean? I think that shared arrays will be attempted to be
linearized via scm_array_contents, which will throw an error for a
non-contiguous array. That's as good as we can do, no?

Andy
-- 
http://wingolog.org/




  reply	other threads:[~2009-06-19  7:50 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <E1MCaTQ-0003wD-Sn@cvs.savannah.gnu.org>
2009-06-06 14:31 ` [Guile-commits] GNU Guile branch, master, updated. 782a82eed13abb64393f7acad92758ae191ce509 Ludovic Courtès
2009-06-07 17:24   ` Andy Wingo
2009-06-18 20:28     ` Ludovic Courtès
2009-06-19  7:50       ` Andy Wingo [this message]
2009-06-19  8:20         ` Ludovic Courtès

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=m3skhw8xwh.fsf@pobox.com \
    --to=wingo@pobox.com \
    --cc=guile-devel@gnu.org \
    --cc=ludo@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).