sequence points

hi

According to the standard these are how we define sequence points:


*the call to a function ,after the arguments have been evaluated

*the end of the first operand of the following operators :

{logical AND :&&

Logical OR :||

Conditional ?

Comma ,


}
*the end of a full declarator


*the end of a full expression:an initializer , the expresion in an
expression statement

the controlling expression of a selection statement (if or switch)

the controlling expresion of while or do statement,eatch of the
expressions of a for statement

the expression in a return statement


*Immediatly before a library function returns


*After the actions associated with eatch formatted input/output
function conversion specifier


*Immediatly before and immediatly after eatch call to a comparison
function,and between any call to a comparison function and any
movement of the objects passed as arguments to that call

can someone explain eatch one deeply?

re: sequence points

Jrdman <ahmed.bou23@gmail.comwrites:
<snip full list of places where sequence point occur in C programs>That's asking for too much work. None of them seem particularly
confusing to me, so it would help if you said which ones are confusing
you. If it really is all of them, then you need to go back and review
some basic C terminology.

--
Ben.

re: sequence points

On Aug 17, 2:52*pm, Ben Bacarisse <ben.use...@bsb.me.ukwrote:Just explain what you can explain (if you want a few ones of them)

re: sequence points

Jrdman wrote:What kind of explanation do you seek? The Standard says
that a sequence point exists at each of these moments in the
execution of a program. It's not a consequence of something
else, with an explanation like "The function arguments are
blue but the function body is yellow; the boundary between
the colors causes a sequence point." What the Standard says
is that there *is* a sequence point between the evaluation
of the arguments and the call to the function, in much the
same way someone might tell you there *is* a maple tree in
front of his house. The maple tree itself defies explanation
(cf. "Trees" by Joyce Kilmer).

--
Eric Sosman
esosman@ieee-dot-org.invalid

re: sequence points

"Jrdman" wrote:
The article in the link should be helpful in this particular case, this is a
situation where other languages may differ.

http://en.wikipedia.org/wiki/Short-circuit_evaluation

I'll leave the other to people with more time on their hands.

re: sequence points

On Sun, 17 Aug 2008 07:47:06 -0700, Jrdman <ahmed.bou23@gmail.comwrote:
<snip>I know you were directed to reading the standard in the other thread, but
I now get the impression that you are probably better off reading the C
FAQ. It explains what sequence points are, how it could affect the code
you write, and gives you several examples.

http://c-faq.com/expr/seqpoints.html


- Anand

re: sequence points

"Jrdman" <ahmed.bou23@gmail.comwrote in message news:|>
Imagine you are an accountant. A certain points, maybe once a week, the tax
people call in and demand to see the books. Management wants a report every
month. The shareholders get an annual report. Just occasionally one of the
subordinantes realises he's made a mistake and you have to go through seeing
if any money has been lost.
However between these points the books are being actively edited. You might
have only half the weeks' sales in the ledger because you are writing them
in. You can't respond to a demand to present the accounts just like that,
you have to have formal times at which the accounts are reconciled and
balanced.

Sequence points are like that. Every time the program needs to present an
account of the variables it holds is a sequence point. At other times, the
variables are under edit.

--
Free games and programming goodies.
http://www.personal.leeds.ac.uk/~bgy1mm

re: sequence points

Jrdman wrote:Go back to the referenced sections, the explanations are clear.

--
Ian Collins.