public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "paul_m_doc at hotmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/9278] Illegal use of typedef to "void"
Date: Fri, 25 May 2007 12:12:00 -0000 [thread overview]
Message-ID: <20070525121153.18076.qmail@sourceware.org> (raw)
In-Reply-To: <bug-9278-501@http.gcc.gnu.org/bugzilla/>
------- Comment #27 from paul_m_doc at hotmail dot com 2007-05-25 13:11 -------
(In reply to comment #26)
> *** Bug 32058 has been marked as a duplicate of this bug. ***
Sigh :(. The response at the October 2006 to DR 577 is enough to make any
template meta-programmer bang their head against the wall in despair.
This is the language that, according to its creator as a design goal should
'trust the programmer', right?
I certainly have a formal position on this and many other similar issues that
affect TMP.
This should have been at most a warning with the option to turn it off.
The Visual C++ compilers may be less fussy than gcc but at least they tend to
do the sensible thing.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=9278
next prev parent reply other threads:[~2007-05-25 12:12 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-9278-501@http.gcc.gnu.org/bugzilla/>
2005-11-24 9:42 ` reichelt at gcc dot gnu dot org
2005-11-25 14:59 ` reichelt at gcc dot gnu dot org
2005-11-25 15:07 ` reichelt at gcc dot gnu dot org
2006-04-22 0:17 ` pinskia at gcc dot gnu dot org
2006-04-23 23:44 ` ben at decadentplace dot org dot uk
2006-04-24 0:41 ` pinskia at gcc dot gnu dot org
2006-11-29 0:41 ` pinskia at gcc dot gnu dot org
2007-02-03 15:06 ` tbm at cyrius dot com
2007-02-03 15:14 ` joseph at codesourcery dot com
2007-05-24 1:56 ` pinskia at gcc dot gnu dot org
2007-05-25 12:12 ` paul_m_doc at hotmail dot com [this message]
2007-06-16 4:53 ` pinskia at gcc dot gnu dot org
2007-08-17 23:34 ` pinskia at gcc dot gnu dot org
[not found] <20030111195600.9278.dave@boost-consulting.com>
2004-01-14 15:31 ` giovannibajo at libero dot it
2004-01-14 18:24 ` dave at boost-consulting dot com
2004-01-14 18:39 ` pinskia at gcc dot gnu dot org
2004-01-14 19:54 ` dave at boost-consulting dot com
2004-01-14 19:58 ` pinskia at gcc dot gnu dot org
2004-01-14 20:37 ` dave at boost-consulting dot com
2004-01-14 20:49 ` pinskia at gcc dot gnu dot org
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=20070525121153.18076.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).