From: tomas@fabula.de
Subject: Re: Strange behaviour of array?
Date: Fri, 15 Nov 2002 09:46:33 +0100 [thread overview]
Message-ID: <20021115084633.GA18194@www> (raw)
In-Reply-To: <20021115021213.B12469@kiwi.pyrotechnics.com>
On Fri, Nov 15, 2002 at 02:12:13AM -0600, Christopher Cramer wrote:
> On Tue, Nov 05, 2002 at 12:57:06PM +0100, tomas@fabula.de wrote:
[...]
> I distinctly remember sending a patch to fix this to either bug-guile or
> guile-devel a loooong time ago, but I can't find it in the archives. I'm
> surprised it's not fixed in 1.6.0, but maybe it's because I never sent
> the patch in...
Thanks a zillion. I'll try this out when out of crunch mode.
I'll keep you informed
Regards
-- tomas
_______________________________________________
Bug-guile mailing list
Bug-guile@gnu.org
http://mail.gnu.org/mailman/listinfo/bug-guile
next prev parent reply other threads:[~2002-11-15 8:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20021105115705.GA6539@www>
2002-11-15 8:12 ` Strange behaviour of array? Christopher Cramer
2002-11-15 8:46 ` tomas [this message]
2002-11-17 15:29 ` Marius Vollmer
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=20021115084633.GA18194@www \
--to=tomas@fabula.de \
/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).