From: sandmann AT clio DOT rice DOT edu (Charles Sandmann)
Message-Id: <10207222257.AA27589@clio.rice.edu>
Subject: Re: Bug in DJGPP 2.03 (with GCC 3.1)
To: djgpp-workers AT delorie DOT com
Date: Mon, 22 Jul 2002 17:57:13 -0500 (CDT)
Cc: jgordeev AT dir DOT bg (Jordan Gordeev)
In-Reply-To: <3D3C5D8A.73ECA0D3@phekda.freeserve.co.uk> from "Richard Dawe" at Jul 22, 2002 08:31:22 PM
X-Mailer: ELM [version 2.5 PL2]
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Reply-To: djgpp-workers AT delorie DOT com
Errors-To: nobody AT delorie DOT com
X-Mailing-List: djgpp-workers AT delorie DOT com
X-Unsubscribes-To: listserv AT delorie DOT com
Precedence: bulk

> tanhf and the other functions listed became part of the C standard in C99. But
> DJGPP doesn't support C99 yet. These functions are in the non-standard section
> of <math.h> and are therefore unavailable, when you use the -ansi option.
> (Look for the #ifndef __STRICT_ANSI__, #ifndef _POSIX_SOURCE lines.)
> 
> I suspect that gcc 2.95.3 didn't have std::tanhf and the others, so this
> problem did not arise.

So this means that 2.03 is incompatible with gcc 3.x with -ansi ?

Should we consider a header change for 2.03 refresh to fix?  Or is it 
more complicated?