From: tomas@fabula.de
Cc: guile-devel@gnu.org
Subject: Re: Introduction of fractions exposes uniform vector prototype bug
Date: Sat, 20 Dec 2003 17:12:08 +0100 [thread overview]
Message-ID: <20031220161208.GA14431@www> (raw)
In-Reply-To: <87zndowks7.fsf@zip.com.au>
On Sat, Dec 20, 2003 at 07:38:16AM +1000, Kevin Ryde wrote:
> Mikael Djurfeldt <mdj@mit.edu> writes:
> >
> > I have no good suggestion for what to do about this, but one thing is
> > certain: We can't suggest people to use 1/3 as prototype for double
> > arrays (at least now without modifying scm_make_uve).
>
> I'd be pretty inclined to make it a special case, for compatibility.
>
> Asking people to change their code after they've followed something
> the manual explicitly said is never nice.
Hmmm. You have a point there...
But sometime you'll have to tell them that Santa ain't really ;-/
(it's quite a surprising thing to carry forever: 1/3 behaves here
as an inexact, whereas 1/6 doesn't).
I'd propose making it a deprecated feature, to let it fade off
slowly. Opinions?
What do we take as prototype now for an inexact? Do we have a
constant for sqrt2 (or better pi -- algebraic numbers might
be coming someday ;)
Someone (was it Mikael?) expressed dislike for this prototype
business. I too think it sticks out a bit. Maybe real names
for number classes would be better.
Regards
-- tomas
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-devel
next prev parent reply other threads:[~2003-12-20 16:12 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-25 23:02 Introduction of fractions exposes uniform vector prototype bug Mikael Djurfeldt
2003-12-19 21:38 ` Kevin Ryde
2003-12-20 16:12 ` tomas [this message]
2003-12-20 17:52 ` Stephen Compall
2003-12-21 0:42 ` Kevin Ryde
2004-01-10 22:19 ` Marius Vollmer
2004-01-10 23:02 ` Kevin Ryde
2004-02-10 0:05 ` Kevin Ryde
2004-02-10 23:30 ` Rob Browning
2004-02-12 0:26 ` Kevin Ryde
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=20031220161208.GA14431@www \
--to=tomas@fabula.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).