From mboxrd@z Thu Jan  1 00:00:00 1970
From: Tristan Plumb <9p-st@imu.li>
To: 9fans@9fans.net
Content-Transfer-Encoding: 8bit
Content-Type: text/plain; charset=UTF-8
Message-Id: <2576c2.2c8ec300.jiSO.mx@tumtum.plumbweb.net>
In-Reply-To: <fff3a08cba89f090f954ec39fb01f078@ladd.quanstro.net>
References: <2576c2.1a8ca4f7.1333.mx@tumtum.plumbweb.net>
	<fff3a08cba89f090f954ec39fb01f078@ladd.quanstro.net>
Date: Sat,  6 Feb 2010 12:14:53 -0500
User-Agent: mx-alpha
Subject: Re: [9fans] NaN, +Inf, and -Inf, constants?
Topicbox-Message-UUID: ce9687ee-ead5-11e9-9d60-3106f5b1d025

> NaN(2) and Inf(2) are not constant functions.  the result depends on
> the settings of the fcr (getfcr(2)).
Really? My reading of /sys/src/libc/port/nan.c makes me think NaN(2)
returns a uvlong value of 0x7ff0000000000001, miss I something?

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).

So if I think of enum definitions as assignment, it makes sense, mostly.

thanks,
tristan

--
All original matter is hereby placed immediately under the public domain.