Re: ambigous overload

[Jaroslav Hajek]

On Wed, Mar 25, 2009 at 2:21 PM, Marco Atzeri <address@hidden> wrote:
>
> Dear Havel,
> on latest mercurial source, building on cygwin we have
> again ambigous overload, now on xisinf
>
> ../../octave_local/liboctave/oct-inttypes.cc: In function 'octave_int<T> 
> operator*(const octave_int<T>&, const double&) [with T = long long unsigned 
> int]':
> ../../octave_local/liboctave/oct-inttypes.cc:410: error: call of overloaded 
> 'xisinf(const octave_int<long long unsigned int>&)' is ambiguous
> ../../octave_local/liboctave/lo-mappers.h:63: note: candidates are: bool 
> xisinf(double)
> ../../octave_local/liboctave/lo-mappers.h:134: note:                 bool 
> xisinf(float)
> ../../octave_local/liboctave/oct-inttypes.cc: In function 'octave_int<T> 
> operator*(const octave_int<T>&, const double&) [with T = long long int]':
> ../../octave_local/liboctave/oct-inttypes.cc:445: error: call of overloaded 
> 'xisinf(const octave_int<long long int>&)' is ambiguous
> ../../octave_local/liboctave/lo-mappers.h:63: note: candidates are: bool 
> xisinf(double)
> ../../octave_local/liboctave/lo-mappers.h:134: note:                 bool 
> xisinf(float)
> make[2]: *** [oct-inttypes.o] Error 1
>
>
> suggestion ?
>
> Regards
> Marco
>

I uploaded a fix:
http://hg.savannah.gnu.org/hgweb/octave/rev/3b1908b58662

this part of code is inactive if you have long double > double, which
is why it may not have been tested enough.

thanks for the report

-- 
RNDr. Jaroslav Hajek
computing expert & GNU Octave developer
Aeronautical Research and Test Institute (VZLU)
Prague, Czech Republic
url: www.highegg.matfyz.cz