CORBA24 — is_equivalent and policies

How should is_equivalent() behave if I compare two references that denote
the same object at the same location, using the same profiles, etc, but
differ in the policies? Do differences in the policies affect the outcome?

My gut feeling is that is_equivalent() should return false in this case
because it uses reference identity, not object identity. However, we
are rapidly approaching the point where is_equivalent() might as well
unconditionally return false because we are adding more and more flavours
of additional information into IORs as time goes by. Invocation policies,
transaction policies, codesets, multiple profiles, optional components,
etc, etc.

Does is_equivalent() require a more precise definition in order to remain
useful?

Incorporate changes and close issue