CORBA26 — Valuetype initialzers need exceptions

Valuetype initializers need exception declarations in order to provide
complete mapping of Java declarations to IDL declarations in Java to IDL
mapping.

Discussion: This was discussed in te past and rejected because of the
backward non-compatible changes required in the IFR. This time
around.... the IFR changes are already part of the backward compatible
changes maded in connection with the addition of exeptions to attributes
etc in CCM in resolution to issue 3233. So all that is needed is change
to one grammar rule and provision of language mappings. As the results
of Components FTF is merged into Core to create CORBA Core 3.0
everything then falls into place to give us initializers with exceptions
for valuetypes.

Issue 3641 in Java-IDL RTF is handling the Java language mapping issue,
and Simon is shepherding that.

We need to create a C++ language mapping issue and resolve it with the
obvious mapping in C++ (Michi?)

Specfic text changes:

All changes specified here relative to document ptc/01-06-10:

1. On page 3-13 change grammar production rule 23 to read:

(23) <init_dcl> ::= “factory” <identifier>
“(“ [ <init_param_decls> ] “)” [ <raises_expr> ] “;”

instead of:

(23) <init_dcl> ::= “factory” <identifier>
“(“ [ <init_param_decls> ] “)” “;”

2. On page 3-26 in section 3.8.1.5 change grammar production
rule 23 to read:

(23) <init_dcl> ::= “factory” <identifier>
“(“ [ <init_param_decls> ] “)” [ <raises_expr> ] “;”

instead of:

(23) <init_dcl> ::= “factory” <identifier>
“(“ [ <init_param_decls> ] “)” “;”

Accept the proposed change based on discussion above