The IDL to C++11 language mapping section 6.31 should be extended for struct inheritance as it is now part of IDL4 (Building Block Extended Data-Types)

Support for struct inheritance

Add mapping for IDL4 struct inheritance

Add support for int8 which is a new type, the other (u)int(8/16/32/64) are just aliases so don't need to be in the language mapping

Add int8/uint8 mapping

Add a new subsection in 6.31 for IDL int8/uint8

The V_factory should have deleted assignment/copy so add
private:
V_factory (const V_factory&) = delete;
V_factory (V_factory&&) = delete;
V_factory& operator =(const V_factory&) = delete;
V_factory& operator =(V_factory&&) = delete;

In the text change
Each generated factory class has a protected virtual destructor, a protected default constructor.
to
Each generated factory class has a protected virtual destructor, a protected default constructor, deleted copy/move constructors, and deleted copy/move assignment operators

Add deleted special member functions to type-specific value factories

Use the "= delete" feature of C++11.

ValueBase has only a protected copy/move copy constructor to allow a derived class to make a copy, the assignment operators are deleted, because of this also for a valuebox the assignment operators should be deleted, so the 3rd bullet should be updated from

Protected copy and move assignment operators

to

Private deleted copy and move assignment operators

And in the code example

ColorValue& operator=(const ColorValue&);
ColorValue& operator=(ColorValue&&);

to

ColorValue& operator=(const ColorValue&) = delete;
ColorValue& operator=(ColorValue&&) = delete;

Duplicates issues CPP1115-5

This appears to be a duplicate

The valuebox created should be using final, so add to the bullets of 6.18.7.2 a first bullet saying "Must be final" and change in the code
class ColorValue : public ValueBase
to
class ColorValue : public ValueBase final

Use the C++ final specifier on value box classes

Make use of the "final" capability of C++11

ValueBase has only a protected copy/move copy constructor to allow a derived class to make a copy, the assignment operators are deleted, because of this also for a valuebox the assignment operators should be deleted, so the 3rd bullet should be updated from

Protected copy and move assignment operators

to

Private deleted copy and move assignment operators

And in the code example

ColorValue& operator=(const ColorValue&);
ColorValue& operator=(ColorValue&&);

to

ColorValue& operator=(const ColorValue&) = delete;
ColorValue& operator=(ColorValue&&) = delete;

Value box classes shouldn't be assignable

Update to work with ValueBase

ValueFactoryBase should have deleted assignment/copy operators so add to the code part

private:
ValueFactoryBase (ValueFactoryBase&&) = delete;
ValueFactoryBase (const ValueFactoryBase&) = delete;
ValueFactoryBase& operator =(const ValueFactoryBase&) = delete;
ValueFactoryBase& operator =(ValueFactoryBase&&) = delete;

Add deleted special member functions to ValueFactoryBase

Use the C++11 "= delete" feature for ValueFactoryBase.

Any C++11 operation in the spec which uses override shouldn't have virtual, that is redundant and shouldn't be done, so for example

virtual void val2 (int32_t) override;

Should be

void val2 (int32_t) override;

Easiest is to search for override and check that any operation that has override doesn't have virtual

Remove uses of the C++ virtual keyword that aren't needed

Member functions declared with "override" should not also have "virtual"

The operation _default_POA currently declared as

IDL::traits<PortableServer::POA>::ref_type _default_POA()

Should be

IDL::traits<PortableServer::POA>::ref_type _default_POA() override

Also the formatting of the constructor of the TIE template should be changed, hard to read. Initializing the members could use std::move so change

: tied_object_(t), poa_(poa)

to

: tied_object_(std::move(t)), poa_(std::move(poa))

Updated code for Delegation-Based Interface Implementation

Update code to reflect C++ best practices

The IDL to C++11 language mapping section 6.31 should be extended for bitset/bitfield/bitmask from IDL4 (Building Block Extended Data-Types)

Bitset and Bitmask mapping

Bitsets and bitmasks are "top-level" IDL4 extended data types that can each be mapped to C++11.