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++/16696] Strange message when operator++ not found
Date: Fri, 23 Jul 2004 21:08:00 -0000 [thread overview]
Message-ID: <20040723210824.7556.qmail@sourceware.org> (raw)
In-Reply-To: <20040723203946.16696.bangerth@dealii.org>
------- Additional Comments From pinskia at gcc dot gnu dot org 2004-07-23 21:08 -------
It is special cased:
case POSTINCREMENT_EXPR:
case POSTDECREMENT_EXPR:
/* Look for an `operator++ (int)'. If they didn't have
one, then we fall back to the old way of doing things. */
if (flags & LOOKUP_COMPLAIN)
pedwarn ("no `%D(int)' declared for postfix `%s', trying prefix operator instead",
fnname,
operator_name_info[code].name);
if (code == POSTINCREMENT_EXPR)
code = PREINCREMENT_EXPR;
else
code = PREDECREMENT_EXPR;
result = build_new_op (code, flags, arg1, NULL_TREE, NULL_TREE,
overloaded_p);
which means -fpermissive does look do the transformation. :(
Why we do this is unknown as it comes from PRE EGCSE (aka CVS days).
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=16696
next prev parent reply other threads:[~2004-07-23 21:08 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-23 20:39 [Bug c++/16696] New: " bangerth at dealii dot org
2004-07-23 20:58 ` [Bug c++/16696] " pinskia at gcc dot gnu dot org
2004-07-23 21:02 ` bangerth at ices dot utexas dot edu
2004-07-23 21:08 ` pinskia at gcc dot gnu dot org [this message]
2004-07-23 21:12 ` bangerth at ices dot utexas dot edu
2004-07-23 21:14 ` pinskia at gcc dot gnu dot org
2004-07-23 21:19 ` bangerth at ices dot utexas dot edu
2004-07-23 21:41 ` schwab at suse dot de
2004-07-23 23:27 ` bangerth at ices dot utexas dot edu
2004-08-11 22:16 ` pinskia at gcc dot gnu dot org
[not found] <bug-16696-102@http.gcc.gnu.org/bugzilla/>
2007-07-06 8:13 ` rob1weld at aol dot com
2007-07-07 18:06 ` rob1weld at aol dot com
2007-07-07 18:27 ` pcarlini at suse dot de
2009-08-04 15:51 ` manu at gcc dot gnu dot org
2009-08-04 15:52 ` manu 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=20040723210824.7556.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).