From: erik quanstrom <quanstro@quanstro.net>
To: 9fans@9fans.net
Subject: Re: [9fans] NaN, +Inf, and -Inf, constants?
Date: Sun, 7 Feb 2010 11:12:00 -0500 [thread overview]
Message-ID: <8b3a3300aaabab272edb6dc24e6091d0@ladd.quanstro.net> (raw)
In-Reply-To: <2576c2.2c8ec300.jiSO.mx@tumtum.plumbweb.net>
> On the other hand, the assignment of NaN to a double depends on the fcr.
> (And on my machine, curiously changes 0x7ff0...1 to 0x7ff8...1).
http://en.wikipedia.org/wiki/NaN explains the difference between
a signaling nan and a quiet nan (the latter).
> So if I think of enum definitions as assignment, it makes sense, mostly.
how does a non-constant enum make sense?
more to the point, in porting code, you're going to have to work
out how to deal with NaNs. plan 9 defaults to using signaling
nans, unless you manually change the fcr. this is good because
it avoids bad conversions. on the other hand, your application
may require and depend on the ability to pass around nan and
±inf.
- erik
next prev parent reply other threads:[~2010-02-07 16:12 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-06 15:38 Tristan Plumb
2010-02-06 15:57 ` erik quanstrom
2010-02-06 17:14 ` Tristan Plumb
2010-02-07 16:12 ` erik quanstrom [this message]
2010-02-07 0:06 ` Russ Cox
2010-02-07 10:46 ` Charles Forsyth
2010-02-07 11:05 ` Charles Forsyth
2010-02-07 20:01 ` Russ Cox
2010-02-07 20:31 ` erik quanstrom
2010-02-07 21:33 ` Charles Forsyth
2010-02-07 22:19 ` Lyndon Nerenberg (VE6BBM/VE7TFX)
2010-02-07 22:37 ` erik quanstrom
2010-02-08 16:39 ` Lyndon Nerenberg (VE6BBM/VE7TFX)
2010-02-08 18:48 ` Russ Cox
2010-02-07 23:16 ` Bakul Shah
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=8b3a3300aaabab272edb6dc24e6091d0@ladd.quanstro.net \
--to=quanstro@quanstro.net \
--cc=9fans@9fans.net \
/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 NNTP newsgroup(s).