This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug c/11751] wrong evaluation order of an expression
- From: "d_picco at hotmail dot com" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: 23 Feb 2005 20:38:56 -0000
- Subject: [Bug c/11751] wrong evaluation order of an expression
- References: <20030731175202.11751.me@elitsa.net>
- Reply-to: gcc-bugzilla at gcc dot gnu dot org
------- Additional Comments From d_picco at hotmail dot com 2005-02-23 20:38 -------
The point I was making with my example is that the native types (int, long,
char, etc...) have different behaviour than a user-defined class with the
operator++. If it is compiler dependent which way the expression is evaluated,
why not at least make them both agree? GCC is also the only compiler out of the
5 that I've tested that exhibits this behaviour... all others unify the
behaviour of native and user-defined operator++.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=11751