public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: Peter Schmid <schmid@snake.iap.physik.tu-darmstadt.de>
To: nobody@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: Re: c++/4624: Bogus warning (private in aggregate types)
Date: Sat, 15 Dec 2001 11:46:00 -0000	[thread overview]
Message-ID: <20011215194601.28801.qmail@sources.redhat.com> (raw)

The following reply was made to PR c++/4624; it has been noted by GNATS.

From: Peter Schmid <schmid@snake.iap.physik.tu-darmstadt.de>
To: nathan@gcc.gnu.org, gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org,
        nobody@gcc.gnu.org, schmid@snake.iap.physik.tu-darmstadt.de,
        gcc-gnats@gcc.gnu.org
Cc:  
Subject: Re: c++/4624: Bogus warning (private in aggregate types)
Date: Sat, 15 Dec 2001 20:44:40 +0100 (CET)

 On 15 Dec 2001 nathan@gcc.gnu.org wrote:
 
 > Synopsis: Bogus warning (private in aggregate types)
 > 
 > State-Changed-From-To: open->closed
 > State-Changed-By: nathan
 > State-Changed-When: Sat Dec 15 11:24:25 2001
 > State-Changed-Why:
 >     I don't think it's bogus. all the user defined members
 >     are private. The class is still POD.
 >     
 > 
 > http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=4624
 > 
 
 Mr John Maddock Implementor of the boost config test suite has a different
 point of view. 
 He says: "The compiler misreads 8.5.1, treating classes as non-aggregate
 if they contain private or protected member functions.",
 cf. boost/libs/config/test/boost_no_priv_aggregate.cxx.
 
 Hope this helps.
 
 Peter Schmid
 


             reply	other threads:[~2001-12-15 19:46 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-12-15 11:46 Peter Schmid [this message]
  -- strict thread matches above, loose matches on Subject: below --
2001-12-15 11:24 nathan
2001-10-19 15:06 Peter Schmid

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=20011215194601.28801.qmail@sources.redhat.com \
    --to=schmid@snake.iap.physik.tu-darmstadt.de \
    --cc=gcc-prs@gcc.gnu.org \
    --cc=nobody@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).