delorie.com/archives/browse.cgi | search |
Date: | Mon, 25 Aug 2003 14:07:34 -0400 |
Message-Id: | <200308251807.h7PI7YE4019687@envy.delorie.com> |
From: | DJ Delorie <dj AT delorie DOT com> |
To: | djgpp-workers AT delorie DOT com |
In-reply-to: | <200308251747.h7PHl6XI023636@speedy.ludd.luth.se> |
(ams AT ludd DOT luth DOT se) | |
Subject: | Re: <math.h> and <libm/math.h> |
References: | <200308251747 DOT h7PHl6XI023636 AT speedy DOT ludd DOT luth DOT se> |
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 |
> Can anyone explain what this in <math.h> is about: The math.h that came with libm's sources came from a different source, and at the time couldn't be used as-is because it didn't meet our portability/standards goals. So I did what you see. The reasoning is similar to the fact that many math functions are duplicated between libc and libm. > What should be done? Should <libm/math.h> be updated according to > <math.h>? If needed, yes, but note that <libm/math.h> is (well, was) mastered elsewhere.
webmaster | delorie software privacy |
Copyright © 2019 by DJ Delorie | Updated Jul 2019 |