Re: [Boost-users] [container] Initialization from transformed_range compilation error

Subject: Re: [Boost-users] [container] Initialization from transformed_range compilation error
From: Ion Gaztañaga (igaztanaga_at_[hidden])
Date: 2011-09-08 02:08:18

El 08/09/2011 0:07, Daniel James escribió:
> 2011/9/7 Ion Gaztañaga<igaztanaga_at_[hidden]>:
>> El 07/09/2011 22:30, Daniel James escribió:
>>>
>>> I noticed that you have a macro BOOST_COPYABLE_AND_MOVABLE_ALT which
>>> doesn't define the assignment operator, is that a way to avoid this
>>> problem? I'd be tempted to do that, implicit move assignment doesn't
>>> seem that important to me.
>>
>> The problem is that containers already define the non-const assignment
>> operator, so there is nothing you can do with this, unless, I put a compile
>> time switch to change move emulation in Boost.Container.
>
> Sorry I wasn't clear. I was asking if BOOST_COPYABLE_AND_MOVABLE_ALT
> is something I can use in my own code instead of
> BOOST_COPYABLE_AND_MOVABLE?

BOOST_COPYABLE_AND_MOVABLE_ALT for C++0x compilers so it is a bit 
useless wouldn't be portable. I guess BOOST_COPYABLE_AND_MOVABLE_ALT was 
there since the review but I forgot to remove it. If there is interest I 
can define and document it as an alternative.

Best,

Ion