From: Kevin Ryde <user42@zip.com.au>
Subject: Re: Bug in make-shared-array.
Date: Thu, 04 May 2006 09:29:41 +1000 [thread overview]
Message-ID: <87ejzag00q.fsf@zip.com.au> (raw)
In-Reply-To: <8764kppcnz.fsf@minimini.mvo.home> (Marius Vollmer's message of "02 May 2006 02:07:12 +0300")
Marius Vollmer <mvo@zagadka.de> writes:
>
> This behavior might or might not be a feature, but if you really want
> it, it is probably better to use array-contents explicitely.
Yep, that should be an error.
_______________________________________________
Bug-guile mailing list
Bug-guile@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-guile
next prev parent reply other threads:[~2006-05-03 23:29 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-27 23:12 Bug in make-shared-array Steve Juranich
2006-03-03 23:52 ` Kevin Ryde
2006-03-11 0:07 ` Neil Jerram
2006-05-01 21:48 ` Marius Vollmer
2006-05-01 22:13 ` Marius Vollmer
2006-05-01 23:07 ` Marius Vollmer
2006-05-03 23:29 ` Kevin Ryde [this message]
2006-05-04 17:55 ` Steve Juranich
2006-05-04 21:27 ` Marius Vollmer
2006-06-14 0:45 ` Neil Jerram
-- strict thread matches above, loose matches on Subject: below --
2006-02-27 18:16 Steve Juranich
2006-02-27 16:16 Steve Juranich
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=87ejzag00q.fsf@zip.com.au \
--to=user42@zip.com.au \
/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).