public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "paolo.carlini at oracle dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/47436] [C++0x] Variadic base-specifier-list of union rejected
Date: Thu, 22 Sep 2011 23:10:00 -0000	[thread overview]
Message-ID: <bug-47436-4-gowLhNBBcS@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-47436-4@http.gcc.gnu.org/bugzilla/>

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

Paolo Carlini <paolo.carlini at oracle dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |RESOLVED
         Resolution|                            |INVALID

--- Comment #8 from Paolo Carlini <paolo.carlini at oracle dot com> 2011-09-22 22:46:26 UTC ---
Good, let's close this as invalid, then.

Thanks for clarifying the error_at thing, I should give it more thought: I was
under the impression that we tend to avoid (not a strict rule) things like
"error: unions cannot have base classes" because on a given line a lot can
happen (other errors together with good code) and an accurate column number is
anyway less convenient (for sure to a human like me!) than a name.


      parent reply	other threads:[~2011-09-22 22:47 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-24 14:47 [Bug c++/47436] New: " schaub.johannes at googlemail dot com
2011-08-22 22:57 ` [Bug c++/47436] " daniel.kruegler at googlemail dot com
2011-09-22 18:12 ` [Bug c++/47436] [C++0x] " paolo.carlini at oracle dot com
2011-09-22 18:16 ` daniel.kruegler at googlemail dot com
2011-09-22 19:20 ` schaub.johannes at googlemail dot com
2011-09-22 19:28 ` redi at gcc dot gnu.org
2011-09-22 21:15 ` paolo.carlini at oracle dot com
2011-09-22 22:17 ` jason at gcc dot gnu.org
2011-09-22 23:10 ` paolo.carlini at oracle dot com [this message]

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-47436-4-gowLhNBBcS@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).