Search:

I tend to keep my mathematical statements simple, and use intermediate values if it helps
reading it and seeing that it will do what's expected. Once it's tested and working, I may
remove the...

Ok, thanks.

Nice to know that the standard is not required reading.

Are C references like those in Pelles C, and the references here, complete enough to afford
a reasonable expectation that...

Ok, thanks for the info, and thanks to Grumpy also.

I believe I understand it.

I am curious about something. Would it be fair to say that undefined behavior is "permitted", in the interest
of...

Agreed. But one doesn't always know that their understanding is wrong. It's in things like this that you question it.
Also, not debating, just trying to understand.



Actually, that's the...

My interpretation of the standard is that the ordinality of certain pointers and therefore the comparison results of those pointers
are defined and guaranteed. For pointers to two different arrays,...

Ok, thanks.

Does the undefined behavior only apply to relational operations?

For example, if you printed (printf) the values of two respective pointers to two arrays,
would the printed values...

So are there then different "types" of pointers to same type? Something that is unaccessable to the programmer?

Is it that a proper conversion will be done for assignment, but not for comparison?...

That makes sense.

So would assignments also be a problem then?
If p1 points to array1, and p2 points to array2, would p1 = p2 be undefined?

-

Isn't it only the ordinality of the pointers that is undefined?
(as opposed to, eg, two pointers to elements in the same array)

Wouldn't the comparison still give you a valid result?

-