From: Rob Browning <rlb@defaultvalue.org>
Cc: guile-devel@gnu.org
Subject: Re: real numbers and integer-expt.
Date: Wed, 20 Mar 2002 16:54:32 -0600 [thread overview]
Message-ID: <87lmcm97fb.fsf@raven.i.defaultvalue.org> (raw)
In-Reply-To: <87g02uyio6.fsf@zagadka.ping.de> (Marius Vollmer's message of "20 Mar 2002 23:32:25 +0100")
Marius Vollmer <mvo@zagadka.ping.de> writes:
>> OK, that's a bit confusing -- we have SCM_COMPLEXP which does *not*
>> mean the same thing as scm_complex_p -- the former checks to make sure
>> the object, tag-wise, is a complex smob, the latter checks to see if
>> the object actually contains a complex number, so we have
>>
>> (complex? 3) -> #t
>>
>> but
>>
>> SCM_COMPLEX(SCM_MKINUM(3)) -> 0
>
> Yes, good point. I wasn't aware of that.
>
>
> I guess we need to first answer what the purpose of 'integer-expt' is.
> Given 'expt' is it useful to have 'integer-expt' as well? Is
> integer-expt really only for exact numbers and not for integers? Is
> it just a subset of 'expt' for use from C code?
All good questions. I get the impression that at least in part, it
was designed as a "helper" for use by other numbers.c functions.
--
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
prev parent reply other threads:[~2002-03-20 22:54 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-13 8:36 real numbers and integer-expt Rob Browning
2002-03-13 19:23 ` 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 [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=87lmcm97fb.fsf@raven.i.defaultvalue.org \
--to=rlb@defaultvalue.org \
--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).