From: Rob Browning <rlb@defaultvalue.org>
Subject: real numbers and integer-expt.
Date: Wed, 13 Mar 2002 02:36:38 -0600 [thread overview]
Message-ID: <876640j23t.fsf@raven.i.defaultvalue.org> (raw)
integer-expt says:
SCM_DEFINE (scm_integer_expt, "integer-expt", 2, 0, 0,
(SCM n, SCM k),
"Return @var{n} raised to the non-negative integer exponent\n"
"@var{k}.\n"
"\n"
but in the code we check to see if k satisfies SCM_REALP and if it
does, we coerce it to an int and see if we get any lossage. If we
don't then we decide it's OK to use it. Is that what we want, or
should callers be required to use inexact->exact when appropriate?
Thanks
--
Rob Browning
rlb @defaultvalue.org, @linuxdevel.com, and @debian.org
Previously @cs.utexas.edu
GPG=1C58 8B2C FB5E 3F64 EA5C 64AE 78FE E5FE F0CB A0AD
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-devel
next reply other threads:[~2002-03-13 8:36 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-13 8:36 Rob Browning [this message]
2002-03-13 19:23 ` real numbers and integer-expt Marius Vollmer
2002-03-13 21:23 ` Rob Browning
2002-03-13 21:32 ` Rob Browning
2002-03-13 21:48 ` Rob Browning
2002-03-20 22:32 ` Marius Vollmer
2002-03-20 22:54 ` 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=876640j23t.fsf@raven.i.defaultvalue.org \
--to=rlb@defaultvalue.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).