Re: [boost] [serialization] Patch : Borlandworkaroundsforshared_ptr_132.hpp

From: Robert Ramey (ramey_at_[hidden])
Date: 2005-07-08 17:19:50

I used patch in merger your patch into my copy.  I've also checked that I
have on line 44:

#if !BOOST_WORKAROUND( _BORLANDC_, BOOST_TESTED_AT( 0x564) )
using namespace boost;
#endif

Note the !

I got my free borland 5.6? from a borland website.  I'm really sure whether
I should have 0x564 or ox560 above.

Hmm - a mystery to me.

Robert Ramey

AlisdairM wrote:
> Robert Ramey wrote:
>
>> Borland C++ 5.6 for Win32 Copyright (c) 1993, 2002 Borland
>>
>> c:\BoostMainCVS\libs\serialization\test\test_shared_ptr_132.cpp:
>>
>> Error E2238
>> C:\BoostMainCVS\boost/serialization/detail/shared_count_132.hpp 75:
>> Multiple declaration for 'bad_weak_ptr'
>>
>> Error E2344 C:\BoostMainCVS\boost/detail/bad_weak_ptr.hpp 39: Earlier
>> declaration of 'bad_weak_ptr'
>>
>> Error E2238
>> C:\BoostMainCVS\boost/serialization/detail/shared_count_132.hpp 95:
>> Multiple declaration for 'sp_counted_base'
>>
>> Error E2344 C:\BoostMainCVS\boost/detail/sp_counted_base_w32.hpp 36:
>> Earlier declaration of 'sp_counted_base'
>>
>> Error E2238
>> C:\BoostMainCVS\boost/serialization/detail/shared_count_132.hpp 320:
>> Multiple declaration for 'shared_count'
>>
>> Error E2228
>> C:\BoostMainCVS\boost/serialization/detail/shared_count_132.hpp 320:
>> Too many error or warning messages
>>
>> *** 6 errors in Compile ***
>
> Strange, those are the exact same errors I was getting *before* I
> applied the patch.
>
> Can you confirm that the first workaround in shared_count_132.hpp
> looks like this:
>
> namespace boost_132 {
>
> #if !BOOST_WORKAROUND( __BORLANDC__, BOOST_TESTED_AT( 0x564) )
> using namespace boost;
> #endif
>
>
> Note the unsual '!' in the BOOST_WORKAROUND test.
>
>
> I am compiling against the latest CVS repositoy, and it appears fine
> to me.
>
> See my reply to Tobias for the precise cause of the problem.  But
> basically we have to remove all 'using namespace boost' directives
> from the Borland view of the files.  If you have any more usings on
> your local copy, they might be the cause an need similar wrapping.