C++11 introduced the "using" keyword (see https://en.cppreference.com/w/cpp/language/type_alias) as alternative way to specify a type alias. In terms of C++11 support usage it would be a good thing to update all example C++11 code within the specification to use "using" instead of "typedef"

Use the C++11 type alias feature in examples

C++11 has type aliasing with the "using" keyword, which is typically preferred to using the "typedef" syntax inherited from C.

The current IDL to C++11 language mapping only describes an inheritance based interface implementation in chapter 6.26.6. The IDL to C++ language mapping also described a delegation based implementation. We propose to add a delegation based implementation to the IDL to C++11 specification.

I will attach a proposal new chapter 6.26.7, only the formatting of IDL and C++ types has to be done in the final document, especially types in the text itself need to be formatted. In the first paragraph there is a number 126, that has to be updated.

Mapping for implementing interfaces via delegation

This issue adds the mapping for implementing interfaces via delegation, a feature of the IDL-to-C++ mapping that has been lacking in this spec.

The C++11 mapping of an IDL union seems to follow that of the classic C++ mapping, where the discriminator does not only have a getter-operation, but also a setter operation. This operation has been added for situations where more than one case label applies to to the same union branch, and the setter operation for that union branch implicitly sets the discriminant value to the first case label that was specified. If you want to pick another value, you should do so by invoking the setter function for the discriminant.

However, this setter operation is confusing to many users, and some seem to think you need to use it every time you passed a value into a branch different than the current branch. On top of that. it seems cumbersome to have to make two separate method invocations to request a single modification that is intended to set branch value and corresponding discriminator value atomically.

Much better would be to take the route that has been adopted in the Java language mapping for the union: if there is more than one case label that applies to a union branch, you add an overloaded setter method for that branch that does not only allow you to pass the value for that branch, but also the value for the discriminator. This overloaded setter function will than validate whether the discriminant value you pass actually applies to the branch that you are trying to set.

Unions: Provide a way to set both the discriminator and value at the same time

Enhance the mapping of IDL union to allow setting the discriminator at the same time a new union element value is provided. This change maintains compatibility for applications written to the current spec version.

Compared to V1.2 in 6.7.6 four bullets before IDL::traits<A>::narrow(ap) got removed

Make part of 6.7.6 a bulleted list

This was somehow lost between v1.2 and v1.3.

The OBV_Example constructor has multiple arguments and shouldn't be explicit. Also a closing ) is lacking from the example code. The operations for val2 should also use "override"

Update OBV_Example class in 6.18.4

Updates as suggested, making the C++ example code consistent with the prose of 6.18.2 and common conventions.

The operation "virtual int16_6& val1() = 0;" is not aligned correctly in the code example

Fix C++ code in 6.18.4

Fixing a minor typo/formatting bug in this section.

Section 6.11 on page 11, 2nd paragraph:

Implementations of the bounded wide string are under no oblication to perform a bounds check [...]

obligation

Table 6.10 on page 14, bottom row, right column

dimensions

std::integral_constant type of value_type uint32_t indicating the number of dimensaions of the array

[...] dimensions of the array

Section 6.18.7.2 page 30 top, continuation of code from p.29

protected:
      ColorValue();
      xplicit ColorValue(Color);

explicit ColorValue(Color);

Section 6.19.1 on page 34, code for class AbstractBase

class AbstractBase {
      public:
            virtual IDL::traits<Object>::ref_type _to_object();
            virtual IDL::traits<ValueBase>::ref_type _to_value();
      protected:
            AbstractBase();
            bstractBase(const AbstractBase&);

AbstractBase(const AbstractBase&);

Section 6.22.2 on page 40 top (code continued from p.39)

            int16_t fixed_scale() const;
            Visibility member_visibility(uin32_t index) const;

Type of index argument should be uint32_t.

Fix typos

The submitted issue (CPP1114-7) lists a few other typos, but those are already fixed in formal/18-01-06.

For struct/exception/valuetype the spec describes that a constructor accepting values for all members has to generated as explicit constructor, but it only has to be explicit when there is one (1) member, when there are >1 member the constructor doesn't need to be explicit. This has to be updated in the text and examples

Reporter of the Issue has asked for it to be withdrawn

Closing this one by request of Reporter.

Reduce the indent of public, should start on the first line, makes it all more readable

Update source code formatting

Remove extra indenting that can force line wrapping and make embedded source code hard to read.

There are tabs between bool and the method names, they should be removed

Update code in 6.26.2

Minor formatting change as suggested.