Re: [Boost-users] strange linker error with boost::function

Subject: Re: [Boost-users] strange linker error with boost::function
From: Noah Roberts (roberts.noah_at_[hidden])
Date: 2009-07-28 17:06:14

Noah Roberts wrote:
> Can anyone think why I would get an unresolved symbol on this 
> monstrosity from the liker:

It gets worse.

The file that seems to be causing me this problem compiles just fine in 
the unit test project now.
> 
> public: __thiscall
> boost::function<
>   class std::auto_ptr<struct esi::command::command>
>   __cdecl(class std::vector<
>                              struct 
> esi::draw::primitives::point_impl<double>
>                             ,class std::allocator<struct 
> esi::draw::primitives::point_impl<double> > > const &
>          )
>  >
> 
> ::function
>   <
>     class std::auto_ptr<struct esi::command::command>
>       __cdecl(class std::vector<
>                                  struct 
> esi::draw::primitives::point_impl<double>
>                                 ,class std::allocator<struct 
> esi::draw::primitives::point_impl<double> > > const &
>               )
>   >
> 
> <
>   class std::auto_ptr<struct esi::command::command>
>     (__cdecl*)(class std::vector<
>                                  struct 
> esi::draw::primitives::point_impl<double>
>                                 ,class std::allocator<struct 
> esi::draw::primitives::point_impl<double> > > const &
>               )
>  >
> (class std::auto_ptr<struct esi::command::command>
>            (__cdecl*)(class std::vector<
>                                          struct 
> esi::draw::primitives::point_impl<double>
>                                         ,class std::allocator<struct 
> esi::draw::primitives::point_impl<double> > > const &
>                      )
>  ,int
> )
> 
> 
> 
> I tried to clean it up a bit.  Looks to me like there's no instantiation 
> of the appropriate constructor to the function template.
> 
> I tried to recreate the problem in a simple sample but can't seem to do 
> it.  Hoping that I'm falling foul of a common issue that someone might 
> be able to just give me pointers toward fixing.