From: Marius Vollmer <mvo@zagadka.de>
Cc: guile-devel@gnu.org
Subject: Re: GMP bignum results using double cells.
Date: 02 Mar 2003 02:40:53 +0100 [thread overview]
Message-ID: <87r89q35qy.fsf@zagadka.ping.de> (raw)
In-Reply-To: <87fzq6y4hx.fsf@raven.i.defaultvalue.org>
Rob Browning <rlb@defaultvalue.org> writes:
> Sure. That'll work. Though we could also use the SCM_CELL_ADDR_1
> approach if you'd rather. I don't feel strongly about it either way.
I don't, either. Please do what you think is best.
--
GPG: D5D4E405 - 2F9B BCCC 8527 692A 04E3 331E FAF8 226A D5D4 E405
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-devel
prev parent reply other threads:[~2003-03-02 1:40 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-26 6:28 GMP bignum results using double cells Rob Browning
2003-02-26 21:54 ` Kevin Ryde
2003-02-27 1:27 ` Rob Browning
2003-02-28 22:45 ` Kevin Ryde
2003-02-27 13:33 ` Marius Vollmer
2003-02-27 16:43 ` Rob Browning
2003-02-27 17:16 ` Rob Browning
2003-02-27 17:46 ` Marius Vollmer
2003-02-27 17:55 ` Rob Browning
2003-03-01 13:43 ` Marius Vollmer
2003-03-02 0:52 ` Rob Browning
2003-03-02 1:40 ` Marius Vollmer [this message]
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=87r89q35qy.fsf@zagadka.ping.de \
--to=mvo@zagadka.de \
--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).