[class.mem] - C++11 → C++14

Files changed (1) hide show

tmp/tmp4t09y4e6/{from.md → to.md} +32 -33

tmp/tmp4t09y4e6/{from.md → to.md} RENAMED Viewed

@@ -7,15 +7,16 @@ member-specification:
 ```
 ``` bnf
 member-declaration:
     attribute-specifier-seqₒₚₜ decl-specifier-seqₒₚₜ member-declarator-listₒₚₜ ';'
-    function-definition ';'ₒₚₜ
     using-declaration
     static_assert-declaration
     template-declaration
     alias-declaration
 ```
 ``` bnf
 member-declarator-list:
     member-declarator
@@ -53,39 +54,37 @@ types, and enumerators. Data members and member functions are static or
 non-static; see  [[class.static]]. Nested types are classes (
 [[class.name]],  [[class.nest]]) and enumerations ([[dcl.enum]])
 defined in the class, and arbitrary types declared as members by use of
 a typedef declaration ([[dcl.typedef]]). The enumerators of an unscoped
 enumeration ([[dcl.enum]]) defined in the class are members of the
-class. Except when used to declare friends ([[class.friend]]) or to
-introduce the name of a member of a base class into a derived class (
-[[namespace.udecl]]), *member-declaration*s declare members of the
-class, and each such *member-declaration* shall declare at least one
-member name of the class. A member shall not be declared twice in the
-*member-specification*, except that a nested class or member class
-template can be declared and then later defined, and except that an
-enumeration can be introduced with an *opaque-enum-declaration* and
-later redeclared with an *enum-specifier*.
 A class is considered a completely-defined object type (
 [[basic.types]]) (or complete type) at the closing `}` of the
 *class-specifier*. Within the class *member-specification*, the class is
 regarded as complete within function bodies, default arguments,
-*exception-specification*s, and *brace-or-equal-initializer*s for
-non-static data members (including such things in nested classes).
-Otherwise it is regarded as incomplete within its own class
-*member-specification*.
 A single name can denote several function members provided their types
 are sufficiently different (Clause  [[over]]).
-A member can be initialized using a constructor; see  [[class.ctor]].
-See Clause  [[special]] for a description of constructors and other
-special member functions.
-A member can be initialized using a *brace-or-equal-initializer*. (For
-static data members, see  [[class.static.data]]; for non-static data
-members, see  [[class.base.init]]).
 A member shall not be declared with the `extern` or `register` . Within
 a class definition, a member shall not be declared with the
 `thread_local` unless also declared `static`.
@@ -143,14 +142,14 @@ pointer of the object `s`; and `s.right->tword[0]` refers to the initial
 character of the `tword` member of the `right` subtree of `s`.
 Nonstatic data members of a (non-union) class with the same access
 control (Clause  [[class.access]]) are allocated so that later members
 have higher addresses within a class object. The order of allocation of
-non-static data members with different access control is unspecified (
-[[class.access]]). Implementation alignment requirements might cause two
-adjacent members not to be allocated immediately after each other; so
-might requirements for space for managing virtual functions (
 [[class.virtual]]) and virtual base classes ([[class.mi]]).
 If `T` is the name of a class, then each of the following shall have a
 name different from `T`:
@@ -165,16 +164,16 @@ name different from `T`:
 In addition, if class `T` has a user-declared constructor (
 [[class.ctor]]), every non-static data member of class `T` shall have a
 name different from `T`.
 Two standard-layout struct (Clause  [[class]]) types are
-layout-compatible if they have the same number of non-static data
 members and corresponding non-static data members (in declaration order)
 have layout-compatible types ([[basic.types]]).
 Two standard-layout union (Clause  [[class]]) types are
-layout-compatible if they have the same number of non-static data
 members and corresponding non-static data members (in any order) have
 layout-compatible types ([[basic.types]]).
 If a standard-layout union contains two or more standard-layout structs
 that share a common initial sequence, and if the standard-layout union
@@ -183,12 +182,12 @@ permitted to inspect the common initial part of any of them. Two
 standard-layout structs share a common initial sequence if corresponding
 members have layout-compatible types and either neither member is a
 bit-field or both are bit-fields with the same width for a sequence of
 one or more initial members.
