From: Kevin Ryde <user42@zip.com.au>
Cc: guile-devel@gnu.org
Subject: Re: DINFINITY alpha not gnu/linux
Date: Tue, 17 Feb 2004 09:06:49 +1000 [thread overview]
Message-ID: <87y8r2vd2u.fsf@zip.com.au> (raw)
In-Reply-To: <16433.18814.653327.782668@devzero.bogus.domain> (John W. Eaton's message of "Mon, 16 Feb 2004 16:51:42 -0600")
"John W. Eaton" <jwe@bevo.che.wisc.edu> writes:
>
> #if defined (SCO)
> volatile double tmp = 1.0;
> tmp_inf = 1.0 / (tmp - tmp);
This is not really sco specific is it? I'd guess anywhere with a
working "volatile" and overflow exceptions masked would be ok.
> to define Inf, but there may be better ways to do this.
C99 INFINITY is probably good, when available.
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-devel
next prev parent reply other threads:[~2004-02-16 23:06 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-16 22:36 DINFINITY alpha not gnu/linux Kevin Ryde
2004-02-16 22:51 ` John W. Eaton
2004-02-16 23:06 ` Kevin Ryde [this message]
2004-02-16 23:41 ` John W. Eaton
2004-02-21 22:08 ` 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=87y8r2vd2u.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).