Boost C++ Libraries: Ticket #2270: Compile Warning: Assignment Operator Could not be generated

attachment set

Fri, 29 Aug 2008 15:20:29 GMT

attachment → assignment_operator_warning.patch

status changed; resolution set

Robert Ramey — Wed, 24 Sep 2008 20:02:33 GMT

status new → closed
resolution → wontfix

Instances of neither one of these classes should be assigned or copy constructed. An attempt to do so would be a serious error. As things are now, any attempt to assign or copy an instance of either of these classes would result in a compile-time error- which is what we want. Including this "fix" would permit the compilation to succeed and produce a program which would fail in subtle ways.

Robert Ramey

status, version, milestone changed; resolution deleted

Wed, 21 Jan 2009 15:15:48 GMT

status closed → reopened
version Boost 1.36.0 → Boost 1.37.0
resolution wontfix
milestone Boost 1.37.0 → To Be Determined

Robert,

Thanks for looking at this. I didn't reply to your comment 4 months ago, because I assumed you'd silence the warning in a different manner.

As the warning from extended_type_info.hpp is still spawned during compilation, I urge you to reconsider this patch.

I understand the design intent is to not allow copying the class. If you look closely at the patch, you'll see that the assignment operator is only declared, not defined. It is also in the private scope of the class.

This will make your intent to prevent copying clear both to the compiler and the programmer, while still producing a compile-time error on an attempt to assign an instance of the class.

Ryan Mulder

Robert Ramey — Sun, 25 Jan 2009 18:26:09 GMT

OK, I've updated extended_type_info to make it non-copyable.

But review array.hpp. I contains make_array which returns a copy of an array wrapper and make_array is in fact used by the system and tests. That is, array must be copyable. I can't explain why this generates a warning. Perhaps array should contain an explicit copy/assignment constructors but I don't see why that should be necessary.

Take another look at array.

Robert Ramey

Mon, 26 Jan 2009 13:10:37 GMT

Thank you for updating extended_type_info.

I posted this patch against 1.36; as of 1.37, I do not see warnings from array. I think this issue is resolved.

Thanks very much for you help.

status changed; resolution set

Robert Ramey — Sat, 31 Jan 2009 18:18:03 GMT

status reopened → closed
resolution → fixed