1.9.1 says:

"The copy constructor deep-copies any data pointed to by the T_var constructor
parameter. This copy will be destroyed when the T_var is destroyed or when a new
value is assigned to it. Compliant implementations may, but are not required to, utilize
some form of reference counting to avoid such copies."

and

"The normal assignment operator deep-copies any data pointed to by the T_var
assignment parameter. This copy will be destroyed when the T_var is destroyed or
when a new value is assigned to it. Assigning a null pointer to a T_var is legal and
results in deallocation of the data pointed to by the T_var."

So my question is, is it legal to use ValueBase::_add_ref() and _remove_ref() instead of _copy_value() in this instance when T_var is representing a valuetype?

Footnote 11 on page 1-48 of the 1.1 version of the C++ language mapping states that sequence _var classes don't have a const version of "operator []". The justification in the footnote is incorrect.

This footnote should be removed, and the operator provided, since it otherwise prevents accessing sequence members through a const reference to a sequence _var.

need an _unchecked_narrow static operation that is similar to the _narrow. It will take in an object pointer but unlike _narrow will not check for compatibility before creating a new object reference.

In IDL it gives:

// IDL
valuetype V

;

But it should be

// IDL
valuetype V

;

the C++ mapping should explicitly list operator == and operator Unable to render embedded object: File (= in the examples and text. If it is not allowed to use ==/) not found.= the methods should be declared private

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

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