From owner-freebsd-current Wed Aug 26 22:26:58 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA09515 for freebsd-current-outgoing; Wed, 26 Aug 1998 22:26:58 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from word.smith.net.au (castles320.castles.com [208.214.167.20]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA09502 for ; Wed, 26 Aug 1998 22:26:48 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id RAA01162; Tue, 25 Aug 1998 17:48:58 GMT (envelope-from mike@dingo.cdrom.com) Message-Id: <199808251748.RAA01162@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Mike Smith cc: Alex , current Subject: Re: MAXDOUBLE and values.h? In-reply-to: Your message of "Tue, 25 Aug 1998 17:39:21 GMT." <199808251739.RAA01034@dingo.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 25 Aug 1998 17:48:57 +0000 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > Ok, I've got a quick question. I've got an app which uses MAXDOUBLE, and > > includes values.h to get at it. values.h has a #warn that tells me it's > > depreciated. So I grep -R'd all the headers in /usr/include, and nothing > > else seemed to have a #define for MAXDOUBLE? Is this a mistake, or should > > MAXDOUBLE be avoided? > > You should use , and MAXDOUBLE will come out of the > machine-specific headers in Blah. I should think faster or type slower. MAXDOUBLE is deprecated. By including , you will implicitly include , which contains the approved (ANSI, POSIX, etc.) constants. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message