public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: Wolfgang Bangerth <bangerth@ticam.utexas.edu> To: nobody@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org, Subject: Re: c++/9278: dependent type in conversion operator bug Date: Tue, 14 Jan 2003 00:36:00 -0000 [thread overview] Message-ID: <20030114003600.19823.qmail@sources.redhat.com> (raw) The following reply was made to PR c++/9278; it has been noted by GNATS. From: Wolfgang Bangerth <bangerth@ticam.utexas.edu> To: David Abrahams <dave@boost-consulting.com> Cc: "Joseph S. Myers" <jsm28@cam.ac.uk>, <gcc-bugs@gcc.gnu.org>, <gcc-gnats@gcc.gnu.org> Subject: Re: c++/9278: dependent type in conversion operator bug Date: Mon, 13 Jan 2003 18:27:36 -0600 (CST) > > Indeed a very obscure feature. (Although, I must admit that, I desperately > > needed something like that not too long ago and had to invent various > > template metaprogramming hoops to work around...) > > I needed exactly that yesterday, which is why it came up ;-) > Using SFINAE to rule out certain conversions was my game, but it > didn't fly :( SFINAE??? In my case, I wanted to make things more uniform in Functor classes: when you call a function, it either returns a value, or void. So this does not go together RETTYPE ret_val = function(args) if RETTYPE==void. What an annoying difference, and how convenient would it be if there were "void variables", i.e. objects to which you can assign the result of a void expression :-) Some template trickery and specilization can get one around this, however. W. ------------------------------------------------------------------------- Wolfgang Bangerth email: bangerth@ticam.utexas.edu www: http://www.ticam.utexas.edu/~bangerth/
next reply other threads:[~2003-01-14 0:36 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2003-01-14 0:36 Wolfgang Bangerth [this message] -- strict thread matches above, loose matches on Subject: below -- 2003-01-14 2:36 David Abrahams 2003-01-14 0:26 David Abrahams 2003-01-13 23:06 Wolfgang Bangerth 2003-01-13 22:56 Joseph S. Myers 2003-01-12 23:52 bangerth 2003-01-12 3:56 dave
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=20030114003600.19823.qmail@sources.redhat.com \ --to=bangerth@ticam.utexas.edu \ --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).