Re: [boost] [serialization][1.36] ktmap contains extended_type_infowith m_key == 0

From: Robert Ramey (ramey_at_[hidden])
Date: 2008-03-29 22:36:58

>>  None are one of my types, there are shared_ptr_1_32 with m_key == 0
>> and others.

The system for type registration has been improved to make the library
truely thread-safe and DLL compatible.  Sounds like there is an oversight
that needs to be fixed. If you can make a small example and indicate which
compiler you're using I would like to see it.

Robert Ramey

Felipe Magno de Almeida wrote:
> I made a workaround for now where I remove the assertions from the
> key_compare and in key_unregister, if nothing is found with
> equal_range (equal_range is faster than using upper and lower_bound)
> then I do a
> linear search.
>
> On Sat, Mar 29, 2008 at 6:43 PM, Felipe Magno de Almeida
> <felipe.m.almeida_at_[hidden]> wrote:
>> Hi Robert,
>>
>>  I'm hitting a assertion with m_key == 0.
>>  With my debugger I can find lots and lots of items with m_key == 0.
>>  None are one of my types, there are shared_ptr_1_32 with m_key == 0
>> and others.
>>
>>  Do you have a newer 1.36 version? Am I doing something wrong?
>>  I'm using the 1.36 version for use with DLLs (export in a DLL and
>>  serialize/deserialize in another).
>>
>>  Thanks,
>>  --
>>  Felipe Magno de Almeida