From: Kevin Ryde <user42@zip.com.au>
Cc: guile-devel@gnu.org
Subject: Re: ash rewrite
Date: Thu, 10 Feb 2005 09:16:29 +1100 [thread overview]
Message-ID: <873bw5xttu.fsf@zip.com.au> (raw)
In-Reply-To: <87zmyd5sn5.fsf@trouble.defaultvalue.org> (Rob Browning's message of "Wed, 09 Feb 2005 15:29:34 -0600")
Rob Browning <rlb@defaultvalue.org> writes:
>
> Hmm I noticed that at least on my machine, make check fails with
> current CVS.
Thanks, I'll remove those.
> ERROR: fractions.test: fractions: (eqv? (ash 1/2 0) 1/2) - arguments: ((wrong-type-arg "ash" "Wrong type argument in position ~A: ~S" (1 1/2) (1/2)))
> ERROR: fractions.test: fractions: (eqv? (ash 1/2 1) 1) - arguments: ((wrong-type-arg "ash" "Wrong type argument in position ~A: ~S" (1 1/2) (1/2)))
ash had worked to left shift a fraction, because it was done with a
multiply. It never right shifted a fraction.
My change unified that, by making neither left nor right work :-).
There'd be nothing wrong with having ash support fractions, or
inexacts for that matter. But it seemed to me a bit of a slippery
slope. You might start thinking other of the "Bitwise Operations"
functions should also work on those. Like logbit? or logand. They'd
have sensible definitions on fractions and inexacts, but it'd be a bit
like hard work implementing it.
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/guile-devel
next prev parent reply other threads:[~2005-02-09 22:16 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-27 22:48 ash rewrite Kevin Ryde
2005-01-27 22:50 ` Kevin Ryde
2005-02-09 21:29 ` Rob Browning
2005-02-09 22:16 ` Kevin Ryde [this message]
2005-02-09 22:33 ` primitive-fork hang (was: ash rewrite) Kevin Ryde
2005-02-28 1:50 ` primitive-fork hang Marius Vollmer
2005-02-28 22:03 ` Kevin Ryde
2005-03-08 17:05 ` 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=873bw5xttu.fsf@zip.com.au \
--to=user42@zip.com.au \
--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).