[intro.compliance] - C++20 → C++23

Files changed (1) hide show

tmp/tmpq9apa0m1/{from.md → to.md} +37 -23

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

@@ -1,87 +1,101 @@
 ## Implementation compliance <a id="intro.compliance">[[intro.compliance]]</a>
 The set of *diagnosable rules* consists of all syntactic and semantic
 rules in this document except for those rules containing an explicit
 notation that “no diagnostic is required” or which are described as
 resulting in “undefined behavior”.
 Although this document states only requirements on C++ implementations,
 those requirements are often easier to understand if they are phrased as
 requirements on programs, parts of programs, or execution of programs.
 Such requirements have the following meaning:
-- If a program contains no violations of the rules in this document, a
-  conforming implementation shall, within its resource limits, accept
- and correctly execute[^2] that program.
-- If a program contains a violation of any diagnosable rule or an
-  occurrence of a construct described in this document as
-  “conditionally-supported” when the implementation does not support
-  that construct, a conforming implementation shall issue at least one
-  diagnostic message.
 - If a program contains a violation of a rule for which no diagnostic is
   required, this document places no requirement on implementations with
   respect to that program.
 [*Note 1*: During template argument deduction and substitution, certain
 constructs that in other contexts require a diagnostic are treated
 differently; see  [[temp.deduct]]. — *end note*]
 For classes and class templates, the library Clauses specify partial
 definitions. Private members [[class.access]] are not specified, but
 each implementation shall supply them to complete the definitions
 according to the description in the library Clauses.
 For functions, function templates, objects, and values, the library
 Clauses specify declarations. Implementations shall supply definitions
 consistent with the descriptions in the library Clauses.
-The names defined in the library have namespace scope
-[[basic.namespace]]. A C++ translation unit [[lex.phases]] obtains
-access to these names by including the appropriate standard library
 header or importing the appropriate standard library named header unit
 [[using.headers]].
 The templates, classes, functions, and objects in the library have
 external linkage [[basic.link]]. The implementation provides definitions
 for standard library entities, as necessary, while combining translation
 units to form a complete C++ program [[lex.phases]].
 Two kinds of implementations are defined: a *hosted implementation* and
-a *freestanding implementation*. For a hosted implementation, this
-document defines the set of available libraries. A freestanding
-implementation is one in which execution may take place without the
-benefit of an operating system, and has an *implementation-defined* set
-of libraries that includes certain language-support libraries
-[[compliance]].
 A conforming implementation may have extensions (including additional
 library functions), provided they do not alter the behavior of any
 well-formed program. Implementations are required to diagnose programs
 that use such extensions that are ill-formed according to this document.
 Having done so, however, they can compile and execute such programs.
 Each implementation shall include documentation that identifies all
 conditionally-supported constructs that it does not support and defines
-all locale-specific characteristics.[^3]
 ### Abstract machine <a id="intro.abstract">[[intro.abstract]]</a>
 The semantic descriptions in this document define a parameterized
 nondeterministic abstract machine. This document places no requirement
 on the structure of conforming implementations. In particular, they need
 not copy or emulate the structure of the abstract machine. Rather,
 conforming implementations are required to emulate (only) the observable
-behavior of the abstract machine as explained below.[^4]
 Certain aspects and operations of the abstract machine are described in
 this document as implementation-defined (for example, `sizeof(int)`).
 These constitute the parameters of the abstract machine. Each
 implementation shall include documentation describing its
-characteristics and behavior in these respects.[^5] Such documentation
-shall define the instance of the abstract machine that corresponds to
-that implementation (referred to as the “corresponding instance” below).
 Certain other aspects and operations of the abstract machine are
 described in this document as unspecified (for example, order of
 evaluation of arguments in a function call [[expr.call]]). Where
 possible, this document defines a set of allowable behaviors. These
@@ -117,7 +131,7 @@ The least requirements on a conforming implementation are:
 These collectively are referred to as the *observable behavior* of the
 program.
 [*Note 2*: More stringent correspondences between abstract and actual
-semantics may be defined by each implementation. — *end note*]

 ## Implementation compliance <a id="intro.compliance">[[intro.compliance]]</a>
