From: Gabriel Dos Reis <gdr@integrable-solutions.net>
To: Mark Kettenis <kettenis@chello.nl>
Cc: drow@mvista.com, jh@suse.cz, aj@suse.de, mark@codesourcery.com,
gdb-patches@sources.redhat.com, gcc@gcc.gnu.org
Subject: Re: [PATCH] Classify non-POD struct types more or less correctly on AMD64
Date: Sun, 11 Jan 2004 15:05:00 -0000 [thread overview]
Message-ID: <m3u132edkz.fsf@uniton.integrable-solutions.net> (raw)
In-Reply-To: <200401111237.i0BCbVPL010349@elgar.kettenis.dyndns.org>
Mark Kettenis <kettenis@chello.nl> writes:
| The 1996 ANSI C++ draft has the following statement about non-POD-ness:
using an old oudated document may lead to confusion (luckily, that is
not the case here).
| "A POD-struct is an aggregate class that has no non-static data members
^^^^^^^^^^^^^^^
| of type pointer to member, non-POD-struct, non-POD- union (or array of
| such types) or reference, and has no user-defined copy assignment
| operator and no user-defined destructor. Similarly, a POD-union is an
| aggregate union that has no non-static data members of type pointer to
| member, non-POD-struct, non-POD-union (or array of such types) or
| reference, and has no user-defined copy assignment operator and no
| user-defined destructor. A POD class is a class that is either a
| POD-struct or a POD-union."
|
| So it doesn't say anything about baseclasses.
Sure it does. A POD-struct ought to be an aggregate class, and an
aggregate class does not have base classes.
-- Gaby
next prev parent reply other threads:[~2004-01-11 15:05 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-10 18:00 Mark Kettenis
2004-01-10 18:36 ` Daniel Jacobowitz
2004-01-10 18:59 ` Mark Kettenis
2004-01-11 4:10 ` Daniel Jacobowitz
2004-01-11 12:38 ` Mark Kettenis
2004-01-11 13:29 ` Jan Hubicka
2004-01-12 5:37 ` Mark Mitchell
2004-01-11 15:05 ` Gabriel Dos Reis [this message]
2004-03-19 0:09 ` Daniel Jacobowitz
2004-03-09 15:39 ` Daniel Jacobowitz
2004-03-19 0:09 ` Mark Mitchell
2004-03-10 3:38 ` Mark Mitchell
2004-03-10 4:21 ` Daniel Jacobowitz
2004-03-19 0:09 ` Daniel Jacobowitz
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=m3u132edkz.fsf@uniton.integrable-solutions.net \
--to=gdr@integrable-solutions.net \
--cc=aj@suse.de \
--cc=drow@mvista.com \
--cc=gcc@gcc.gnu.org \
--cc=gdb-patches@sources.redhat.com \
--cc=jh@suse.cz \
--cc=kettenis@chello.nl \
--cc=mark@codesourcery.com \
/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