public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/21510] Possible bug
Date: Sun, 15 May 2005 14:13:00 -0000 [thread overview]
Message-ID: <20050515141257.11814.qmail@sourceware.org> (raw)
In-Reply-To: <20050511102800.21510.sven@clio.in-berlin.de>
------- Additional Comments From pinskia at gcc dot gnu dot org 2005-05-15 14:12 -------
(In reply to comment #4)
> If there is no other way to distinguish reliable between unions and classes,
> add it into the extension list. Unions should be avoided in object oriented
> design, anyway, but it is a nice-to-have feature.
Extensions are bad. Even just bugs in the compiler is a bad thing beause people would think the bug
was an extension and start depending on it and then when the bug was fixed, people complain their
code no longer compiles.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=21510
next prev parent reply other threads:[~2005-05-15 14:13 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-11 10:28 [Bug c++/21510] New: " sven at clio dot in-berlin dot de
2005-05-11 11:10 ` [Bug c++/21510] " pinskia at gcc dot gnu dot org
2005-05-12 9:49 ` sven at clio dot in-berlin dot de
2005-05-15 12:37 ` lerdsuwa at gcc dot gnu dot org
2005-05-15 14:08 ` sven at clio dot in-berlin dot de
2005-05-15 14:13 ` pinskia at gcc dot gnu dot org [this message]
2005-05-15 14:46 ` sven at clio dot in-berlin dot de
2005-05-15 15:04 ` pcarlini at suse dot de
2005-05-16 10:22 ` sven at clio dot in-berlin dot de
2005-05-16 19:19 ` gdr at integrable-solutions dot net
2005-05-17 11:43 ` sven at clio dot in-berlin dot de
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=20050515141257.11814.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).