From: Andy Wingo <wingo@pobox.com>
To: Daniel Llorens <daniel.llorens@bluewin.ch>
Cc: ludo@gnu.org, guile-devel@gnu.org
Subject: Re: propose deprecation of generalized-vector-*
Date: Wed, 23 Jan 2013 10:06:50 +0100 [thread overview]
Message-ID: <87mww0nu8l.fsf@pobox.com> (raw)
In-Reply-To: <2E5FFE0D-9001-409C-BCD4-9EE3BF9883F0@bluewin.ch> (Daniel Llorens's message of "Tue, 22 Jan 2013 15:31:19 +0100")
On Tue 22 Jan 2013 15:31, Daniel Llorens <daniel.llorens@bluewin.ch> writes:
> On Jan 21, 2013, at 17:11, Andy Wingo wrote:
>
> The patch attached applies over yours and is to document this function
> and a couple others in the manual.
Thanks, applied and pushed to wip-generalized-vectors.
> Maybe we should have scm_array_ref_1, scm_array_ref_2, etc. as it is
> done for some other functions taking rest lists. I can write a patch
> for that.
For C, that makes sense. Something should be done for Scheme as well,
but it's not terribly urgent. Perhaps make scm_array_ref not be bound
to "array-ref", and instead bind "array-ref" to some function that takes
two optional arguments and a rest argument. A poor man's case-lambda...
> It makes sense to let vector- work on uniform vectors because the
> implementation should be identical.
FWIW this is not the case. Vectors hold SCM objects, whereas uniform
vectors hold unpacked machine values. It's possible to have a
one-dimensional slice of a uniform array also.
Now on to your next mail...
Andy
--
http://wingolog.org/
next prev parent reply other threads:[~2013-01-23 9:06 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.153.1351958430.10005.guile-devel@gnu.org>
2012-11-03 16:52 ` propose deprecation of generalized-vector-* Daniel Llorens
2012-11-03 21:10 ` Ludovic Courtès
2013-01-21 16:11 ` Andy Wingo
2013-01-22 14:31 ` Daniel Llorens
2013-01-22 18:31 ` Daniel Llorens
2013-01-22 20:52 ` Andy Wingo
2013-01-22 23:27 ` Daniel Llorens
2013-01-23 9:20 ` Andy Wingo
2013-01-23 14:55 ` Ludovic Courtès
2013-01-23 9:06 ` Andy Wingo [this message]
2013-01-23 12:20 ` Daniel Llorens
2013-02-18 15:55 ` Andy Wingo
2013-02-18 16:05 ` Noah Lavine
2013-02-18 16:25 ` Mike Gran
2013-02-18 16:29 ` Noah Lavine
2013-02-18 17:11 ` David Pirotte
2013-02-18 17:17 ` Mike Gran
2013-02-18 23:57 ` Daniel Hartwig
2013-02-18 23:12 ` Problems with 'number->string' (was Re: propose deprecation of generalized-vector-*) Mark H Weaver
2013-02-21 1:13 ` propose deprecation of generalized-vector-* Daniel Llorens
2013-02-22 0:22 ` Noah Lavine
2013-02-28 19:10 ` Daniel Llorens
2013-03-01 2:42 ` Noah Lavine
2013-03-01 3:46 ` Noah Lavine
2013-03-01 9:01 ` Daniel Llorens
2013-03-01 9:44 ` Andy Wingo
2013-03-04 2:27 ` Noah Lavine
2013-03-08 23:42 ` array operations Daniel Llorens
2013-02-18 15:40 ` propose deprecation of generalized-vector-* Andy Wingo
2013-02-28 23:04 Nelson H. F. Beebe
2013-03-04 12:48 ` Aharon Robbins
[not found] <mailman.191.1348070449.18828.guile-devel@gnu.org>
2012-09-19 17:20 ` Daniel Llorens
-- strict thread matches above, loose matches on Subject: below --
2012-09-18 14:49 Daniel Llorens
2012-09-19 12:02 ` Peter TB Brett
2012-11-02 23:27 ` 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=87mww0nu8l.fsf@pobox.com \
--to=wingo@pobox.com \
--cc=daniel.llorens@bluewin.ch \
--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).