The ORB interface destroy() operation defined in the core CORBA 2.3 spec seems to be missing from the associated C++ language mapping.

Add the destroy operation to the ORB definition in 4.35.1 and 4.45.21

Summary: We recently added _ptr_type and _var_type typedefs into interface classes
to make writing templates for interface types easier. We should add the
same typedefs for valuetype classes.

Add the missing typedefs

The spec defines: // C++ class Seq_var; class Seq

; We propose to extend this to the following to make it possible to write more generic C++ code. // C++ class Seq_var; class Seq_out; class Seq

;

In section 4.11 add to the example at the end Seq_out and a _out_type typedef
as in the revised text below.
The _size_type typedef will make it possible in the user code to differentiate
between the index of a sequence type and a user defined ULong value. To
section 4.15 add the sentence
To facilitate template-based programming, a nested public typedef _size_type is delivered as the type
representing the length of the sequence.
And to the sequence class examples in section 4.15 the following
typedef ULong _size_type;

I was looking at the OMG IDL to C++ mapping specification, specifically
page 123 and came across the below. It looks to me that their
implementation in the spec is NOT correct. Shouldn't the swap function
take the "tmp" Servant_var?

Servant_var& operator=(Servant* p)
{
if (_ptr != p)

return *this;
}

Servant_var&
operator=(const Servant_var& b)
{
if (_ptr != b._ptr)

return *this;
}

Update assignment operator as proposed

To really support template meta programming the valuetype classes should deliver a typedef _out_type besides the _ptr_type and _var_type which are proposed to be added as part of issue 1794

Add a _out_type typedef to the valuetype class

To really support template meta programming the inteface should deliver a typedef _out_type besides the already defined _ptr_type and _var_type

Add a _out_type typedef to the interface class

The C++ keywords in section 4.47 should be updated and extended with the addition of C++0x

Add the following keywords to the table on page 154 as part of section 4.47

In section 4.5.4 it says: Unlike _duplicate, the parameter to _narrow is a reference of an object of any interface type (Object_ptr). If the actual (runtime) type of the parameter object can be widened to the requested interface’s type, then _narrow will return a valid object reference; it should say (widened to narrowed) Unlike _duplicate, the parameter to _narrow is a reference of an object of any interface type (Object_ptr). If the actual (runtime) type of the parameter object can be narrowed to the requested interface’s type, then _narrow will return a valid object reference;

In section 4.5.4 change widened to narrowed

Section 1.31.3 says:

• In the C mapping, set_one_value used strings, while
  others used NamedValues containg any. Even though implementations
  need only support strings as values, the signatures now uniformly
  allow alternatives.

I would suggest to delete the entire bullet point. In particular, the notion
of allowing alternative data types as propery values for contexts doesn't
work because the receiver expects a sequence of strings with an even number
of elements; if anything but a string sequence is sent, the receiver
has no chance of unmarshaling it.

Remove bullet as suggested

The Object::get_policy returns a Policy in IDL, not a Policy_ptr, that is the C++ return value

Replace in 4.36.1 the text Policy_ptr to Policy