Mailing-List: contact cygwin-help@sourceware.cygnus.com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@sources.redhat.com Delivered-To: mailing list cygwin@sources.redhat.com Date: Thu, 4 Jan 2001 15:44:40 -0500 From: Christopher Faylor To: Cygwin Mailing List Subject: Re: values.h / 2 Message-ID: <20010104154440.A22244@redhat.com> Reply-To: cygwin@cygwin.com Mail-Followup-To: Cygwin Mailing List References: <80575AFA5F0DD31197CE00805F650D7602CE47@wilber.adroit.com> <200101042042.f04KgFO25740@capella.ssd.hal.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.3.11i In-Reply-To: <200101042042.f04KgFO25740@capella.ssd.hal.com>; from jjf@bcs.org.uk on Thu, Jan 04, 2001 at 12:42:15PM -0800 On Thu, Jan 04, 2001 at 12:42:15PM -0800, J. J. Farrell wrote: >values.h is an old UNIX standard file for these things - it was >documented in issues 1 and 2 of the X/Open Portability Guide. >float.h was standardized in ANSI C in 1989 and had become widely >used before then. values.h was withdrawn from the standard in >issue 3 of the XPG in 1989, and never made it into POSIX at all. > >In short, values.h has been obsolete for over 12 years - any code >which wants to be portable should be changed to use the float.h >identifiers instead. If anyone wanted to do it, I can't imagine >any harm in adding a values.h to the cygwin distribution which >#defines the values.h identifiers to their float.h equivalents, >but it would be better if the software which uses values.h were >changed to not do so. FWIW, I'll accept a patch which creates values.h with this criteria. cgf -- Want to unsubscribe from this list? Check out: http://cygwin.com/ml/#unsubscribe-simple