From: Marius Vollmer <mvo@zagadka.ping.de>
Cc: guile-devel@gnu.org
Subject: Re: bug in numbers.c integer-expt, expt?
Date: 13 Mar 2002 20:30:35 +0100 [thread overview]
Message-ID: <87y9gwmfj8.fsf@zagadka.ping.de> (raw)
In-Reply-To: <87adtcj2hr.fsf@raven.i.defaultvalue.org>
Rob Browning <rlb@defaultvalue.org> writes:
> Is integer-expt supposed to behave like expt wrt (integer-expt 0 0)?
>
> Right now I get
>
> guile> (integer-expt 0 0)
> 0
> guile> (expt 0 0)
> 0
>
> but r5rs says:
>
> - procedure: expt z1 z2
> Returns Z1 raised to the power Z2. For z_1 ~= 0
>
> z_1^z_2 = e^z_2 log z_1
> 0^z is 1 if z = 0 and 0 otherwise.
Looks like a bug. I think you can't really deduce what 0^0 should be,
so you must decide it. Let's follow R5RS.
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-devel
next prev parent reply other threads:[~2002-03-13 19:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-13 8:28 bug in numbers.c integer-expt, expt? Rob Browning
2002-03-13 19:30 ` Marius Vollmer [this message]
2002-03-13 21:20 ` Rob Browning
2002-03-14 17:30 ` 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=87y9gwmfj8.fsf@zagadka.ping.de \
--to=mvo@zagadka.ping.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).