Path: utzoo!utgpu!news-server.csri.toronto.edu!bonnie.concordia.ca!thunder.mcrcim.mcgill.edu!snorkelwacker.mit.edu!apple!julius.cs.uiuc.edu!rpi!crdgw1!camelback!volpe
From: volpe@camelback.crd.ge.com (Christopher R Volpe)
Newsgroups: comp.lang.c
Subject: Re: Here's a challenge for floating point lovers.
Message-ID: <16035@crdgw1.crd.ge.com>
Date: 24 Jan 91 01:56:45 GMT
References: <1991Jan21.215629.8393@watdragon.waterloo.edu> <1991Jan22.180927.29232@zoo.toronto.edu> <14938@smoke.brl.mil>
Sender: news@crdgw1.crd.ge.com
Reply-To: volpe@camelback.crd.ge.com (Christopher R Volpe)
Lines: 16

In article <14938@smoke.brl.mil>, gwyn@smoke.brl.mil (Doug Gwyn) writes:
|>The
|>standard does NOT require that the values of the <float.h> macros be
|>CONSTANT expressions; in particular they may access external storage at
|>run time (contents of such a union, for example).  Note also that this
|>means that FLT_RADIX and other <float.h> macros must not be used in #if
|>expressions in strictly conforming programs.
  
2.2.4.2.2:
  Of the values in the <float.h> header, FLT_RADIX shall be a constant
expression suitable for use in #if preprocessing directives; all other
values need not be constant expressions.            
==================
Chris Volpe
G.E. Corporate R&D
volpecr@crd.ge.com