Re: OT? Legacy code and constants / good and portable coding (RE: Compiling Wine in Cygwin)

Re: OT? Legacy code and constants / good and portable coding (RE: Compiling Wine in Cygwin)

[Brian Ford]

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/

OT? Legacy code and constants / good and portable coding (RE: Compiling Wine in Cygwin)

[Hannu E K Nevalainen (garbage mail)]

> From: cygwin-owner@cygwin.com [mailto:cygwin-owner@cygwin.com]On Behalf
> Of Marcel Telka

> On 05.09.2003 22:06, Gregory Nutt wrote:
> > Trying to compile wine-20030813 in the first release of the 1.5.x
> > series.
> >
> > I discovered that shader.c is looking for -HUGE which is apparently
> > supposed to be defined in math.h.  I was able to make it compile by
> > changing the shader.c to look for -HUGE_VAL which is defined in
> > cygwin's math.h.  However, I'd like to know if this is a bug to report
> > to Wine or a bug to report to Cygwin.  Since Wine compiles on Linux
> > without a problem, I thought I'd start with Cygwin.
>
> IMHO, that is wine-related problem.
> <http://www.opengroup.org/onlinepubs/007904975/basedefs/math.h.html>
>
--

Ughhh... I wonder who it was that wrote:

> 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!?

/Hannu E K Nevalainen, B.Sc. EE - 59°16.37'N, 17°12.60'E
--END OF MESSAGE--


--
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/