CORBA3 — Sloppy text in CORBA 3.0, 4.3.8.1 get_policy

In CORBA 3.0 section 4.3.8.1, the description of the Object::get_policy
operation says:

"Invoking non_existent on an object reference prior to get_policy
ensures the accuracy of the returned effective Policy.Ifget_policy is
invoked prior to the object reference being bound, the returned
effective Policy is implementation dependent. In that situation, a
compliant implementation may do any of the following: raise the standard
system exception BAD_INV_ORDER, return some value for that PolicyType
which may be subject to change once a binding is performed, or attempt a
binding and then return the effective Policy."

This is silly, since the only portable thing that applications can do is
to call validate_connection or non_existent before calling get_policy,
having two other non-portable behaviors just serves to make the standard
larger and confuse users.

We should pick one of the two reasonable behaviors--throw BAD_INV_ORDER
or force a binding before returning a valid policy value--and make that
the only valid behavior. Either one will be backwards compatible with
portable code.

Makes sense. Fix it as suggested