This is the mail archive of the
libstdc++@gcc.gnu.org
mailing list for the libstdc++ project.
Re: Use of strings in new exception implementation (report libstd c++/1972)
- To: libstdc++ at gcc dot gnu dot org
- Subject: Re: Use of strings in new exception implementation (report libstd c++/1972)
- From: Nathan Myers <ncm at nospam dot cantrip dot org>
- Date: Wed, 14 Feb 2001 19:11:03 -0800
- References: <F888C30C3021D411B9DA00B0D0209BE8096889@CVO-EXCHANGE>
- Reply-To: libstdc++ at gcc dot gnu dot org
On Wed, Feb 14, 2001 at 04:30:08PM -0800, Greg Bumgardner wrote:
> I'm also curious about the handling of assignment operators. The standard
> shows that exception has an assignment operator, even though it has nothing
> to assign, but none of the derived classes have them. If we don't design
> these classes to correctly support assignment, then the operator should
> probably be declared private.
The standard mentions assignment and copy ctor when it has something
to say about their semantics. The assumption (as documented in
chapter 17) is that if you do something under the hood that would
make the compiler-generated version do the wrong thing, it's your
responsibility (as implementor) to cover up by defining one that
works right.
Nathan Myers
ncm at cantrip dot org