|
From: | John W. Eaton |
Subject: | Re: log2 on MinGW |
Date: | Mon, 04 Nov 2013 12:54:14 -0500 |
User-agent: | Mozilla/5.0 (X11; Linux x86_64; rv:10.0.12) Gecko/20130116 Icedove/10.0.12 |
On 11/04/2013 12:05 PM, Rik wrote:
Aside from performance, does using gnulib::frexp solve the original problem? The gnulib documentation is somewhat minimal and they suggest that they only replace an existing library function if the function is buggy. Otherwise, they fall back on the library version that is available. This may be, however, only when you use the bare function such as 'frexp' rather than the namespace-qualified version 'gnulib::frexp'.
The namespace thing allows gnulib to replace the function in C++ code without introducing macros that screw things up in other places. But the replacement code is still only used if needed. It works by using a function pointer in the namespace that either refers to the replacement function (usually called rpl_FOO) or the system function FOO. So there shouldn't be much of a penalty if the system function is used.
jwe
[Prev in Thread] | Current Thread | [Next in Thread] |