octave-maintainers
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: error: target of using declaration conflicts with declaration alread


From: John W. Eaton
Subject: Re: error: target of using declaration conflicts with declaration already in scope
Date: Thu, 2 Jun 2016 11:30:52 -0400
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Icedove/38.5.0

On 06/01/2016 07:55 PM, Ben Abbott wrote:

Almost there.

   CXX      libinterp/dldfcn/libinterp_dldfcn___delaunayn___la-__delaunayn__.lo
In file included from libinterp/dldfcn/__delaunayn__.cc:50:
In file included from libinterp/corefcn/Cell.h:33:
In file included from ./libinterp/octave-value/ov.h:35:
In file included from ./liboctave/array/Range.h:30:
In file included from ./liboctave/array/dMatrix.h:28:
In file included from ./liboctave/array/dNDArray.h:28:
In file included from ./liboctave/array/MArray.h:30:
In file included from liboctave/operators/mx-inlines.cc:41:
In file included from ./liboctave/util/oct-inttypes.h:36:
liboctave/numeric/lo-mappers.h:474:40: error: no viable conversion from 
'complex<double>' to 'double'
inline double conj (double x) { return octave::math::conj (x); }
                                        ^~~~~~~~~~~~~~~~~~~~~~
liboctave/numeric/lo-mappers.h:476:38: error: no viable conversion from 
'complex<float>' to 'float'
inline float conj (float x) { return octave::math::conj (x); }
                                      ^~~~~~~~~~~~~~~~~~~~~~
libinterp/dldfcn/__delaunayn__.cc:197:19: warning: use of old-style cast 
[-Wold-style-cast]
                   FOREACHvertex_ (facet->vertices)
                   ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
/sw/include/libqhull/libqhull.h:912:34: note: expanded from macro 
'FOREACHvertex_'
#define FOREACHvertex_(vertices) FOREACHsetelement_(vertexT, vertices,vertex)
                                  ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
/sw/include/libqhull/qset.h:137:24: note: expanded from macro 
'FOREACHsetelement_'
           variable##p= (type **)&((set)->e[0].p); \
                        ^        ~~~~~~~~~~~~~~~~
1 warning and 2 errors generated.

OK, so in the past we had "conj (real value)" returning a real value, not complex, but the C++ standard library provides a template for conj (real value) that returns a complex value. Hmm. But it looks like we never actually use the real versions of conj that were defined, so maybe we can just make the attached change little or no trouble?

jwe

Attachment: diffs.txt
Description: Text document


reply via email to

[Prev in Thread] Current Thread [Next in Thread]