From mboxrd@z Thu Jan 1 00:00:00 1970 Message-ID: From: Charles Forsyth Date: Sun, 7 Feb 2010 21:33:36 +0000 To: 9fans@9fans.net In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit Subject: Re: [9fans] NaN, +Inf, and -Inf, constants? Topicbox-Message-UUID: d00d418a-ead5-11e9-9d60-3106f5b1d025 >seems like a bug to me. the spec is pretty clear: it's quite deliberate, having looked at the code. i suspect the rationale was that, finally, C provided a way outside the preprocessor to give symbolic names to constants. why restrict that to int? you can't easily get the same effect by adding #define names to the output symbol table, because those are arbitrary text, not guaranteed either to be constants, or to be safe for substitution (without surrounding ())