From: Brian Ford <ford@vss.fsi.com>
To: cygwin@cygwin.com
Subject: Re: OT? Legacy code and constants / good and portable coding (RE: Compiling Wine in Cygwin)
Date: Mon, 08 Sep 2003 15:58:00 -0000 [thread overview]
Message-ID: <Pine.GSO.4.56.0309081047010.685@eos> (raw)
On Sun, 7 Sep 2003, Hannu E K Nevalainen wrote:
> Ughhh... I wonder who it was that wrote:
>
It was me.
>> On Fri, 5 Sep 2003, Igor Pechtchanski wrote:
>>
>>> HUGE is a SVID-specific value that is equal to MAXFLOAT on my RedHat
>>> 7.3 box. That is *not* the same as HUGE_VAL, BTW, so I'd use MAXFLOAT
>>> instead.
>>>
>>
>> MAXFLOAT is outdated. I would suggest FLT_MAX in float.h.
>
> As there seems to some confusion regarding this: Thus I wonder;
>
> Is there ANY good reading on what is legacy/outdated - and what isn't!?
>
Not that I am really aware of. I just went through a porting effort from
Sun Solaris to Cygwin and then to Linux. I found the above from the Linux
port while looking for a common denominator.
On my Redhat 9 box, MAXFLOAT is found in values.h that contains this
comment:
Old compatibility names for <limits.h> and <float.h> constants.
This interface is obsolete. New programs should use <limits.h> and/or
<float.h> instead of <values.h>.
float.h, on the other hand, is provided by gcc and contains IEEE
floating point standard definitions as stated by "info libc" on the same
box.
--
Brian Ford
Senior Realtime Software Engineer
VITAL - Visual Simulation Systems
FlightSafety International
Phone: 314-551-8460
Fax: 314-551-8444
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/
next reply other threads:[~2003-09-08 15:58 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-08 15:58 Brian Ford [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-09-05 20:20 Compiling Wine in Cygwin Marcel Telka
2003-09-07 10:26 ` OT? Legacy code and constants / good and portable coding (RE: Compiling Wine in Cygwin) Hannu E K Nevalainen (garbage mail)
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=Pine.GSO.4.56.0309081047010.685@eos \
--to=ford@vss.fsi.com \
--cc=cygwin@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).