From: Mark H Weaver <mhw@netris.org>
To: bil@ccrma.Stanford.EDU
Cc: 30427-done@debbugs.gnu.org
Subject: bug#30427: division inconsistency?
Date: Mon, 12 Feb 2018 16:04:11 -0500 [thread overview]
Message-ID: <87zi4dq5ro.fsf@netris.org> (raw)
In-Reply-To: <8b2d86cfda8cc0fb6b654cb59e222646@ccrma.stanford.edu> (bil@ccrma.stanford.edu's message of "Sun, 11 Feb 2018 15:21:54 -0800")
bil@ccrma.Stanford.EDU writes:
> I forgot to include:
>
> scheme@(guile-user)> (help '/)
> - Scheme Procedure: / [x [y . rest]]
> Divide the first argument by the product of the remaining
> arguments. If called with one argument Z1, 1/Z1 is returned.
This email caused a second bug to be filed. I'm closing this one, but
the first bug will remain open for discussion.
Thanks,
Mark
prev parent reply other threads:[~2018-02-12 21:04 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-11 23:21 bug#30427: division inconsistency? bil
2018-02-12 21:04 ` Mark H Weaver [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=87zi4dq5ro.fsf@netris.org \
--to=mhw@netris.org \
--cc=30427-done@debbugs.gnu.org \
--cc=bil@ccrma.Stanford.EDU \
/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).