From: Bill Schottstaedt <bil@ccrma.Stanford.EDU>
Subject: inexact integers in modulo etc
Date: Mon, 15 Apr 2002 05:32:27 -0700 [thread overview]
Message-ID: <200204151232.FAA21621@cmn14.stanford.edu> (raw)
I guess this is not news, but just in case... Some Guile numerical
primitives that should (could?) accept inexact integers (at least that's
the way I read r5rs) do not. The remainder example below is taken
from r5rs:
guile> (version)
"1.7.0"
guile> (modulo 4.0 2)
Backtrace:
In standard input:
2: 0* [modulo 4.0 2]
standard input:2:1: In procedure modulo in expression (modulo 4.0 2):
standard input:2:1: Wrong type argument in position 1: 4.0
ABORT: (wrong-type-arg)
guile> (remainder -13 -4.0)
Backtrace:
In standard input:
1: 0* [remainder -13 -4.0]
standard input:1:1: In procedure remainder in expression (remainder -13 -4.0):
standard input:1:1: Wrong type argument in position 2: -4.0
ABORT: (wrong-type-arg)
Others are quotient, gcd, lcm, even?, odd?
_______________________________________________
Bug-guile mailing list
Bug-guile@gnu.org
http://mail.gnu.org/mailman/listinfo/bug-guile
next reply other threads:[~2002-04-15 12:32 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-15 12:32 Bill Schottstaedt [this message]
2002-04-22 14:12 ` inexact integers in modulo etc Rob Browning
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=200204151232.FAA21621@cmn14.stanford.edu \
--to=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).