public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: David Abrahams <dave@boost-consulting.com> To: nobody@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org, Subject: Re: c++/9278: Illegal use of typedef to "void" Date: Tue, 14 Jan 2003 00:16:00 -0000 [thread overview] Message-ID: <20030114001602.8282.qmail@sources.redhat.com> (raw) The following reply was made to PR c++/9278; it has been noted by GNATS. From: David Abrahams <dave@boost-consulting.com> To: bangerth@dealii.org Cc: gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org, nobody@gcc.gnu.org, gcc-gnats@gcc.gnu.org Subject: Re: c++/9278: Illegal use of typedef to "void" Date: Mon, 13 Jan 2003 19:11:46 -0500 bangerth@dealii.org writes: > Old Synopsis: dependent type in conversion operator bug > New Synopsis: Illegal use of typedef to "void" > > State-Changed-From-To: analyzed->open > State-Changed-By: bangerth > State-Changed-When: Mon Jan 13 13:59:57 2003 > State-Changed-Why: > Given the mail by Dave, the original code was in error, and > the converse held. So this is what should _not_ compile, but > does, according to him. (It does so since at least 2.95.) > I think I have no idea myself whether this is legal or > not, I did not even know whether one can typedef void... Please insert a reference to http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/cwg_closed.html#18 in the GNATs issue record. It explains what I'm saying. > ---------------------------- > struct voidify { typedef void type; }; > > struct X { > operator int (voidify::type) const { return 1; } > }; > > X x; > --------------------- > > http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=9278 > -- David Abrahams dave@boost-consulting.com * http://www.boost-consulting.com Boost support, enhancements, training, and commercial distribution
next reply other threads:[~2003-01-14 0:16 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2003-01-14 0:16 David Abrahams [this message] -- strict thread matches above, loose matches on Subject: below -- 2003-04-07 11:06 Giovanni Bajo 2003-01-14 0:22 bangerth 2003-01-13 22:00 bangerth
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=20030114001602.8282.qmail@sources.redhat.com \ --to=dave@boost-consulting.com \ --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: linkBe 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).