public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/60318] Documentation bug: C++ Misunderstandings: Implicit Copy-Assignment for Virtual Bases
Date: Wed, 08 Sep 2021 23:31:59 +0000 [thread overview]
Message-ID: <bug-60318-4-TQvU5vsCw7@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-60318-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=60318
--- Comment #6 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The releases/gcc-10 branch has been updated by Jonathan Wakely
<redi@gcc.gnu.org>:
https://gcc.gnu.org/g:b9f52acb7dc74fb7b4591f98d81cdcf54b36df38
commit r10-10102-gb9f52acb7dc74fb7b4591f98d81cdcf54b36df38
Author: Jonathan Wakely <jwakely@redhat.com>
Date: Tue Aug 31 09:46:41 2021 +0100
c++: Fix docs on assignment of virtual bases [PR60318]
The description of behaviour is incorrect, the virtual base gets
assigned before entering the bodies of A::operator= and B::operator=,
not after.
The example is also ill-formed (passing a string literal to char*) and
undefined (missing return from Base::operator=).
Signed-off-by: Jonathan Wakely <jwakely@redhat.com>
gcc/ChangeLog:
PR c++/60318
* doc/trouble.texi (Copy Assignment): Fix description of
behaviour and fix code in example.
(cherry picked from commit 3c64582372cf445eabc4f9e99def7e33fb0270ee)
next prev parent reply other threads:[~2021-09-08 23:31 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-22 18:09 [Bug c++/60318] New: " JuergenGCC at bund dot us
2021-08-30 3:16 ` [Bug c++/60318] " pinskia at gcc dot gnu.org
2021-08-31 8:42 ` redi at gcc dot gnu.org
2021-08-31 9:09 ` redi at gcc dot gnu.org
2021-09-08 21:34 ` cvs-commit at gcc dot gnu.org
2021-09-08 23:30 ` cvs-commit at gcc dot gnu.org
2021-09-08 23:31 ` cvs-commit at gcc dot gnu.org [this message]
2021-09-08 23:34 ` cvs-commit at gcc dot gnu.org
2021-09-08 23:35 ` redi at gcc dot gnu.org
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-60318-4-TQvU5vsCw7@http.gcc.gnu.org/bugzilla/ \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@gcc.gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).