-A pointer to a standard-layout struct object, suitably converted using a
-`reinterpret_cast`, points to its initial member (or if that member is a
-bit-field, then to the unit in which it resides) and vice versa. There
-might therefore be unnamed padding within a standard-layout struct
-object, but not at its beginning, as necessary to achieve appropriate
-alignment.

 ```
 ``` bnf
 member-declaration:
     attribute-specifier-seqₒₚₜ decl-specifier-seqₒₚₜ member-declarator-listₒₚₜ ';'
+    function-definition
     using-declaration
     static_assert-declaration
     template-declaration
     alias-declaration
+    empty-declaration
 ```
 ``` bnf
 member-declarator-list:
     member-declarator
 non-static; see  [[class.static]]. Nested types are classes (
 [[class.name]],  [[class.nest]]) and enumerations ([[dcl.enum]])
 defined in the class, and arbitrary types declared as members by use of
 a typedef declaration ([[dcl.typedef]]). The enumerators of an unscoped
 enumeration ([[dcl.enum]]) defined in the class are members of the
+class. Except when used to declare friends ([[class.friend]]), to
+declare an unnamed bit-field ([[class.bit]]), or to introduce the name
+of a member of a base class into a derived class ([[namespace.udecl]]),
+or when the declaration is an *empty-declaration*, *member-declaration*s
+declare members of the class, and each such *member-declaration* shall
+declare at least one member name of the class. A member shall not be
+declared twice in the *member-specification*, except that a nested class
+or member class template can be declared and then later defined, and
+except that an enumeration can be introduced with an
+*opaque-enum-declaration* and later redeclared with an *enum-specifier*.
 A class is considered a completely-defined object type (
 [[basic.types]]) (or complete type) at the closing `}` of the
 *class-specifier*. Within the class *member-specification*, the class is
 regarded as complete within function bodies, default arguments,
+*using-declaration*s introducing inheriting constructors (
+[[class.inhctor]]), *exception-specification*s, and
+*brace-or-equal-initializer*s for non-static data members (including
+such things in nested classes). Otherwise it is regarded as incomplete
+within its own class *member-specification*.
 A single name can denote several function members provided their types
 are sufficiently different (Clause  [[over]]).
+A *brace-or-equal-initializer* shall appear only in the declaration of a
+data member. (For static data members, see  [[class.static.data]]; for
+non-static data members, see  [[class.base.init]]).
 A member shall not be declared with the `extern` or `register` . Within
 a class definition, a member shall not be declared with the
 `thread_local` unless also declared `static`.
 character of the `tword` member of the `right` subtree of `s`.
 Nonstatic data members of a (non-union) class with the same access
 control (Clause  [[class.access]]) are allocated so that later members
 have higher addresses within a class object. The order of allocation of
+non-static data members with different access control is unspecified
+(Clause  [[class.access]]). Implementation alignment requirements might
+cause two adjacent members not to be allocated immediately after each
+other; so might requirements for space for managing virtual functions (
 [[class.virtual]]) and virtual base classes ([[class.mi]]).
 If `T` is the name of a class, then each of the following shall have a
 name different from `T`:
 In addition, if class `T` has a user-declared constructor (
 [[class.ctor]]), every non-static data member of class `T` shall have a
 name different from `T`.
 Two standard-layout struct (Clause  [[class]]) types are
+*layout-compatible* if they have the same number of non-static data
 members and corresponding non-static data members (in declaration order)
 have layout-compatible types ([[basic.types]]).
 Two standard-layout union (Clause  [[class]]) types are
+*layout-compatible* if they have the same number of non-static data
 members and corresponding non-static data members (in any order) have
 layout-compatible types ([[basic.types]]).
 If a standard-layout union contains two or more standard-layout structs
 that share a common initial sequence, and if the standard-layout union
 standard-layout structs share a common initial sequence if corresponding
 members have layout-compatible types and either neither member is a
 bit-field or both are bit-fields with the same width for a sequence of
 one or more initial members.
+If a standard-layout class object has any non-static data members, its
+address is the same as the address of its first non-static data member.
+Otherwise, its address is the same as the address of its first base
+class subobject (if any). There might therefore be unnamed padding
+within a standard-layout struct object, but not at its beginning, as
+necessary to achieve appropriate alignment.

Diff to HTML by rtfpessoa