Linker error - VS2005 thinks it's a function declaration?

L

Lawrence Spector

Base base;
BaseWrap& baseWrap(reinterpret_cast<BaseWrap&>(base));
boost::python::eek:bject obj(boost::shared_ptr<BaseWrap>(&baseWrap)); //
Compile error

Results in this error:

1>PythonPassReference.obj : error LNK2019: unresolved external symbol
"class boost::python::api::eek:bject __cdecl obj(class
boost::shared_ptr<struct BaseWrap> &)" (?obj@@YA?
AVobject@api@python@boost@@AAV?$shared_ptr@UBaseWrap@@@4@@Z)
referenced in function _main

My first thought is somehow that looks like a function declaration
instead of creating an object on the stack and instantiating it. If I
remove the shared_ptr, the error goes away.

In case it helps, here's a few more details.

boost::python::eek:bject has the following constructor:

// explicit conversion from any C++ object to Python
template <class T>
explicit object(
T const& x
# if BOOST_WORKAROUND(BOOST_MSVC, < 1300)
// use some SFINAE to un-confuse MSVC about its
// copy-initialization ambiguity claim.
, typename mpl::if_<is_proxy<T>,int&,int>::type* = 0
# endif
)
: object_base(object_base_initializer(x))
{
}

boost::shared_ptr<T> has the following constructor:

template<class Y>
explicit shared_ptr( Y * p ): px( p ), pn( p ) // Y must be
complete
{
boost::detail::sp_enable_shared_from_this( pn, p, p );
}

Any tips on how to solve this would be greatly appreciated. I'm
probably overlooking something obvious.

Thanks in advance,

Lawrence
 
V

Victor Bazarov

Lawrence said:
Base base;
BaseWrap& baseWrap(reinterpret_cast<BaseWrap&>(base));
boost::python::eek:bject obj(boost::shared_ptr<BaseWrap>(&baseWrap)); //
Compile error

Results in this error:

1>PythonPassReference.obj : error LNK2019: unresolved external symbol
"class boost::python::api::eek:bject __cdecl obj(class
boost::shared_ptr<struct BaseWrap> &)" (?obj@@YA?
AVobject@api@python@boost@@AAV?$shared_ptr@UBaseWrap@@@4@@Z)
referenced in function _main

My first thought is somehow that looks like a function declaration
instead of creating an object on the stack and instantiating it. If I
remove the shared_ptr, the error goes away.


Any tips on how to solve this would be greatly appreciated. I'm
probably overlooking something obvious.

You are overlooking something, but it's not that obvious. Your 'obj'
declaration is similar to

double obj(int(&blah));

Care to parse it? A hint: the parentheses around &blah don't matter.

....

Give up? It's the same as

double obj(int &blah);

Look familiar? It's a function declaration!

How do you prevent this from being treated as a function declaration?
Put extra parentheses around the "argument":

double obj((int(&blah)));

In your case:

boost::python::eek:bject obj( (boost::shared_ptr<BaseWrap>(&baseWrap)) );

V
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Members online

Forum statistics

Threads
473,744
Messages
2,569,479
Members
44,899
Latest member
RodneyMcAu

Latest Threads

Top