> Date: Mon, 24 Nov 2014 11:21:51 +
> From: Gisle Vanem
>
> Another thing that puzzles me with Gnulib's math-functions for MSVC.
> MSVC v18 (VS Express 2013, Vista+) has more math functions than MSVC v16.
> For example "exp2()". So if a Gnulib imp-lib built with MSVC v18 is linked
> to a prog
On 24/11/14 11:21, Gisle Vanem wrote:
> Pádraig Brady wrote:
>
>>> I assume if some vendor have 'cosf' it should be undefined
>>> before Gnulib is trying to override or replace it. Not vice
>>> versa. So shouldn't this be:
>>># if @HAVE_COSF@ || @REPLACE_COSF@
>>># undef cosf
>>
>> Well a
Pádraig Brady wrote:
I assume if some vendor have 'cosf' it should be undefined
before Gnulib is trying to override or replace it. Not vice
versa. So shouldn't this be:
# if @HAVE_COSF@ || @REPLACE_COSF@
# undef cosf
Well all the ...f() variants seem to be treated like this:
acosf() cos
On 22/11/14 20:53, Gisle Vanem wrote:
> I'm trying to understand the logic behind the generation
> of some statements in math.h (from math.in.h). The MSVC
> compiler has cosf() defined as a macro in it's :
> #define cosf(x) ((float)cos((double)(x)))
>
> (for x86,C). Then how is Gnulib suppos
I'm trying to understand the logic behind the generation
of some statements in math.h (from math.in.h). The MSVC
compiler has cosf() defined as a macro in it's :
#define cosf(x) ((float)cos((double)(x)))
(for x86,C). Then how is Gnulib supposed to replace that?
Since no matter what's put in
