tmp/tmpiy2hij8l/{from.md → to.md}
RENAMED
|
@@ -31,10 +31,18 @@ original feature:** Change to semantics of well-defined feature.
|
|
| 31 |
Semantic transformation. If the hidden name that needs to be accessed is
|
| 32 |
at global scope, the `::` C++operator can be used. If the hidden name is
|
| 33 |
at block scope, either the type or the struct tag has to be renamed.
|
| 34 |
Seldom.
|
| 35 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 36 |
[[class.nest]] **Change:** In C++, the name of a nested class is local
|
| 37 |
to its enclosing class. In C the name of the nested class belongs to the
|
| 38 |
same scope as the name of the outermost enclosing class.
|
| 39 |
|
| 40 |
Example:
|
|
|
|
| 31 |
Semantic transformation. If the hidden name that needs to be accessed is
|
| 32 |
at global scope, the `::` C++operator can be used. If the hidden name is
|
| 33 |
at block scope, either the type or the struct tag has to be renamed.
|
| 34 |
Seldom.
|
| 35 |
|
| 36 |
+
[[class.bit]] **Change:** Bit-fields of type plain `int` are signed.
|
| 37 |
+
**Rationale:** Leaving the choice of signedness to implementations could
|
| 38 |
+
lead to inconsistent definitions of template specializations. For
|
| 39 |
+
consistency, the implementation freedom was eliminated for non-dependent
|
| 40 |
+
types, too. **Effect on original feature:** The choise is
|
| 41 |
+
implementation-defined in C, but not so in C++. Syntactic
|
| 42 |
+
transformation. Seldom.
|
| 43 |
+
|
| 44 |
[[class.nest]] **Change:** In C++, the name of a nested class is local
|
| 45 |
to its enclosing class. In C the name of the nested class belongs to the
|
| 46 |
same scope as the name of the outermost enclosing class.
|
| 47 |
|
| 48 |
Example:
|