Legacy Issue Number: 1251
Summary: Above rules seem to imply that the
"safe" keyword identifier can only occur before the first scoped name in the
<value_parent_spec>, whereas I think the actual intent is that it can only
occur before a non-abstract value type, of which there is at most one in the
list, although it need not be the first. Since this can"t be expressed in the
rules exactly, I would simply amend the rule to be:
<value_parent_spec> ::= ":" [ <safe_token> ] <scoped_name>
and simply express the semantic restriction in the text. There already is a
brief mention of the semantics of the "safe" keyword in section 220.127.116.11
"Substitutability Issues". Perhaps another sentence or two would help clarify
the intended usage.
Reported: CORBA 2.2 — Tue, 28 Apr 1998 04:00 GMT
Disposition: Deferred — CORBA 3.4
This proposal was generated automatically by request of the Task Force Chair Adam Mitz.
Updated: Mon, 30 Mar 2020 19:47 GMT