public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jeff at schwabcenter dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/40192] [4.4/4.5 Regression] Unable to use std::vector with typedef'd array types
Date: Tue, 19 May 2009 17:09:00 -0000	[thread overview]
Message-ID: <20090519170920.9771.qmail@sourceware.org> (raw)
In-Reply-To: <bug-40192-17730@http.gcc.gnu.org/bugzilla/>



------- Comment #7 from jeff at schwabcenter dot com  2009-05-19 17:09 -------
I understand the desire for backward compatibility, but are the semantics
actually the same?  Are the vector values arrays, or do they decay to pointers?
 Section 23.1 says standard container elements have to be CopyConstructible and
assignable, but raw arrays are neither.

Is there at least some flag to re-enable the diagnostic?  If you're saying this
is a necessary evil for reasons of backward compatibility, then I understand,
but in my opinion, this is a step backward that will confuse newcomers like
Brian and hurt cross-compatibility.  Speaking strictly as a GCC user, I don't
see any reason to reduce the compiler's ability to deduce an obvious mistake
with ill-defined semantics.


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=40192


  parent reply	other threads:[~2009-05-19 17:09 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-18 21:06 [Bug c++/40192] New: " coleb at eyesopen dot com
2009-05-18 22:34 ` [Bug c++/40192] [4.4/4.5 Regression] " paolo dot carlini at oracle dot com
2009-05-18 23:16 ` paolo at gcc dot gnu dot org
2009-05-18 23:17 ` paolo at gcc dot gnu dot org
2009-05-18 23:18 ` paolo dot carlini at oracle dot com
2009-05-19 16:36 ` jeff at schwabcenter dot com
2009-05-19 16:42 ` paolo dot carlini at oracle dot com
2009-05-19 17:09 ` jeff at schwabcenter dot com [this message]
2009-05-19 17:12 ` paolo dot carlini at oracle dot com
2009-05-19 17:33 ` jeff at schwabcenter dot com
2009-05-19 17:38 ` paolo dot carlini at oracle dot com
2009-05-19 17:58 ` coleb at eyesopen dot com
2009-05-19 18:07 ` jeff at schwabcenter dot com
2009-05-19 18:19 ` paolo dot carlini at oracle dot com

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=20090519170920.9771.qmail@sourceware.org \
    --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).