🚀 go-pugleaf

Well, it's been a couple of days, and I'm about to leave, and *nobody*
has replied (as far as our news server knows), so I'll stick my neck
out in public again....

In article <18221@autodesk.COM>, larsn@Autodesk.COM (Lars Nyman) writes:

> I *think* there is language in the standard that says something to
> the effect that comparisons of pointers to two objects that are NOT
> members of the same aggregate or union object is undefined (with one
> exception - one or both pointers pointing past the last object of an
> array).

The actual situation is close.  For the time being, let us consider
pointers pointing one element past the end of an array as actually
pointing into that array.  With that proviso, pointer comparison using
<, <=, >, or >= is undefined when the two pointers don't point into the
same object.

Pointer comparison using == or != is always well-defined, and the
pointers compare equal exactly when they point to the same thing (and
!= is the complement of ==).

> So, if I have two different objects of same type, and they are not in
> the same array or aggregate, the result of comparing pointers to them
> is undefined !!???

Yes, except with == or !=.

					der Mouse

			    mouse@larry.mcrcim.mcgill.edu