* Eric Blake (ebl...@redhat.com) [20111018 23:07]:
> But since octave is written in C++, we could avoid the macros and
> instead have three overloaded functions named signbit which operate
> on the correct types, so as not to pollute the namespace with a
> macro.
That's why the C++ standard has
Eric Blake wrote:
> in C++, we could avoid the macros and
> instead have three overloaded functions named signbit which operate on
> the correct types, so as not to pollute the namespace with a macro.
> POSIX does not speak to C++ compliance, so using overloads instead of a
> macro for C++ does
On 10/18/2011 02:51 PM, Michael Goffioul wrote:
Hi,
With a current version of gnulib and MSVC10, I get a compilation error
in octave due to signbit being #define'd by gnulib's math.h module.
The configure script ends up with GNULIB_SIGNBIT being 1 and
REPLACE_SIGNBIT being 1. This causes signbit
Hi,
With a current version of gnulib and MSVC10, I get a compilation error
in octave due to signbit being #define'd by gnulib's math.h module.
The configure script ends up with GNULIB_SIGNBIT being 1 and
REPLACE_SIGNBIT being 1. This causes signbit being #define'd as
# define signbit(x) \
(si
