Opened 11 years ago

Closed 10 years ago

#1923 closed Bugs (fixed)

Unordered move implementation doesn't work in Borland.

Reported by: Daniel James Owned by: Daniel James
Milestone: Boost 1.36.0 Component: unordered
Version: Boost Development Trunk Severity: Problem
Keywords: Cc:


A ticket to track Borland fixes.

For a start: [45409] Borland doesn't seem to be able to cope with 'has_move_assign'.

Change History (3)

comment:1 Changed 11 years ago by Daniel James

(In [45573]) Fix for older versions of the Borland C++ compiler which create the default 'operator=' even when an 'operator=' which takes its argument by value has been defined. This causes assignments to be ambiguous. To work around this, I'm removing the definitions on those compilers - breaking move assignment, but allowing other assignments to work.

I'm using 0x0593 because that's the earliest compiler that I've seen do the right thing, but it might also work on earlier 5.9.x versions.

Refs #1923.

comment:2 Changed 11 years ago by Daniel James

Milestone: To Be DeterminedBoost 1.36.0
Status: newassigned

comment:3 Changed 10 years ago by Daniel James

Resolution: fixed
Status: assignedclosed
Note: See TracTickets for help on using tickets.