Re: [Boost-users] Re: Using shared_ptr across shared library boun dary

From: Peter Dimov (pdimov_at_[hidden])
Date: 2004-03-12 07:19:12

Ferdinand Prantl wrote:
>> From: David Abrahams [mailto:dave_at_[hidden]]
>>> "Jim.Hyslop" <Jim.Hyslop_at_[hidden]> writes:
>>> It's been my experience
>>> (with Visual Studio, at least) that allocating memory in
>>> one DLL and
>>> deallocating it in another leads to problems. Sometimes it
>>> doesn't go
>>> noticed, but when it does, it's really noticeable.
>> 
>> The library cleverly avoids that, provided the first
>> shared_ptr to take ownership of the memory does so in the
>> same DLL where the object was allocated.
> 
> Actually, I came into the same problem as Jim - I had to
> ensure the same version of the msvcrt and moreover its
> debug/release versions to get the code working well.
> 
> All classes in checked_delete.hpp, smart_count.hpp and shared_ptr.hpp
> are either templates or completely in headers. The operations with
> new/delete and allocators are translated/inlined by the compiler into
> every unit, IMHO.

Please post an example that fails.