+### General <a id="intro.compliance.general">[[intro.compliance.general]]</a>
 The set of *diagnosable rules* consists of all syntactic and semantic
 rules in this document except for those rules containing an explicit
 notation that “no diagnostic is required” or which are described as
 resulting in “undefined behavior”.
 Although this document states only requirements on C++ implementations,
 those requirements are often easier to understand if they are phrased as
 requirements on programs, parts of programs, or execution of programs.
 Such requirements have the following meaning:
+- If a program contains no violations of the rules in [[lex]] through
+ [[thread]] and [[depr]], a conforming implementation shall, within its
+ resource limits as described in [[implimits]], accept and correctly
+  execute[^3] that program.
 - If a program contains a violation of a rule for which no diagnostic is
   required, this document places no requirement on implementations with
   respect to that program.
+- Otherwise, if a program contains a violation of any diagnosable rule
+  or an occurrence of a construct described in this document as
+  “conditionally-supported” when the implementation does not support
+  that construct, a conforming implementation shall issue at least one
+  diagnostic message.
 [*Note 1*: During template argument deduction and substitution, certain
 constructs that in other contexts require a diagnostic are treated
 differently; see  [[temp.deduct]]. — *end note*]
+Furthermore, a conforming implementation
+- shall not accept a preprocessing translation unit containing a
+  `#error` preprocessing directive [[cpp.error]],
+- shall issue at least one diagnostic message for each `#warning` or
+  `#error` preprocessing directive not following a `#error`
+  preprocessing directive in a preprocessing translation unit, and
+- shall not accept a translation unit with a *static_assert-declaration*
+  that fails [[dcl.pre]].
 For classes and class templates, the library Clauses specify partial
 definitions. Private members [[class.access]] are not specified, but
 each implementation shall supply them to complete the definitions
 according to the description in the library Clauses.
 For functions, function templates, objects, and values, the library
 Clauses specify declarations. Implementations shall supply definitions
 consistent with the descriptions in the library Clauses.
+A C++ translation unit [[lex.phases]] obtains access to the names
+defined in the library by including the appropriate standard library
 header or importing the appropriate standard library named header unit
 [[using.headers]].
 The templates, classes, functions, and objects in the library have
 external linkage [[basic.link]]. The implementation provides definitions
 for standard library entities, as necessary, while combining translation
 units to form a complete C++ program [[lex.phases]].
 Two kinds of implementations are defined: a *hosted implementation* and
+a *freestanding implementation*. A freestanding implementation is one in
+which execution may take place without the benefit of an operating
+system. A hosted implementation supports all the facilities described in
+this document, while a freestanding implementation supports the entire
+C++ language described in [[lex]] through [[cpp]] and the subset of the
+library facilities described in [[compliance]].
 A conforming implementation may have extensions (including additional
 library functions), provided they do not alter the behavior of any
 well-formed program. Implementations are required to diagnose programs
 that use such extensions that are ill-formed according to this document.
 Having done so, however, they can compile and execute such programs.
 Each implementation shall include documentation that identifies all
 conditionally-supported constructs that it does not support and defines
+all locale-specific characteristics.[^4]
 ### Abstract machine <a id="intro.abstract">[[intro.abstract]]</a>
 The semantic descriptions in this document define a parameterized
 nondeterministic abstract machine. This document places no requirement
 on the structure of conforming implementations. In particular, they need
 not copy or emulate the structure of the abstract machine. Rather,
 conforming implementations are required to emulate (only) the observable
+behavior of the abstract machine as explained below.[^5]
 Certain aspects and operations of the abstract machine are described in
 this document as implementation-defined (for example, `sizeof(int)`).
 These constitute the parameters of the abstract machine. Each
 implementation shall include documentation describing its
+characteristics and behavior in these respects.[^6]
+Such documentation shall define the instance of the abstract machine
+that corresponds to that implementation (referred to as the
+“corresponding instance” below).
 Certain other aspects and operations of the abstract machine are
 described in this document as unspecified (for example, order of
 evaluation of arguments in a function call [[expr.call]]). Where
 possible, this document defines a set of allowable behaviors. These
 These collectively are referred to as the *observable behavior* of the
 program.
 [*Note 2*: More stringent correspondences between abstract and actual
+semantics can be defined by each implementation. — *end note*]

Diff to HTML by rtfpessoa