From: Marius Vollmer <mvo@zagadka.de>
Subject: Re: HEAD has now exact fractions
Date: Wed, 19 Nov 2003 01:05:01 +0100 [thread overview]
Message-ID: <87vfphmdea.fsf@zagadka.ping.de> (raw)
In-Reply-To: <877k1xffts.fsf@zip.com.au> (Kevin Ryde's message of "Wed, 19 Nov 2003 08:54:23 +1000")
Kevin Ryde <user42@zip.com.au> writes:
> Marius Vollmer <mvo@zagadka.de> writes:
>>
>> (inexact->exact 1.234)
>
> You might like to show for instance 1.375 there, something that has an
> exact binary representation.
Hmm, isn't that part of the point that 1.234 is indeed not exactly
representable and that the result of (inexact->exact 1.234) is not
something simple like 617/500?
--
GPG: D5D4E405 - 2F9B BCCC 8527 692A 04E3 331E FAF8 226A D5D4 E405
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-devel
next prev parent reply other threads:[~2003-11-19 0:05 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-18 22:14 HEAD has now exact fractions Marius Vollmer
2003-11-18 22:23 ` Neil Jerram
2003-11-18 22:54 ` Kevin Ryde
2003-11-19 0:05 ` Marius Vollmer [this message]
2003-11-19 0:59 ` Kevin Ryde
2003-11-19 2:03 ` Neil Jerram
2003-11-19 4:33 ` 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=87vfphmdea.fsf@zagadka.ping.de \
--to=mvo@zagadka.de \
/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).