From 00d583e6544ea4d2955e120555fbdcd3c7d7da47 Mon Sep 17 00:00:00 2001 From: Pragmatic Software Date: Mon, 8 Aug 2022 13:14:05 -0700 Subject: [PATCH] applets: Linkify section identifiers in n{1256,1570}.html --- applets/n1256.html | 16302 +++++++++++++-------------------- applets/n1570.html | 21035 ++++++++++++++++--------------------------- 2 files changed, 14094 insertions(+), 23243 deletions(-) diff --git a/applets/n1256.html b/applets/n1256.html index 5e8ea60c..a9a37074 100644 --- a/applets/n1256.html +++ b/applets/n1256.html @@ -1,12 +1,10 @@

ISO/IEC 9899:TC3 Committee Draft September 7, 2007 WG14/N1256

- +

FOREWORD. [Foreword]

-

-
-
+
 
1   ISO (the International Organization for Standardization) and IEC (the International
     Electrotechnical Commission) form the specialized system for worldwide
     standardization. National bodies that are member of ISO or IEC participate in the
@@ -16,20 +14,17 @@
     organizations, governmental and non-governmental, in liaison with ISO and IEC, also
     take part in the work.
 

-
-
+
 
2   International Standards are drafted in accordance with the rules given in the ISO/IEC
     Directives, Part 3.
 

-
-
+
 
3   In the field of information technology, ISO and IEC have established a joint technical
     committee, ISO/IEC JTC 1. Draft International Standards adopted by the joint technical
     committee are circulated to national bodies for voting. Publication as an International
     Standard requires approval by at least 75% of the national bodies casting a vote.
 

-
-
+
 
4   International Standard ISO/IEC 9899 was prepared by Joint Technical Committee
     ISO/IEC JTC 1, Information technology , Subcommittee SC 22, Programming languages,
     their environments and system software interfaces. The Working Group responsible for
@@ -38,8 +33,7 @@
     information relevant to this standard such as a Rationale for many of the decisions made
     during its preparation and a log of Defect Reports and Responses.
 

-
-
+
 
5   This second edition cancels and replaces the first edition, ISO/IEC 9899:1990, as
     amended and corrected by ISO/IEC 9899/COR1:1994, ISO/IEC 9899/AMD1:1995, and
     ISO/IEC 9899/COR2:1996. Major changes from the previous edition include:
@@ -102,43 +96,36 @@
     -- return without expression not permitted in function that returns a value (and vice
        versa)
 

-
-
+
 
6   Annexes D and F form a normative part of this standard; annexes A, B, C, E, G, H, I, J,
     the bibliography, and the index are for information only. In accordance with Part 3 of the
     ISO/IEC Directives, this foreword, the introduction, notes, footnotes, and examples are
     also for information only.
 
 

-
-
+
 

 
INTRODUCTION. [Introduction]

-

-
-
+
 
1   With the introduction of new devices and extended character sets, new features may be
     added to this International Standard. Subclauses in the language and library clauses warn
     implementors and programmers of usages which, though valid in themselves, may
     conflict with future additions.
 

-
-
+
 
2   Certain features are obsolescent , which means that they may be considered for
     withdrawal in future revisions of this International Standard. They are retained because
     of their widespread use, but their use in new implementations (for implementation
-    features) or new programs (for language [6.11] or library features [7.26]) is discouraged.
+    features) or new programs (for language [6.11] or library features [7.26]) is discouraged.
 

-
-
+
 
3   This International Standard is divided into four major subdivisions:
     -- preliminary elements (clauses 1-4);
     -- the characteristics of environments that translate and execute C programs (clause 5);
     -- the language syntax, constraints, and semantics (clause 6);
     -- the library facilities (clause 7).
 

-
-
+
 
4   Examples are provided to illustrate possible forms of the constructions described.
     Footnotes are provided to emphasize consequences of the rules described in that
     subclause or elsewhere in this International Standard. References are used to refer to
@@ -147,26 +134,21 @@
     contained in this International Standard. A bibliography lists documents that were
     referred to during the preparation of the standard.
 

-
-
+
 
5   The language clause (clause 6) is derived from ``The C Reference Manual''.
 

-
-
+
 
6   The library clause (clause 7) is based on the 1984 /usr/group Standard .
     xiv                                     Introduction
-    INTERNATIONAL STANDARD                                ©ISO/IEC                  ISO/IEC 9899:TC3
+    INTERNATIONAL STANDARD                                \xA9ISO/IEC                  ISO/IEC 9899:TC3
     Programming languages -- C
 

-
-
+
 

 
1. [Scope]

-

-
-
+
 
1   This International Standard specifies the form and establishes the interpretation of
-    programs written in the C programming language.1) It specifies
+    programs written in the C programming language.[1] It specifies
     -- the representation of C programs;
     -- the syntax and constraints of the C language;
     -- the semantic rules for interpreting C programs;
@@ -174,13 +156,14 @@
     -- the representation of output data produced by C programs;
     -- the restrictions and limits imposed by a conforming implementation of C.
 

-
 
 
Footnote 1) This International Standard is designed to promote the portability of C programs among a variety of
          data-processing systems. It is intended for use by implementors and programmers.
+    -- all minimal requirements of a data-processing system that is capable of supporting a
+       conforming implementation.
 

 
-
+
 
2   This International Standard does not specify
     -- the mechanism by which C programs are transformed for use by a data-processing
        system;
@@ -191,17 +174,12 @@
        program;
     -- the size or complexity of a program and its data that will exceed the capacity of any
        specific data-processing system or the capacity of a particular processor;
-    -- all minimal requirements of a data-processing system that is capable of supporting a
-       conforming implementation.
 
 

-
-
+
 

 
2. [Normative references]

-

-
-
+
 
1   The following normative documents contain provisions which, through reference in this
     text, constitute provisions of this International Standard. For dated references,
     subsequent amendments to, or revisions of, any of these publications do not apply.
@@ -211,47 +189,37 @@
     document referred to applies. Members of ISO and IEC maintain registers of currently
     valid International Standards.
 

-
-
+
 
2   ISO 31-11:1992, Quantities and units -- Part 11: Mathematical signs and symbols for
     use in the physical sciences and technology .
 

-
-
+
 
3   ISO/IEC 646, Information technology -- ISO 7-bit coded character set for information
     interchange.
 

-
-
+
 
4   ISO/IEC 2382-1:1993, Information technology -- Vocabulary -- Part 1: Fundamental
     terms.
 

-
-
+
 
5   ISO 4217, Codes for the representation of currencies and funds.
 

-
-
+
 
6   ISO 8601, Data elements and interchange formats -- Information interchange --
     Representation of dates and times.
 

-
-
+
 
7   ISO/IEC 10646 (all parts), Information technology -- Universal Multiple-Octet Coded
     Character Set (UCS).
 

-
-
+
 
8   IEC 60559:1989, Binary floating-point arithmetic for microprocessor systems (previously
     designated IEC 559:1989).
 

-
-
+
 

 
3. [Terms, definitions, and symbols]

-

-
-
+
 
1   For the purposes of this International Standard, the following definitions apply. Other
     terms are defined where they appear in italic type or on the left side of a syntax rule.
     Terms explicitly defined in this International Standard are not to be presumed to refer
@@ -259,49 +227,37 @@
     Standard are to be interpreted according to ISO/IEC 2382-1. Mathematical symbols not
     defined in this International Standard are to be interpreted according to ISO 31-11.
 

-
-
+
 

 
3.1 [Terms, definitions, and symbols]

-

-
-
+
 
1   access
     execution-time action to read or modify the value of an object
 

-
-
+
 
2   NOTE 1   Where only one of these two actions is meant, ``read'' or ``modify'' is used.
 
 

-
-
+
 
3   NOTE 2   "Modify'' includes the case where the new value being stored is the same as the previous value.
 
 

-
-
+
 
4   NOTE 3   Expressions that are not evaluated do not access objects.
 
 

-
-
+
 

 
3.2 [Terms, definitions, and symbols]

-

-
-
+
 
1   alignment
     requirement that objects of a particular type be located on storage boundaries with
     addresses that are particular multiples of a byte address
 

-
-
+
 

 
3.3 [Terms, definitions, and symbols]

-

-
-
+
 
1   argument
     actual argument
     actual parameter (deprecated)
@@ -309,268 +265,201 @@
     expression, or a sequence of preprocessing tokens in the comma-separated list bounded
     by the parentheses in a function-like macro invocation
 

-
-
+
 

 
3.4 [Terms, definitions, and symbols]

-

-
-
+
 
1   behavior
     external appearance or action
 

-
-
+
 

 
3.4.1 [Terms, definitions, and symbols]

-

-
-
+
 
1   implementation-defined behavior
     unspecified behavior where each implementation documents how the choice is made
 

-
-
+
 
2   EXAMPLE An example of implementation-defined behavior is the propagation of the high-order bit
     when a signed integer is shifted right.
 
 

-
-
+
 

 
3.4.2 [Terms, definitions, and symbols]

-

-
-
+
 
1   locale-specific behavior
     behavior that depends on local conventions of nationality, culture, and language that each
     implementation documents
 

-
-
+
 
2   EXAMPLE An example of locale-specific behavior is whether the islower function returns true for
     characters other than the 26 lowercase Latin letters.
 
 

-
-
+
 

 
3.4.3 [Terms, definitions, and symbols]

-

-
-
+
 
1   undefined behavior
     behavior, upon use of a nonportable or erroneous program construct or of erroneous data,
     for which this International Standard imposes no requirements
 

-
-
+
 
2   NOTE Possible undefined behavior ranges from ignoring the situation completely with unpredictable
     results, to behaving during translation or program execution in a documented manner characteristic of the
     environment (with or without the issuance of a diagnostic message), to terminating a translation or
     execution (with the issuance of a diagnostic message).
 
 

-
-
+
 
3   EXAMPLE        An example of undefined behavior is the behavior on integer overflow.
 
 

-
-
+
 

 
3.4.4 [Terms, definitions, and symbols]

-

-
-
+
 
1   unspecified behavior
     use of an unspecified value, or other behavior where this International Standard provides
     two or more possibilities and imposes no further requirements on which is chosen in any
     instance
 

-
-
+
 
2   EXAMPLE        An example of unspecified behavior is the order in which the arguments to a function are
     evaluated.
 
 

-
-
+
 

 
3.5 [Terms, definitions, and symbols]

-

-
-
+
 
1   bit
     unit of data storage in the execution environment large enough to hold an object that may
     have one of two values
 

-
-
+
 
2   NOTE      It need not be possible to express the address of each individual bit of an object.
 
 

-
-
+
 

 
3.6 [Terms, definitions, and symbols]

-

-
-
+
 
1   byte
     addressable unit of data storage large enough to hold any member of the basic character
     set of the execution environment
 

-
-
+
 
2   NOTE 1     It is possible to express the address of each individual byte of an object uniquely.
 
 

-
-
+
 
3   NOTE 2 A byte is composed of a contiguous sequence of bits, the number of which is implementation-
     defined. The least significant bit is called the low-order bit ; the most significant bit is called the high-order
     bit .
 
 

-
-
+
 

 
3.7 [Terms, definitions, and symbols]

-

-
-
+
 
1   character
     abstract member of a set of elements used for the organization, control, or
     representation of data
 

-
-
+
 

 
3.7.1 [Terms, definitions, and symbols]

-

-
-
+
 
1   character
     single-byte character
     C bit representation that fits in a byte
 

-
-
+
 

 
3.7.2 [Terms, definitions, and symbols]

-

-
-
+
 
1   multibyte character
     sequence of one or more bytes representing a member of the extended character set of
     either the source or the execution environment
 

-
-
+
 
2   NOTE    The extended character set is a superset of the basic character set.
 
 

-
-
+
 

 
3.7.3 [Terms, definitions, and symbols]

-

-
-
+
 
1   wide character
     bit representation that fits in an object of type wchar_t, capable of representing any
     character in the current locale
 

-
-
+
 

 
3.8 [Terms, definitions, and symbols]

-

-
-
+
 
1   constraint
     restriction, either syntactic or semantic, by which the exposition of language elements is
     to be interpreted
 

-
-
+
 

 
3.9 [Terms, definitions, and symbols]

-

-
-
+
 
1   correctly rounded result
     representation in the result format that is nearest in value, subject to the current rounding
     mode, to what the result would be given unlimited range and precision
 

-
-
+
 

 
3.10 [Terms, definitions, and symbols]

-

-
-
+
 
1   diagnostic message
     message belonging to an implementation-defined subset of the implementation's message
     output
 

-
-
+
 

 
3.11 [Terms, definitions, and symbols]

-

-
-
+
 
1   forward reference
     reference to a later subclause of this International Standard that contains additional
     information relevant to this subclause
 

-
-
+
 

 
3.12 [Terms, definitions, and symbols]

-

-
-
+
 
1   implementation
     particular set of software, running in a particular translation environment under particular
     control options, that performs translation of programs for, and supports execution of
     functions in, a particular execution environment
 

-
-
+
 

 
3.13 [Terms, definitions, and symbols]

-

-
-
+
 
1   implementation limit
     restriction imposed upon programs by the implementation
 

-
-
+
 

 
3.14 [Terms, definitions, and symbols]

-

-
-
+
 
1   object
     region of data storage in the execution environment, the contents of which can represent
     values
 

-
-
-
2   NOTE     When referenced, an object may be interpreted as having a particular type; see 6.3.2.1.
+
+
2   NOTE     When referenced, an object may be interpreted as having a particular type; see 6.3.2.1.
 
 

-
-
+
 

 
3.15 [Terms, definitions, and symbols]

-

-
-
+
 
1   parameter
     formal parameter
     formal argument (deprecated)
@@ -578,130 +467,98 @@
     entry to the function, or an identifier from the comma-separated list bounded by the
     parentheses immediately following the macro name in a function-like macro definition
 

-
-
+
 

 
3.16 [Terms, definitions, and symbols]

-

-
-
+
 
1   recommended practice
     specification that is strongly recommended as being in keeping with the intent of the
     standard, but that may be impractical for some implementations
 

-
-
+
 

 
3.17 [Terms, definitions, and symbols]

-

-
-
+
 
1   value
     precise meaning of the contents of an object when interpreted as having a specific type
 

-
-
+
 

 
3.17.1 [Terms, definitions, and symbols]

-

-
-
+
 
1   implementation-defined value
     unspecified value where each implementation documents how the choice is made
 

-
-
+
 

 
3.17.2 [Terms, definitions, and symbols]

-

-
-
+
 
1   indeterminate value
     either an unspecified value or a trap representation
 

-
-
+
 

 
3.17.3 [Terms, definitions, and symbols]

-

-
-
+
 
1   unspecified value
     valid value of the relevant type where this International Standard imposes no
     requirements on which value is chosen in any instance
 

-
-
+
 
2   NOTE     An unspecified value cannot be a trap representation.
 
 

-
-
+
 

 
3.18 [Terms, definitions, and symbols]

-

-
-
+
 
1    x
     ceiling of x : the least integer greater than or equal to x
 

-
-
+
 
2   EXAMPLE       2. 4 is 3, -2. 4 is -2.
 
 

-
-
+
 

 
3.19 [Terms, definitions, and symbols]

-

-
-
+
 
1    x
     floor of x : the greatest integer less than or equal to x
 

-
-
+
 
2   EXAMPLE       2. 4 is 2, -2. 4 is -3.
 

-
-
+
 

 
4. [Conformance]

-

-
-
+
 
1   In this International Standard, ``shall'' is to be interpreted as a requirement on an
     implementation or on a program; conversely, ``shall not'' is to be interpreted as a
     prohibition.
 

-
-
+
 
2   If a ``shall'' or ``shall not'' requirement that appears outside of a constraint is violated, the
     behavior is undefined. Undefined behavior is otherwise indicated in this International
     Standard by the words ``undefined behavior'' or by the omission of any explicit definition
     of behavior. There is no difference in emphasis among these three; they all describe
     ``behavior that is undefined''.
 

-
-
+
 
3   A program that is correct in all other aspects, operating on correct data, containing
-    unspecified behavior shall be a correct program and act in accordance with 5.1.2.3.
+    unspecified behavior shall be a correct program and act in accordance with 5.1.2.3.
 

-
-
+
 
4   The implementation shall not successfully translate a preprocessing translation unit
     containing a #error preprocessing directive unless it is part of a group skipped by
     conditional inclusion.
 

-
-
+
 
5   A strictly conforming program shall use only those features of the language and library
-    specified in this International Standard.2) It shall not produce output dependent on any
+    specified in this International Standard.[2] It shall not produce output dependent on any
     unspecified, undefined, or implementation-defined behavior, and shall not exceed any
     minimum implementation limit.
 

-
 
 
Footnote 2) A strictly conforming program can use conditional features (such as those in annex F) provided the
          use is guarded by a #ifdef directive with the appropriate macro. For example:
@@ -712,7 +569,7 @@
                  #endif
 

 
-
+
 
6   The two forms of conforming implementation are hosted and freestanding. A conforming
     hosted implementation shall accept any strictly conforming program. A conforming
     freestanding implementation shall accept any strictly conforming program that does not
@@ -721,40 +578,35 @@
     <iso646.h>, <limits.h>, <stdarg.h>, <stdbool.h>, <stddef.h>, and
     <stdint.h>. A conforming implementation may have extensions (including additional
     library functions), provided they do not alter the behavior of any strictly conforming
-    program.3)
+    program.[3]
 

-
 
 
Footnote 3) This implies that a conforming implementation reserves no identifiers other than those explicitly
          reserved in this International Standard.
 

 
-
-
7   A conforming program is one that is acceptable to a conforming implementation.4)
+
+
7   A conforming program is one that is acceptable to a conforming implementation.[4]
 

-
 
 
Footnote 4) Strictly conforming programs are intended to be maximally portable among conforming
          implementations. Conforming programs may depend upon nonportable features of a conforming
          implementation.
 

 
-
+
 
8   An implementation shall be accompanied by a document that defines all implementation-
     defined and locale-specific characteristics and all extensions.
-    Forward references: conditional inclusion (6.10.1), error directive (6.10.5),
-    characteristics of floating types <float.h> (7.7), alternative spellings <iso646.h>
-    (7.9), sizes of integer types <limits.h> (7.10), variable arguments <stdarg.h>
-    (7.15), boolean type and values <stdbool.h> (7.16), common definitions
-    <stddef.h> (7.17), integer types <stdint.h> (7.18).
+    Forward references: conditional inclusion (6.10.1), error directive (6.10.5),
+    characteristics of floating types <float.h> (7.7), alternative spellings <iso646.h>
+    (7.9), sizes of integer types <limits.h> (7.10), variable arguments <stdarg.h>
+    (7.15), boolean type and values <stdbool.h> (7.16), common definitions
+    <stddef.h> (7.17), integer types <stdint.h> (7.18).
 

-
-
+
 

 
5. [Environment]

-

-
-
+
 
1   An implementation translates C source files and executes C programs in two data-
     processing-system environments, which will be called the translation environment and
     the execution environment in this International Standard. Their characteristics define and
@@ -763,25 +615,16 @@
     Forward references: In this clause, only a few of many possible forward references
     have been noted.
 

-
-
+
 

 
5.1 [Conceptual models]

-
 Conceptual models
-

-
-
+
 

 
5.1.1 [Translation environment]

-
 Translation environment
-

-
-
+
 

 
5.1.1.1 [Program structure]

-

-
-
+
 
1   A C program need not all be translated at the same time. The text of the program is kept
     in units called source files, (or preprocessing files) in this International Standard. A
     source file together with all the headers and source files included via the preprocessing
@@ -792,22 +635,26 @@
     linkage, manipulation of objects whose identifiers have external linkage, or manipulation
     of data files. Translation units may be separately translated and then later linked to
     produce an executable program.
-    Forward references: linkages of identifiers (6.2.2), external definitions (6.9),
-    preprocessing directives (6.10).
+    Forward references: linkages of identifiers (6.2.2), external definitions (6.9),
+    preprocessing directives (6.10).
 

-
-
+
 

 
5.1.1.2 [Translation phases]

-

-
-
+
 
1   The precedence among the syntax rules of translation is specified by the following
-    phases.5)
+    phases.[5]
          1.   Physical source file multibyte characters are mapped, in an implementation-
               defined manner, to the source character set (introducing new-line characters for
               end-of-line indicators) if necessary. Trigraph sequences are replaced by
               corresponding single-character internal representations.
+

+
+
Footnote 5) Implementations shall behave as if these separate phases occur, even though many are typically folded
+          together in practice. Source files, translation units, and translated translation units need not
+          necessarily be stored as files, nor need there be any one-to-one correspondence between these entities
+          and any external representation. The description is conceptual only, and does not specify any
+          particular implementation.
      2.   Each instance of a backslash character (\) immediately followed by a new-line
           character is deleted, splicing physical source lines to form logical source lines.
           Only the last backslash on any physical source line shall be eligible for being part
@@ -823,7 +670,7 @@
      4.   Preprocessing directives are executed, macro invocations are expanded, and
           _Pragma unary operator expressions are executed. If a character sequence that
           matches the syntax of a universal character name is produced by token
-          concatenation (6.10.3.3), the behavior is undefined. A #include preprocessing
+          concatenation (6.10.3.3), the behavior is undefined. A #include preprocessing
           directive causes the named header or source file to be processed from phase 1
           through phase 4, recursively. All preprocessing directives are then deleted.
      5.   Each source character set member and escape sequence in character constants and
@@ -838,48 +685,27 @@
           linked to satisfy external references to functions and objects not defined in the
           current translation. All such translator output is collected into a program image
           which contains information needed for execution in its execution environment.
-    Forward references: universal character names (6.4.3), lexical elements (6.4),
-    preprocessing directives (6.10), trigraph sequences (5.2.1.1), external definitions (6.9).
-

-
-
-
Footnote 5) Implementations shall behave as if these separate phases occur, even though many are typically folded
-          together in practice. Source files, translation units, and translated translation units need not
-          necessarily be stored as files, nor need there be any one-to-one correspondence between these entities
-          and any external representation. The description is conceptual only, and does not specify any
-          particular implementation.
+    Forward references: universal character names (6.4.3), lexical elements (6.4),
+    preprocessing directives (6.10), trigraph sequences (5.2.1.1), external definitions (6.9).
 

 
-
-
Footnote 6) As described in 6.4, the process of dividing a source file's characters into preprocessing tokens is
-          context-dependent. For example, see the handling of < within a #include preprocessing directive.
-

-
-
-
Footnote 7) An implementation need not convert all non-corresponding source characters to the same execution
-          character.
-

-
-
+
 

 
5.1.1.3 [Diagnostics]

-

-
-
+
 
1   A conforming implementation shall produce at least one diagnostic message (identified in
     an implementation-defined manner) if a preprocessing translation unit or translation unit
     contains a violation of any syntax rule or constraint, even if the behavior is also explicitly
     specified as undefined or implementation-defined. Diagnostic messages need not be
-    produced in other circumstances.8)
+    produced in other circumstances.[8]
 

-
 
 
Footnote 8) The intent is that an implementation should identify the nature of, and where possible localize, each
          violation. Of course, an implementation is free to produce any number of diagnostics as long as a
          valid program is still correctly translated. It may also successfully translate an invalid program.
 

 
-
+
 
2   EXAMPLE        An implementation shall issue a diagnostic for the translation unit:
              char i;
              int i;
@@ -887,55 +713,42 @@
     as being both a constraint error and resulting in undefined behavior, the constraint error shall be diagnosed.
 
 

-
-
+
 

 
5.1.2 [Execution environments]

-

-
-
+
 
1   Two execution environments are defined: freestanding and hosted . In both cases,
     program startup occurs when a designated C function is called by the execution
     environment. All objects with static storage duration shall be initialized (set to their
     initial values) before program startup. The manner and timing of such initialization are
     otherwise unspecified. Program termination returns control to the execution
     environment.
-    Forward references: storage durations of objects (6.2.4), initialization (6.7.8).
+    Forward references: storage durations of objects (6.2.4), initialization (6.7.8).
 

-
-
+
 

 
5.1.2.1 [Freestanding environment]

-

-
-
+
 
1   In a freestanding environment (in which C program execution may take place without any
     benefit of an operating system), the name and type of the function called at program
     startup are implementation-defined. Any library facilities available to a freestanding
     program, other than the minimal set required by clause 4, are implementation-defined.
 

-
-
+
 
2   The effect of program termination in a freestanding environment is implementation-
     defined.
 

-
-
+
 

 
5.1.2.2 [Hosted environment]

-

-
-
+
 
1   A hosted environment need not be provided, but shall conform to the following
     specifications if present.
 

-
-
+
 

 
5.1.2.2.1 [Program startup]

-

-
-
+
 
1   The function called at program startup is named main. The implementation declares no
     prototype for this function. It shall be defined with a return type of int and with no
     parameters:
@@ -943,15 +756,14 @@
     or with two parameters (referred to here as argc and argv, though any names may be
     used, as they are local to the function in which they are declared):
             int main(int argc, char *argv[]) { /* ... */ }
-    or equivalent;9) or in some other implementation-defined manner.
+    or equivalent;[9] or in some other implementation-defined manner.
 

-
 
 
Footnote 9) Thus, int can be replaced by a typedef name defined as int, or the type of argv can be written as
          char ** argv, and so on.
 

 
-
+
 
2   If they are declared, the parameters to the main function shall obey the following
     constraints:
     -- The value of argc shall be nonnegative.
@@ -972,55 +784,44 @@
        be modifiable by the program, and retain their last-stored values between program
        startup and program termination.
 

-
-
+
 

 
5.1.2.2.2 [Program execution]

-

-
-
+
 
1   In a hosted environment, a program may use all the functions, macros, type definitions,
     and objects described in the library clause (clause 7).
 

-
-
+
 

 
5.1.2.2.3 [Program termination]

-

-
-
+
 
1   If the return type of the main function is a type compatible with int, a return from the
     initial call to the main function is equivalent to calling the exit function with the value
-    returned by the main function as its argument;10) reaching the } that terminates the
+    returned by the main function as its argument;[10] reaching the } that terminates the
     main function returns a value of 0. If the return type is not compatible with int, the
     termination status returned to the host environment is unspecified.
-    Forward references: definition of terms (7.1.1), the exit function (7.20.4.3).
+    Forward references: definition of terms (7.1.1), the exit function (7.20.4.3).
 

-
 
-
Footnote 10) In accordance with 6.2.4, the lifetimes of objects with automatic storage duration declared in main
+
Footnote 10) In accordance with 6.2.4, the lifetimes of objects with automatic storage duration declared in main
         will have ended in the former case, even where they would not have in the latter.
 

 
-
+
 

 
5.1.2.3 [Program execution]

-

-
-
+
 
1   The semantic descriptions in this International Standard describe the behavior of an
     abstract machine in which issues of optimization are irrelevant.
 

-
-
+
 
2   Accessing a volatile object, modifying an object, modifying a file, or calling a function
-    that does any of those operations are all side effects,11) which are changes in the state of
+    that does any of those operations are all side effects,[11] which are changes in the state of
     the execution environment. Evaluation of an expression may produce side effects. At
     certain specified points in the execution sequence called sequence points, all side effects
     of previous evaluations shall be complete and no side effects of subsequent evaluations
     shall have taken place. (A summary of the sequence points is given in annex C.)
 

-
 
 
Footnote 11) The IEC 60559 standard for binary floating-point arithmetic requires certain user-accessible status
         flags and control modes. Floating-point operations implicitly set the status flags; modes affect result
@@ -1028,50 +829,44 @@
         required to regard changes to it as side effects -- see annex F for details. The floating-point
         environment library <fenv.h> provides a programming facility for indicating when these side
         effects matter, freeing the implementations in other cases.
+     -- At program termination, all data written into files shall be identical to the result that
+        execution of the program according to the abstract semantics would have produced.
+     -- The input and output dynamics of interactive devices shall take place as specified in
+        7.19.3. The intent of these requirements is that unbuffered or line-buffered output
+        appear as soon as possible, to ensure that prompting messages actually appear prior to
+        a program waiting for input.
 

 
-
+
 
3   In the abstract machine, all expressions are evaluated as specified by the semantics. An
     actual implementation need not evaluate part of an expression if it can deduce that its
     value is not used and that no needed side effects are produced (including any caused by
     calling a function or accessing a volatile object).
 

-
-
+
 
4   When the processing of the abstract machine is interrupted by receipt of a signal, only the
     values of objects as of the previous sequence point may be relied on. Objects that may be
     modified between the previous sequence point and the next sequence point need not have
     received their correct values yet.
 

-
-
+
 
5   The least requirements on a conforming implementation are:
     -- At sequence points, volatile objects are stable in the sense that previous accesses are
        complete and subsequent accesses have not yet occurred.
-     -- At program termination, all data written into files shall be identical to the result that
-        execution of the program according to the abstract semantics would have produced.
-     -- The input and output dynamics of interactive devices shall take place as specified in
-        7.19.3. The intent of these requirements is that unbuffered or line-buffered output
-        appear as soon as possible, to ensure that prompting messages actually appear prior to
-        a program waiting for input.
 

-
-
+
 
6    What constitutes an interactive device is implementation-defined.
 

-
-
+
 
7    More stringent correspondences between abstract and actual semantics may be defined by
      each implementation.
 

-
-
+
 
8    EXAMPLE 1 An implementation might define a one-to-one correspondence between abstract and actual
      semantics: at every sequence point, the values of the actual objects would agree with those specified by the
      abstract semantics. The keyword volatile would then be redundant.
 

-
-
+
 
9    Alternatively, an implementation might perform various optimizations within each translation unit, such
      that the actual semantics would agree with the abstract semantics only when making function calls across
      translation unit boundaries. In such an implementation, at the time of each function entry and function
@@ -1084,8 +879,7 @@
      restrictions.
 
 

-
-
+
 
10   EXAMPLE 2       In executing the fragment
               char c1, c2;
               /* ... */
@@ -1096,8 +890,7 @@
      produce the same result, possibly omitting the promotions.
 
 

-
-
+
 
11   EXAMPLE 3       Similarly, in the fragment
               float f1, f2;
               double d;
@@ -1108,8 +901,7 @@
      were replaced by the constant 2.0, which has type double).
 
 

-
-
+
 
12   EXAMPLE 4 Implementations employing wide registers have to take care to honor appropriate
      semantics. Values are independent of whether they are represented in a register or in memory. For
      example, an implicit spilling of a register is not permitted to alter the value. Also, an explicit store and load
@@ -1122,14 +914,13 @@
      the values assigned to d1 and d2 are required to have been converted to float.
 
 

-
-
+
 
13   EXAMPLE 5 Rearrangement for floating-point expressions is often restricted because of limitations in
      precision as well as range. The implementation cannot generally apply the mathematical associative rules
      for addition or multiplication, nor the distributive rule, because of roundoff error, even in the absence of
      overflow and underflow. Likewise, implementations cannot generally replace decimal constants in order to
      rearrange expressions. In the following fragment, rearrangements suggested by mathematical rules for real
-     numbers are often not valid (see F.8).
+     numbers are often not valid (see F.8).
               double x, y, z;
               /* ... */
               x = (x * y) * z;            //   not equivalent to x   *= y * z;
@@ -1138,8 +929,7 @@
               y = x / 5.0;                //   not equivalent to y   = x * 0.2;
 
 

-
-
+
 
14   EXAMPLE 6       To illustrate the grouping behavior of expressions, in the following fragment
               int a, b;
               /* ... */
@@ -1162,8 +952,7 @@
      same result will occur.
 
 

-
-
+
 
15   EXAMPLE 7 The grouping of an expression does not completely determine its evaluation. In the
      following fragment
               #include <stdio.h>
@@ -1177,23 +966,17 @@
      sequence point (the ;), and the call to getchar can occur at any point prior to the need of its returned
      value.
 
-     Forward references: expressions (6.5), type qualifiers (6.7.3), statements (6.8), the
-     signal function (7.14), files (7.19.3).
+     Forward references: expressions (6.5), type qualifiers (6.7.3), statements (6.8), the
+     signal function (7.14), files (7.19.3).
 
 

-
-
+
 

 
5.2 [Environmental considerations]

-
 Environmental considerations
-

-
-
+
 

 
5.2.1 [Character sets]

-

-
-
+
 
1   Two sets of characters and their associated collating sequences shall be defined: the set in
     which source files are written (the source character set ), and the set interpreted in the
     execution environment (the execution character set ). Each set is further divided into a
@@ -1202,16 +985,14 @@
     extended characters. The combined set is also called the extended character set . The
     values of the members of the execution character set are implementation-defined.
 

-
-
+
 
2   In a character constant or string literal, members of the execution character set shall be
     represented by corresponding members of the source character set or by escape
     sequences consisting of the backslash \ followed by one or more characters. A byte with
     all bits set to 0, called the null character , shall exist in the basic execution character set; it
     is used to terminate a character string.
 

-
-
+
 
3   Both the basic source and basic execution character sets shall have the following
     members: the 26 uppercase letters of the Latin alphabet
              A   B    C     D   E   F    G    H    I    J    K    L    M
@@ -1236,26 +1017,21 @@
     constant, a string literal, a header name, a comment, or a preprocessing token that is never
     converted to a token), the behavior is undefined.
 

-
-
+
 
4   A letter is an uppercase letter or a lowercase letter as defined above; in this International
     Standard the term does not include other characters that are letters in other alphabets.
 

-
-
+
 
5   The universal character name construct provides a way to name other characters.
-    Forward references: universal character names (6.4.3), character constants (6.4.4.4),
-    preprocessing directives (6.10), string literals (6.4.5), comments (6.4.9), string (7.1.1).
+    Forward references: universal character names (6.4.3), character constants (6.4.4.4),
+    preprocessing directives (6.10), string literals (6.4.5), comments (6.4.9), string (7.1.1).
 

-
-
+
 

 
5.2.1.1 [Trigraph sequences]

-

-
-
+
 
1   Before any other processing takes place, each occurrence of one of the following
-    sequences of three characters (called trigraph sequences12)) is replaced with the
+    sequences of three characters (called trigraph sequences[12]) is replaced with the
     corresponding single character.
            ??=      #                       ??)      ]                       ??!      |
            ??(      [                       ??'      ^                       ??>      }
@@ -1263,42 +1039,9 @@
     No other trigraph sequences exist. Each ? that does not begin one of the trigraphs listed
     above is not changed.
 

-
 
 
Footnote 12) The trigraph sequences enable the input of characters that are not defined in the Invariant Code Set as
         described in ISO/IEC 646, which is a subset of the seven-bit US ASCII code set.
-

-
-
-
2   EXAMPLE 1
-              ??=define arraycheck(a, b) a??(b??) ??!??! b??(a??)
-    becomes
-              #define arraycheck(a, b) a[b] || b[a]
-
-

-
-
-
3   EXAMPLE 2       The following source line
-              printf("Eh???/n");
-    becomes (after replacement of the trigraph sequence ??/)
-              printf("Eh?\n");
-
-

-
-
-

-
5.2.1.2 [Multibyte characters]

-

-
-
-
1   The source character set may contain multibyte characters, used to represent members of
-    the extended character set. The execution character set may also contain multibyte
-    characters, which need not have the same encoding as for the source character set. For
-    both character sets, the following shall hold:
-    -- The basic character set shall be present and each character shall be encoded as a
-       single byte.
-    -- The presence, meaning, and representation of any additional members is locale-
-       specific.
     -- A multibyte character set may have a state-dependent encoding, wherein each
        sequence of multibyte characters begins in an initial shift state and enters other
        locale-specific shift states when specific multibyte characters are encountered in the
@@ -1307,22 +1050,46 @@
        in the sequence is a function of the current shift state.
     -- A byte with all bits zero shall be interpreted as a null character independent of shift
        state. Such a byte shall not occur as part of any other multibyte character.
-

+

 
-
+
+
2   EXAMPLE 1
+              ??=define arraycheck(a, b) a??(b??) ??!??! b??(a??)
+    becomes
+              #define arraycheck(a, b) a[b] || b[a]
+
+

+
+
3   EXAMPLE 2       The following source line
+              printf("Eh???/n");
+    becomes (after replacement of the trigraph sequence ??/)
+              printf("Eh?\n");
+
+

+
+

+
5.2.1.2 [Multibyte characters]

+
+
1   The source character set may contain multibyte characters, used to represent members of
+    the extended character set. The execution character set may also contain multibyte
+    characters, which need not have the same encoding as for the source character set. For
+    both character sets, the following shall hold:
+    -- The basic character set shall be present and each character shall be encoded as a
+       single byte.
+    -- The presence, meaning, and representation of any additional members is locale-
+       specific.
+

+
 
2   For source files, the following shall hold:
     -- An identifier, comment, string literal, character constant, or header name shall begin
        and end in the initial shift state.
     -- An identifier, comment, string literal, character constant, or header name shall consist
        of a sequence of valid multibyte characters.
 

-
-
+
 

 
5.2.2 [Character display semantics]

-

-
-
+
 
1   The active position is that location on a display device where the next character output by
     the fputc function would appear. The intent of writing a printing character (as defined
     by the isprint function) to a display device is to display a graphic representation of
@@ -1331,8 +1098,7 @@
     position is at the final position of a line (if there is one), the behavior of the display device
     is unspecified.
 

-
-
+
 
2   Alphabetic escape sequences representing nongraphic characters in the execution
     character set are intended to produce actions on display devices as follows:
     \a ( alert ) Produces an audible or visible alert without changing the active position.
@@ -1350,21 +1116,17 @@
         tabulation position. If the active position is at or past the last defined vertical
          tabulation position, the behavior of the display device is unspecified.
 

-
-
+
 
3   Each of these escape sequences shall produce a unique implementation-defined value
     which can be stored in a single char object. The external representations in a text file
     need not be identical to the internal representations, and are outside the scope of this
     International Standard.
-    Forward references: the isprint function (7.4.1.8), the fputc function (7.19.7.3).
+    Forward references: the isprint function (7.4.1.8), the fputc function (7.19.7.3).
 

-
-
+
 

 
5.2.3 [Signals and interrupts]

-

-
-
+
 
1   Functions shall be implemented such that they may be interrupted at any time by a signal,
     or may be called by a signal handler, or both, with no alteration to earlier, but still active,
     invocations' control flow (after the interruption), function return values, or objects with
@@ -1372,27 +1134,21 @@
     image (the instructions that compose the executable representation of a function) on a
     per-invocation basis.
 

-
-
+
 

 
5.2.4 [Environmental limits]

-

-
-
+
 
1   Both the translation and execution environments constrain the implementation of
     language translators and libraries. The following summarizes the language-related
     environmental limits on a conforming implementation; the library-related limits are
     discussed in clause 7.
 

-
-
+
 

 
5.2.4.1 [Translation limits]

-

-
-
+
 
1   The implementation shall be able to translate and execute at least one program that
-    contains at least one instance of every one of the following limits:13)
+    contains at least one instance of every one of the following limits:[13]
     -- 127 nesting levels of blocks
     -- 63 nesting levels of conditional inclusion
     -- 12 pointer, array, and function declarators (in any combinations) modifying an
@@ -1404,6 +1160,12 @@
        character)
     -- 31 significant initial characters in an external identifier (each universal character name
        specifying a short identifier of 0000FFFF or less is considered 6 characters, each
+

+
+
Footnote 13) Implementations should avoid imposing fixed translation limits whenever possible.
+        universal character name specifying a short identifier of 00010000 or more is
+        considered 10 characters, and each extended source character is considered the same
+        number of characters as the corresponding universal character name, if any)14)
     -- 4095 external identifiers in one translation unit
     -- 511 identifiers with block scope declared in one block
     -- 4095 macro identifiers simultaneously defined in one preprocessing translation unit
@@ -1420,104 +1182,60 @@
     -- 1023 members in a single structure or union
     -- 1023 enumeration constants in a single enumeration
     -- 63 levels of nested structure or union definitions in a single struct-declaration-list
-

+

 
-
+
 

 
5.2.4.2 [Numerical limits]

-

-
-
+
 
1   An implementation is required to document all the limits specified in this subclause,
     which are specified in the headers <limits.h> and <float.h>. Additional limits are
     specified in <stdint.h>.
-    Forward references: integer types <stdint.h> (7.18).
+    Forward references: integer types <stdint.h> (7.18).
 

-
-
+
 

-
5.2.4.2.1 [Sizes of integer types ]

-

-
-
+
5.2.4.2.1 [Sizes of integer types <limits.h>]

+
 
1   The values given below shall be replaced by constant expressions suitable for use in #if
     preprocessing directives. Moreover, except for CHAR_BIT and MB_LEN_MAX, the
     following shall be replaced by expressions that have the same type as would an
     expression that is an object of the corresponding type converted according to the integer
     promotions. Their implementation-defined values shall be equal or greater in magnitude
-    (absolute value) to those shown, with the same sign.
-    -- number of bits for smallest object that is not a bit-field (byte)
-       CHAR_BIT                                            8
-    -- minimum value for an object of type signed char
-       SCHAR_MIN                                -127 // -(27 - 1)
-    -- maximum value for an object of type signed char
-       SCHAR_MAX                                +127 // 27 - 1
-    -- maximum value for an object of type unsigned char
-       UCHAR_MAX                                 255 // 28 - 1
-    -- minimum value for an object of type char
-       CHAR_MIN                               see below
-    -- maximum value for an object of type char
-       CHAR_MAX                              see below
-    -- maximum number of bytes in a multibyte character, for any supported locale
-       MB_LEN_MAX                                    1
-    -- minimum value for an object of type short int
-       SHRT_MIN                               -32767 // -(215 - 1)
-    -- maximum value for an object of type short int
-       SHRT_MAX                               +32767 // 215 - 1
-    -- maximum value for an object of type unsigned short int
-       USHRT_MAX                               65535 // 216 - 1
-    -- minimum value for an object of type int
-       INT_MIN                                 -32767 // -(215 - 1)
-    -- maximum value for an object of type int
-       INT_MAX                                +32767 // 215 - 1
-    -- maximum value for an object of type unsigned int
-       UINT_MAX                                65535 // 216 - 1
-    -- minimum value for an object of type long int
-       LONG_MIN                         -2147483647 // -(231 - 1)
-    -- maximum value for an object of type long int
-       LONG_MAX                         +2147483647 // 231 - 1
-    -- maximum value for an object of type unsigned long int
-       ULONG_MAX                         4294967295 // 232 - 1
-    -- minimum value for an object of type long long int
-       LLONG_MIN          -9223372036854775807 // -(263 - 1)
-    -- maximum value for an object of type long long int
-       LLONG_MAX          +9223372036854775807 // 263 - 1
-    -- maximum value for an object of type unsigned long long int
-       ULLONG_MAX         18446744073709551615 // 264 - 1
 

-
-
+
 
2   If the value of an object of type char is treated as a signed integer when used in an
     expression, the value of CHAR_MIN shall be the same as that of SCHAR_MIN and the
     value of CHAR_MAX shall be the same as that of SCHAR_MAX. Otherwise, the value of
     CHAR_MIN shall be 0 and the value of CHAR_MAX shall be the same as that of
-    UCHAR_MAX.15) The value UCHAR_MAX shall equal 2CHAR_BIT - 1.
-    Forward references: representations of types (6.2.6), conditional inclusion (6.10.1).
+    UCHAR_MAX.[15] The value UCHAR_MAX shall equal 2CHAR_BIT - 1.
+    Forward references: representations of types (6.2.6), conditional inclusion (6.10.1).
 

+
+
Footnote 15) See 6.2.5.
+

 
-
+
 

-
5.2.4.2.2 [Characteristics of floating types ]

-

-
-
+
5.2.4.2.2 [Characteristics of floating types <float.h>]

+
 
1   The characteristics of floating types are defined in terms of a model that describes a
     representation of floating-point numbers and values that provide information about an
-    implementation's floating-point arithmetic.16) The following parameters are used to
+    implementation's floating-point arithmetic.[16] The following parameters are used to
     define the model for each floating-point type:
-           s          sign (±1)
+           s          sign (\xB11)
            b          base or radix of exponent representation (an integer > 1)
            e          exponent (an integer between a minimum emin and a maximum emax )
            p          precision (the number of base-b digits in the significand)
             fk        nonnegative integers less than b (the significand digits)
 

-
 
 
Footnote 16) The floating-point model is intended to clarify the description of each floating-point characteristic and
         does not require the floating-point arithmetic of the implementation to be identical.
+    arithmetic operand.17)
 

 
-
+
 
2   A floating-point number ( x ) is defined by the following model:
                        p
            x = sb e
@@ -1525,8 +1243,7 @@
                            f k b-k ,    emin  e  emax
 
 

-
-
+
 
3   In addition to normalized floating-point numbers ( f 1 > 0 if x  0), floating types may be
     able to contain other kinds of floating-point numbers, such as subnormal floating-point
     numbers ( x  0, e = emin , f 1 = 0) and unnormalized floating-point numbers ( x  0,
@@ -1534,23 +1251,14 @@
     NaNs. A NaN is an encoding signifying Not-a-Number. A quiet NaN propagates
     through almost every arithmetic operation without raising a floating-point exception; a
     signaling NaN generally raises a floating-point exception when occurring as an
-    arithmetic operand.17)
 

-
-
-
Footnote 17) IEC 60559:1989 specifies quiet and signaling NaNs. For implementations that do not support
-        IEC 60559:1989, the terms quiet NaN and signaling NaN are intended to apply to encodings with
-        similar behavior.
-

-
-
+
 
4   An implementation may give zero and non-numeric values (such as infinities and NaNs) a
     sign or may leave them unsigned. Wherever such values are unsigned, any requirement
     in this International Standard to retrieve the sign shall produce an unspecified sign, and
     any requirement to set the sign shall be ignored.
 

-
-
+
 
5   The accuracy of the floating-point operations (+, -, *, /) and of the library functions in
     <math.h> and <complex.h> that return floating-point results is implementation-
     defined, as is the accuracy of the conversion between floating-point internal
@@ -1558,8 +1266,7 @@
     <stdio.h>, <stdlib.h>, and <wchar.h>. The implementation may state that the
     accuracy is unknown.
 

-
-
+
 
6   All integer values in the <float.h> header, except FLT_ROUNDS, shall be constant
     expressions suitable for use in #if preprocessing directives; all floating values shall be
     constant expressions. All except DECIMAL_DIG, FLT_EVAL_METHOD, FLT_RADIX,
@@ -1567,10 +1274,9 @@
     point model representation is provided for all values except FLT_EVAL_METHOD and
     FLT_ROUNDS.
 

-
-
+
 
7   The rounding mode for floating-point addition is characterized by the implementation-
-    defined value of FLT_ROUNDS:18)
+    defined value of FLT_ROUNDS:[18]
           -1      indeterminable
            0      toward zero
            1      to nearest
@@ -1579,7 +1285,6 @@
     All other values for FLT_ROUNDS characterize implementation-defined rounding
     behavior.
 

-
 
 
Footnote 18) Evaluation of FLT_ROUNDS correctly reflects any execution-time change of rounding mode through
         the function fesetround in <fenv.h>.
@@ -1592,59 +1297,34 @@
                      type;
             2        evaluate all operations and constants to the range and precision of the
                      long double type.
+    All other negative values for FLT_EVAL_METHOD characterize implementation-defined
+    behavior.
 

 
-
+
 
8   Except for assignment and cast (which remove all extra range and precision), the values
     of operations with floating operands and values subject to the usual arithmetic
     conversions and of floating constants are evaluated to a format whose range and precision
     may be greater than required by the type. The use of evaluation formats is characterized
-    by the implementation-defined value of FLT_EVAL_METHOD:19)
-    All other negative values for FLT_EVAL_METHOD characterize implementation-defined
-    behavior.
+    by the implementation-defined value of FLT_EVAL_METHOD:[19]
 

-
 
 
Footnote 19) The evaluation method determines evaluation formats of expressions involving all floating types, not
         just real types. For example, if FLT_EVAL_METHOD is 1, then the product of two float
         _Complex operands is represented in the double _Complex format, and its parts are evaluated to
         double.
              p log10 b        if b is a power of 10
-            
              ( p - 1) log10 b otherwise
         FLT_DIG                                      6
         DBL_DIG                                     10
         LDBL_DIG                                    10
-

-
-
-
9   The values given in the following list shall be replaced by constant expressions with
-    implementation-defined values that are greater or equal in magnitude (absolute value) to
-    those shown, with the same sign:
-    -- radix of exponent representation, b
-       FLT_RADIX                                                 2
-    -- number of base-FLT_RADIX digits in the floating-point significand, p
-        FLT_MANT_DIG
-        DBL_MANT_DIG
-        LDBL_MANT_DIG
-    -- number of decimal digits, n, such that any floating-point number in the widest
-       supported floating type with pmax radix b digits can be rounded to a floating-point
-       number with n decimal digits and back again without change to the value,
-             pmax log10 b        if b is a power of 10
-            
-             1 + pmax log10 b otherwise
-        DECIMAL_DIG                                            10
-    -- number of decimal digits, q , such that any floating-point number with q decimal digits
-       can be rounded into a floating-point number with p radix b digits and back again
-       without change to the q decimal digits,
      -- minimum negative integer such that FLT_RADIX raised to one less than that power is
         a normalized floating-point number, emin
         FLT_MIN_EXP
         DBL_MIN_EXP
         LDBL_MIN_EXP
      -- minimum negative integer such that 10 raised to that power is in the range of
-        normalized floating-point numbers, log10 b emin -1 
-                                                           
+        normalized floating-point numbers, log10 b emin -1
         FLT_MIN_10_EXP                                 -37
         DBL_MIN_10_EXP                                 -37
         LDBL_MIN_10_EXP                                -37
@@ -1658,9 +1338,30 @@
         FLT_MAX_10_EXP                                  +37
         DBL_MAX_10_EXP                                  +37
         LDBL_MAX_10_EXP                                 +37
-

+

 
-
+
+
9   The values given in the following list shall be replaced by constant expressions with
+    implementation-defined values that are greater or equal in magnitude (absolute value) to
+    those shown, with the same sign:
+    -- radix of exponent representation, b
+       FLT_RADIX                                                 2
+    -- number of base-FLT_RADIX digits in the floating-point significand, p
+        FLT_MANT_DIG
+        DBL_MANT_DIG
+        LDBL_MANT_DIG
+    -- number of decimal digits, n, such that any floating-point number in the widest
+       supported floating type with pmax radix b digits can be rounded to a floating-point
+       number with n decimal digits and back again without change to the value,
+             pmax log10 b        if b is a power of 10
+
+             1 + pmax log10 b otherwise
+        DECIMAL_DIG                                            10
+    -- number of decimal digits, q , such that any floating-point number with q decimal digits
+       can be rounded into a floating-point number with p radix b digits and back again
+       without change to the q decimal digits,
+

+
 
10   The values given in the following list shall be replaced by constant expressions with
      implementation-defined values that are greater than or equal to those shown:
      -- maximum representable finite floating-point number, (1 - b- p )b emax
@@ -1668,8 +1369,7 @@
         DBL_MAX                                      1E+37
         LDBL_MAX                                     1E+37
 

-
-
+
 
11   The values given in the following list shall be replaced by constant expressions with
      implementation-defined (positive) values that are less than or equal to those shown:
      -- the difference between 1 and the least value greater than 1 that is representable in the
@@ -1683,13 +1383,11 @@
          LDBL_MIN                                             1E-37
      Recommended practice
 

-
-
+
 
12   Conversion from (at least) double to decimal with DECIMAL_DIG digits and back
      should be the identity function.
 

-
-
+
 
13   EXAMPLE 1 The following describes an artificial floating-point representation that meets the minimum
      requirements of this International Standard, and the appropriate values in a <float.h> header for type
      float:
@@ -1703,17 +1401,16 @@
              FLT_EPSILON                       9.53674316E-07F
              FLT_DIG                                         6
              FLT_MIN_EXP                                   -31
-             FLT_MIN                           2.93873588E-39F
+             FLT_MIN                           2.93873588E-39F
              FLT_MIN_10_EXP                                -38
              FLT_MAX_EXP                                   +32
-             FLT_MAX                           3.40282347E+38F
+             FLT_MAX                           3.40282347E+38F
              FLT_MAX_10_EXP                                +38
 
 

-
-
+
 
14   EXAMPLE 2 The following describes floating-point representations that also meet the requirements for
-     single-precision and double-precision normalized numbers in IEC 60559,20) and the appropriate values in a
+     single-precision and double-precision normalized numbers in IEC 60559,[20] and the appropriate values in a
      <float.h> header for types float and double:
                         24
            x f = s 2e
@@ -1728,57 +1425,114 @@
              FLT_RADIX                                       2
              DECIMAL_DIG                                    17
              FLT_MANT_DIG                                   24
-             FLT_EPSILON                       1.19209290E-07F // decimal constant
+             FLT_EPSILON                       1.19209290E-07F // decimal constant
              FLT_EPSILON                              0X1P-23F // hex constant
+     [20] The floating-point model in that standard sums powers of b from zero, so the values of the exponent
+         limits are one less than shown here.
+        FLT_DIG                           6
+        FLT_MIN_EXP                    -125
+        FLT_MIN             1.17549435E-38F               // decimal constant
+        FLT_MIN                   0X1P-126F               // hex constant
+        FLT_MIN_10_EXP                  -37
+        FLT_MAX_EXP                    +128
+        FLT_MAX             3.40282347E+38F               // decimal constant
+        FLT_MAX             0X1.fffffeP127F               // hex constant
+        FLT_MAX_10_EXP                  +38
+        DBL_MANT_DIG                     53
+        DBL_EPSILON 2.2204460492503131E-16                // decimal constant
+        DBL_EPSILON                 0X1P-52               // hex constant
+        DBL_DIG                          15
+        DBL_MIN_EXP                   -1021
+        DBL_MIN     2.2250738585072014E-308               // decimal constant
+        DBL_MIN                   0X1P-1022               // hex constant
+        DBL_MIN_10_EXP                 -307
+        DBL_MAX_EXP                   +1024
+        DBL_MAX     1.7976931348623157E+308               // decimal constant
+        DBL_MAX      0X1.fffffffffffffP1023               // hex constant
+        DBL_MAX_10_EXP                 +308
 
   If a type wider than double were supported, then DECIMAL_DIG would be greater than 17. For
   example, if the widest type were to use the minimal-width IEC 60559 double-extended format (64 bits of
   precision), then DECIMAL_DIG would be 21.
 
-Forward references:         conditional inclusion (6.10.1), complex arithmetic
-<complex.h> (7.3), extended multibyte and wide character utilities <wchar.h>
-(7.24), floating-point environment <fenv.h> (7.6), general utilities <stdlib.h>
-(7.20), input/output <stdio.h> (7.19), mathematics <math.h> (7.12).
+Forward references:         conditional inclusion (6.10.1), complex arithmetic
+<complex.h> (7.3), extended multibyte and wide character utilities <wchar.h>
+(7.24), floating-point environment <fenv.h> (7.6), general utilities <stdlib.h>
+(7.20), input/output <stdio.h> (7.19), mathematics <math.h> (7.12).
 

+
+
Footnote 20) The floating-point model in that standard sums powers of b from zero, so the values of the exponent
+         limits are one less than shown here.
+        FLT_DIG                           6
+        FLT_MIN_EXP                    -125
+        FLT_MIN             1.17549435E-38F               // decimal constant
+        FLT_MIN                   0X1P-126F               // hex constant
+        FLT_MIN_10_EXP                  -37
+        FLT_MAX_EXP                    +128
+        FLT_MAX             3.40282347E+38F               // decimal constant
+        FLT_MAX             0X1.fffffeP127F               // hex constant
+        FLT_MAX_10_EXP                  +38
+        DBL_MANT_DIG                     53
+        DBL_EPSILON 2.2204460492503131E-16                // decimal constant
+        DBL_EPSILON                 0X1P-52               // hex constant
+        DBL_DIG                          15
+        DBL_MIN_EXP                   -1021
+        DBL_MIN     2.2250738585072014E-308               // decimal constant
+        DBL_MIN                   0X1P-1022               // hex constant
+        DBL_MIN_10_EXP                 -307
+        DBL_MAX_EXP                   +1024
+        DBL_MAX     1.7976931348623157E+308               // decimal constant
+        DBL_MAX      0X1.fffffffffffffP1023               // hex constant
+        DBL_MAX_10_EXP                 +308
+  If a type wider than double were supported, then DECIMAL_DIG would be greater than 17. For
+  example, if the widest type were to use the minimal-width IEC 60559 double-extended format (64 bits of
+  precision), then DECIMAL_DIG would be 21.
+Forward references:         conditional inclusion (6.10.1), complex arithmetic
+<complex.h> (7.3), extended multibyte and wide character utilities <wchar.h>
+(7.24), floating-point environment <fenv.h> (7.6), general utilities <stdlib.h>
+(7.20), input/output <stdio.h> (7.19), mathematics <math.h> (7.12).
+

 
 
 
Footnote 20) The floating-point model in that standard sums powers of b from zero, so the values of the exponent
          limits are one less than shown here.
         FLT_DIG                           6
         FLT_MIN_EXP                    -125
-        FLT_MIN             1.17549435E-38F               // decimal constant
+        FLT_MIN             1.17549435E-38F               // decimal constant
         FLT_MIN                   0X1P-126F               // hex constant
         FLT_MIN_10_EXP                  -37
         FLT_MAX_EXP                    +128
-        FLT_MAX             3.40282347E+38F               // decimal constant
+        FLT_MAX             3.40282347E+38F               // decimal constant
         FLT_MAX             0X1.fffffeP127F               // hex constant
         FLT_MAX_10_EXP                  +38
         DBL_MANT_DIG                     53
-        DBL_EPSILON 2.2204460492503131E-16                // decimal constant
+        DBL_EPSILON 2.2204460492503131E-16                // decimal constant
         DBL_EPSILON                 0X1P-52               // hex constant
         DBL_DIG                          15
         DBL_MIN_EXP                   -1021
-        DBL_MIN     2.2250738585072014E-308               // decimal constant
+        DBL_MIN     2.2250738585072014E-308               // decimal constant
         DBL_MIN                   0X1P-1022               // hex constant
         DBL_MIN_10_EXP                 -307
         DBL_MAX_EXP                   +1024
-        DBL_MAX     1.7976931348623157E+308               // decimal constant
+        DBL_MAX     1.7976931348623157E+308               // decimal constant
         DBL_MAX      0X1.fffffffffffffP1023               // hex constant
         DBL_MAX_10_EXP                 +308
+  If a type wider than double were supported, then DECIMAL_DIG would be greater than 17. For
+  example, if the widest type were to use the minimal-width IEC 60559 double-extended format (64 bits of
+  precision), then DECIMAL_DIG would be 21.
+Forward references:         conditional inclusion (6.10.1), complex arithmetic
+<complex.h> (7.3), extended multibyte and wide character utilities <wchar.h>
+(7.24), floating-point environment <fenv.h> (7.6), general utilities <stdlib.h>
+(7.20), input/output <stdio.h> (7.19), mathematics <math.h> (7.12).
 

 
-
+
 

 
6. [Language]

-
 Language
-

-
-
+
 

 
6.1 [Notation]

-

-
-
+
 
1   In the syntax notation used in this clause, syntactic categories (nonterminals) are
     indicated by italic type, and literal words and character set members (terminals) by bold
     type. A colon (:) following a nonterminal introduces its definition. Alternative
@@ -1787,28 +1541,20 @@ Forward references:         conditional inclusion (6.10.1), complex arithmetic
              { expressionopt }
     indicates an optional expression enclosed in braces.
 

-
-
+
 
2   When syntactic categories are referred to in the main text, they are not italicized and
     words are separated by spaces instead of hyphens.
 

-
-
+
 
3   A summary of the language syntax is given in annex A.
 

-
-
+
 

 
6.2 [Concepts]

-
 Concepts
-

-
-
+
 

 
6.2.1 [Scopes of identifiers]

-

-
-
+
 
1   An identifier can denote an object; a function; a tag or a member of a structure, union, or
     enumeration; a typedef name; a label name; a macro name; or a macro parameter. The
     same identifier can denote different entities at different points in the program. A member
@@ -1817,22 +1563,19 @@ Forward references:         conditional inclusion (6.10.1), complex arithmetic
     program translation any occurrences of macro names in the source file are replaced by the
     preprocessing token sequences that constitute their macro definitions.
 

-
-
+
 
2   For each different entity that an identifier designates, the identifier is visible (i.e., can be
     used) only within a region of program text called its scope. Different entities designated
     by the same identifier either have different scopes, or are in different name spaces. There
     are four kinds of scopes: function, file, block, and function prototype. (A function
     prototype is a declaration of a function that declares the types of its parameters.)
 

-
-
+
 
3   A label name is the only kind of identifier that has function scope. It can be used (in a
     goto statement) anywhere in the function in which it appears, and is declared implicitly
     by its syntactic appearance (followed by a : and a statement).
 

-
-
+
 
4   Every other identifier has scope determined by the placement of its declaration (in a
     declarator or type specifier). If the declarator or type specifier that declares the identifier
     appears outside of any block or list of parameters, the identifier has file scope, which
@@ -1848,100 +1591,81 @@ Forward references:         conditional inclusion (6.10.1), complex arithmetic
     identifier designates the entity declared in the inner scope; the entity declared in the outer
     scope is hidden (and not visible) within the inner scope.
 

-
-
+
 
5   Unless explicitly stated otherwise, where this International Standard uses the term
     ``identifier'' to refer to some entity (as opposed to the syntactic construct), it refers to the
     entity in the relevant name space whose declaration is visible at the point the identifier
     occurs.
 

-
-
+
 
6   Two identifiers have the same scope if and only if their scopes terminate at the same
     point.
 

-
-
+
 
7   Structure, union, and enumeration tags have scope that begins just after the appearance of
     the tag in a type specifier that declares the tag. Each enumeration constant has scope that
     begins just after the appearance of its defining enumerator in an enumerator list. Any
     other identifier has scope that begins just after the completion of its declarator.
-    Forward references: declarations (6.7), function calls (6.5.2.2), function definitions
-    (6.9.1), identifiers (6.4.2), name spaces of identifiers (6.2.3), macro replacement (6.10.3),
-    source file inclusion (6.10.2), statements (6.8).
+    Forward references: declarations (6.7), function calls (6.5.2.2), function definitions
+    (6.9.1), identifiers (6.4.2), name spaces of identifiers (6.2.3), macro replacement (6.10.3),
+    source file inclusion (6.10.2), statements (6.8).
 

-
-
+
 

 
6.2.2 [Linkages of identifiers]

-

-
-
+
 
1   An identifier declared in different scopes or in the same scope more than once can be
-    made to refer to the same object or function by a process called linkage.21) There are
+    made to refer to the same object or function by a process called linkage.[21] There are
     three kinds of linkage: external, internal, and none.
 

-
 
 
Footnote 21) There is no linkage between different identifiers.
 

 
-
+
 
2   In the set of translation units and libraries that constitutes an entire program, each
     declaration of a particular identifier with external linkage denotes the same object or
     function. Within one translation unit, each declaration of an identifier with internal
     linkage denotes the same object or function. Each declaration of an identifier with no
     linkage denotes a unique entity.
 

-
-
+
 
3   If the declaration of a file scope identifier for an object or a function contains the storage-
-    class specifier static, the identifier has internal linkage.22)
+    class specifier static, the identifier has internal linkage.[22]
 

-
 
 
Footnote 22) A function declaration can contain the storage-class specifier static only if it is at file scope; see
-        6.7.1.
-

-
-
-
4   For an identifier declared with the storage-class specifier extern in a scope in which a
+        6.7.1.
     prior declaration of that identifier is visible,23) if the prior declaration specifies internal or
     external linkage, the linkage of the identifier at the later declaration is the same as the
     linkage specified at the prior declaration. If no prior declaration is visible, or if the prior
     declaration specifies no linkage, then the identifier has external linkage.
-

-
-
-
Footnote 23) As specified in 6.2.1, the later declaration might hide the prior declaration.
 

 
-
+
+
4   For an identifier declared with the storage-class specifier extern in a scope in which a
+

+
 
5   If the declaration of an identifier for a function has no storage-class specifier, its linkage
     is determined exactly as if it were declared with the storage-class specifier extern. If
     the declaration of an identifier for an object has file scope and no storage-class specifier,
     its linkage is external.
 

-
-
+
 
6   The following identifiers have no linkage: an identifier declared to be anything other than
     an object or a function; an identifier declared to be a function parameter; a block scope
     identifier for an object declared without the storage-class specifier extern.
 

-
-
+
 
7   If, within a translation unit, the same identifier appears with both internal and external
     linkage, the behavior is undefined.
-    Forward references: declarations (6.7), expressions (6.5), external definitions (6.9),
-    statements (6.8).
+    Forward references: declarations (6.7), expressions (6.5), external definitions (6.9),
+    statements (6.8).
 

-
-
+
 

 
6.2.3 [Name spaces of identifiers]

-

-
-
+
 
1   If more than one declaration of a particular identifier is visible at any point in a
     translation unit, the syntactic context disambiguates uses that refer to different entities.
     Thus, there are separate name spaces for various categories of identifiers, as follows:
@@ -1953,29 +1677,24 @@ Forward references:         conditional inclusion (6.10.1), complex arithmetic
        member via the . or -> operator);
     -- all other identifiers, called ordinary identifiers (declared in ordinary declarators or as
        enumeration constants).
-    Forward references: enumeration specifiers (6.7.2.2), labeled statements (6.8.1),
-    structure and union specifiers (6.7.2.1), structure and union members (6.5.2.3), tags
-    (6.7.2.3), the goto statement (6.8.6.1).
+    Forward references: enumeration specifiers (6.7.2.2), labeled statements (6.8.1),
+    structure and union specifiers (6.7.2.1), structure and union members (6.5.2.3), tags
+    (6.7.2.3), the goto statement (6.8.6.1).
 

-
-
+
 

 
6.2.4 [Storage durations of objects]

-

-
-
+
 
1   An object has a storage duration that determines its lifetime. There are three storage
-    durations: static, automatic, and allocated. Allocated storage is described in 7.20.3.
+    durations: static, automatic, and allocated. Allocated storage is described in 7.20.3.
 

-
-
+
 
2   The lifetime of an object is the portion of program execution during which storage is
-    guaranteed to be reserved for it. An object exists, has a constant address,25) and retains
-    its last-stored value throughout its lifetime.26) If an object is referred to outside of its
+    guaranteed to be reserved for it. An object exists, has a constant address,[25] and retains
+    its last-stored value throughout its lifetime.[26] If an object is referred to outside of its
     lifetime, the behavior is undefined. The value of a pointer becomes indeterminate when
     the object it points to reaches the end of its lifetime.
 

-
 
 
Footnote 25) The term ``constant address'' means that two pointers to the object constructed at possibly different
         times will compare equal. The address may be different during two different executions of the same
@@ -1986,19 +1705,17 @@ Forward references:         conditional inclusion (6.10.1), complex arithmetic
 
Footnote 26) In the case of a volatile object, the last store need not be explicit in the program.
 

 
-
+
 
3   An object whose identifier is declared with external or internal linkage, or with the
     storage-class specifier static has static storage duration. Its lifetime is the entire
     execution of the program and its stored value is initialized only once, prior to program
     startup.
 

-
-
+
 
4   An object whose identifier is declared with no linkage and without the storage-class
     specifier static has automatic storage duration.
 

-
-
+
 
5   For such an object that does not have a variable length array type, its lifetime extends
     from entry into the block with which it is associated until execution of that block ends in
     any way. (Entering an enclosed block or calling a function suspends, but does not end,
@@ -2008,27 +1725,23 @@ Forward references:         conditional inclusion (6.10.1), complex arithmetic
     reached in the execution of the block; otherwise, the value becomes indeterminate each
     time the declaration is reached.
 

-
-
+
 
6   For such an object that does have a variable length array type, its lifetime extends from
     the declaration of the object until execution of the program leaves the scope of the
-    declaration.27) If the scope is entered recursively, a new instance of the object is created
+    declaration.[27] If the scope is entered recursively, a new instance of the object is created
     each time. The initial value of the object is indeterminate.
-    Forward references: statements (6.8), function calls (6.5.2.2), declarators (6.7.5), array
-    declarators (6.7.5.2), initialization (6.7.8).
+    Forward references: statements (6.8), function calls (6.5.2.2), declarators (6.7.5), array
+    declarators (6.7.5.2), initialization (6.7.8).
 

-
 
 
Footnote 27) Leaving the innermost block containing the declaration, or jumping to a point in that block or an
         embedded block prior to the declaration, leaves the scope of the declaration.
 

 
-
+
 

 
6.2.5 [Types]

-

-
-
+
 
1   The meaning of a value stored in an object or returned by a function is determined by the
     type of the expression used to access it. (An identifier declared to be an object is the
     simplest such expression; the type is specified in the declaration of the identifier.) Types
@@ -2036,30 +1749,26 @@ Forward references:         conditional inclusion (6.10.1), complex arithmetic
     that describe functions), and incomplete types (types that describe objects but lack
     information needed to determine their sizes).
 

-
-
+
 
2   An object declared as type _Bool is large enough to store the values 0 and 1.
 

-
-
+
 
3   An object declared as type char is large enough to store any member of the basic
     execution character set. If a member of the basic execution character set is stored in a
     char object, its value is guaranteed to be nonnegative. If any other character is stored in
     a char object, the resulting value is implementation-defined but shall be within the range
     of values that can be represented in that type.
 

-
-
+
 
4   There are five standard signed integer types, designated as signed char, short
     int, int, long int, and long long int. (These and other types may be
-    designated in several additional ways, as described in 6.7.2.) There may also be
-    implementation-defined extended signed integer types.28) The standard and extended
-    signed integer types are collectively called signed integer types.29)
+    designated in several additional ways, as described in 6.7.2.) There may also be
+    implementation-defined extended signed integer types.[28] The standard and extended
+    signed integer types are collectively called signed integer types.[29]
 

-
 
 
Footnote 28) Implementation-defined keywords shall have the form of an identifier reserved for any use as
-        described in 7.1.3.
+        described in 7.1.3.
 

 
 
@@ -2067,14 +1776,13 @@ Forward references:         conditional inclusion (6.10.1), complex arithmetic
         signed integer types.
 

 
-
+
 
5   An object declared as type signed char occupies the same amount of storage as a
     ``plain'' char object. A ``plain'' int object has the natural size suggested by the
     architecture of the execution environment (large enough to contain any value in the range
     INT_MIN to INT_MAX as defined in the header <limits.h>).
 

-
-
+
 
6   For each of the signed integer types, there is a corresponding (but different) unsigned
     integer type (designated with the keyword unsigned) that uses the same amount of
     storage (including sign information) and has the same alignment requirements. The type
@@ -2082,126 +1790,112 @@ Forward references:         conditional inclusion (6.10.1), complex arithmetic
     types are the standard unsigned integer types. The unsigned integer types that
     correspond to the extended signed integer types are the extended unsigned integer types.
     The standard and extended unsigned integer types are collectively called unsigned integer
-    types.30)
+    types.[30]
 

-
 
 
Footnote 30) Therefore, any statement in this Standard about unsigned integer types also applies to the extended
         unsigned integer types.
 

 
-
+
 
7    The standard signed integer types and standard unsigned integer types are collectively
      called the standard integer types, the extended signed integer types and extended
      unsigned integer types are collectively called the extended integer types.
 

-
-
+
 
8    For any two integer types with the same signedness and different integer conversion rank
-     (see 6.3.1.1), the range of values of the type with smaller integer conversion rank is a
+     (see 6.3.1.1), the range of values of the type with smaller integer conversion rank is a
      subrange of the values of the other type.
 

-
-
+
 
9    The range of nonnegative values of a signed integer type is a subrange of the
      corresponding unsigned integer type, and the representation of the same value in each
-     type is the same.31) A computation involving unsigned operands can never overflow,
+     type is the same.[31] A computation involving unsigned operands can never overflow,
      because a result that cannot be represented by the resulting unsigned integer type is
      reduced modulo the number that is one greater than the largest value that can be
      represented by the resulting type.
 

-
 
 
Footnote 31) The same representation and alignment requirements are meant to imply interchangeability as
          arguments to functions, return values from functions, and members of unions.
 

 
-
+
 
10   There are three real floating types, designated as float, double, and long
-     double.32) The set of values of the type float is a subset of the set of values of the
+     double.[32] The set of values of the type float is a subset of the set of values of the
      type double; the set of values of the type double is a subset of the set of values of the
      type long double.
 

-
 
-
Footnote 32) See ``future language directions'' (6.11.1).
+
Footnote 32) See ``future language directions'' (6.11.1).
 

 
-
+
 
11   There are three complex types, designated as float _Complex, double
-     _Complex, and long double _Complex.33) The real floating and complex types
+     _Complex, and long double _Complex.[33] The real floating and complex types
      are collectively called the floating types.
 

-
 
 
Footnote 33) A specification for imaginary types is in informative annex G.
 

 
-
+
 
12   For each floating type there is a corresponding real type, which is always a real floating
      type. For real floating types, it is the same type. For complex types, it is the type given
      by deleting the keyword _Complex from the type name.
 

-
-
+
 
13   Each complex type has the same representation and alignment requirements as an array
      type containing exactly two elements of the corresponding real type; the first element is
      equal to the real part, and the second element to the imaginary part, of the complex
      number.
 

-
-
+
 
14   The type char, the signed and unsigned integer types, and the floating types are
      collectively called the basic types. Even if the implementation defines two or more basic
-     types to have the same representation, they are nevertheless different types.34)
+     types to have the same representation, they are nevertheless different types.[34]
 

-
 
 
Footnote 34) An implementation may define new keywords that provide alternative ways to designate a basic (or
          any other) type; this does not violate the requirement that all basic types be different.
          Implementation-defined keywords shall have the form of an identifier reserved for any use as
-         described in 7.1.3.
+         described in 7.1.3.
 

 
-
+
 
15   The three types char, signed char, and unsigned char are collectively called
      the character types. The implementation shall define char to have the same range,
-     representation, and behavior as either signed char or unsigned char.35)
+     representation, and behavior as either signed char or unsigned char.[35]
 

-
 
 
Footnote 35) CHAR_MIN, defined in <limits.h>, will have one of the values 0 or SCHAR_MIN, and this can be
          used to distinguish the two options. Irrespective of the choice made, char is a separate type from the
          other two and is not compatible with either.
 

 
-
+
 
16   An enumeration comprises a set of named integer constant values. Each distinct
      enumeration constitutes a different enumerated type.
 

-
-
+
 
17   The type char, the signed and unsigned integer types, and the enumerated types are
      collectively called integer types. The integer and real floating types are collectively called
      real types.
 

-
-
+
 
18   Integer and floating types are collectively called arithmetic types. Each arithmetic type
      belongs to one type domain: the real type domain comprises the real types, the complex
      type domain comprises the complex types.
 

-
-
+
 
19   The void type comprises an empty set of values; it is an incomplete type that cannot be
      completed.
 

-
-
+
 
20   Any number of derived types can be constructed from the object, function, and
      incomplete types, as follows:
      -- An array type describes a contiguously allocated nonempty set of objects with a
-        particular member object type, called the element type.36) Array types are
+        particular member object type, called the element type.[36] Array types are
         characterized by their element type and by the number of elements in the array. An
         array type is said to be derived from its element type, and if its element type is T , the
         array type is sometimes called ``array of T ''. The construction of an array type from
@@ -2216,129 +1910,115 @@ Forward references:         conditional inclusion (6.10.1), complex arithmetic
         function type is said to be derived from its return type, and if its return type is T , the
         function type is sometimes called ``function returning T ''. The construction of a
         function type from a return type is called ``function type derivation''.
+

+
+
Footnote 36) Since object types do not include incomplete types, an array of incomplete type cannot be constructed.
      -- A pointer type may be derived from a function type, an object type, or an incomplete
         type, called the referenced type. A pointer type describes an object whose value
         provides a reference to an entity of the referenced type. A pointer type derived from
         the referenced type T is sometimes called ``pointer to T ''. The construction of a
         pointer type from a referenced type is called ``pointer type derivation''.
      These methods of constructing derived types can be applied recursively.
-

-
-
-
Footnote 36) Since object types do not include incomplete types, an array of incomplete type cannot be constructed.
 

 
-
+
 
21   Arithmetic types and pointer types are collectively called scalar types. Array and
-     structure types are collectively called aggregate types.37)
+     structure types are collectively called aggregate types.[37]
 

-
 
 
Footnote 37) Note that aggregate type does not include union type because an object with union type can only
          contain one member at a time.
 

 
-
+
 
22   An array type of unknown size is an incomplete type. It is completed, for an identifier of
      that type, by specifying the size in a later declaration (with internal or external linkage).
-     A structure or union type of unknown content (as described in 6.7.2.3) is an incomplete
+     A structure or union type of unknown content (as described in 6.7.2.3) is an incomplete
      type. It is completed, for all declarations of that type, by declaring the same structure or
      union tag with its defining content later in the same scope.
 

-
-
+
 
23   A type has known constant size if the type is not incomplete and is not a variable length
      array type.
 

-
-
+
 
24   Array, function, and pointer types are collectively called derived declarator types. A
      declarator type derivation from a type T is the construction of a derived declarator type
      from T by the application of an array-type, a function-type, or a pointer-type derivation to
      T.
 

-
-
+
 
25   A type is characterized by its type category , which is either the outermost derivation of a
      derived type (as noted above in the construction of derived types), or the type itself if the
      type consists of no derived types.
 

-
-
+
 
26   Any type so far mentioned is an unqualified type. Each unqualified type has several
-     qualified versions of its type,38) corresponding to the combinations of one, two, or all
+     qualified versions of its type,[38] corresponding to the combinations of one, two, or all
      three of the const, volatile, and restrict qualifiers. The qualified or unqualified
      versions of a type are distinct types that belong to the same type category and have the
-     same representation and alignment requirements.39) A derived type is not qualified by the
+     same representation and alignment requirements.[39] A derived type is not qualified by the
      qualifiers (if any) of the type from which it is derived.
 

-
 
-
Footnote 38) See 6.7.3 regarding qualified array and function types.
+
Footnote 38) See 6.7.3 regarding qualified array and function types.
 

 
 
 
Footnote 39) The same representation and alignment requirements are meant to imply interchangeability as
          arguments to functions, return values from functions, and members of unions.
-

-
-
-
27   A pointer to void shall have the same representation and alignment requirements as a
-     pointer to a character type.39) Similarly, pointers to qualified or unqualified versions of
-     compatible types shall have the same representation and alignment requirements. All
      pointers to structure types shall have the same representation and alignment requirements
      as each other. All pointers to union types shall have the same representation and
      alignment requirements as each other. Pointers to other types need not have the same
      representation or alignment requirements.
-

+

 
+
+
27   A pointer to void shall have the same representation and alignment requirements as a
+     pointer to a character type.[39] Similarly, pointers to qualified or unqualified versions of
+     compatible types shall have the same representation and alignment requirements. All
+

 
 
Footnote 39) The same representation and alignment requirements are meant to imply interchangeability as
          arguments to functions, return values from functions, and members of unions.
+     pointers to structure types shall have the same representation and alignment requirements
+     as each other. All pointers to union types shall have the same representation and
+     alignment requirements as each other. Pointers to other types need not have the same
+     representation or alignment requirements.
 

 
-
+
 
28   EXAMPLE 1 The type designated as ``float *'' has type ``pointer to float''. Its type category is
      pointer, not a floating type. The const-qualified version of this type is designated as ``float * const''
      whereas the type designated as ``const float *'' is not a qualified type -- its type is ``pointer to const-
      qualified float'' and is a pointer to a qualified type.
 
 

-
-
+
 
29   EXAMPLE 2 The type designated as ``struct tag (*[5])(float)'' has type ``array of pointer to
      function returning struct tag''. The array has length five and the function has a single parameter of type
      float. Its type category is array.
 
-     Forward references: compatible type and composite type (6.2.7), declarations (6.7).
+     Forward references: compatible type and composite type (6.2.7), declarations (6.7).
 

-
-
+
 

 
6.2.6 [Representations of types]

-
 Representations of types
-

-
-
+
 

 
6.2.6.1 [General]

-

-
-
+
 
1    The representations of all types are unspecified except as stated in this subclause.
 

-
-
+
 
2    Except for bit-fields, objects are composed of contiguous sequences of one or more bytes,
      the number, order, and encoding of which are either explicitly specified or
      implementation-defined.
 

-
-
+
 
3    Values stored in unsigned bit-fields and objects of type unsigned char shall be
-     represented using a pure binary notation.40)
+     represented using a pure binary notation.[40]
 

-
 
 
Footnote 40) A positional representation for integers that uses the binary digits 0 and 1, in which the values
          represented by successive bits are additive, begin with 1, and are multiplied by successive integral
@@ -2347,10 +2027,11 @@ Forward references:         conditional inclusion (6.10.1), complex arithmetic
          type unsigned char range from 0 to 2
                                                    CHAR_BIT
                                                              - 1.
+    a trap representation.
 

 
-
-
4    Values stored in non-bit-field objects of any other object type consist of n × CHAR_BIT
+
+
4    Values stored in non-bit-field objects of any other object type consist of n \xD7 CHAR_BIT
      bits, where n is the size of an object of that type, in bytes. The value may be copied into
      an object of type unsigned char [n] (e.g., by memcpy); the resulting set of bytes is
      called the object representation of the value. Values stored in bit-fields consist of m bits,
@@ -2359,49 +2040,43 @@ Forward references:         conditional inclusion (6.10.1), complex arithmetic
      than NaNs) with the same object representation compare equal, but values that compare
      equal may have different object representations.
 

-
-
+
 
5    Certain object representations need not represent a value of the object type. If the stored
      value of an object has such a representation and is read by an lvalue expression that does
      not have character type, the behavior is undefined. If such a representation is produced
      by a side effect that modifies all or any part of the object by an lvalue expression that
-     does not have character type, the behavior is undefined.41) Such a representation is called
-    a trap representation.
+     does not have character type, the behavior is undefined.[41] Such a representation is called
 

-
 
 
Footnote 41) Thus, an automatic variable can be initialized to a trap representation without causing undefined
         behavior, but the value of the variable cannot be used until a proper value is stored in it.
 

 
-
+
 
6   When a value is stored in an object of structure or union type, including in a member
     object, the bytes of the object representation that correspond to any padding bytes take
-    unspecified values.42) The value of a structure or union object is never a trap
+    unspecified values.[42] The value of a structure or union object is never a trap
     representation, even though the value of a member of the structure or union object may be
     a trap representation.
 

-
 
 
Footnote 42) Thus, for example, structure assignment need not copy any padding bits.
 

 
-
+
 
7   When a value is stored in a member of an object of union type, the bytes of the object
     representation that do not correspond to that member but do correspond to other members
     take unspecified values.
 

-
-
+
 
8   Where an operator is applied to a value that has more than one object representation,
-    which object representation is used shall not affect the value of the result.43) Where a
+    which object representation is used shall not affect the value of the result.[43] Where a
     value is stored in an object using a type that has more than one object representation for
     that value, it is unspecified which representation is used, but a trap representation shall
     not be generated.
-    Forward references: declarations (6.7), expressions (6.5), lvalues, arrays, and function
-    designators (6.3.2.1).
+    Forward references: declarations (6.7), expressions (6.5), lvalues, arrays, and function
+    designators (6.3.2.1).
 

-
 
 
Footnote 43) It is possible for objects x and y with the same effective type T to have the same value when they are
         accessed as objects of type T, but to have different values in other contexts. In particular, if == is
@@ -2410,31 +2085,23 @@ Forward references:         conditional inclusion (6.10.1), complex arithmetic
         on values of type T may distinguish between them.
 

 
-
+
 

 
6.2.6.2 [Integer types]

-

-
-
+
 
1   For unsigned integer types other than unsigned char, the bits of the object
     representation shall be divided into two groups: value bits and padding bits (there need
     not be any of the latter). If there are N value bits, each bit shall represent a different
     power of 2 between 1 and 2 N -1 , so that objects of that type shall be capable of
     representing values from 0 to 2 N - 1 using a pure binary representation; this shall be
-    known as the value representation. The values of any padding bits are unspecified.44)
+    known as the value representation. The values of any padding bits are unspecified.[44]
 

-
 
 
Footnote 44) Some combinations of padding bits might generate trap representations, for example, if one padding
         bit is a parity bit. Regardless, no arithmetic operation on valid values can generate a trap
         representation other than as part of an exceptional condition such as an overflow, and this cannot occur
         with unsigned types. All other combinations of padding bits are alternative object representations of
         the value specified by the value bits.
-

-
-
-
2   For signed integer types, the bits of the object representation shall be divided into three
-    groups: value bits, padding bits, and the sign bit. There need not be any padding bits;
     there shall be exactly one sign bit. Each bit that is a value bit shall have the same value as
     the same bit in the object representation of the corresponding unsigned type (if there are
     M value bits in the signed type and N in the unsigned type, then M  N ). If the sign bit
@@ -2448,9 +2115,13 @@ Forward references:         conditional inclusion (6.10.1), complex arithmetic
     complement), is a trap representation or a normal value. In the case of sign and
     magnitude and ones' complement, if this representation is a normal value it is called a
     negative zero.
-

+

 
-
+
+
2   For signed integer types, the bits of the object representation shall be divided into three
+    groups: value bits, padding bits, and the sign bit. There need not be any padding bits;
+

+
 
3   If the implementation supports negative zeros, they shall be generated only by:
     -- the &, |, ^, ~, <<, and >> operators with arguments that produce such a value;
     -- the +, -, *, /, and % operators where one argument is a negative zero and the result is
@@ -2459,44 +2130,38 @@ Forward references:         conditional inclusion (6.10.1), complex arithmetic
     It is unspecified whether these cases actually generate a negative zero or a normal zero,
     and whether a negative zero becomes a normal zero when stored in an object.
 

-
-
+
 
4   If the implementation does not support negative zeros, the behavior of the &, |, ^, ~, <<,
     and >> operators with arguments that would produce such a value is undefined.
 

-
-
-
5   The values of any padding bits are unspecified.45) A valid (non-trap) object representation
+
+
5   The values of any padding bits are unspecified.[45] A valid (non-trap) object representation
     of a signed integer type where the sign bit is zero is a valid object representation of the
     corresponding unsigned type, and shall represent the same value. For any integer type,
     the object representation where all the bits are zero shall be a representation of the value
     zero in that type.
 

-
 
 
Footnote 45) Some combinations of padding bits might generate trap representations, for example, if one padding
         bit is a parity bit. Regardless, no arithmetic operation on valid values can generate a trap
         representation other than as part of an exceptional condition such as an overflow. All other
         combinations of padding bits are alternative object representations of the value specified by the value
         bits.
+    for signed integer types the width is one greater than the precision.
 

 
-
+
 
6   The precision of an integer type is the number of bits it uses to represent values,
     excluding any sign and padding bits. The width of an integer type is the same but
     including any sign bit; thus for unsigned integer types the two values are the same, while
-    for signed integer types the width is one greater than the precision.
 

-
-
+
 

 
6.2.7 [Compatible type and composite type]

-

-
-
+
 
1   Two types have compatible type if their types are the same. Additional rules for
-    determining whether two types are compatible are described in 6.7.2 for type specifiers,
-    in 6.7.3 for type qualifiers, and in 6.7.5 for declarators.46) Moreover, two structure,
+    determining whether two types are compatible are described in 6.7.2 for type specifiers,
+    in 6.7.3 for type qualifiers, and in 6.7.5 for declarators.[46] Moreover, two structure,
     union, or enumerated types declared in separate translation units are compatible if their
     tags and members satisfy the following requirements: If one is declared with a tag, the
     other shall be declared with the same tag. If both are complete types, then the following
@@ -2508,17 +2173,15 @@ Forward references:         conditional inclusion (6.10.1), complex arithmetic
     bit-fields shall have the same widths. For two enumerations, corresponding members
     shall have the same values.
 

-
 
 
Footnote 46) Two types need not be identical to be compatible.
 

 
-
+
 
2   All declarations that refer to the same object or function shall have compatible type;
     otherwise, the behavior is undefined.
 

-
-
+
 
3   A composite type can be constructed from two types that are compatible; it is a type that
     is compatible with both of the two types and satisfies the following conditions:
     -- If one type is an array of known constant size, the composite type is an array of that
@@ -2530,19 +2193,17 @@ Forward references:         conditional inclusion (6.10.1), complex arithmetic
        parameters.
     These rules apply recursively to the types from which the two types are derived.
 

-
-
+
 
4   For an identifier with internal or external linkage declared in a scope in which a prior
-    declaration of that identifier is visible,47) if the prior declaration specifies internal or
+    declaration of that identifier is visible,[47] if the prior declaration specifies internal or
     external linkage, the type of the identifier at the later declaration becomes the composite
     type.
 

-
 
-
Footnote 47) As specified in 6.2.1, the later declaration might hide the prior declaration.
+
Footnote 47) As specified in 6.2.1, the later declaration might hide the prior declaration.
 

 
-
+
 
5   EXAMPLE        Given the following two file scope declarations:
              int f(int (*)(), double (*)[3]);
              int f(int (*)(char *), double (*)[]);
@@ -2550,38 +2211,28 @@ Forward references:         conditional inclusion (6.10.1), complex arithmetic
              int f(int (*)(char *), double (*)[3]);
 
 

-
-
+
 

 
6.3 [Conversions]

-

-
-
+
 
1   Several operators convert operand values from one type to another automatically. This
     subclause specifies the result required from such an implicit conversion, as well as those
-    that result from a cast operation (an explicit conversion). The list in 6.3.1.8 summarizes
+    that result from a cast operation (an explicit conversion). The list in 6.3.1.8 summarizes
     the conversions performed by most ordinary operators; it is supplemented as required by
-    the discussion of each operator in 6.5.
+    the discussion of each operator in 6.5.
 

-
-
+
 
2   Conversion of an operand value to a compatible type causes no change to the value or the
     representation.
-    Forward references: cast operators (6.5.4).
+    Forward references: cast operators (6.5.4).
 

-
-
+
 

 
6.3.1 [Arithmetic operands]

-
 Arithmetic operands
-

-
-
+
 

 
6.3.1.1 [Boolean, characters, and integers]

-

-
-
+
 
1   Every integer type has an integer conversion rank defined as follows:
     -- No two signed integer types shall have the same rank, even if they have the same
        representation.
@@ -2597,15 +2248,14 @@ Forward references:         conditional inclusion (6.10.1), complex arithmetic
     -- The rank of char shall equal the rank of signed char and unsigned char.
     -- The rank of _Bool shall be less than the rank of all other standard integer types.
     -- The rank of any enumerated type shall equal the rank of the compatible integer type
-       (see 6.7.2.2).
+       (see 6.7.2.2).
     -- The rank of any extended signed integer type relative to another extended signed
        integer type with the same precision is implementation-defined, but still subject to the
        other rules for determining the integer conversion rank.
     -- For all integer types T1, T2, and T3, if T1 has greater rank than T2 and T2 has
        greater rank than T3, then T1 has greater rank than T3.
 

-
-
+
 
2   The following may be used in an expression wherever an int or unsigned int may
     be used:
     -- An object or expression with an integer type whose integer conversion rank is less
@@ -2613,138 +2263,111 @@ Forward references:         conditional inclusion (6.10.1), complex arithmetic
     -- A bit-field of type _Bool, int, signed int, or unsigned int.
     If an int can represent all values of the original type, the value is converted to an int;
     otherwise, it is converted to an unsigned int. These are called the integer
-    promotions.48) All other types are unchanged by the integer promotions.
+    promotions.[48] All other types are unchanged by the integer promotions.
 

-
 
 
Footnote 48) The integer promotions are applied only: as part of the usual arithmetic conversions, to certain
         argument expressions, to the operands of the unary +, -, and ~ operators, and to both operands of the
         shift operators, as specified by their respective subclauses.
 

 
-
+
 
3   The integer promotions preserve value including sign. As discussed earlier, whether a
     ``plain'' char is treated as signed is implementation-defined.
-    Forward references: enumeration specifiers (6.7.2.2), structure and union specifiers
-    (6.7.2.1).
+    Forward references: enumeration specifiers (6.7.2.2), structure and union specifiers
+    (6.7.2.1).
 

-
-
+
 

 
6.3.1.2 [Boolean type]

-

-
-
+
 
1   When any scalar value is converted to _Bool, the result is 0 if the value compares equal
     to 0; otherwise, the result is 1.
 

-
-
+
 

 
6.3.1.3 [Signed and unsigned integers]

-

-
-
+
 
1   When a value with integer type is converted to another integer type other than _Bool, if
     the value can be represented by the new type, it is unchanged.
 

-
-
+
 
2   Otherwise, if the new type is unsigned, the value is converted by repeatedly adding or
     subtracting one more than the maximum value that can be represented in the new type
-    until the value is in the range of the new type.49)
+    until the value is in the range of the new type.[49]
 

-
 
 
Footnote 49) The rules describe arithmetic on the mathematical value, not the value of a given type of expression.
 

 
-
+
 
3   Otherwise, the new type is signed and the value cannot be represented in it; either the
     result is implementation-defined or an implementation-defined signal is raised.
 

-
-
+
 

 
6.3.1.4 [Real floating and integer]

-

-
-
+
 
1   When a finite value of real floating type is converted to an integer type other than _Bool,
     the fractional part is discarded (i.e., the value is truncated toward zero). If the value of
-    the integral part cannot be represented by the integer type, the behavior is undefined.50)
+    the integral part cannot be represented by the integer type, the behavior is undefined.[50]
 

-
 
 
Footnote 50) The remaindering operation performed when a value of integer type is converted to unsigned type
         need not be performed when a value of real floating type is converted to unsigned type. Thus, the
         range of portable real floating values is (-1, Utype_MAX+1).
-

-
-
-
2   When a value of integer type is converted to a real floating type, if the value being
-    converted can be represented exactly in the new type, it is unchanged. If the value being
-    converted is in the range of values that can be represented but cannot be represented
     exactly, the result is either the nearest higher or nearest lower representable value, chosen
     in an implementation-defined manner. If the value being converted is outside the range of
     values that can be represented, the behavior is undefined.
-

+

 
-
+
+
2   When a value of integer type is converted to a real floating type, if the value being
+    converted can be represented exactly in the new type, it is unchanged. If the value being
+    converted is in the range of values that can be represented but cannot be represented
+

+
 

 
6.3.1.5 [Real floating types]

-

-
-
+
 
1   When a float is promoted to double or long double, or a double is promoted
     to long double, its value is unchanged (if the source value is represented in the
     precision and range of its type).
 

-
-
+
 
2   When a double is demoted to float, a long double is demoted to double or
     float, or a value being represented in greater precision and range than required by its
-    semantic type (see 6.3.1.8) is explicitly converted (including to its own type), if the value
+    semantic type (see 6.3.1.8) is explicitly converted (including to its own type), if the value
     being converted can be represented exactly in the new type, it is unchanged. If the value
     being converted is in the range of values that can be represented but cannot be
     represented exactly, the result is either the nearest higher or nearest lower representable
     value, chosen in an implementation-defined manner. If the value being converted is
     outside the range of values that can be represented, the behavior is undefined.
 

-
-
+
 

 
6.3.1.6 [Complex types]

-

-
-
+
 
1   When a value of complex type is converted to another complex type, both the real and
     imaginary parts follow the conversion rules for the corresponding real types.
 

-
-
+
 

 
6.3.1.7 [Real and complex]

-

-
-
+
 
1   When a value of real type is converted to a complex type, the real part of the complex
     result value is determined by the rules of conversion to the corresponding real type and
     the imaginary part of the complex result value is a positive zero or an unsigned zero.
 

-
-
+
 
2   When a value of complex type is converted to a real type, the imaginary part of the
     complex value is discarded and the value of the real part is converted according to the
     conversion rules for the corresponding real type.
 

-
-
+
 

 
6.3.1.8 [Usual arithmetic conversions]

-

-
-
+
 
1   Many operators that expect operands of arithmetic type cause conversions and yield result
     types in a similar way. The purpose is to determine a common real type for the operands
     and result. For the specified operands, each operand is converted, without change of type
@@ -2760,7 +2383,7 @@ Forward references:         conditional inclusion (6.10.1), complex arithmetic
           corresponding real type is double.
           Otherwise, if the corresponding real type of either operand is float, the other
           operand is converted, without change of type domain, to a type whose
-          corresponding real type is float.51)
+          corresponding real type is float.[51]
           Otherwise, the integer promotions are performed on both operands. Then the
           following rules are applied to the promoted operands:
                  If both operands have the same type, then no further conversion is needed.
@@ -2778,36 +2401,29 @@ Forward references:         conditional inclusion (6.10.1), complex arithmetic
                  Otherwise, both operands are converted to the unsigned integer type
                  corresponding to the type of the operand with signed integer type.
 

-
 
 
Footnote 51) For example, addition of a double _Complex and a float entails just the conversion of the
         float operand to double (and yields a double _Complex result).
 

 
-
+
 
2   The values of floating operands and of the results of floating expressions may be
     represented in greater precision and range than that required by the type; the types are not
-    changed thereby.52)
+    changed thereby.[52]
 

-
 
 
Footnote 52) The cast and assignment operators are still required to perform their specified conversions as
-        described in 6.3.1.4 and 6.3.1.5.
+        described in 6.3.1.4 and 6.3.1.5.
 

 
-
+
 

 
6.3.2 [Other operands]

-
 Other operands
-

-
-
+
 

 
6.3.2.1 [Lvalues, arrays, and function designators]

-

-
-
-
1   An lvalue is an expression with an object type or an incomplete type other than void;53)
+
+
1   An lvalue is an expression with an object type or an incomplete type other than void;[53]
     if an lvalue does not designate an object when it is evaluated, the behavior is undefined.
     When an object is said to have a particular type, the type is specified by the lvalue used to
     designate the object. A modifiable lvalue is an lvalue that does not have array type, does
@@ -2815,7 +2431,6 @@ Forward references:         conditional inclusion (6.10.1), complex arithmetic
     or union, does not have any member (including, recursively, any member or element of
     all contained aggregates or unions) with a const-qualified type.
 

-
 
 
Footnote 53) The name ``lvalue'' comes originally from the assignment expression E1 = E2, in which the left
         operand E1 is required to be a (modifiable) lvalue. It is perhaps better considered as representing an
@@ -2825,7 +2440,7 @@ Forward references:         conditional inclusion (6.10.1), complex arithmetic
          expression that is a pointer to an object, *E is an lvalue that designates the object to which E points.
 

 
-
+
 
2   Except when it is the operand of the sizeof operator, the unary & operator, the ++
     operator, the -- operator, or the left operand of the . operator or an assignment operator,
     an lvalue that does not have array type is converted to the value stored in the designated
@@ -2834,128 +2449,111 @@ Forward references:         conditional inclusion (6.10.1), complex arithmetic
     lvalue. If the lvalue has an incomplete type and does not have array type, the behavior is
     undefined.
 

-
-
+
 
3   Except when it is the operand of the sizeof operator or the unary & operator, or is a
     string literal used to initialize an array, an expression that has type ``array of type'' is
     converted to an expression with type ``pointer to type'' that points to the initial element of
     the array object and is not an lvalue. If the array object has register storage class, the
     behavior is undefined.
 

-
-
+
 
4   A function designator is an expression that has function type. Except when it is the
-    operand of the sizeof operator54) or the unary & operator, a function designator with
+    operand of the sizeof operator[54] or the unary & operator, a function designator with
     type ``function returning type'' is converted to an expression that has type ``pointer to
     function returning type''.
-    Forward references: address and indirection operators (6.5.3.2), assignment operators
-    (6.5.16), common definitions <stddef.h> (7.17), initialization (6.7.8), postfix
-    increment and decrement operators (6.5.2.4), prefix increment and decrement operators
-    (6.5.3.1), the sizeof operator (6.5.3.4), structure and union members (6.5.2.3).
+    Forward references: address and indirection operators (6.5.3.2), assignment operators
+    (6.5.16), common definitions <stddef.h> (7.17), initialization (6.7.8), postfix
+    increment and decrement operators (6.5.2.4), prefix increment and decrement operators
+    (6.5.3.1), the sizeof operator (6.5.3.4), structure and union members (6.5.2.3).
 

-
 
 
Footnote 54) Because this conversion does not occur, the operand of the sizeof operator remains a function
-        designator and violates the constraint in 6.5.3.4.
+        designator and violates the constraint in 6.5.3.4.
 

 
-
+
 

 
6.3.2.2 [void]

-

-
-
+
 
1   The (nonexistent) value of a void expression (an expression that has type void) shall not
     be used in any way, and implicit or explicit conversions (except to void) shall not be
     applied to such an expression. If an expression of any other type is evaluated as a void
     expression, its value or designator is discarded. (A void expression is evaluated for its
     side effects.)
 

-
-
+
 

 
6.3.2.3 [Pointers]

-

-
-
+
 
1   A pointer to void may be converted to or from a pointer to any incomplete or object
     type. A pointer to any incomplete or object type may be converted to a pointer to void
     and back again; the result shall compare equal to the original pointer.
 

-
-
+
 
2   For any qualifier q , a pointer to a non-q -qualified type may be converted to a pointer to
     the q -qualified version of the type; the values stored in the original and converted pointers
     shall compare equal.
 

-
-
+
 
3   An integer constant expression with the value 0, or such an expression cast to type
-    void *, is called a null pointer constant .55) If a null pointer constant is converted to a
+    void *, is called a null pointer constant .[55] If a null pointer constant is converted to a
     pointer type, the resulting pointer, called a null pointer , is guaranteed to compare unequal
     to a pointer to any object or function.
 

-
 
-
Footnote 55) The macro NULL is defined in <stddef.h> (and other headers) as a null pointer constant; see 7.17.
+
Footnote 55) The macro NULL is defined in <stddef.h> (and other headers) as a null pointer constant; see 7.17.
 

 
-
+
 
4   Conversion of a null pointer to another pointer type yields a null pointer of that type.
     Any two null pointers shall compare equal.
 

-
-
+
 
5   An integer may be converted to any pointer type. Except as previously specified, the
     result is implementation-defined, might not be correctly aligned, might not point to an
-    entity of the referenced type, and might be a trap representation.56)
+    entity of the referenced type, and might be a trap representation.[56]
 

-
 
 
Footnote 56) The mapping functions for converting a pointer to an integer or an integer to a pointer are intended to
         be consistent with the addressing structure of the execution environment.
 

 
-
+
 
6   Any pointer type may be converted to an integer type. Except as previously specified, the
     result is implementation-defined. If the result cannot be represented in the integer type,
     the behavior is undefined. The result need not be in the range of values of any integer
     type.
 

-
-
+
 
7   A pointer to an object or incomplete type may be converted to a pointer to a different
-    object or incomplete type. If the resulting pointer is not correctly aligned57) for the
+    object or incomplete type. If the resulting pointer is not correctly aligned[57] for the
     pointed-to type, the behavior is undefined. Otherwise, when converted back again, the
     result shall compare equal to the original pointer. When a pointer to an object is
-    converted to a pointer to a character type, the result points to the lowest addressed byte of
-    the object. Successive increments of the result, up to the size of the object, yield pointers
-    to the remaining bytes of the object.
 

-
 
 
Footnote 57) In general, the concept ``correctly aligned'' is transitive: if a pointer to type A is correctly aligned for a
         pointer to type B, which in turn is correctly aligned for a pointer to type C, then a pointer to type A is
         correctly aligned for a pointer to type C.
+    converted to a pointer to a character type, the result points to the lowest addressed byte of
+    the object. Successive increments of the result, up to the size of the object, yield pointers
+    to the remaining bytes of the object.
 

 
-
+
 
8   A pointer to a function of one type may be converted to a pointer to a function of another
     type and back again; the result shall compare equal to the original pointer. If a converted
     pointer is used to call a function whose type is not compatible with the pointed-to type,
     the behavior is undefined.
-    Forward references: cast operators (6.5.4), equality operators (6.5.9), integer types
-    capable of holding object pointers (7.18.1.4), simple assignment (6.5.16.1).
+    Forward references: cast operators (6.5.4), equality operators (6.5.9), integer types
+    capable of holding object pointers (7.18.1.4), simple assignment (6.5.16.1).
 
 

-
-
+
 

 
6.4 [Lexical elements]

-

-
-
-
1            token:
+
+
1 Syntax
+            token:
                       keyword
                       identifier
                       constant
@@ -2971,36 +2569,33 @@ Forward references:         conditional inclusion (6.10.1), complex arithmetic
                     each non-white-space character that cannot be one of the above
     Constraints
 

-
-
+
 
2   Each preprocessing token that is converted to a token shall have the lexical form of a
     keyword, an identifier, a constant, a string literal, or a punctuator.
     Semantics
 

-
-
+
 
3   A token is the minimal lexical element of the language in translation phases 7 and 8. The
     categories of tokens are: keywords, identifiers, constants, string literals, and punctuators.
     A preprocessing token is the minimal lexical element of the language in translation
     phases 3 through 6. The categories of preprocessing tokens are: header names,
     identifiers, preprocessing numbers, character constants, string literals, punctuators, and
     single non-white-space characters that do not lexically match the other preprocessing
-    token categories.58) If a ' or a " character matches the last category, the behavior is
+    token categories.[58] If a ' or a " character matches the last category, the behavior is
     undefined. Preprocessing tokens can be separated by white space; this consists of
     comments (described later), or white-space characters (space, horizontal tab, new-line,
-    vertical tab, and form-feed), or both. As described in 6.10, in certain circumstances
+    vertical tab, and form-feed), or both. As described in 6.10, in certain circumstances
     during translation phase 4, white space (or the absence thereof) serves as more than
     preprocessing token separation. White space may appear within a preprocessing token
     only as part of a header name or between the quotation characters in a character constant
     or string literal.
 

-
 
-
Footnote 58) An additional category, placemarkers, is used internally in translation phase 4 (see 6.10.3.3); it cannot
+
Footnote 58) An additional category, placemarkers, is used internally in translation phase 4 (see 6.10.3.3); it cannot
         occur in source files.
 

 
-
+
 
4   If the input stream has been parsed into preprocessing tokens up to a given character, the
     next preprocessing token is the longest sequence of characters that could constitute a
     preprocessing token. There is one exception to this rule: header name preprocessing
@@ -3009,8 +2604,7 @@ Forward references:         conditional inclusion (6.10.1), complex arithmetic
     sequence of characters that could be either a header name or a string literal is recognized
     as the former.
 

-
-
+
 
5   EXAMPLE 1 The program fragment 1Ex is parsed as a preprocessing number token (one that is not a
     valid floating or integer constant token), even though a parse as the pair of preprocessing tokens 1 and Ex
     might produce a valid expression (for example, if Ex were a macro defined as +1). Similarly, the program
@@ -3018,25 +2612,22 @@ Forward references:         conditional inclusion (6.10.1), complex arithmetic
     not E is a macro name.
 
 

-
-
+
 
6   EXAMPLE 2 The program fragment x+++++y is parsed as x ++ ++ + y, which violates a constraint on
     increment operators, even though the parse x ++ + ++ y might yield a correct expression.
 
-    Forward references: character constants (6.4.4.4), comments (6.4.9), expressions (6.5),
-    floating constants (6.4.4.2), header names (6.4.7), macro replacement (6.10.3), postfix
-    increment and decrement operators (6.5.2.4), prefix increment and decrement operators
-    (6.5.3.1), preprocessing directives (6.10), preprocessing numbers (6.4.8), string literals
-    (6.4.5).
+    Forward references: character constants (6.4.4.4), comments (6.4.9), expressions (6.5),
+    floating constants (6.4.4.2), header names (6.4.7), macro replacement (6.10.3), postfix
+    increment and decrement operators (6.5.2.4), prefix increment and decrement operators
+    (6.5.3.1), preprocessing directives (6.10), preprocessing numbers (6.4.8), string literals
+    (6.4.5).
 

-
-
+
 

 
6.4.1 [Keywords]

-

-
-
-
1            keyword: one of
+
+
1 Syntax
+            keyword: one of
                    auto                     enum                  restrict              unsigned
                    break                    extern                return                void
                    case                     float                 short                 volatile
@@ -3049,30 +2640,24 @@ Forward references:         conditional inclusion (6.10.1), complex arithmetic
                    else                     register              union
     Semantics
 

-
-
+
 
2   The above tokens (case sensitive) are reserved (in translation phases 7 and 8) for use as
     keywords, and shall not be used otherwise. The keyword _Imaginary is reserved for
-    specifying imaginary types.59)
+    specifying imaginary types.[59]
 

-
 
 
Footnote 59) One possible specification for imaginary types appears in annex G.
 

 
-
+
 

 
6.4.2 [Identifiers]

-
 Identifiers
-

-
-
+
 

 
6.4.2.1 [General]

-

-
-
-
1            identifier:
+
+
1 Syntax
+            identifier:
                       identifier-nondigit
                       identifier identifier-nondigit
                       identifier digit
@@ -3089,75 +2674,66 @@ Forward references:         conditional inclusion (6.10.1), complex arithmetic
                     0 1        2     3    4    5    6     7    8    9
     Semantics
 

-
-
+
 
2   An identifier is a sequence of nondigit characters (including the underscore _, the
     lowercase and uppercase Latin letters, and other characters) and digits, which designates
-    one or more entities as described in 6.2.1. Lowercase and uppercase letters are distinct.
+    one or more entities as described in 6.2.1. Lowercase and uppercase letters are distinct.
     There is no specific limit on the maximum length of an identifier.
 

-
-
+
 
3   Each universal character name in an identifier shall designate a character whose encoding
-    in ISO/IEC 10646 falls into one of the ranges specified in annex D.60) The initial
+    in ISO/IEC 10646 falls into one of the ranges specified in annex D.[60] The initial
     character shall not be a universal character name designating a digit. An implementation
     may allow multibyte characters that are not part of the basic source character set to
     appear in identifiers; which characters and their correspondence to universal character
     names is implementation-defined.
 

-
 
 
Footnote 60) On systems in which linkers cannot accept extended characters, an encoding of the universal character
         name may be used in forming valid external identifiers. For example, some otherwise unused
         character or sequence of characters may be used to encode the \u in a universal character name.
         Extended characters may produce a long external identifier.
+    Implementation limits
 

 
-
+
 
4   When preprocessing tokens are converted to tokens during translation phase 7, if a
     preprocessing token could be converted to either a keyword or an identifier, it is converted
     to a keyword.
-    Implementation limits
 

-
-
-
5   As discussed in 5.2.4.1, an implementation may limit the number of significant initial
+
+
5   As discussed in 5.2.4.1, an implementation may limit the number of significant initial
     characters in an identifier; the limit for an external name (an identifier that has external
     linkage) may be more restrictive than that for an internal name (a macro name or an
     identifier that does not have external linkage). The number of significant characters in an
     identifier is implementation-defined.
 

-
-
+
 
6   Any identifiers that differ in a significant character are different identifiers. If two
     identifiers differ only in nonsignificant characters, the behavior is undefined.
-    Forward references: universal character names (6.4.3), macro replacement (6.10.3).
+    Forward references: universal character names (6.4.3), macro replacement (6.10.3).
 

-
-
+
 

 
6.4.2.2 [Predefined identifiers]

-

-
-
-
1   The identifier _ _func_ _ shall be implicitly declared by the translator as if,
+
+
1 Semantics
+   The identifier _ _func_ _ shall be implicitly declared by the translator as if,
     immediately following the opening brace of each function definition, the declaration
              static const char _ _func_ _[] = "function-name";
-    appeared, where function-name is the name of the lexically-enclosing function.61)
+    appeared, where function-name is the name of the lexically-enclosing function.[61]
 

-
 
-
Footnote 61) Since the name _ _func_ _ is reserved for any use by the implementation (7.1.3), if any other
+
Footnote 61) Since the name _ _func_ _ is reserved for any use by the implementation (7.1.3), if any other
         identifier is explicitly declared using the name _ _func_ _, the behavior is undefined.
 

 
-
+
 
2   This name is encoded as if the implicit declaration had been written in the source
     character set and then translated into the execution character set as indicated in translation
     phase 5.
 

-
-
+
 
3   EXAMPLE        Consider the code fragment:
              #include <stdio.h>
              void myfunc(void)
@@ -3168,16 +2744,14 @@ Forward references:         conditional inclusion (6.10.1), complex arithmetic
     Each time the function is called, it will print to the standard output stream:
              myfunc
 
-    Forward references: function definitions (6.9.1).
+    Forward references: function definitions (6.9.1).
 

-
-
+
 

 
6.4.3 [Universal character names]

-

-
-
-
1            universal-character-name:
+
+
1 Syntax
+            universal-character-name:
                     \u hex-quad
                     \U hex-quad hex-quad
              hex-quad:
@@ -3185,68 +2759,59 @@ Forward references:         conditional inclusion (6.10.1), complex arithmetic
                                  hexadecimal-digit hexadecimal-digit
     Constraints
 

-
-
+
 
2   A universal character name shall not specify a character whose short identifier is less than
     00A0 other than 0024 ($), 0040 (@), or 0060 (`), nor one in the range D800 through
-    DFFF inclusive.62)
+    DFFF inclusive.[62]
     Description
 

-
 
 
Footnote 62) The disallowed characters are the characters in the basic character set and the code positions reserved
         by ISO/IEC 10646 for control characters, the character DELETE, and the S-zone (reserved for use by
         UTF-16).
 

 
-
+
 
3   Universal character names may be used in identifiers, character constants, and string
     literals to designate characters that are not in the basic character set.
     Semantics
 

-
-
+
 
4   The universal character name \Unnnnnnnn designates the character whose eight-digit
-    short identifier (as specified by ISO/IEC 10646) is nnnnnnnn.63) Similarly, the universal
+    short identifier (as specified by ISO/IEC 10646) is nnnnnnnn.[63] Similarly, the universal
     character name \unnnn designates the character whose four-digit short identifier is nnnn
     (and whose eight-digit short identifier is 0000 nnnn).
 

-
 
 
Footnote 63) Short identifiers for characters were first specified in ISO/IEC 10646-1/AMD9:1997.
 

 
-
+
 

 
6.4.4 [Constants]

-

-
-
-
1            constant:
+
+
1 Syntax
+            constant:
                     integer-constant
                     floating-constant
                     enumeration-constant
                     character-constant
     Constraints
 

-
-
+
 
2   Each constant shall have a type and the value of a constant shall be in the range of
     representable values for its type.
     Semantics
 

-
-
+
 
3   Each constant has a type, determined by its form and value, as detailed later.
 

-
-
+
 

 
6.4.4.1 [Integer constants]

-

-
-
-
1            integer-constant:
+
+
1 Syntax
+            integer-constant:
                      decimal-constant integer-suffixopt
                      octal-constant integer-suffixopt
                      hexadecimal-constant integer-suffixopt
@@ -3282,13 +2847,11 @@ Forward references:         conditional inclusion (6.10.1), complex arithmetic
                   ll LL
     Description
 

-
-
+
 
2   An integer constant begins with a digit, but has no period or exponent part. It may have a
     prefix that specifies its base and a suffix that specifies its type.
 

-
-
+
 
3   A decimal constant begins with a nonzero digit and consists of a sequence of decimal
     digits. An octal constant consists of the prefix 0 optionally followed by a sequence of the
     digits 0 through 7 only. A hexadecimal constant consists of the prefix 0x or 0X followed
@@ -3296,13 +2859,11 @@ Forward references:         conditional inclusion (6.10.1), complex arithmetic
     10 through 15 respectively.
     Semantics
 

-
-
+
 
4   The value of a decimal constant is computed base 10; that of an octal constant, base 8;
     that of a hexadecimal constant, base 16. The lexically first digit is the most significant.
 

-
-
+
 
5   The type of an integer constant is the first of the corresponding list in which its value can
     be represented.
 
@@ -3334,8 +2895,7 @@ Forward references:         conditional inclusion (6.10.1), complex arithmetic
     Both u or U         unsigned long long int                 unsigned long long int
     and ll or LL
 

-
-
+
 
6   If an integer constant cannot be represented by any type in its list, it may have an
     extended integer type, if the extended integer type can represent its value. If all of the
     types in the list for the constant are signed, the extended integer type shall be signed. If
@@ -3345,14 +2905,12 @@ Forward references:         conditional inclusion (6.10.1), complex arithmetic
     its list and has no extended integer type, then the integer constant has no type.
 
 

-
-
+
 

 
6.4.4.2 [Floating constants]

-

-
-
-
1            floating-constant:
+
+
1 Syntax
+            floating-constant:
                      decimal-floating-constant
                      hexadecimal-floating-constant
              decimal-floating-constant:
@@ -3388,8 +2946,7 @@ Forward references:         conditional inclusion (6.10.1), complex arithmetic
                      f l F L
     Description
 

-
-
+
 
2   A floating constant has a significand part that may be followed by an exponent part and a
     suffix that specifies its type. The components of the significand part may include a digit
     sequence representing the whole-number part, followed by a period (.), followed by a
@@ -3399,8 +2956,7 @@ Forward references:         conditional inclusion (6.10.1), complex arithmetic
     constants, either the period or the exponent part has to be present.
     Semantics
 

-
-
+
 
3   The significand part is interpreted as a (decimal or hexadecimal) rational number; the
     digit sequence in the exponent part is interpreted as a decimal integer. For decimal
     floating constants, the exponent indicates the power of 10 by which the significand part is
@@ -3412,60 +2968,51 @@ Forward references:         conditional inclusion (6.10.1), complex arithmetic
     For hexadecimal floating constants when FLT_RADIX is a power of 2, the result is
     correctly rounded.
 

-
-
+
 
4   An unsuffixed floating constant has type double. If suffixed by the letter f or F, it has
     type float. If suffixed by the letter l or L, it has type long double.
 

-
-
+
 
5   Floating constants are converted to internal format as if at translation-time. The
     conversion of a floating constant shall not raise an exceptional condition or a floating-
     point exception at execution time.
     Recommended practice
 

-
-
+
 
6   The implementation should produce a diagnostic message if a hexadecimal constant
     cannot be represented exactly in its evaluation format; the implementation should then
     proceed with the translation of the program.
 

-
-
+
 
7   The translation-time conversion of floating constants should match the execution-time
     conversion of character strings by library functions, such as strtod, given matching
     inputs suitable for both conversions, the same result format, and default execution-time
-    rounding.64)
+    rounding.[64]
 

-
 
 
Footnote 64) The specification for the library functions recommends more accurate conversion than required for
-        floating constants (see 7.20.1.3).
+        floating constants (see 7.20.1.3).
 

 
-
+
 

 
6.4.4.3 [Enumeration constants]

-

-
-
-
1            enumeration-constant:
+
+
1 Syntax
+            enumeration-constant:
                    identifier
     Semantics
 

-
-
+
 
2   An identifier declared as an enumeration constant has type int.
-    Forward references: enumeration specifiers (6.7.2.2).
+    Forward references: enumeration specifiers (6.7.2.2).
 

-
-
+
 

 
6.4.4.4 [Character constants]

-

-
-
-
1            character-constant:
+
+
1 Syntax
+            character-constant:
                     ' c-char-sequence '
                     L' c-char-sequence '
              c-char-sequence:
@@ -3492,16 +3039,14 @@ Forward references:         conditional inclusion (6.10.1), complex arithmetic
                    hexadecimal-escape-sequence hexadecimal-digit
     Description
 

-
-
+
 
2   An integer character constant is a sequence of one or more multibyte characters enclosed
     in single-quotes, as in 'x'. A wide character constant is the same, except prefixed by the
     letter L. With a few exceptions detailed later, the elements of the sequence are any
     members of the source character set; they are mapped in an implementation-defined
     manner to members of the execution character set.
 

-
-
+
 
3   The single-quote ', the double-quote ", the question-mark ?, the backslash \, and
     arbitrary integer values are representable according to the following table of escape
     sequences:
@@ -3512,54 +3057,47 @@ Forward references:         conditional inclusion (6.10.1), complex arithmetic
            octal character                \octal digits
            hexadecimal character          \x hexadecimal digits
 

-
-
+
 
4   The double-quote " and question-mark ? are representable either by themselves or by the
     escape sequences \" and \?, respectively, but the single-quote ' and the backslash \
     shall be represented, respectively, by the escape sequences \' and \\.
 

-
-
+
 
5   The octal digits that follow the backslash in an octal escape sequence are taken to be part
     of the construction of a single character for an integer character constant or of a single
     wide character for a wide character constant. The numerical value of the octal integer so
     formed specifies the value of the desired character or wide character.
 

-
-
+
 
6   The hexadecimal digits that follow the backslash and the letter x in a hexadecimal escape
     sequence are taken to be part of the construction of a single character for an integer
     character constant or of a single wide character for a wide character constant. The
     numerical value of the hexadecimal integer so formed specifies the value of the desired
     character or wide character.
 

-
-
+
 
7   Each octal or hexadecimal escape sequence is the longest sequence of characters that can
     constitute the escape sequence.
 

-
-
+
 
8   In addition, characters not in the basic character set are representable by universal
     character names and certain nongraphic characters are representable by escape sequences
     consisting of the backslash \ followed by a lowercase letter: \a, \b, \f, \n, \r, \t,
-    and \v.65)
-     Constraints
+    and \v.[65]
 

-
 
-
Footnote 65) The semantics of these characters were discussed in 5.2.2. If any other character follows a backslash,
-        the result is not a token and a diagnostic is required. See ``future language directions'' (6.11.4).
+
Footnote 65) The semantics of these characters were discussed in 5.2.2. If any other character follows a backslash,
+        the result is not a token and a diagnostic is required. See ``future language directions'' (6.11.4).
+     Constraints
 

 
-
+
 
9    The value of an octal or hexadecimal escape sequence shall be in the range of
      representable values for the type unsigned char for an integer character constant, or
      the unsigned type corresponding to wchar_t for a wide character constant.
      Semantics
 

-
-
+
 
10   An integer character constant has type int. The value of an integer character constant
      containing a single character that maps to a single-byte execution character is the
      numerical value of the representation of the mapped character interpreted as an integer.
@@ -3570,8 +3108,7 @@ Forward references:         conditional inclusion (6.10.1), complex arithmetic
      type char whose value is that of the single character or escape sequence is converted to
      type int.
 

-
-
+
 
11   A wide character constant has type wchar_t, an integer type defined in the
      <stddef.h> header. The value of a wide character constant containing a single
      multibyte character that maps to a member of the extended execution character set is the
@@ -3581,21 +3118,18 @@ Forward references:         conditional inclusion (6.10.1), complex arithmetic
      character or escape sequence not represented in the extended execution character set, is
      implementation-defined.
 

-
-
+
 
12   EXAMPLE 1      The construction '\0' is commonly used to represent the null character.
 
 

-
-
+
 
13   EXAMPLE 2 Consider implementations that use two's-complement representation for integers and eight
      bits for objects that have type char. In an implementation in which type char has the same range of
      values as signed char, the integer character constant '\xFF' has the value -1; if type char has the
      same range of values as unsigned char, the character constant '\xFF' has the value +255.
 
 

-
-
+
 
14   EXAMPLE 3 Even if eight bits are used for objects that have type char, the construction '\x123'
      specifies an integer character constant containing only one character, since a hexadecimal escape sequence
      is terminated only by a non-hexadecimal character. To specify an integer character constant containing the
@@ -3604,24 +3138,21 @@ Forward references:         conditional inclusion (6.10.1), complex arithmetic
      constant is implementation-defined.)
 
 

-
-
+
 
15   EXAMPLE 4 Even if 12 or more bits are used for objects that have type wchar_t, the construction
      L'\1234' specifies the implementation-defined value that results from the combination of the values
      0123 and '4'.
 
-     Forward references: common definitions <stddef.h> (7.17), the mbtowc function
-     (7.20.7.2).
+     Forward references: common definitions <stddef.h> (7.17), the mbtowc function
+     (7.20.7.2).
 
 

-
-
+
 

 
6.4.5 [String literals]

-

-
-
-
1            string-literal:
+
+
1 Syntax
+            string-literal:
                      " s-char-sequenceopt "
                      L" s-char-sequenceopt "
              s-char-sequence:
@@ -3633,14 +3164,12 @@ Forward references:         conditional inclusion (6.10.1), complex arithmetic
                        escape-sequence
     Description
 

-
-
+
 
2   A character string literal is a sequence of zero or more multibyte characters enclosed in
     double-quotes, as in "xyz". A wide string literal is the same, except prefixed by the
     letter L.
 

-
-
+
 
3   The same considerations apply to each element of the sequence in a character string
     literal or a wide string literal as if it were in an integer character constant or a wide
     character constant, except that the single-quote ' is representable either by itself or by the
@@ -3648,57 +3177,51 @@ Forward references:         conditional inclusion (6.10.1), complex arithmetic
     \".
     Semantics
 

-
-
+
 
4   In translation phase 6, the multibyte character sequences specified by any sequence of
     adjacent character and wide string literal tokens are concatenated into a single multibyte
     character sequence. If any of the tokens are wide string literal tokens, the resulting
     multibyte character sequence is treated as a wide string literal; otherwise, it is treated as a
     character string literal.
 

-
-
+
 
5   In translation phase 7, a byte or code of value zero is appended to each multibyte
-    character sequence that results from a string literal or literals.66) The multibyte character
+    character sequence that results from a string literal or literals.[66] The multibyte character
     sequence is then used to initialize an array of static storage duration and length just
     sufficient to contain the sequence. For character string literals, the array elements have
     type char, and are initialized with the individual bytes of the multibyte character
     sequence; for wide string literals, the array elements have type wchar_t, and are
     initialized with the sequence of wide characters corresponding to the multibyte character
+

+
+
Footnote 66) A character string literal need not be a string (see 7.1.1), because a null character may be embedded in
+        it by a \0 escape sequence.
     sequence, as defined by the mbstowcs function with an implementation-defined current
     locale. The value of a string literal containing a multibyte character or escape sequence
     not represented in the execution character set is implementation-defined.
-

-
-
-
Footnote 66) A character string literal need not be a string (see 7.1.1), because a null character may be embedded in
-        it by a \0 escape sequence.
 

 
-
+
 
6   It is unspecified whether these arrays are distinct provided their elements have the
     appropriate values. If the program attempts to modify such an array, the behavior is
     undefined.
 

-
-
+
 
7   EXAMPLE       This pair of adjacent character string literals
              "\x12" "3"
     produces a single character string literal containing the two characters whose values are '\x12' and '3',
     because escape sequences are converted into single members of the execution character set just prior to
     adjacent string literal concatenation.
 
-    Forward references: common definitions <stddef.h> (7.17), the mbstowcs
-    function (7.20.8.1).
+    Forward references: common definitions <stddef.h> (7.17), the mbstowcs
+    function (7.20.8.1).
 

-
-
+
 

 
6.4.6 [Punctuators]

-

-
-
-
1            punctuator: one of
+
+
1 Syntax
+            punctuator: one of
                     [ ] ( ) { } . ->
                     ++ -- & * + - ~ !
                     / % << >> < > <= >=                               ==     !=     ^    |     &&     ||
@@ -3708,8 +3231,7 @@ Forward references:         conditional inclusion (6.10.1), complex arithmetic
                     <: :> <% %> %: %:%:
     Semantics
 

-
-
+
 
2   A punctuator is a symbol that has independent syntactic and semantic significance.
     Depending on context, it may specify an operation to be performed (which in turn may
     yield a value or a function designator, produce a side effect, or some combination thereof)
@@ -3717,33 +3239,33 @@ Forward references:         conditional inclusion (6.10.1), complex arithmetic
     contexts). An operand is an entity on which an operator acts.
 
 

-
-
-
3   In all aspects of the language, the six tokens67)
+
+
3   In all aspects of the language, the six tokens[67]
              <:    :>      <%    %>     %:     %:%:
     behave, respectively, the same as the six tokens
              [     ]       {     }      #      ##
-    except for their spelling.68)
-    Forward references: expressions (6.5), declarations (6.7), preprocessing directives
-    (6.10), statements (6.8).
+    except for their spelling.[68]
+    Forward references: expressions (6.5), declarations (6.7), preprocessing directives
+    (6.10), statements (6.8).
 

-
 
 
Footnote 67) These tokens are sometimes called ``digraphs''.
 

 
 
-
Footnote 68) Thus [ and <: behave differently when ``stringized'' (see 6.10.3.2), but can otherwise be freely
+
Footnote 68) Thus [ and <: behave differently when ``stringized'' (see 6.10.3.2), but can otherwise be freely
         interchanged.
+    sequence between the " delimiters, the behavior is undefined.69) Header name
+    preprocessing tokens are recognized only within #include preprocessing directives and
+    in implementation-defined locations within #pragma directives.70)
 

 
-
+
 

 
6.4.7 [Header names]

-

-
-
-
1            header-name:
+
+
1 Syntax
+            header-name:
                     < h-char-sequence >
                     " q-char-sequence "
              h-char-sequence:
@@ -3760,29 +3282,15 @@ Forward references:         conditional inclusion (6.10.1), complex arithmetic
                                     the new-line character and "
     Semantics
 

-
-
+
 
2   The sequences in both forms of header names are mapped in an implementation-defined
-    manner to headers or external source file names as specified in 6.10.2.
+    manner to headers or external source file names as specified in 6.10.2.
 

-
-
+
 
3   If the characters ', \, ", //, or /* occur in the sequence between the < and > delimiters,
     the behavior is undefined. Similarly, if the characters ', \, //, or /* occur in the
-    sequence between the " delimiters, the behavior is undefined.69) Header name
-    preprocessing tokens are recognized only within #include preprocessing directives and
-    in implementation-defined locations within #pragma directives.70)
 

-
-
-
Footnote 69) Thus, sequences of characters that resemble escape sequences cause undefined behavior.
-

-
-
-
Footnote 70) For an example of a header name preprocessing token used in a #pragma directive, see 6.10.9.
-

-
-
+
 
4   EXAMPLE       The following sequence of characters:
              0x3<1/a.h>1e2
              #include <1/a.h>
@@ -3793,16 +3301,14 @@ Forward references:         conditional inclusion (6.10.1), complex arithmetic
              {#}{include} {<1/a.h>}
              {#}{define} {const}{.}{member}{@}{$}
 
-    Forward references: source file inclusion (6.10.2).
+    Forward references: source file inclusion (6.10.2).
 

-
-
+
 

 
6.4.8 [Preprocessing numbers]

-

-
-
-
1            pp-number:
+
+
1 Syntax
+            pp-number:
                    digit
                    . digit
                    pp-number       digit
@@ -3814,47 +3320,39 @@ Forward references:         conditional inclusion (6.10.1), complex arithmetic
                    pp-number       .
     Description
 

-
-
+
 
2   A preprocessing number begins with a digit optionally preceded by a period (.) and may
     be followed by valid identifier characters and the character sequences e+, e-, E+, E-,
     p+, p-, P+, or P-.
 

-
-
+
 
3   Preprocessing number tokens lexically include all floating and integer constant tokens.
     Semantics
 

-
-
+
 
4   A preprocessing number does not have type or a value; it acquires both after a successful
     conversion (as part of translation phase 7) to a floating constant token or an integer
     constant token.
 

-
-
+
 

 
6.4.9 [Comments]

-

-
-
+
 
1   Except within a character constant, a string literal, or a comment, the characters /*
     introduce a comment. The contents of such a comment are examined only to identify
-    multibyte characters and to find the characters */ that terminate it.71)
+    multibyte characters and to find the characters */ that terminate it.[71]
 

-
 
 
Footnote 71) Thus, /* ... */ comments do not nest.
 

 
-
+
 
2   Except within a character constant, a string literal, or a comment, the characters //
     introduce a comment that includes all multibyte characters up to, but not including, the
     next new-line character. The contents of such a comment are examined only to identify
     multibyte characters and to find the terminating new-line character.
 

-
-
+
 
3   EXAMPLE
             "a//b"                              //   four-character string literal
             #include "//e"                      //   undefined behavior
@@ -3870,24 +3368,19 @@ Forward references:         conditional inclusion (6.10.1), complex arithmetic
             m = n//**/o
                + p;                             // equivalent to m = n + p;
 

-
-
+
 

 
6.5 [Expressions]

-

-
-
+
 
1   An expression is a sequence of operators and operands that specifies computation of a
     value, or that designates an object or a function, or that generates side effects, or that
     performs a combination thereof.
 

-
-
+
 
2   Between the previous and next sequence point an object shall have its stored value
-    modified at most once by the evaluation of an expression.72) Furthermore, the prior value
-    shall be read only to determine the value to be stored.73)
+    modified at most once by the evaluation of an expression.[72] Furthermore, the prior value
+    shall be read only to determine the value to be stored.[73]
 

-
 
 
Footnote 72) A floating-point status flag is not an object and can be set more than once within an expression.
 

@@ -3901,41 +3394,41 @@ Forward references:         conditional inclusion (6.10.1), complex arithmetic
                    a[i] = i;
 

 
-
-
3   The grouping of operators and operands is indicated by the syntax.74) Except as specified
+
+
3   The grouping of operators and operands is indicated by the syntax.[74] Except as specified
     later (for the function-call (), &&, ||, ?:, and comma operators), the order of evaluation
     of subexpressions and the order in which side effects take place are both unspecified.
 

-
 
 
Footnote 74) The syntax specifies the precedence of operators in the evaluation of an expression, which is the same
         as the order of the major subclauses of this subclause, highest precedence first. Thus, for example, the
-        expressions allowed as the operands of the binary + operator (6.5.6) are those expressions defined in
-        6.5.1 through 6.5.6. The exceptions are cast expressions (6.5.4) as operands of unary operators
-        (6.5.3), and an operand contained between any of the following pairs of operators: grouping
-        parentheses () (6.5.1), subscripting brackets [] (6.5.2.1), function-call parentheses () (6.5.2.2), and
-        the conditional operator ?: (6.5.15).
+        expressions allowed as the operands of the binary + operator (6.5.6) are those expressions defined in
+        6.5.1 through 6.5.6. The exceptions are cast expressions (6.5.4) as operands of unary operators
+        (6.5.3), and an operand contained between any of the following pairs of operators: grouping
+        parentheses () (6.5.1), subscripting brackets [] (6.5.2.1), function-call parentheses () (6.5.2.2), and
+        the conditional operator ?: (6.5.15).
            Within each major subclause, the operators have the same precedence. Left- or right-associativity is
            indicated in each subclause by the syntax for the expressions discussed therein.
 

 
-
+
 
4   Some operators (the unary operator ~, and the binary operators <<, >>, &, ^, and |,
     collectively described as bitwise operators) are required to have operands that have
     integer type. These operators yield values that depend on the internal representations of
     integers, and have implementation-defined and undefined aspects for signed types.
 

-
-
+
 
5   If an exceptional condition occurs during the evaluation of an expression (that is, if the
     result is not mathematically defined or not in the range of representable values for its
     type), the behavior is undefined.
 

-
-
+
 
6   The effective type of an object for an access to its stored value is the declared type of the
-    object, if any.75) If a value is stored into an object having no declared type through an
+    object, if any.[75] If a value is stored into an object having no declared type through an
     lvalue having a type that is not a character type, then the type of the lvalue becomes the
+

+
+
Footnote 75) Allocated objects have no declared type.
     effective type of the object for that access and for subsequent accesses that do not modify
     the stored value. If a value is copied into an object having no declared type using
     memcpy or memmove, or is copied as an array of character type, then the effective type
@@ -3943,15 +3436,11 @@ Forward references:         conditional inclusion (6.10.1), complex arithmetic
     value is the effective type of the object from which the value is copied, if it has one. For
     all other accesses to an object having no declared type, the effective type of the object is
     simply the type of the lvalue used for the access.
-

-
-
-
Footnote 75) Allocated objects have no declared type.
 

 
-
+
 
7   An object shall have its stored value accessed only by an lvalue expression that has one of
-    the following types:76)
+    the following types:[76]
     -- a type compatible with the effective type of the object,
     -- a qualified version of a type compatible with the effective type of the object,
     -- a type that is the signed or unsigned type corresponding to the effective type of the
@@ -3962,20 +3451,18 @@ Forward references:         conditional inclusion (6.10.1), complex arithmetic
        members (including, recursively, a member of a subaggregate or contained union), or
     -- a character type.
 

-
 
 
Footnote 76) The intent of this list is to specify those circumstances in which an object may or may not be aliased.
 

 
-
+
 
8   A floating expression may be contracted , that is, evaluated as though it were an atomic
     operation, thereby omitting rounding errors implied by the source code and the
-    expression evaluation method.77) The FP_CONTRACT pragma in <math.h> provides a
+    expression evaluation method.[77] The FP_CONTRACT pragma in <math.h> provides a
     way to disallow contracted expressions. Otherwise, whether and how expressions are
-    contracted is implementation-defined.78)
-    Forward references: the FP_CONTRACT pragma (7.12.2), copying functions (7.21.2).
+    contracted is implementation-defined.[78]
+    Forward references: the FP_CONTRACT pragma (7.12.2), copying functions (7.21.2).
 

-
 
 
Footnote 77) A contracted expression might also omit the raising of floating-point exceptions.
 

@@ -3987,26 +3474,23 @@ Forward references:         conditional inclusion (6.10.1), complex arithmetic
         documented.
 

 
-
+
 

 
6.5.1 [Primary expressions]

-

-
-
-
1            primary-expression:
+
+
1 Syntax
+            primary-expression:
                     identifier
                     constant
                     string-literal
                     ( expression )
     Semantics
 

-
-
+
 
2   An identifier is a primary expression, provided it has been declared as designating an
     object (in which case it is an lvalue) or a function (in which case it is a function
-    designator).79)
+    designator).[79]
 

-
 
 
Footnote 79) Thus, an undeclared identifier is a violation of the syntax.
              argument-expression-list:
@@ -4014,29 +3498,25 @@ Forward references:         conditional inclusion (6.10.1), complex arithmetic
                    argument-expression-list , assignment-expression
 

 
-
-
3   A constant is a primary expression. Its type depends on its form and value, as detailed in 6.4.4.
+
+
3   A constant is a primary expression. Its type depends on its form and value, as detailed in 6.4.4.
 

-
-
-
4   A string literal is a primary expression. It is an lvalue with type as detailed in 6.4.5.
+
+
4   A string literal is a primary expression. It is an lvalue with type as detailed in 6.4.5.
 

-
-
+
 
5   A parenthesized expression is a primary expression. Its type and value are identical to
     those of the unparenthesized expression. It is an lvalue, a function designator, or a void
     expression if the unparenthesized expression is, respectively, an lvalue, a function
     designator, or a void expression.
-    Forward references: declarations (6.7).
+    Forward references: declarations (6.7).
 

-
-
+
 

 
6.5.2 [Postfix operators]

-

-
-
-
1            postfix-expression:
+
+
1 Syntax
+            postfix-expression:
                      primary-expression
                      postfix-expression [ expression ]
                      postfix-expression ( argument-expression-listopt )
@@ -4047,19 +3527,16 @@ Forward references:         conditional inclusion (6.10.1), complex arithmetic
                      ( type-name ) { initializer-list }
                      ( type-name ) { initializer-list , }
 

-
-
+
 

 
6.5.2.1 [Array subscripting]

-

-
-
-
1   One of the expressions shall have type ``pointer to object type'', the other expression shall
+
+
1 Constraints
+   One of the expressions shall have type ``pointer to object type'', the other expression shall
     have integer type, and the result has type ``type''.
     Semantics
 

-
-
+
 
2   A postfix expression followed by an expression in square brackets [] is a subscripted
     designation of an element of an array object. The definition of the subscript operator []
     is that E1[E2] is identical to (*((E1)+(E2))). Because of the conversion rules that
@@ -4067,21 +3544,19 @@ Forward references:         conditional inclusion (6.10.1), complex arithmetic
     initial element of an array object) and E2 is an integer, E1[E2] designates the E2-th
     element of E1 (counting from zero).
 

-
-
+
 
3   Successive subscript operators designate an element of a multidimensional array object.
-    If E is an n-dimensional array ( n  2) with dimensions i × j × . . . × k , then E (used as
+    If E is an n-dimensional array ( n  2) with dimensions i \xD7 j \xD7 . . . \xD7 k , then E (used as
     other than an lvalue) is converted to a pointer to an ( n - 1)-dimensional array with
-    dimensions j × . . . × k . If the unary * operator is applied to this pointer explicitly, or
+    dimensions j \xD7 . . . \xD7 k . If the unary * operator is applied to this pointer explicitly, or
     implicitly as a result of subscripting, the result is the pointed-to ( n - 1)-dimensional array,
     which itself is converted into a pointer if used as other than an lvalue. It follows from this
     that arrays are stored in row-major order (last subscript varies fastest).
 

-
-
+
 
4   EXAMPLE        Consider the array object defined by the declaration
              int x[3][5];
-    Here x is a 3 × 5 array of ints; more precisely, x is an array of three element objects, each of which is an
+    Here x is a 3 \xD7 5 array of ints; more precisely, x is an array of three element objects, each of which is an
     array of five ints. In the expression x[i], which is equivalent to (*((x)+(i))), x is first converted to
     a pointer to the initial array of five ints. Then i is adjusted according to the type of x, which conceptually
     entails multiplying i by the size of the object to which the pointer points, namely an array of five int
@@ -4089,61 +3564,58 @@ Forward references:         conditional inclusion (6.10.1), complex arithmetic
     expression x[i][j], that array is in turn converted to a pointer to the first of the ints, so x[i][j]
     yields an int.
 
-    Forward references: additive operators (6.5.6), address and indirection operators
-    (6.5.3.2), array declarators (6.7.5.2).
+    Forward references: additive operators (6.5.6), address and indirection operators
+    (6.5.3.2), array declarators (6.7.5.2).
 
 

-
-
+
 

 
6.5.2.2 [Function calls]

-

-
-
-
1   The expression that denotes the called function80) shall have type pointer to function
+
+
1 Constraints
+   The expression that denotes the called function[80] shall have type pointer to function
     returning void or returning an object type other than an array type.
 

-
 
 
Footnote 80) Most often, this is the result of converting an identifier that is a function designator.
 

 
-
+
 
2   If the expression that denotes the called function has a type that includes a prototype, the
     number of arguments shall agree with the number of parameters. Each argument shall
     have a type such that its value may be assigned to an object with the unqualified version
     of the type of its corresponding parameter.
     Semantics
 

-
-
+
 
3   A postfix expression followed by parentheses () containing a possibly empty, comma-
     separated list of expressions is a function call. The postfix expression denotes the called
     function. The list of expressions specifies the arguments to the function.
 

-
-
+
 
4   An argument may be an expression of any object type. In preparing for the call to a
     function, the arguments are evaluated, and each parameter is assigned the value of the
-    corresponding argument.81)
+    corresponding argument.[81]
 

-
 
 
Footnote 81) A function may change the values of its parameters, but these changes cannot affect the values of the
         arguments. On the other hand, it is possible to pass a pointer to an object, and the function may
         change the value of the object pointed to. A parameter declared to have array or function type is
-        adjusted to have a pointer type as described in 6.9.1.
+        adjusted to have a pointer type as described in 6.9.1.
+     -- one promoted type is a signed integer type, the other promoted type is the
+        corresponding unsigned integer type, and the value is representable in both types;
+     -- both types are pointers to qualified or unqualified versions of a character type or
+        void.
 

 
-
+
 
5   If the expression that denotes the called function has type pointer to function returning an
     object type, the function call expression has the same type as that object type, and has the
-    value determined as specified in 6.8.6.4. Otherwise, the function call has type void. If
+    value determined as specified in 6.8.6.4. Otherwise, the function call has type void. If
     an attempt is made to modify the result of a function call or to access it after the next
     sequence point, the behavior is undefined.
 

-
-
+
 
6   If the expression that denotes the called function has a type that does not include a
     prototype, the integer promotions are performed on each argument, and arguments that
     have type float are promoted to double. These are called the default argument
@@ -4154,13 +3626,8 @@ Forward references:         conditional inclusion (6.10.1), complex arithmetic
     If the function is defined with a type that does not include a prototype, and the types of
     the arguments after promotion are not compatible with those of the parameters after
     promotion, the behavior is undefined, except for the following cases:
-     -- one promoted type is a signed integer type, the other promoted type is the
-        corresponding unsigned integer type, and the value is representable in both types;
-     -- both types are pointers to qualified or unqualified versions of a character type or
-        void.
 

-
-
+
 
7    If the expression that denotes the called function has a type that does include a prototype,
      the arguments are implicitly converted, as if by assignment, to the types of the
      corresponding parameters, taking the type of each parameter to be the unqualified version
@@ -4168,86 +3635,75 @@ Forward references:         conditional inclusion (6.10.1), complex arithmetic
      argument type conversion to stop after the last declared parameter. The default argument
      promotions are performed on trailing arguments.
 

-
-
+
 
8    No other conversions are performed implicitly; in particular, the number and types of
      arguments are not compared with those of the parameters in a function definition that
      does not include a function prototype declarator.
 

-
-
+
 
9    If the function is defined with a type that is not compatible with the type (of the
      expression) pointed to by the expression that denotes the called function, the behavior is
      undefined.
 

-
-
+
 
10   The order of evaluation of the function designator, the actual arguments, and
      subexpressions within the actual arguments is unspecified, but there is a sequence point
      before the actual call.
 

-
-
+
 
11   Recursive function calls shall be permitted, both directly and indirectly through any chain
      of other functions.
 

-
-
+
 
12   EXAMPLE       In the function call
              (*pf[f1()]) (f2(), f3() + f4())
      the functions f1, f2, f3, and f4 may be called in any order. All side effects have to be completed before
      the function pointed to by pf[f1()] is called.
 
-     Forward references: function declarators (including prototypes) (6.7.5.3), function
-     definitions (6.9.1), the return statement (6.8.6.4), simple assignment (6.5.16.1).
+     Forward references: function declarators (including prototypes) (6.7.5.3), function
+     definitions (6.9.1), the return statement (6.8.6.4), simple assignment (6.5.16.1).
 

-
-
+
 

 
6.5.2.3 [Structure and union members]

-

-
-
-
1    The first operand of the . operator shall have a qualified or unqualified structure or union
+
+
1 Constraints
+    The first operand of the . operator shall have a qualified or unqualified structure or union
      type, and the second operand shall name a member of that type.
 

-
-
+
 
2    The first operand of the -> operator shall have type ``pointer to qualified or unqualified
      structure'' or ``pointer to qualified or unqualified union'', and the second operand shall
      name a member of the type pointed to.
 
     Semantics
 

-
-
+
 
3   A postfix expression followed by the . operator and an identifier designates a member of
-    a structure or union object. The value is that of the named member,82) and is an lvalue if
+    a structure or union object. The value is that of the named member,[82] and is an lvalue if
     the first expression is an lvalue. If the first expression has qualified type, the result has
     the so-qualified version of the type of the designated member.
 

-
 
 
Footnote 82) If the member used to access the contents of a union object is not the same as the member last used to
         store a value in the object, the appropriate part of the object representation of the value is reinterpreted
-        as an object representation in the new type as described in 6.2.6 (a process sometimes called "type
+        as an object representation in the new type as described in 6.2.6 (a process sometimes called "type
         punning"). This might be a trap representation.
 

 
-
+
 
4   A postfix expression followed by the -> operator and an identifier designates a member
     of a structure or union object. The value is that of the named member of the object to
-    which the first expression points, and is an lvalue.83) If the first expression is a pointer to
+    which the first expression points, and is an lvalue.[83] If the first expression is a pointer to
     a qualified type, the result has the so-qualified version of the type of the designated
     member.
 

-
 
 
Footnote 83) If &E is a valid pointer expression (where & is the ``address-of '' operator, which generates a pointer to
-        its operand), the expression (&E)->MOS is the same as E.MOS.
+        its operand), the expression (&E)->MOS is the same as E.MOS.
 

 
-
+
 
5   One special guarantee is made in order to simplify the use of unions: if a union contains
     several structures that share a common initial sequence (see below), and if the union
     object currently contains one of these structures, it is permitted to inspect the common
@@ -4256,14 +3712,12 @@ Forward references:         conditional inclusion (6.10.1), complex arithmetic
     compatible types (and, for bit-fields, the same widths) for a sequence of one or more
     initial members.
 

-
-
+
 
6   EXAMPLE 1 If f is a function returning a structure or union, and x is a member of that structure or
     union, f().x is a valid postfix expression but is not an lvalue.
 
 

-
-
+
 
7   EXAMPLE 2       In:
              struct s { int i; const int ci; };
              struct s s;
@@ -4277,8 +3731,7 @@ Forward references:         conditional inclusion (6.10.1), complex arithmetic
              vs.i         volatile int
              vs.ci        volatile const int
 

-
-
+
 
8   EXAMPLE 3       The following is a valid fragment:
              union {
                      struct {
@@ -4294,7 +3747,7 @@ Forward references:         conditional inclusion (6.10.1), complex arithmetic
                      } nf;
              } u;
              u.nf.type = 1;
-             u.nf.doublenode = 3.14;
+             u.nf.doublenode = 3.14;
              /* ... */
              if (u.n.alltypes == 1)
                      if (sin(u.nf.doublenode) == 0.0)
@@ -4318,23 +3771,20 @@ Forward references:         conditional inclusion (6.10.1), complex arithmetic
                    return f(&u.s1, &u.s2);
              }
 
-    Forward references: address and indirection operators (6.5.3.2), structure and union
-    specifiers (6.7.2.1).
+    Forward references: address and indirection operators (6.5.3.2), structure and union
+    specifiers (6.7.2.1).
 
 

-
-
+
 

 
6.5.2.4 [Postfix increment and decrement operators]

-

-
-
-
1   The operand of the postfix increment or decrement operator shall have qualified or
+
+
1 Constraints
+   The operand of the postfix increment or decrement operator shall have qualified or
     unqualified real or pointer type and shall be a modifiable lvalue.
     Semantics
 

-
-
+
 
2   The result of the postfix ++ operator is the value of the operand. After the result is
     obtained, the value of the operand is incremented. (That is, the value 1 of the appropriate
     type is added to it.) See the discussions of additive operators and compound assignment
@@ -4342,81 +3792,70 @@ Forward references:         conditional inclusion (6.10.1), complex arithmetic
     pointers. The side effect of updating the stored value of the operand shall occur between
     the previous and the next sequence point.
 

-
-
+
 
3   The postfix -- operator is analogous to the postfix ++ operator, except that the value of
     the operand is decremented (that is, the value 1 of the appropriate type is subtracted from
     it).
-    Forward references: additive operators (6.5.6), compound assignment (6.5.16.2).
+    Forward references: additive operators (6.5.6), compound assignment (6.5.16.2).
 

-
-
+
 

 
6.5.2.5 [Compound literals]

-

-
-
-
1   The type name shall specify an object type or an array of unknown size, but not a variable
+
+
1 Constraints
+   The type name shall specify an object type or an array of unknown size, but not a variable
     length array type.
 

-
-
+
 
2   No initializer shall attempt to provide a value for an object not contained within the entire
     unnamed object specified by the compound literal.
 

-
-
+
 
3   If the compound literal occurs outside the body of a function, the initializer list shall
     consist of constant expressions.
     Semantics
 

-
-
+
 
4   A postfix expression that consists of a parenthesized type name followed by a brace-
     enclosed list of initializers is a compound literal . It provides an unnamed object whose
-    value is given by the initializer list.84)
+    value is given by the initializer list.[84]
 

-
 
 
Footnote 84) Note that this differs from a cast expression. For example, a cast specifies a conversion to scalar types
         or void only, and the result of a cast expression is not an lvalue.
 

 
-
+
 
5   If the type name specifies an array of unknown size, the size is determined by the
-    initializer list as specified in 6.7.8, and the type of the compound literal is that of the
+    initializer list as specified in 6.7.8, and the type of the compound literal is that of the
     completed array type. Otherwise (when the type name specifies an object type), the type
     of the compound literal is that specified by the type name. In either case, the result is an
     lvalue.
 

-
-
+
 
6    The value of the compound literal is that of an unnamed object initialized by the
      initializer list. If the compound literal occurs outside the body of a function, the object
      has static storage duration; otherwise, it has automatic storage duration associated with
      the enclosing block.
 

-
-
-
7    All the semantic rules and constraints for initializer lists in 6.7.8 are applicable to
-     compound literals.85)
+
+
7    All the semantic rules and constraints for initializer lists in 6.7.8 are applicable to
+     compound literals.[85]
 

-
 
 
Footnote 85) For example, subobjects without explicit initializers are initialized to zero.
 

 
-
+
 
8    String literals, and compound literals with const-qualified types, need not designate
-     distinct objects.86)
+     distinct objects.[86]
 

-
 
 
Footnote 86) This allows implementations to share storage for string literals and constant compound literals with
          the same or overlapping representations.
 

 
-
+
 
9    EXAMPLE 1       The file scope definition
               int *p = (int []){2, 4};
      initializes p to point to the first element of an array of two ints, the first having the value two and the
@@ -4424,8 +3863,7 @@ Forward references:         conditional inclusion (6.10.1), complex arithmetic
      has static storage duration.
 
 

-
-
+
 
10   EXAMPLE 2       In contrast, in
               void f(void)
               {
@@ -4439,8 +3877,7 @@ Forward references:         conditional inclusion (6.10.1), complex arithmetic
      unnamed object has automatic storage duration.
 
 

-
-
+
 
11   EXAMPLE 3 Initializers with designations can be combined with compound literals. Structure objects
      created using compound literals can be passed to functions without depending on member order:
               drawline((struct point){.x=1, .y=1},
@@ -4450,13 +3887,11 @@ Forward references:         conditional inclusion (6.10.1), complex arithmetic
                     &(struct point){.x=3, .y=4});
 
 

-
-
+
 
12   EXAMPLE 4       A read-only compound literal can be specified through constructions like:
               (const float []){1e0, 1e1, 1e2, 1e3, 1e4, 1e5, 1e6}
 

-
-
+
 
13   EXAMPLE 5        The following three expressions have different meanings:
               "/tmp/fileXXXXXX"
               (char []){"/tmp/fileXXXXXX"}
@@ -4466,16 +3901,14 @@ Forward references:         conditional inclusion (6.10.1), complex arithmetic
      two is modifiable.
 
 

-
-
+
 
14   EXAMPLE 6 Like string literals, const-qualified compound literals can be placed into read-only memory
      and can even be shared. For example,
               (const char []){"abc"} == "abc"
      might yield 1 if the literals' storage is shared.
 
 

-
-
+
 
15   EXAMPLE 7 Since compound literals are unnamed, a single compound literal cannot specify a circularly
      linked object. For example, there is no way to write a self-referential compound literal that could be used
      as the function argument in place of the named object endless_zeros below:
@@ -4484,8 +3917,7 @@ Forward references:         conditional inclusion (6.10.1), complex arithmetic
               eval(endless_zeros);
 
 

-
-
+
 
16   EXAMPLE 8        Each compound literal creates only a single object in a given scope:
               struct s { int i; };
               int f (void)
@@ -4499,23 +3931,20 @@ Forward references:         conditional inclusion (6.10.1), complex arithmetic
               }
      The function f() always returns the value 1.
 

-
-
+
 
17   Note that if an iteration statement were used instead of an explicit goto and a labeled statement, the
      lifetime of the unnamed object would be the body of the loop only, and on entry next time around p would
      have an indeterminate value, which would result in undefined behavior.
 
-     Forward references: type names (6.7.6), initialization (6.7.8).
+     Forward references: type names (6.7.6), initialization (6.7.8).
 
 

-
-
+
 

 
6.5.3 [Unary operators]

-

-
-
-
1            unary-expression:
+
+
1 Syntax
+            unary-expression:
                     postfix-expression
                     ++ unary-expression
                     -- unary-expression
@@ -4525,48 +3954,40 @@ Forward references:         conditional inclusion (6.10.1), complex arithmetic
              unary-operator: one of
                     & * + - ~             !
 

-
-
+
 

 
6.5.3.1 [Prefix increment and decrement operators]

-

-
-
-
1   The operand of the prefix increment or decrement operator shall have qualified or
+
+
1 Constraints
+   The operand of the prefix increment or decrement operator shall have qualified or
     unqualified real or pointer type and shall be a modifiable lvalue.
     Semantics
 

-
-
+
 
2   The value of the operand of the prefix ++ operator is incremented. The result is the new
     value of the operand after incrementation. The expression ++E is equivalent to (E+=1).
     See the discussions of additive operators and compound assignment for information on
     constraints, types, side effects, and conversions and the effects of operations on pointers.
 

-
-
+
 
3   The prefix -- operator is analogous to the prefix ++ operator, except that the value of the
     operand is decremented.
-    Forward references: additive operators (6.5.6), compound assignment (6.5.16.2).
+    Forward references: additive operators (6.5.6), compound assignment (6.5.16.2).
 

-
-
+
 

 
6.5.3.2 [Address and indirection operators]

-

-
-
-
1   The operand of the unary & operator shall be either a function designator, the result of a
+
+
1 Constraints
+   The operand of the unary & operator shall be either a function designator, the result of a
     [] or unary * operator, or an lvalue that designates an object that is not a bit-field and is
     not declared with the register storage-class specifier.
 

-
-
+
 
2   The operand of the unary * operator shall have pointer type.
     Semantics
 

-
-
+
 
3   The unary & operator yields the address of its operand. If the operand has type ``type'',
     the result has type ``pointer to type''. If the operand is the result of a unary * operator,
     neither that operator nor the & operator is evaluated and the result is as if both were
@@ -4576,17 +3997,15 @@ Forward references:         conditional inclusion (6.10.1), complex arithmetic
     were removed and the [] operator were changed to a + operator. Otherwise, the result is
     a pointer to the object or function designated by its operand.
 

-
-
+
 
4   The unary * operator denotes indirection. If the operand points to a function, the result is
     a function designator; if it points to an object, the result is an lvalue designating the
     object. If the operand has type ``pointer to type'', the result has type ``type''. If an
     invalid value has been assigned to the pointer, the behavior of the unary * operator is
-    undefined.87)
-    Forward references: storage-class specifiers (6.7.1), structure and union specifiers
-    (6.7.2.1).
+    undefined.[87]
+    Forward references: storage-class specifiers (6.7.1), structure and union specifiers
+    (6.7.2.1).
 

-
 
 
Footnote 87) Thus, &*E is equivalent to E (even if E is a null pointer), and &(E1[E2]) to ((E1)+(E2)). It is
         always true that if E is a function designator or an lvalue that is a valid operand of the unary &
@@ -4597,86 +4016,77 @@ Forward references:         conditional inclusion (6.10.1), complex arithmetic
          end of its lifetime.
 

 
-
+
 

 
6.5.3.3 [Unary arithmetic operators]

-

-
-
-
1   The operand of the unary + or - operator shall have arithmetic type; of the ~ operator,
+
+
1 Constraints
+   The operand of the unary + or - operator shall have arithmetic type; of the ~ operator,
     integer type; of the ! operator, scalar type.
     Semantics
 

-
-
+
 
2   The result of the unary + operator is the value of its (promoted) operand. The integer
     promotions are performed on the operand, and the result has the promoted type.
 

-
-
+
 
3   The result of the unary - operator is the negative of its (promoted) operand. The integer
     promotions are performed on the operand, and the result has the promoted type.
 

-
-
+
 
4   The result of the ~ operator is the bitwise complement of its (promoted) operand (that is,
     each bit in the result is set if and only if the corresponding bit in the converted operand is
     not set). The integer promotions are performed on the operand, and the result has the
     promoted type. If the promoted type is an unsigned type, the expression ~E is equivalent
     to the maximum value representable in that type minus E.
 

-
-
+
 
5   The result of the logical negation operator ! is 0 if the value of its operand compares
     unequal to 0, 1 if the value of its operand compares equal to 0. The result has type int.
     The expression !E is equivalent to (0==E).
 

-
-
+
 

 
6.5.3.4 [The sizeof operator]

-

-
-
-
1   The sizeof operator shall not be applied to an expression that has function type or an
+
+
1 Constraints
+   The sizeof operator shall not be applied to an expression that has function type or an
     incomplete type, to the parenthesized name of such a type, or to an expression that
     designates a bit-field member.
     Semantics
 

-
-
+
 
2   The sizeof operator yields the size (in bytes) of its operand, which may be an
     expression or the parenthesized name of a type. The size is determined from the type of
     the operand. The result is an integer. If the type of the operand is a variable length array
     type, the operand is evaluated; otherwise, the operand is not evaluated and the result is an
     integer constant.
 

-
-
+
 
3   When applied to an operand that has type char, unsigned char, or signed char,
     (or a qualified version thereof) the result is 1. When applied to an operand that has array
-    type, the result is the total number of bytes in the array.88) When applied to an operand
+    type, the result is the total number of bytes in the array.[88] When applied to an operand
     that has structure or union type, the result is the total number of bytes in such an object,
     including internal and trailing padding.
 

-
 
 
Footnote 88) When applied to a parameter declared to have array or function type, the sizeof operator yields the
-        size of the adjusted (pointer) type (see 6.9.1).
+        size of the adjusted (pointer) type (see 6.9.1).
              int main()
              {
                    size_t size;
                    size = fsize3(10); // fsize3 returns 13
                    return 0;
              }
+    Forward references: common definitions <stddef.h> (7.17), declarations (6.7),
+    structure and union specifiers (6.7.2.1), type names (6.7.6), array declarators (6.7.5.2).
 

 
-
+
 
4   The value of the result is implementation-defined, and its type (an unsigned integer type)
     is size_t, defined in <stddef.h> (and other headers).
 

-
-
+
 
5   EXAMPLE 1 A principal use of the sizeof operator is in communication with routines such as storage
     allocators and I/O systems. A storage-allocation function might accept a size (in bytes) of an object to
     allocate and return a pointer to void. For example:
@@ -4686,14 +4096,12 @@ Forward references:         conditional inclusion (6.10.1), complex arithmetic
     conversion to a pointer to double.
 
 

-
-
+
 
6   EXAMPLE 2      Another use of the sizeof operator is to compute the number of elements in an array:
             sizeof array / sizeof array[0]
 
 

-
-
+
 
7   EXAMPLE 3      In this example, the size of a variable length array is computed and returned from a
     function:
             #include <stddef.h>
@@ -4702,147 +4110,122 @@ Forward references:         conditional inclusion (6.10.1), complex arithmetic
                   char b[n+3];                  // variable length array
                   return sizeof b;              // execution time sizeof
             }
-
-    Forward references: common definitions <stddef.h> (7.17), declarations (6.7),
-    structure and union specifiers (6.7.2.1), type names (6.7.6), array declarators (6.7.5.2).
 

-
-
+
 

 
6.5.4 [Cast operators]

-

-
-
-
1            cast-expression:
+
+
1 Syntax
+            cast-expression:
                     unary-expression
                     ( type-name ) cast-expression
     Constraints
 

-
-
+
 
2   Unless the type name specifies a void type, the type name shall specify qualified or
     unqualified scalar type and the operand shall have scalar type.
 

-
-
+
 
3   Conversions that involve pointers, other than where permitted by the constraints of
-      6.5.16.1, shall be specified by means of an explicit cast.
+      6.5.16.1, shall be specified by means of an explicit cast.
     Semantics
 

-
-
+
 
4   Preceding an expression by a parenthesized type name converts the value of the
-    expression to the named type. This construction is called a cast .89) A cast that specifies
+    expression to the named type. This construction is called a cast .[89] A cast that specifies
     no conversion has no effect on the type or value of an expression.
 

-
 
 
Footnote 89) A cast does not yield an lvalue. Thus, a cast to a qualified type has the same effect as a cast to the
         unqualified version of the type.
 

 
-
+
 
5   If the value of the expression is represented with greater precision or range than required
-    by the type named by the cast (6.3.1.8), then the cast specifies a conversion even if the
+    by the type named by the cast (6.3.1.8), then the cast specifies a conversion even if the
     type of the expression is the same as the named type.
-    Forward references: equality operators (6.5.9), function declarators (including
-    prototypes) (6.7.5.3), simple assignment (6.5.16.1), type names (6.7.6).
+    Forward references: equality operators (6.5.9), function declarators (including
+    prototypes) (6.7.5.3), simple assignment (6.5.16.1), type names (6.7.6).
 

-
-
+
 

 
6.5.5 [Multiplicative operators]

-

-
-
-
1            multiplicative-expression:
+
+
1 Syntax
+            multiplicative-expression:
                      cast-expression
                      multiplicative-expression * cast-expression
                      multiplicative-expression / cast-expression
                      multiplicative-expression % cast-expression
     Constraints
 

-
-
+
 
2   Each of the operands shall have arithmetic type. The operands of the % operator shall
     have integer type.
     Semantics
 

-
-
+
 
3   The usual arithmetic conversions are performed on the operands.
 

-
-
+
 
4   The result of the binary * operator is the product of the operands.
 

-
-
+
 
5   The result of the / operator is the quotient from the division of the first operand by the
     second; the result of the % operator is the remainder. In both operations, if the value of
     the second operand is zero, the behavior is undefined.
 

-
-
+
 
6   When integers are divided, the result of the / operator is the algebraic quotient with any
-    fractional part discarded.90) If the quotient a/b is representable, the expression
+    fractional part discarded.[90] If the quotient a/b is representable, the expression
     (a/b)*b + a%b shall equal a.
 

-
 
 
Footnote 90) This is often called ``truncation toward zero''.
-

-
-
-

-
6.5.6 [Additive operators]

-

-
-
-
1            additive-expression:
-                     multiplicative-expression
-                     additive-expression + multiplicative-expression
-                    additive-expression - multiplicative-expression
-    Constraints
-

-
-
-
2   For addition, either both operands shall have arithmetic type, or one operand shall be a
-    pointer to an object type and the other shall have integer type. (Incrementing is
-    equivalent to adding 1.)
-

-
-
-
3   For subtraction, one of the following shall hold:
-    -- both operands have arithmetic type;
     -- both operands are pointers to qualified or unqualified versions of compatible object
        types; or
     -- the left operand is a pointer to an object type and the right operand has integer type.
     (Decrementing is equivalent to subtracting 1.)
     Semantics
-

+

 
-
+
+

+
6.5.6 [Additive operators]

+
+
1 Syntax
+            additive-expression:
+                     multiplicative-expression
+                     additive-expression + multiplicative-expression
+                    additive-expression - multiplicative-expression
+    Constraints
+

+
+
2   For addition, either both operands shall have arithmetic type, or one operand shall be a
+    pointer to an object type and the other shall have integer type. (Incrementing is
+    equivalent to adding 1.)
+

+
+
3   For subtraction, one of the following shall hold:
+    -- both operands have arithmetic type;
+

+
 
4   If both operands have arithmetic type, the usual arithmetic conversions are performed on
     them.
 

-
-
+
 
5   The result of the binary + operator is the sum of the operands.
 

-
-
+
 
6   The result of the binary - operator is the difference resulting from the subtraction of the
     second operand from the first.
 

-
-
+
 
7   For the purposes of these operators, a pointer to an object that is not an element of an
     array behaves the same as a pointer to the first element of an array of length one with the
     type of the object as its element type.
 

-
-
+
 
8   When an expression that has integer type is added to or subtracted from a pointer, the
     result has the type of the pointer operand. If the pointer operand points to an element of
     an array object, and the array is large enough, the result points to an element offset from
@@ -4859,8 +4242,7 @@ Forward references:         conditional inclusion (6.10.1), complex arithmetic
     behavior is undefined. If the result points one past the last element of the array object, it
     shall not be used as the operand of a unary * operator that is evaluated.
 

-
-
+
 
9   When two pointers are subtracted, both shall point to elements of the same array object,
     or one past the last element of the array object; the result is the difference of the
     subscripts of the two array elements. The size of the result is implementation-defined,
@@ -4873,9 +4255,8 @@ Forward references:         conditional inclusion (6.10.1), complex arithmetic
     to the last element of the same array object, the expression ((Q)+1)-(P) has the same
      value as ((Q)-(P))+1 and as -((P)-((Q)+1)), and has the value zero if the
      expression P points one past the last element of the array object, even though the
-     expression (Q)+1 does not point to an element of the array object.91)
+     expression (Q)+1 does not point to an element of the array object.[91]
 

-
 
 
Footnote 91) Another way to approach pointer arithmetic is first to convert the pointer(s) to character pointer(s): In
          this scheme the integer expression added to or subtracted from the converted pointer is first multiplied
@@ -4887,7 +4268,7 @@ Forward references:         conditional inclusion (6.10.1), complex arithmetic
           element'' requirements.
 

 
-
+
 
10   EXAMPLE        Pointer arithmetic is well defined with pointers to variable length array types.
               {
                        int n = 4, m = 3;
@@ -4898,62 +4279,53 @@ Forward references:         conditional inclusion (6.10.1), complex arithmetic
                        n = p - a;                  //   n == 1
               }
 

-
-
+
 
11   If array a in the above example were declared to be an array of known constant size, and pointer p were
      declared to be a pointer to an array of the same known constant size (pointing to a), the results would be
      the same.
 
-     Forward references: array declarators (6.7.5.2), common definitions <stddef.h>
-     (7.17).
+     Forward references: array declarators (6.7.5.2), common definitions <stddef.h>
+     (7.17).
 

-
-
+
 

 
6.5.7 [Bitwise shift operators]

-

-
-
-
1             shift-expression:
+
+
1 Syntax
+             shift-expression:
                       additive-expression
                       shift-expression << additive-expression
                       shift-expression >> additive-expression
      Constraints
 

-
-
+
 
2    Each of the operands shall have integer type.
      Semantics
 

-
-
+
 
3    The integer promotions are performed on each of the operands. The type of the result is
      that of the promoted left operand. If the value of the right operand is negative or is
      greater than or equal to the width of the promoted left operand, the behavior is undefined.
 

-
-
+
 
4   The result of E1 << E2 is E1 left-shifted E2 bit positions; vacated bits are filled with
-    zeros. If E1 has an unsigned type, the value of the result is E1 × 2E2 , reduced modulo
+    zeros. If E1 has an unsigned type, the value of the result is E1 \xD7 2E2 , reduced modulo
     one more than the maximum value representable in the result type. If E1 has a signed
-    type and nonnegative value, and E1 × 2E2 is representable in the result type, then that is
+    type and nonnegative value, and E1 \xD7 2E2 is representable in the result type, then that is
     the resulting value; otherwise, the behavior is undefined.
 

-
-
+
 
5   The result of E1 >> E2 is E1 right-shifted E2 bit positions. If E1 has an unsigned type
     or if E1 has a signed type and a nonnegative value, the value of the result is the integral
     part of the quotient of E1 / 2E2 . If E1 has a signed type and a negative value, the
     resulting value is implementation-defined.
 

-
-
+
 

 
6.5.8 [Relational operators]

-

-
-
-
1            relational-expression:
+
+
1 Syntax
+            relational-expression:
                      shift-expression
                      relational-expression   <    shift-expression
                      relational-expression   >    shift-expression
@@ -4961,8 +4333,7 @@ Forward references:         conditional inclusion (6.10.1), complex arithmetic
                      relational-expression   >=   shift-expression
     Constraints
 

-
-
+
 
2   One of the following shall hold:
     -- both operands have real type;
     -- both operands are pointers to qualified or unqualified versions of compatible object
@@ -4971,19 +4342,16 @@ Forward references:         conditional inclusion (6.10.1), complex arithmetic
        incomplete types.
     Semantics
 

-
-
+
 
3   If both of the operands have arithmetic type, the usual arithmetic conversions are
     performed.
 

-
-
+
 
4   For the purposes of these operators, a pointer to an object that is not an element of an
     array behaves the same as a pointer to the first element of an array of length one with the
     type of the object as its element type.
 

-
-
+
 
5   When two pointers are compared, the result depends on the relative locations in the
     address space of the objects pointed to. If two pointers to object or incomplete types both
     point to the same object, or both point one past the last element of the same array object,
@@ -4996,32 +4364,28 @@ Forward references:         conditional inclusion (6.10.1), complex arithmetic
     last element of the same array object, the pointer expression Q+1 compares greater than P.
     In all other cases, the behavior is undefined.
 

-
-
+
 
6   Each of the operators < (less than), > (greater than), <= (less than or equal to), and >=
-    (greater than or equal to) shall yield 1 if the specified relation is true and 0 if it is false.92)
+    (greater than or equal to) shall yield 1 if the specified relation is true and 0 if it is false.[92]
     The result has type int.
 

-
 
 
Footnote 92) The expression a<b<c is not interpreted as in ordinary mathematics. As the syntax indicates, it
         means (a<b)<c; in other words, ``if a is less than b, compare 1 to c; otherwise, compare 0 to c''.
 

 
-
+
 

 
6.5.9 [Equality operators]

-

-
-
-
1            equality-expression:
+
+
1 Syntax
+            equality-expression:
                      relational-expression
                     equality-expression == relational-expression
                     equality-expression != relational-expression
     Constraints
 

-
-
+
 
2   One of the following shall hold:
     -- both operands have arithmetic type;
     -- both operands are pointers to qualified or unqualified versions of compatible types;
@@ -5030,42 +4394,37 @@ Forward references:         conditional inclusion (6.10.1), complex arithmetic
     -- one operand is a pointer and the other is a null pointer constant.
     Semantics
 

-
-
+
 
3   The == (equal to) and != (not equal to) operators are analogous to the relational
-    operators except for their lower precedence.93) Each of the operators yields 1 if the
+    operators except for their lower precedence.[93] Each of the operators yields 1 if the
     specified relation is true and 0 if it is false. The result has type int. For any pair of
     operands, exactly one of the relations is true.
 

-
 
 
Footnote 93) Because of the precedences, a<b == c<d is 1 whenever a<b and c<d have the same truth-value.
 

 
-
+
 
4   If both of the operands have arithmetic type, the usual arithmetic conversions are
     performed. Values of complex types are equal if and only if both their real parts are equal
     and also their imaginary parts are equal. Any two values of arithmetic types from
     different type domains are equal if and only if the results of their conversions to the
     (complex) result type determined by the usual arithmetic conversions are equal.
 

-
-
+
 
5   Otherwise, at least one operand is a pointer. If one operand is a pointer and the other is a
     null pointer constant, the null pointer constant is converted to the type of the pointer. If
     one operand is a pointer to an object or incomplete type and the other is a pointer to a
     qualified or unqualified version of void, the former is converted to the type of the latter.
 

-
-
+
 
6   Two pointers compare equal if and only if both are null pointers, both are pointers to the
     same object (including a pointer to an object and a subobject at its beginning) or function,
     both are pointers to one past the last element of the same array object, or one is a pointer
     to one past the end of one array object and the other is a pointer to the start of a different
     array object that happens to immediately follow the first array object in the address
-    space.94)
+    space.[94]
 

-
 
 
Footnote 94) Two objects may be adjacent in memory because they are adjacent elements of a larger array or
         adjacent members of a structure with no padding between them, or because the implementation chose
@@ -5074,168 +4433,139 @@ Forward references:         conditional inclusion (6.10.1), complex arithmetic
         behavior.
 

 
-
+
 
7   For the purposes of these operators, a pointer to an object that is not an element of an
     array behaves the same as a pointer to the first element of an array of length one with the
     type of the object as its element type.
 

-
-
+
 

 
6.5.10 [Bitwise AND operator]

-

-
-
-
1            AND-expression:
+
+
1 Syntax
+            AND-expression:
                    equality-expression
                    AND-expression & equality-expression
     Constraints
 

-
-
+
 
2   Each of the operands shall have integer type.
     Semantics
 

-
-
+
 
3   The usual arithmetic conversions are performed on the operands.
 

-
-
+
 
4   The result of the binary & operator is the bitwise AND of the operands (that is, each bit in
     the result is set if and only if each of the corresponding bits in the converted operands is
     set).
 

-
-
+
 

 
6.5.11 [Bitwise exclusive OR operator]

-

-
-
-
1            exclusive-OR-expression:
+
+
1 Syntax
+            exclusive-OR-expression:
                      AND-expression
                      exclusive-OR-expression ^ AND-expression
     Constraints
 

-
-
+
 
2   Each of the operands shall have integer type.
     Semantics
 

-
-
+
 
3   The usual arithmetic conversions are performed on the operands.
 

-
-
+
 
4   The result of the ^ operator is the bitwise exclusive OR of the operands (that is, each bit
     in the result is set if and only if exactly one of the corresponding bits in the converted
     operands is set).
 

-
-
+
 

 
6.5.12 [Bitwise inclusive OR operator]

-

-
-
-
1            inclusive-OR-expression:
+
+
1 Syntax
+            inclusive-OR-expression:
                      exclusive-OR-expression
                      inclusive-OR-expression | exclusive-OR-expression
     Constraints
 

-
-
+
 
2   Each of the operands shall have integer type.
     Semantics
 

-
-
+
 
3   The usual arithmetic conversions are performed on the operands.
 

-
-
+
 
4   The result of the | operator is the bitwise inclusive OR of the operands (that is, each bit in
     the result is set if and only if at least one of the corresponding bits in the converted
     operands is set).
 
 

-
-
+
 

 
6.5.13 [Logical AND operator]

-

-
-
-
1             logical-AND-expression:
+
+
1 Syntax
+             logical-AND-expression:
                       inclusive-OR-expression
                       logical-AND-expression && inclusive-OR-expression
     Constraints
 

-
-
+
 
2   Each of the operands shall have scalar type.
     Semantics
 

-
-
+
 
3   The && operator shall yield 1 if both of its operands compare unequal to 0; otherwise, it
     yields 0. The result has type int.
 

-
-
+
 
4   Unlike the bitwise binary & operator, the && operator guarantees left-to-right evaluation;
     there is a sequence point after the evaluation of the first operand. If the first operand
     compares equal to 0, the second operand is not evaluated.
 

-
-
+
 

 
6.5.14 [Logical OR operator]

-

-
-
-
1             logical-OR-expression:
+
+
1 Syntax
+             logical-OR-expression:
                       logical-AND-expression
                       logical-OR-expression || logical-AND-expression
     Constraints
 

-
-
+
 
2   Each of the operands shall have scalar type.
     Semantics
 

-
-
+
 
3   The || operator shall yield 1 if either of its operands compare unequal to 0; otherwise, it
     yields 0. The result has type int.
 

-
-
+
 
4   Unlike the bitwise | operator, the || operator guarantees left-to-right evaluation; there is
     a sequence point after the evaluation of the first operand. If the first operand compares
     unequal to 0, the second operand is not evaluated.
 
 

-
-
+
 

 
6.5.15 [Conditional operator]

-

-
-
-
1            conditional-expression:
+
+
1 Syntax
+            conditional-expression:
                     logical-OR-expression
                     logical-OR-expression ? expression : conditional-expression
     Constraints
 

-
-
+
 
2   The first operand shall have scalar type.
 

-
-
+
 
3   One of the following shall hold for the second and third operands:
     -- both operands have arithmetic type;
     -- both operands have the same structure or union type;
@@ -5246,28 +4576,26 @@ Forward references:         conditional inclusion (6.10.1), complex arithmetic
        qualified or unqualified version of void.
     Semantics
 

-
-
+
 
4   The first operand is evaluated; there is a sequence point after its evaluation. The second
     operand is evaluated only if the first compares unequal to 0; the third operand is evaluated
     only if the first compares equal to 0; the result is the value of the second or third operand
-    (whichever is evaluated), converted to the type described below.95) If an attempt is made
+    (whichever is evaluated), converted to the type described below.[95] If an attempt is made
     to modify the result of a conditional operator or to access it after the next sequence point,
     the behavior is undefined.
 

-
 
 
Footnote 95) A conditional expression does not yield an lvalue.
+    pointer to an appropriately qualified version of void.
 

 
-
+
 
5   If both the second and third operands have arithmetic type, the result type that would be
     determined by the usual arithmetic conversions, were they applied to those two operands,
     is the type of the result. If both the operands have structure or union type, the result has
     that type. If both operands have void type, the result has void type.
 

-
-
+
 
6   If both the second and third operands are pointers or one is a null pointer constant and the
     other is a pointer, the result type is a pointer to a type qualified with all the type qualifiers
     of the types pointed-to by both operands. Furthermore, if both operands are pointers to
@@ -5275,16 +4603,13 @@ Forward references:         conditional inclusion (6.10.1), complex arithmetic
     a pointer to an appropriately qualified version of the composite type; if one operand is a
     null pointer constant, the result has the type of the other operand; otherwise, one operand
     is a pointer to void or a qualified version of void, in which case the result type is a
-    pointer to an appropriately qualified version of void.
 

-
-
+
 
7   EXAMPLE The common type that results when the second and third operands are pointers is determined
     in two independent stages. The appropriate qualifiers, for example, do not depend on whether the two
     pointers have compatible types.
 

-
-
+
 
8   Given the declarations
              const void *c_vp;
              void *vp;
@@ -5302,27 +4627,23 @@ Forward references:         conditional inclusion (6.10.1), complex arithmetic
              vp       ip        void *
 
 

-
-
+
 

 
6.5.16 [Assignment operators]

-

-
-
-
1            assignment-expression:
+
+
1 Syntax
+            assignment-expression:
                     conditional-expression
                     unary-expression assignment-operator assignment-expression
              assignment-operator: one of
                     = *= /= %= +=                       -=     <<=      >>=      &=     ^=     |=
     Constraints
 

-
-
+
 
2   An assignment operator shall have a modifiable lvalue as its left operand.
     Semantics
 

-
-
+
 
3   An assignment operator stores a value in the object designated by the left operand. An
     assignment expression has the value of the left operand after the assignment, but is not an
     lvalue. The type of an assignment expression is the type of the left operand unless the
@@ -5330,20 +4651,17 @@ Forward references:         conditional inclusion (6.10.1), complex arithmetic
     the left operand. The side effect of updating the stored value of the left operand shall
     occur between the previous and the next sequence point.
 

-
-
+
 
4   The order of evaluation of the operands is unspecified. If an attempt is made to modify
     the result of an assignment operator or to access it after the next sequence point, the
     behavior is undefined.
 

-
-
+
 

 
6.5.16.1 [Simple assignment]

-

-
-
-
1   One of the following shall hold:96)
+
+
1 Constraints
+   One of the following shall hold:[96]
     -- the left operand has qualified or unqualified arithmetic type and the right has
        arithmetic type;
     -- the left operand has a qualified or unqualified version of a structure or union type
@@ -5358,28 +4676,27 @@ Forward references:         conditional inclusion (6.10.1), complex arithmetic
     -- the left operand has type _Bool and the right is a pointer.
     Semantics
 

-
 
 
Footnote 96) The asymmetric appearance of these constraints with respect to type qualifiers is due to the conversion
-        (specified in 6.3.2.1) that changes lvalues to ``the value of the expression'' and thus removes any type
+        (specified in 6.3.2.1) that changes lvalues to ``the value of the expression'' and thus removes any type
         qualifiers that were applied to the type category of the expression (for example, it removes const but
         not volatile from the type int volatile * const).
+    negative, so the operands of the comparison can never compare equal. Therefore, for full portability, the
+    variable c should be declared as int.
 

 
-
+
 
2   In simple assignment (=), the value of the right operand is converted to the type of the
     assignment expression and replaces the value stored in the object designated by the left
     operand.
 

-
-
+
 
3   If the value being stored in an object is read from another object that overlaps in any way
     the storage of the first object, then the overlap shall be exact and the two objects shall
     have qualified or unqualified versions of a compatible type; otherwise, the behavior is
     undefined.
 

-
-
+
 
4   EXAMPLE 1       In the program fragment
             int f(void);
             char c;
@@ -5389,12 +4706,9 @@ Forward references:         conditional inclusion (6.10.1), complex arithmetic
     the int value returned by the function may be truncated when stored in the char, and then converted back
     to int width prior to the comparison. In an implementation in which ``plain'' char has the same range of
     values as unsigned char (and char is narrower than int), the result of the conversion cannot be
-    negative, so the operands of the comparison can never compare equal. Therefore, for full portability, the
-    variable c should be declared as int.
 
 

-
-
+
 
5   EXAMPLE 2       In the fragment:
             char c;
             int i;
@@ -5405,8 +4719,7 @@ Forward references:         conditional inclusion (6.10.1), complex arithmetic
     that is, long int type.
 
 

-
-
+
 
6   EXAMPLE 3       Consider the fragment:
             const char **cpp;
             char *p;
@@ -5418,54 +4731,46 @@ Forward references:         conditional inclusion (6.10.1), complex arithmetic
     value of the const object c.
 
 

-
-
+
 

 
6.5.16.2 [Compound assignment]

-

-
-
-
1   For the operators += and -= only, either the left operand shall be a pointer to an object
+
+
1 Constraints
+   For the operators += and -= only, either the left operand shall be a pointer to an object
     type and the right shall have integer type, or the left operand shall have qualified or
     unqualified arithmetic type and the right shall have arithmetic type.
 

-
-
+
 
2   For the other operators, each operand shall have arithmetic type consistent with those
     allowed by the corresponding binary operator.
     Semantics
 

-
-
+
 
3   A compound assignment of the form E1 op = E2 differs from the simple assignment
     expression E1 = E1 op (E2) only in that the lvalue E1 is evaluated only once.
 
 

-
-
+
 

 
6.5.17 [Comma operator]

-

-
-
-
1            expression:
+
+
1 Syntax
+            expression:
                     assignment-expression
                     expression , assignment-expression
     Semantics
 

-
-
+
 
2   The left operand of a comma operator is evaluated as a void expression; there is a
     sequence point after its evaluation. Then the right operand is evaluated; the result has its
-    type and value.97) If an attempt is made to modify the result of a comma operator or to
+    type and value.[97] If an attempt is made to modify the result of a comma operator or to
     access it after the next sequence point, the behavior is undefined.
 

-
 
 
Footnote 97) A comma operator does not yield an lvalue.
 

 
-
+
 
3   EXAMPLE As indicated by the syntax, the comma operator (as described in this subclause) cannot
     appear in contexts where a comma is used to separate items in a list (such as arguments to functions or lists
     of initializers). On the other hand, it can be used within a parenthesized expression or within the second
@@ -5473,83 +4778,73 @@ Forward references:         conditional inclusion (6.10.1), complex arithmetic
              f(a, (t=3, t+2), c)
     the function has three arguments, the second of which has the value 5.
 
-    Forward references: initialization (6.7.8).
+    Forward references: initialization (6.7.8).
 

-
-
+
 

 
6.6 [Constant expressions]

-

-
-
-
1            constant-expression:
+
+
1 Syntax
+            constant-expression:
                     conditional-expression
     Description
 

-
-
+
 
2   A constant expression can be evaluated during translation rather than runtime, and
     accordingly may be used in any place that a constant may be.
     Constraints
 

-
-
+
 
3   Constant expressions shall not contain assignment, increment, decrement, function-call,
     or comma operators, except when they are contained within a subexpression that is not
-    evaluated.98)
+    evaluated.[98]
 

-
 
-
Footnote 98) The operand of a sizeof operator is usually not evaluated (6.5.3.4).
+
Footnote 98) The operand of a sizeof operator is usually not evaluated (6.5.3.4).
 

 
-
+
 
4   Each constant expression shall evaluate to a constant that is in the range of representable
     values for its type.
     Semantics
 

-
-
+
 
5   An expression that evaluates to a constant is required in several contexts. If a floating
     expression is evaluated in the translation environment, the arithmetic precision and range
     shall be at least as great as if the expression were being evaluated in the execution
     environment.
 

-
-
-
6   An integer constant expression99) shall have integer type and shall only have operands
+
+
6   An integer constant expression[99] shall have integer type and shall only have operands
     that are integer constants, enumeration constants, character constants, sizeof
     expressions whose results are integer constants, and floating constants that are the
     immediate operands of casts. Cast operators in an integer constant expression shall only
     convert arithmetic types to integer types, except as part of an operand to the sizeof
     operator.
 

-
 
 
Footnote 99) An integer constant expression is used to specify the size of a bit-field member of a structure, the
         value of an enumeration constant, the size of an array, or the value of a case constant. Further
         constraints that apply to the integer constant expressions used in conditional-inclusion preprocessing
-        directives are discussed in 6.10.1.
+        directives are discussed in 6.10.1.
+     -- an address constant, or
+     -- an address constant for an object type plus or minus an integer constant expression.
 

 
-
+
 
7   More latitude is permitted for constant expressions in initializers. Such a constant
     expression shall be, or evaluate to, one of the following:
     -- an arithmetic constant expression,
     -- a null pointer constant,
-     -- an address constant, or
-     -- an address constant for an object type plus or minus an integer constant expression.
 

-
-
+
 
8    An arithmetic constant expression shall have arithmetic type and shall only have
      operands that are integer constants, floating constants, enumeration constants, character
      constants, and sizeof expressions. Cast operators in an arithmetic constant expression
      shall only convert arithmetic types to arithmetic types, except as part of an operand to a
      sizeof operator whose result is an integer constant.
 

-
-
+
 
9    An address constant is a null pointer, a pointer to an lvalue designating an object of static
      storage duration, or a pointer to a function designator; it shall be created explicitly using
      the unary & operator or an integer constant cast to pointer type, or implicitly by the use of
@@ -5558,30 +4853,26 @@ Forward references:         conditional inclusion (6.10.1), complex arithmetic
      be used in the creation of an address constant, but the value of an object shall not be
      accessed by use of these operators.
 

-
-
+
 
10   An implementation may accept other forms of constant expressions.
 

-
-
+
 
11   The semantic rules for the evaluation of a constant expression are the same as for
-     nonconstant expressions.100)
-     Forward references: array declarators (6.7.5.2), initialization (6.7.8).
+     nonconstant expressions.[100]
+     Forward references: array declarators (6.7.5.2), initialization (6.7.8).
 

-
 
 
Footnote 100) Thus, in the following initialization,
                    static int i = 2 || 1 / 0;
           the expression is a valid integer constant expression with value one.
 

 
-
+
 

 
6.7 [Declarations]

-

-
-
-
1            declaration:
+
+
1 Syntax
+            declaration:
                     declaration-specifiers init-declarator-listopt ;
              declaration-specifiers:
                     storage-class-specifier declaration-specifiersopt
@@ -5596,61 +4887,53 @@ Forward references:         conditional inclusion (6.10.1), complex arithmetic
                      declarator = initializer
     Constraints
 

-
-
+
 
2   A declaration shall declare at least a declarator (other than the parameters of a function or
     the members of a structure or union), a tag, or the members of an enumeration.
 

-
-
+
 
3   If an identifier has no linkage, there shall be no more than one declaration of the identifier
     (in a declarator or type specifier) with the same scope and in the same name space, except
-    for tags as specified in 6.7.2.3.
+    for tags as specified in 6.7.2.3.
 

-
-
+
 
4   All declarations in the same scope that refer to the same object or function shall specify
     compatible types.
     Semantics
 

-
-
+
 
5   A declaration specifies the interpretation and attributes of a set of identifiers. A definition
     of an identifier is a declaration for that identifier that:
     -- for an object, causes storage to be reserved for that object;
-    -- for a function, includes the function body;101)
+    -- for a function, includes the function body;[101]
     -- for an enumeration constant or typedef name, is the (only) declaration of the
        identifier.
 

-
 
-
Footnote 101) Function definitions have a different syntax, described in 6.9.1.
+
Footnote 101) Function definitions have a different syntax, described in 6.9.1.
+    additional type information, or an initializer, or both. The declarators contain the
+    identifiers (if any) being declared.
 

 
-
+
 
6   The declaration specifiers consist of a sequence of specifiers that indicate the linkage,
     storage duration, and part of the type of the entities that the declarators denote. The init-
     declarator-list is a comma-separated sequence of declarators, each of which may have
-    additional type information, or an initializer, or both. The declarators contain the
-    identifiers (if any) being declared.
 

-
-
+
 
7   If an identifier for an object is declared with no linkage, the type for the object shall be
     complete by the end of its declarator, or by the end of its init-declarator if it has an
     initializer; in the case of function parameters (including in prototypes), it is the adjusted
-    type (see 6.7.5.3) that is required to be complete.
-    Forward references: declarators (6.7.5), enumeration specifiers (6.7.2.2), initialization
-    (6.7.8).
+    type (see 6.7.5.3) that is required to be complete.
+    Forward references: declarators (6.7.5), enumeration specifiers (6.7.2.2), initialization
+    (6.7.8).
 

-
-
+
 

 
6.7.1 [Storage-class specifiers]

-

-
-
-
1            storage-class-specifier:
+
+
1 Syntax
+            storage-class-specifier:
                     typedef
                     extern
                     static
@@ -5658,58 +4941,51 @@ Forward references:         conditional inclusion (6.10.1), complex arithmetic
                     register
     Constraints
 

-
-
+
 
2   At most, one storage-class specifier may be given in the declaration specifiers in a
-    declaration.102)
+    declaration.[102]
     Semantics
 

-
 
-
Footnote 102) See ``future language directions'' (6.11.5).
+
Footnote 102) See ``future language directions'' (6.11.5).
 

 
-
+
 
3   The typedef specifier is called a ``storage-class specifier'' for syntactic convenience
-    only; it is discussed in 6.7.7. The meanings of the various linkages and storage durations
-    were discussed in 6.2.2 and 6.2.4.
+    only; it is discussed in 6.7.7. The meanings of the various linkages and storage durations
+    were discussed in 6.2.2 and 6.2.4.
 

-
-
+
 
4   A declaration of an identifier for an object with storage-class specifier register
     suggests that access to the object be as fast as possible. The extent to which such
-    suggestions are effective is implementation-defined.103)
+    suggestions are effective is implementation-defined.[103]
 

-
 
 
Footnote 103) The implementation may treat any register declaration simply as an auto declaration. However,
          whether or not addressable storage is actually used, the address of any part of an object declared with
          storage-class specifier register cannot be computed, either explicitly (by use of the unary &
-         operator as discussed in 6.5.3.2) or implicitly (by converting an array name to a pointer as discussed in
-         6.3.2.1). Thus, the only operator that can be applied to an array declared with storage-class specifier
+         operator as discussed in 6.5.3.2) or implicitly (by converting an array name to a pointer as discussed in
+         6.3.2.1). Thus, the only operator that can be applied to an array declared with storage-class specifier
          register is sizeof.
 

 
-
+
 
5   The declaration of an identifier for a function that has block scope shall have no explicit
     storage-class specifier other than extern.
 

-
-
+
 
6   If an aggregate or union object is declared with a storage-class specifier other than
     typedef, the properties resulting from the storage-class specifier, except with respect to
     linkage, also apply to the members of the object, and so on recursively for any aggregate
     or union member objects.
-    Forward references: type definitions (6.7.7).
+    Forward references: type definitions (6.7.7).
 

-
-
+
 

 
6.7.2 [Type specifiers]

-

-
-
-
1            type-specifier:
+
+
1 Syntax
+            type-specifier:
                     void
                     char
                     short
@@ -5721,13 +4997,12 @@ Forward references:         conditional inclusion (6.10.1), complex arithmetic
                     unsigned
                     _Bool
                     _Complex
-                    struct-or-union-specifier                                                       
+                    struct-or-union-specifier
                     enum-specifier
                     typedef-name
     Constraints
 

-
-
+
 
2   At least one type specifier shall be given in the declaration specifiers in each declaration,
     and in the specifier-qualifier list in each struct declaration and type name. Each list of
     type specifiers shall be one of the following sets (delimited by commas, when there is
@@ -5753,42 +5028,37 @@ Forward references:         conditional inclusion (6.10.1), complex arithmetic
     -- float _Complex
     -- double _Complex
     -- long double _Complex
-    -- struct or union specifier                                                                   
+    -- struct or union specifier
     -- enum specifier
     -- typedef name
 

-
-
+
 
3   The type specifier _Complex shall not be used if the implementation does not provide
-    complex types.104)
+    complex types.[104]
     Semantics
 

-
 
-
Footnote 104) Freestanding implementations are not required to provide complex types.                   
+
Footnote 104) Freestanding implementations are not required to provide complex types.
 

 
-
-
4   Specifiers for structures, unions, and enumerations are discussed in 6.7.2.1 through 6.7.2.3. 
-    Declarations of typedef names are discussed in 6.7.7. The characteristics of the
-    other types are discussed in 6.2.5.
+
+
4   Specifiers for structures, unions, and enumerations are discussed in 6.7.2.1 through 6.7.2.3.
+    Declarations of typedef names are discussed in 6.7.7. The characteristics of the
+    other types are discussed in 6.2.5.
 

-
-
+
 
5   Each of the comma-separated sets designates the same type, except that for bit-fields, it is
     implementation-defined whether the specifier int designates the same type as signed
     int or the same type as unsigned int.
-    Forward references: enumeration specifiers (6.7.2.2), structure and union specifiers
-    (6.7.2.1), tags (6.7.2.3), type definitions (6.7.7).
+    Forward references: enumeration specifiers (6.7.2.2), structure and union specifiers
+    (6.7.2.1), tags (6.7.2.3), type definitions (6.7.7).
 

-
-
+
 

 
6.7.2.1 [Structure and union specifiers]

-

-
-
-
1            struct-or-union-specifier:
+
+
1 Syntax
+            struct-or-union-specifier:
                      struct-or-union identifieropt { struct-declaration-list }
                      struct-or-union identifier
              struct-or-union:
@@ -5810,8 +5080,7 @@ Forward references:         conditional inclusion (6.10.1), complex arithmetic
                      declaratoropt : constant-expression
     Constraints
 

-
-
+
 
2   A structure or union shall not contain a member with incomplete or function type (hence,
     a structure shall not contain an instance of itself, but may contain a pointer to an instance
     of itself), except that the last member of a structure with more than one named member
@@ -5819,49 +5088,42 @@ Forward references:         conditional inclusion (6.10.1), complex arithmetic
     recursively, a member that is such a structure) shall not be a member of a structure or an
     element of an array.
 

-
-
+
 
3   The expression that specifies the width of a bit-field shall be an integer constant
     expression with a nonnegative value that does not exceed the width of an object of the
     type that would be specified were the colon and expression omitted. If the value is zero,
     the declaration shall have no declarator.
 

-
-
+
 
4   A bit-field shall have a type that is a qualified or unqualified version of _Bool, signed
     int, unsigned int, or some other implementation-defined type.
      Semantics
 

-
-
-
5    As discussed in 6.2.5, a structure is a type consisting of a sequence of members, whose
+
+
5    As discussed in 6.2.5, a structure is a type consisting of a sequence of members, whose
      storage is allocated in an ordered sequence, and a union is a type consisting of a sequence
      of members whose storage overlap.
 

-
-
+
 
6    Structure and union specifiers have the same form. The keywords struct and union
      indicate that the type being specified is, respectively, a structure type or a union type.
 

-
-
+
 
7    The presence of a struct-declaration-list in a struct-or-union-specifier declares a new type,
      within a translation unit. The struct-declaration-list is a sequence of declarations for the
      members of the structure or union. If the struct-declaration-list contains no named
      members, the behavior is undefined. The type is incomplete until after the } that
      terminates the list.
 

-
-
+
 
8    A member of a structure or union may have any object type other than a variably
-     modified type.105) In addition, a member may be declared to consist of a specified
-     number of bits (including a sign bit, if any). Such a member is called a bit-field ;106) its
+     modified type.[105] In addition, a member may be declared to consist of a specified
+     number of bits (including a sign bit, if any). Such a member is called a bit-field ;[106] its
      width is preceded by a colon.
 

-
 
 
Footnote 105) A structure or union can not contain a member with a variably modified type because member names
-          are not ordinary identifiers as defined in 6.2.3.
+          are not ordinary identifiers as defined in 6.2.3.
 

 
 
@@ -5869,18 +5131,17 @@ Forward references:         conditional inclusion (6.10.1), complex arithmetic
           or arrays of bit-field objects.
 

 
-
+
 
9    A bit-field is interpreted as a signed or unsigned integer type consisting of the specified
-     number of bits.107) If the value 0 or 1 is stored into a nonzero-width bit-field of type
+     number of bits.[107] If the value 0 or 1 is stored into a nonzero-width bit-field of type
      _Bool, the value of the bit-field shall compare equal to the value stored.
 

-
 
-
Footnote 107) As specified in 6.7.2 above, if the actual type specifier used is int or a typedef-name defined as int,
+
Footnote 107) As specified in 6.7.2 above, if the actual type specifier used is int or a typedef-name defined as int,
           then it is implementation-defined whether the bit-field is signed or unsigned.
 

 
-
+
 
10   An implementation may allocate any addressable storage unit large enough to hold a bit-
      field. If enough space remains, a bit-field that immediately follows another bit-field in a
      structure shall be packed into adjacent bits of the same unit. If insufficient space remains,
@@ -5889,44 +5150,38 @@ Forward references:         conditional inclusion (6.10.1), complex arithmetic
      low-order or low-order to high-order) is implementation-defined. The alignment of the
      addressable storage unit is unspecified.
 

-
-
+
 
11   A bit-field declaration with no declarator, but only a colon and a width, indicates an
-     unnamed bit-field.108) As a special case, a bit-field structure member with a width of 0
+     unnamed bit-field.[108] As a special case, a bit-field structure member with a width of 0
      indicates that no further bit-field is to be packed into the unit in which the previous bit-
      field, if any, was placed.
 

-
 
 
Footnote 108) An unnamed bit-field structure member is useful for padding to conform to externally imposed
           layouts.
 

 
-
+
 
12   Each non-bit-field member of a structure or union object is aligned in an implementation-
      defined manner appropriate to its type.
 

-
-
+
 
13   Within a structure object, the non-bit-field members and the units in which bit-fields
      reside have addresses that increase in the order in which they are declared. A pointer to a
      structure object, suitably converted, 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 may be unnamed
      padding within a structure object, but not at its beginning.
 

-
-
+
 
14   The size of a union is sufficient to contain the largest of its members. The value of at
      most one of the members can be stored in a union object at any time. A pointer to a
      union object, suitably converted, points to each of its members (or if a member is a bit-
      field, then to the unit in which it resides), and vice versa.
 

-
-
+
 
15   There may be unnamed padding at the end of a structure or union.
 

-
-
+
 
16   As a special case, the last element of a structure with more than one named member may
      have an incomplete array type; this is called a flexible array member . In most situations,
      the flexible array member is ignored. In particular, the size of the structure is as if the
@@ -5940,8 +5195,7 @@ Forward references:         conditional inclusion (6.10.1), complex arithmetic
      it had one element but the behavior is undefined if any attempt is made to access that
      element or to generate a pointer one past it.
 

-
-
+
 
17   EXAMPLE       After the declaration:
              struct s { int n; double d[]; };
      the structure struct s has a flexible array member d. A typical way to use this is:
@@ -5953,8 +5207,7 @@ Forward references:         conditional inclusion (6.10.1), complex arithmetic
      (there are circumstances in which this equivalence is broken; in particular, the offsets of member d might
      not be the same).
 

-
-
+
 
18   Following the above declaration:
 
               struct s t1 = { 0 };                         //   valid
@@ -5967,8 +5220,7 @@ Forward references:         conditional inclusion (6.10.1), complex arithmetic
      in which case the assignment would be legitimate. Nevertheless, it cannot appear in strictly conforming
      code.
 

-
-
+
 
19   After the further declaration:
               struct ss { int n; };
      the expressions:
@@ -5976,8 +5228,7 @@ Forward references:         conditional inclusion (6.10.1), complex arithmetic
               sizeof (struct s) >= offsetof(struct s, d)
      are always equal to 1.
 

-
-
+
 
20   If sizeof (double) is 8, then after the following code is executed:
               struct s *s1;
               struct s *s2;
@@ -5988,8 +5239,7 @@ Forward references:         conditional inclusion (6.10.1), complex arithmetic
               struct { int n; double d[8]; } *s1;
               struct { int n; double d[5]; } *s2;
 

-
-
+
 
21   Following the further successful assignments:
               s1 = malloc(sizeof (struct s) + 10);
               s2 = malloc(sizeof (struct s) + 6);
@@ -6002,23 +5252,20 @@ Forward references:         conditional inclusion (6.10.1), complex arithmetic
               dp = &(s2->d[0]);           //   valid
               *dp = 42;                   //   undefined behavior
 

-
-
+
 
22   The assignment:
               *s1 = *s2;
      only copies the member n; if any of the array elements are within the first sizeof (struct s) bytes
      of the structure, they might be copied or simply overwritten with indeterminate values.
 
-     Forward references: tags (6.7.2.3).
+     Forward references: tags (6.7.2.3).
 

-
-
+
 

 
6.7.2.2 [Enumeration specifiers]

-

-
-
-
1            enum-specifier:
+
+
1 Syntax
+            enum-specifier:
                    enum identifieropt { enumerator-list }
                    enum identifieropt { enumerator-list , }
                    enum identifier
@@ -6030,16 +5277,14 @@ Forward references:         conditional inclusion (6.10.1), complex arithmetic
                    enumeration-constant = constant-expression
     Constraints
 

-
-
+
 
2   The expression that defines the value of an enumeration constant shall be an integer
     constant expression that has a value representable as an int.
     Semantics
 

-
-
+
 
3   The identifiers in an enumerator list are declared as constants that have type int and
-    may appear wherever such are permitted.109) An enumerator with = defines its
+    may appear wherever such are permitted.[109] An enumerator with = defines its
     enumeration constant as the value of the constant expression. If the first enumerator has
     no =, the value of its enumeration constant is 0. Each subsequent enumerator with no =
     defines its enumeration constant as the value of the constant expression obtained by
@@ -6047,26 +5292,24 @@ Forward references:         conditional inclusion (6.10.1), complex arithmetic
     = may produce enumeration constants with values that duplicate other values in the same
     enumeration.) The enumerators of an enumeration are also known as its members.
 

-
 
 
Footnote 109) Thus, the identifiers of enumeration constants declared in the same scope shall all be distinct from
          each other and from other identifiers declared in ordinary declarators.
 

 
-
+
 
4   Each enumerated type shall be compatible with char, a signed integer type, or an
-    unsigned integer type. The choice of type is implementation-defined,110) but shall be
+    unsigned integer type. The choice of type is implementation-defined,[110] but shall be
     capable of representing the values of all the members of the enumeration. The
     enumerated type is incomplete until after the } that terminates the list of enumerator
     declarations.
 

-
 
 
Footnote 110) An implementation may delay the choice of which integer type until all enumeration constants have
          been seen.
 

 
-
+
 
5   EXAMPLE       The following fragment:
             enum hue { chartreuse, burgundy, claret=20, winedark };
             enum hue col, *cp;
@@ -6077,50 +5320,45 @@ Forward references:         conditional inclusion (6.10.1), complex arithmetic
     makes hue the tag of an enumeration, and then declares col as an object that has that type and cp as a
     pointer to an object that has that type. The enumerated values are in the set { 0, 1, 20, 21 }.
 
-    Forward references: tags (6.7.2.3).
+    Forward references: tags (6.7.2.3).
 

-
-
+
 

 
6.7.2.3 [Tags]

-

-
-
-
1   A specific type shall have its content defined at most once.
+
+
1 Constraints
+   A specific type shall have its content defined at most once.
 

-
-
+
 
2   Where two declarations that use the same tag declare the same type, they shall both use
     the same choice of struct, union, or enum.
 

-
-
+
 
3   A type specifier of the form
             enum identifier
     without an enumerator list shall only appear after the type it specifies is complete.
     Semantics
 

-
-
+
 
4   All declarations of structure, union, or enumerated types that have the same scope and
-    use the same tag declare the same type. The type is incomplete111) until the closing brace
+    use the same tag declare the same type. The type is incomplete[111] until the closing brace
     of the list defining the content, and complete thereafter.
 

-
 
 
Footnote 111) An incomplete type may only by used when the size of an object of that type is not needed. It is not
          needed, for example, when a typedef name is declared to be a specifier for a structure or union, or
          when a pointer to or a function returning a structure or union is being declared. (See incomplete types
-         in 6.2.5.) The specification has to be complete before such a function is called or defined.
+         in 6.2.5.) The specification has to be complete before such a function is called or defined.
+     union content , or enumeration content . If an identifier is provided,112) the type specifier
+     also declares the identifier to be the tag of that type.
 

 
-
+
 
5   Two declarations of structure, union, or enumerated types which are in different scopes or
     use different tags declare distinct types. Each declaration of a structure, union, or
     enumerated type which does not include a tag declares a distinct type.
 

-
-
+
 
6   A type specifier of the form
             struct-or-union identifieropt { struct-declaration-list }
     or
@@ -6128,23 +5366,12 @@ Forward references:         conditional inclusion (6.10.1), complex arithmetic
     or
             enum identifier { enumerator-list , }
     declares a structure, union, or enumerated type. The list defines the structure content ,
-     union content , or enumeration content . If an identifier is provided,112) the type specifier
-     also declares the identifier to be the tag of that type.
 

-
-
-
Footnote 112) If there is no identifier, the type can, within the translation unit, only be referred to by the declaration
-          of which it is a part. Of course, when the declaration is of a typedef name, subsequent declarations
-          can make use of that typedef name to declare objects having the specified structure, union, or
-          enumerated type.
-

-
-
+
 
7    A declaration of the form
               struct-or-union identifier ;
-     specifies a structure or union type and declares the identifier as a tag of that type.113)
+     specifies a structure or union type and declares the identifier as a tag of that type.[113]
 

-
 
 
Footnote 113) A similar construction with enum does not exist.
               typedef struct tnode TNODE;
@@ -6155,14 +5382,13 @@ Forward references:         conditional inclusion (6.10.1), complex arithmetic
               TNODE s, *sp;
 

 
-
+
 
8    If a type specifier of the form
               struct-or-union identifier
      occurs other than as part of one of the above forms, and no other declaration of the
      identifier as a tag is visible, then it declares an incomplete structure or union type, and
-     declares the identifier as the tag of that type.113)
+     declares the identifier as the tag of that type.[113]
 

-
 
 
Footnote 113) A similar construction with enum does not exist.
               typedef struct tnode TNODE;
@@ -6173,7 +5399,7 @@ Forward references:         conditional inclusion (6.10.1), complex arithmetic
               TNODE s, *sp;
 

 
-
+
 
9    If a type specifier of the form
               struct-or-union identifier
      or
@@ -6182,8 +5408,7 @@ Forward references:         conditional inclusion (6.10.1), complex arithmetic
      tag is visible, then it specifies the same type as that other declaration, and does not
      redeclare the tag.
 

-
-
+
 
10   EXAMPLE 1       This mechanism allows declaration of a self-referential structure.
               struct tnode {
                     int count;
@@ -6197,13 +5422,11 @@ Forward references:         conditional inclusion (6.10.1), complex arithmetic
      which sp points; the expression s.right->count designates the count member of the right struct
      tnode pointed to from s.
 

-
-
+
 
11   The following alternative formulation uses the typedef mechanism:
 
 

-
-
+
 
12   EXAMPLE 2 To illustrate the use of prior declaration of a tag to specify a pair of mutually referential
      structures, the declarations
               struct s1 { struct s2 *s2p; /* ... */ }; // D1
@@ -6215,69 +5438,61 @@ Forward references:         conditional inclusion (6.10.1), complex arithmetic
      may be inserted ahead of D1. This declares a new tag s2 in the inner scope; the declaration D2 then
      completes the specification of the new type.
 
-     Forward references: declarators (6.7.5), array declarators (6.7.5.2), type definitions
-     (6.7.7).
+     Forward references: declarators (6.7.5), array declarators (6.7.5.2), type definitions
+     (6.7.7).
 

-
-
+
 

 
6.7.3 [Type qualifiers]

-

-
-
-
1             type-qualifier:
+
+
1 Syntax
+             type-qualifier:
                      const
                      restrict
                      volatile
      Constraints
 

-
-
+
 
2    Types other than pointer types derived from object or incomplete types shall not be
      restrict-qualified.
      Semantics
 

-
-
+
 
3    The properties associated with qualified types are meaningful only for expressions that
-     are lvalues.114)
+     are lvalues.[114]
 

-
 
 
Footnote 114) The implementation may place a const object that is not volatile in a read-only region of
           storage. Moreover, the implementation need not allocate storage for such an object if its address is
           never used.
 

 
-
+
 
4    If the same qualifier appears more than once in the same specifier-qualifier-list , either
      directly or via one or more typedefs, the behavior is the same as if it appeared only
      once.
 

-
-
+
 
5    If an attempt is made to modify an object defined with a const-qualified type through use
      of an lvalue with non-const-qualified type, the behavior is undefined. If an attempt is
      made to refer to an object defined with a volatile-qualified type through use of an lvalue
-     with non-volatile-qualified type, the behavior is undefined.115)
+     with non-volatile-qualified type, the behavior is undefined.[115]
 

-
 
 
Footnote 115) This applies to those objects that behave as if they were defined with qualified types, even if they are
           never actually defined as objects in the program (such as an object at a memory-mapped input/output
           address).
 

 
-
+
 
6    An object that has volatile-qualified type may be modified in ways unknown to the
      implementation or have other unknown side effects. Therefore any expression referring
      to such an object shall be evaluated strictly according to the rules of the abstract machine,
-     as described in 5.1.2.3. Furthermore, at every sequence point the value last stored in the
+     as described in 5.1.2.3. Furthermore, at every sequence point the value last stored in the
      object shall agree with that prescribed by the abstract machine, except as modified by the
-     unknown factors mentioned previously.116) What constitutes an access to an object that
+     unknown factors mentioned previously.[116] What constitutes an access to an object that
      has volatile-qualified type is implementation-defined.
 

-
 
 
Footnote 116) A volatile declaration may be used to describe an object corresponding to a memory-mapped
           input/output port or an object accessed by an asynchronously interrupting function. Actions on
@@ -6285,44 +5500,40 @@ Forward references:         conditional inclusion (6.10.1), complex arithmetic
           permitted by the rules for evaluating expressions.
 

 
-
+
 
7    An object that is accessed through a restrict-qualified pointer has a special association
-     with that pointer. This association, defined in 6.7.3.1 below, requires that all accesses to
-     that object use, directly or indirectly, the value of that particular pointer.117) The intended
+     with that pointer. This association, defined in 6.7.3.1 below, requires that all accesses to
+     that object use, directly or indirectly, the value of that particular pointer.[117] The intended
      use of the restrict qualifier (like the register storage class) is to promote
      optimization, and deleting all instances of the qualifier from all preprocessing translation
      units composing a conforming program does not change its meaning (i.e., observable
      behavior).
 

-
 
 
Footnote 117) For example, a statement that assigns a value returned by malloc to a single pointer establishes this
           association between the allocated object and the pointer.
 

 
-
+
 
8    If the specification of an array type includes any type qualifiers, the element type is so-
      qualified, not the array type. If the specification of a function type includes any type
-     qualifiers, the behavior is undefined.118)
+     qualifiers, the behavior is undefined.[118]
 

-
 
 
Footnote 118) Both of these can occur through the use of typedefs.
 

 
-
+
 
9    For two qualified types to be compatible, both shall have the identically qualified version
      of a compatible type; the order of type qualifiers within a list of specifiers or qualifiers
      does not affect the specified type.
 

-
-
+
 
10   EXAMPLE 1       An object declared
               extern const volatile int real_time_clock;
      may be modifiable by hardware, but cannot be assigned to, incremented, or decremented.
 

-
-
+
 
11   EXAMPLE 2 The following declarations and expressions illustrate the behavior when type qualifiers
      modify an aggregate type:
              const struct s { int mem; } cs = { 1 };
@@ -6338,39 +5549,34 @@ Forward references:         conditional inclusion (6.10.1), complex arithmetic
              pci = &cs.mem;        //   valid
              pi = a[0];            //   invalid: a[0] has type ``const int *''
 

-
-
+
 

 
6.7.3.1 [Formal definition of restrict]

-

-
-
+
 
1    Let D be a declaration of an ordinary identifier that provides a means of designating an
      object P as a restrict-qualified pointer to type T.
 

-
-
+
 
2    If D appears inside a block and does not have storage class extern, let B denote the
      block. If D appears in the list of parameter declarations of a function definition, let B
      denote the associated block. Otherwise, let B denote the block of main (or the block of
      whatever function is called at program startup in a freestanding environment).
 

-
-
+
 
3    In what follows, a pointer expression E is said to be based on object P if (at some
      sequence point in the execution of B prior to the evaluation of E) modifying P to point to
-     a copy of the array object into which it formerly pointed would change the value of E.119)
+     a copy of the array object into which it formerly pointed would change the value of E.[119]
      Note that ``based'' is defined only for expressions with pointer types.
 

-
 
 
Footnote 119) In other words, E depends on the value of P itself rather than on the value of an object referenced
           indirectly through P. For example, if identifier p has type (int **restrict), then the pointer
           expressions p and p+1 are based on the restricted pointer object designated by p, but the pointer
           expressions *p and p[1] are not.
+     associated with B.
 

 
-
+
 
4    During each execution of B, let L be any lvalue that has &L based on P. If L is used to
      access the value of the object X that it designates, and X is also modified (by any means),
      then the following requirements apply: T shall not be const-qualified. Every other lvalue
@@ -6381,18 +5587,14 @@ Forward references:         conditional inclusion (6.10.1), complex arithmetic
      the execution of B, or the execution of B2 shall end prior to the assignment. If these
      requirements are not met, then the behavior is undefined.
 

-
-
+
 
5    Here an execution of B means that portion of the execution of the program that would
      correspond to the lifetime of an object with scalar type and automatic storage duration
-     associated with B.
 

-
-
+
 
6    A translator is free to ignore any or all aliasing implications of uses of restrict.
 

-
-
+
 
7    EXAMPLE 1       The file scope declarations
               int * restrict a;
               int * restrict b;
@@ -6401,8 +5603,7 @@ Forward references:         conditional inclusion (6.10.1), complex arithmetic
      program, then it is never accessed using either of the other two.
 
 

-
-
+
 
8    EXAMPLE 2 The function parameter declarations in the following example
               void f(int n, int * restrict p, int * restrict q)
               {
@@ -6412,8 +5613,7 @@ Forward references:         conditional inclusion (6.10.1), complex arithmetic
      assert that, during each execution of the function, if an object is accessed through one of the pointer
      parameters, then it is not also accessed through the other.
 

-
-
+
 
9    The benefit of the restrict qualifiers is that they enable a translator to make an effective dependence
      analysis of function f without examining any of the calls of f in the program. The cost is that the
      programmer has to examine all of those calls to ensure that none give undefined behavior. For example, the
@@ -6427,8 +5627,7 @@ Forward references:         conditional inclusion (6.10.1), complex arithmetic
               }
 
 

-
-
+
 
10   EXAMPLE 3       The function parameter declarations
               void h(int n, int * restrict p, int * restrict q, int * restrict r)
               {
@@ -6441,8 +5640,7 @@ Forward references:         conditional inclusion (6.10.1), complex arithmetic
      modified within function h.
 
 

-
-
+
 
11   EXAMPLE 4 The rule limiting assignments between restricted pointers does not distinguish between a
      function call and an equivalent nested block. With one exception, only ``outer-to-inner'' assignments
      between restricted pointers declared in nested blocks have defined behavior.
@@ -6459,8 +5657,7 @@ Forward references:         conditional inclusion (6.10.1), complex arithmetic
                        }
               }
 

-
-
+
 
12   The one exception allows the value of a restricted pointer to be carried out of the block in which it (or, more
      precisely, the ordinary identifier used to designate it) is declared when that block finishes execution. For
      example, this permits new_vector to return a vector.
@@ -6473,42 +5670,35 @@ Forward references:         conditional inclusion (6.10.1), complex arithmetic
                     return t;
               }
 

-
-
+
 

 
6.7.4 [Function specifiers]

-

-
-
-
1             function-specifier:
+
+
1 Syntax
+             function-specifier:
                      inline
      Constraints
 

-
-
+
 
2    Function specifiers shall be used only in the declaration of an identifier for a function.
 

-
-
+
 
3    An inline definition of a function with external linkage shall not contain a definition of a
      modifiable object with static storage duration, and shall not contain a reference to an
      identifier with internal linkage.
 

-
-
+
 
4    In a hosted environment, the inline function specifier shall not appear in a declaration
      of main.
      Semantics
 

-
-
+
 
5    A function declared with an inline function specifier is an inline function. The
      function specifier may appear more than once; the behavior is the same as if it appeared
      only once. Making a function an inline function suggests that calls to the function be as
-     fast as possible.120) The extent to which such suggestions are effective is
-     implementation-defined.121)
+     fast as possible.[120] The extent to which such suggestions are effective is
+     implementation-defined.[121]
 

-
 
 
Footnote 120) By using, for example, an alternative to the usual function call mechanism, such as ``inline
          substitution''. Inline substitution is not textual substitution, nor does it create a new function.
@@ -6524,7 +5714,7 @@ Forward references:         conditional inclusion (6.10.1), complex arithmetic
          substitutions to calls in the scope of an inline declaration.
 

 
-
+
 
6    Any function with internal linkage can be an inline function. For a function with external
      linkage, the following restrictions apply: If a function is declared with an inline
     function specifier, then it shall also be defined in the same translation unit. If all of the
@@ -6534,16 +5724,15 @@ Forward references:         conditional inclusion (6.10.1), complex arithmetic
     and does not forbid an external definition in another translation unit. An inline definition
     provides an alternative to an external definition, which a translator may use to implement
     any call to the function in the same translation unit. It is unspecified whether a call to the
-    function uses the inline definition or the external definition.122)
+    function uses the inline definition or the external definition.[122]
 

-
 
 
Footnote 122) Since an inline definition is distinct from the corresponding external definition and from any other
          corresponding inline definitions in other translation units, all corresponding objects with static storage
          duration are also distinct in each of the definitions.
 

 
-
+
 
7   EXAMPLE The declaration of an inline function with external linkage can result in either an external
     definition, or a definition available for use only within the translation unit. A file scope declaration with
     extern creates an external definition. The following example shows an entire translation unit.
@@ -6562,23 +5751,20 @@ Forward references:         conditional inclusion (6.10.1), complex arithmetic
                    return is_fahr ? cels(temp) : fahr(temp);
              }
 

-
-
+
 
8   Note that the definition of fahr is an external definition because fahr is also declared with extern, but
     the definition of cels is an inline definition. Because cels has external linkage and is referenced, an
-    external definition has to appear in another translation unit (see 6.9); the inline definition and the external
+    external definition has to appear in another translation unit (see 6.9); the inline definition and the external
     definition are distinct and either may be used for the call.
 
-    Forward references: function definitions (6.9.1).
+    Forward references: function definitions (6.9.1).
 

-
-
+
 

 
6.7.5 [Declarators]

-

-
-
-
1            declarator:
+
+
1 Syntax
+            declarator:
                     pointeropt direct-declarator
              direct-declarator:
                      identifier
@@ -6609,36 +5795,31 @@ Forward references:         conditional inclusion (6.10.1), complex arithmetic
                       identifier-list , identifier
     Semantics
 

-
-
+
 
2   Each declarator declares one identifier, and asserts that when an operand of the same
     form as the declarator appears in an expression, it designates a function or object with the
     scope, storage duration, and type indicated by the declaration specifiers.
 

-
-
+
 
3   A full declarator is a declarator that is not part of another declarator. The end of a full
     declarator is a sequence point. If, in the nested sequence of declarators in a full
     declarator, there is a declarator specifying a variable length array type, the type specified
     by the full declarator is said to be variably modified . Furthermore, any type derived by
     declarator type derivation from a variably modified type is itself variably modified.
 

-
-
+
 
4   In the following subclauses, consider a declaration
             T D1
     where T contains the declaration specifiers that specify a type T (such as int) and D1 is
     a declarator that contains an identifier ident . The type specified for the identifier ident in
     the various forms of declarator is described inductively using this notation.
 

-
-
+
 
5   If, in the declaration ``T D1'', D1 has the form
             identifier
     then the type specified for ident is T .
 

-
-
+
 
6   If, in the declaration ``T D1'', D1 has the form
             ( D )
     then ident has the type specified by the declaration ``T D''. Thus, a declarator in
@@ -6646,33 +5827,28 @@ Forward references:         conditional inclusion (6.10.1), complex arithmetic
     declarators may be altered by parentheses.
     Implementation limits
 

-
-
-
7   As discussed in 5.2.4.1, an implementation may limit the number of pointer, array, and
+
+
7   As discussed in 5.2.4.1, an implementation may limit the number of pointer, array, and
     function declarators that modify an arithmetic, structure, union, or incomplete type, either
     directly or via one or more typedefs.
-    Forward references: array declarators (6.7.5.2), type definitions (6.7.7).
+    Forward references: array declarators (6.7.5.2), type definitions (6.7.7).
 

-
-
+
 

 
6.7.5.1 [Pointer declarators]

-

-
-
-
1   If, in the declaration ``T D1'', D1 has the form
+
+
1 Semantics
+   If, in the declaration ``T D1'', D1 has the form
             * type-qualifier-listopt D
     and the type specified for ident in the declaration ``T D'' is `` derived-declarator-type-list
     T '', then the type specified for ident is `` derived-declarator-type-list type-qualifier-list
     pointer to T ''. For each type qualifier in the list, ident is a so-qualified pointer.
 

-
-
+
 
2   For two pointer types to be compatible, both shall be identically qualified and both shall
     be pointers to compatible types.
 

-
-
+
 
3   EXAMPLE The following pair of declarations demonstrates the difference between a ``variable pointer
     to a constant value'' and a ``constant pointer to a variable value''.
 
@@ -6683,8 +5859,7 @@ Forward references:         conditional inclusion (6.10.1), complex arithmetic
     int pointed to by constant_ptr may be modified, but constant_ptr itself shall always point to the
     same location.
 

-
-
+
 
4   The declaration of the constant pointer constant_ptr may be clarified by including a definition for the
     type ``pointer to int''.
              typedef int *int_ptr;
@@ -6692,14 +5867,12 @@ Forward references:         conditional inclusion (6.10.1), complex arithmetic
     declares constant_ptr as an object that has type ``const-qualified pointer to int''.
 
 

-
-
+
 

 
6.7.5.2 [Array declarators]

-

-
-
-
1   In addition to optional type qualifiers and the keyword static, the [ and ] may delimit
+
+
1 Constraints
+   In addition to optional type qualifiers and the keyword static, the [ and ] may delimit
     an expression or *. If they delimit an expression (which specifies the size of an array), the
     expression shall have an integer type. If the expression is a constant expression, it shall
     have a value greater than zero. The element type shall not be an incomplete or function
@@ -6707,43 +5880,39 @@ Forward references:         conditional inclusion (6.10.1), complex arithmetic
     declaration of a function parameter with an array type, and then only in the outermost
     array type derivation.
 

-
-
-
2   An ordinary identifier (as defined in 6.2.3) that has a variably modified type shall have
+
+
2   An ordinary identifier (as defined in 6.2.3) that has a variably modified type shall have
     either block scope and no linkage or function prototype scope. If an identifier is declared
     to be an object with static storage duration, it shall not have a variable length array type.
     Semantics
 

-
-
+
 
3   If, in the declaration ``T D1'', D1 has one of the forms:
              D[ type-qualifier-listopt assignment-expressionopt ]
              D[ static type-qualifier-listopt assignment-expression ]
              D[ type-qualifier-list static assignment-expression ]
              D[ type-qualifier-listopt * ]
     and the type specified for ident in the declaration ``T D'' is `` derived-declarator-type-list
-    T '', then the type specified for ident is `` derived-declarator-type-list array of T ''.123)
-    (See 6.7.5.3 for the meaning of the optional type qualifiers and the keyword static.)
+    T '', then the type specified for ident is `` derived-declarator-type-list array of T ''.[123]
+    (See 6.7.5.3 for the meaning of the optional type qualifiers and the keyword static.)
 

-
 
 
Footnote 123) When several ``array of'' specifications are adjacent, a multidimensional array is declared.
-

-
-
-
4   If the size is not present, the array type is an incomplete type. If the size is * instead of
-    being an expression, the array type is a variable length array type of unspecified size,
-    which can only be used in declarations with function prototype scope;124) such arrays are
-    nonetheless complete types. If the size is an integer constant expression and the element
     type has a known constant size, the array type is not a variable length array type;
     otherwise, the array type is a variable length array type.
-

-
-
-
Footnote 124) Thus, * can be used only in function declarations that are not definitions (see 6.7.5.3).
 

 
-
+
+
4   If the size is not present, the array type is an incomplete type. If the size is * instead of
+    being an expression, the array type is a variable length array type of unspecified size,
+    which can only be used in declarations with function prototype scope;[124] such arrays are
+    nonetheless complete types. If the size is an integer constant expression and the element
+

+
+
Footnote 124) Thus, * can be used only in function declarations that are not definitions (see 6.7.5.3).
+

+
+
 
5   If the size is an expression that is not an integer constant expression: if it occurs in a
     declaration at function prototype scope, it is treated as if it were replaced by *; otherwise,
     each time it is evaluated it shall have a value greater than zero. The size of each instance
@@ -6752,23 +5921,20 @@ Forward references:         conditional inclusion (6.10.1), complex arithmetic
     size expression would not affect the result of the operator, it is unspecified whether or not
     the size expression is evaluated.
 

-
-
+
 
6   For two array types to be compatible, both shall have compatible element types, and if
     both size specifiers are present, and are integer constant expressions, then both size
     specifiers shall have the same constant value. If the two array types are used in a context
     which requires them to be compatible, it is undefined behavior if the two size specifiers
     evaluate to unequal values.
 

-
-
+
 
7   EXAMPLE 1
              float fa[11], *afp[17];
     declares an array of float numbers and an array of pointers to float numbers.
 
 

-
-
+
 
8   EXAMPLE 2       Note the distinction between the declarations
              extern int *x;
              extern int y[];
@@ -6776,8 +5942,7 @@ Forward references:         conditional inclusion (6.10.1), complex arithmetic
     (an incomplete type), the storage for which is defined elsewhere.
 
 

-
-
+
 
9   EXAMPLE 3       The following declarations demonstrate the compatibility rules for variably modified types.
              extern int n;
              extern int m;
@@ -6792,8 +5957,7 @@ Forward references:         conditional inclusion (6.10.1), complex arithmetic
                                // n == 6 and m == n+1
              }
 

-
-
+
 
10   EXAMPLE 4 All declarations of variably modified (VM) types have to be at either block scope or
      function prototype scope. Array objects declared with the static or extern storage-class specifier
      cannot have a variable length array (VLA) type. However, an object declared with the static storage-
@@ -6819,36 +5983,30 @@ Forward references:         conditional inclusion (6.10.1), complex arithmetic
                        static int (*q)[m] = &B;                      //   valid: q is a static block pointer to VLA
               }
 
-     Forward references:            function declarators (6.7.5.3), function definitions (6.9.1),
-     initialization (6.7.8).
+     Forward references:            function declarators (6.7.5.3), function definitions (6.9.1),
+     initialization (6.7.8).
 

-
-
+
 

 
6.7.5.3 [Function declarators (including prototypes)]

-

-
-
-
1    A function declarator shall not specify a return type that is a function type or an array
+
+
1 Constraints
+    A function declarator shall not specify a return type that is a function type or an array
      type.
 

-
-
+
 
2    The only storage-class specifier that shall occur in a parameter declaration is register.
 

-
-
+
 
3    An identifier list in a function declarator that is not part of a definition of that function
      shall be empty.
 

-
-
+
 
4    After adjustment, the parameters in a parameter type list in a function declarator that is
      part of a definition of that function shall not have incomplete type.
      Semantics
 

-
-
+
 
5    If, in the declaration ``T D1'', D1 has the form
               D( parameter-type-list )
      or
@@ -6857,13 +6015,11 @@ Forward references:         conditional inclusion (6.10.1), complex arithmetic
      T '', then the type specified for ident is `` derived-declarator-type-list function returning
      T ''.
 

-
-
+
 
6    A parameter type list specifies the types of, and may declare identifiers for, the
      parameters of the function.
 

-
-
+
 
7    A declaration of a parameter as ``array of type'' shall be adjusted to ``qualified pointer to
      type'', where the type qualifiers (if any) are those specified within the [ and ] of the
      array type derivation. If the keyword static also appears within the [ and ] of the
@@ -6871,58 +6027,53 @@ Forward references:         conditional inclusion (6.10.1), complex arithmetic
      actual argument shall provide access to the first element of an array with at least as many
      elements as specified by the size expression.
 

-
-
+
 
8    A declaration of a parameter as ``function returning type'' shall be adjusted to ``pointer to
-     function returning type'', as in 6.3.2.1.
+     function returning type'', as in 6.3.2.1.
 

-
-
+
 
9    If the list terminates with an ellipsis (, ...), no information about the number or types
-     of the parameters after the comma is supplied.125)
+     of the parameters after the comma is supplied.[125]
 

-
 
-
Footnote 125) The macros defined in the <stdarg.h> header (7.15) may be used to access arguments that
+
Footnote 125) The macros defined in the <stdarg.h> header (7.15) may be used to access arguments that
           correspond to the ellipsis.
 

 
-
+
 
10   The special case of an unnamed parameter of type void as the only item in the list
      specifies that the function has no parameters.
 

-
-
+
 
11   If, in a parameter declaration, an identifier can be treated either as a typedef name or as a
      parameter name, it shall be taken as a typedef name.
 

-
-
+
 
12   If the function declarator is not part of a definition of that function, parameters may have
      incomplete type and may use the [*] notation in their sequences of declarator specifiers
      to specify variable length array types.
 

-
-
+
 
13   The storage-class specifier in the declaration specifiers for a parameter declaration, if
      present, is ignored unless the declared parameter is one of the members of the parameter
      type list for a function definition.
 

-
-
+
 
14   An identifier list declares only the identifiers of the parameters of the function. An empty
      list in a function declarator that is part of a definition of that function specifies that the
      function has no parameters. The empty list in a function declarator that is not part of a
      definition of that function specifies that no information about the number or types of the
-     parameters is supplied.126)
+     parameters is supplied.[126]
 

-
 
-
Footnote 126) See ``future language directions'' (6.11.6).
+
Footnote 126) See ``future language directions'' (6.11.6).
 

 
-
-
15   For two function types to be compatible, both shall specify compatible return types.127)
+
+
15   For two function types to be compatible, both shall specify compatible return types.[127]
+

+
+
Footnote 127) If both function types are ``old style'', parameter types are not compared.
      Moreover, the parameter type lists, if both are present, shall agree in the number of
      parameters and in use of the ellipsis terminator; corresponding parameters shall have
      compatible types. If one type has a parameter type list and the other type is specified by a
@@ -6937,13 +6088,9 @@ Forward references:         conditional inclusion (6.10.1), complex arithmetic
      compatibility and of a composite type, each parameter declared with function or array
      type is taken as having the adjusted type and each parameter declared with qualified type
      is taken as having the unqualified version of its declared type.)
-

-
-
-
Footnote 127) If both function types are ``old style'', parameter types are not compared.
 

 
-
+
 
16   EXAMPLE 1       The declaration
               int f(void), *fip(), (*pfi)();
      declares a function f with no parameters returning an int, a function fip with no parameter specification
@@ -6954,16 +6101,14 @@ Forward references:         conditional inclusion (6.10.1), complex arithmetic
      extra parentheses are necessary to indicate that indirection through a pointer to a function yields a function
      designator, which is then used to call the function; it returns an int.
 

-
-
+
 
17   If the declaration occurs outside of any function, the identifiers have file scope and external linkage. If the
      declaration occurs inside a function, the identifiers of the functions f and fip have block scope and either
      internal or external linkage (depending on what file scope declarations for these identifiers are visible), and
      the identifier of the pointer pfi has block scope and no linkage.
 
 

-
-
+
 
18   EXAMPLE 2       The declaration
               int (*apfi[3])(int *x, int *y);
      declares an array apfi of three pointers to functions returning int. Each of these functions has two
@@ -6971,8 +6116,7 @@ Forward references:         conditional inclusion (6.10.1), complex arithmetic
      go out of scope at the end of the declaration of apfi.
 
 

-
-
+
 
19   EXAMPLE 3       The declaration
               int (*fpfi(int (*)(long), int))(int, ...);
      declares a function fpfi that returns a pointer to a function returning an int. The function fpfi has two
@@ -6981,8 +6125,7 @@ Forward references:         conditional inclusion (6.10.1), complex arithmetic
      additional arguments of any type.
 
 

-
-
+
 
20   EXAMPLE 4        The following prototype has a variably modified parameter.
                void addscalar(int n, int m,
                      double a[n][n*m+300], double x);
@@ -7002,8 +6145,7 @@ Forward references:         conditional inclusion (6.10.1), complex arithmetic
                }
 
 

-
-
+
 
21   EXAMPLE 5        The following are all compatible function prototype declarators.
                double    maximum(int       n,   int   m,   double    a[n][m]);
                double    maximum(int       n,   int   m,   double    a[*][*]);
@@ -7017,17 +6159,15 @@ Forward references:         conditional inclusion (6.10.1), complex arithmetic
      (Note that the last declaration also specifies that the argument corresponding to a in any call to f must be a
      non-null pointer to the first of at least three arrays of 5 doubles, which the others do not.)
 
-     Forward references: function definitions (6.9.1), type names (6.7.6).
+     Forward references: function definitions (6.9.1), type names (6.7.6).
 
 

-
-
+
 

 
6.7.6 [Type names]

-

-
-
-
1            type-name:
+
+
1 Syntax
+            type-name:
                     specifier-qualifier-list abstract-declaratoropt
              abstract-declarator:
                     pointer
@@ -7044,19 +6184,17 @@ Forward references:         conditional inclusion (6.10.1), complex arithmetic
                      direct-abstract-declaratoropt ( parameter-type-listopt )
     Semantics
 

-
-
+
 
2   In several contexts, it is necessary to specify a type. This is accomplished using a type
     name, which is syntactically a declaration for a function or an object of that type that
-    omits the identifier.128)
+    omits the identifier.[128]
 

-
 
 
Footnote 128) As indicated by the syntax, empty parentheses in a type name are interpreted as ``function with no
          parameter specification'', rather than redundant parentheses around the omitted identifier.
 

 
-
+
 
3   EXAMPLE        The constructions
              (a)      int
              (b)      int   *
@@ -7073,27 +6211,23 @@ Forward references:         conditional inclusion (6.10.1), complex arithmetic
     parameter that has type unsigned int and an unspecified number of other parameters, returning an
     int.
 

-
-
+
 

 
6.7.7 [Type definitions]

-

-
-
-
1            typedef-name:
+
+
1 Syntax
+            typedef-name:
                     identifier
     Constraints
 

-
-
+
 
2   If a typedef name specifies a variably modified type then it shall have block scope.
     Semantics
 

-
-
+
 
3   In a declaration whose storage-class specifier is typedef, each declarator defines an
     identifier to be a typedef name that denotes the type specified for the identifier in the way
-    described in 6.7.5. Any array size expressions associated with variable length array
+    described in 6.7.5. Any array size expressions associated with variable length array
     declarators are evaluated each time the declaration of the typedef name is reached in the
     order of execution. A typedef declaration does not introduce a new type, only a
     synonym for the type so specified. That is, in the following declarations:
@@ -7105,8 +6239,7 @@ Forward references:         conditional inclusion (6.10.1), complex arithmetic
     typedef name shares the same name space as other identifiers declared in ordinary
     declarators.
 

-
-
+
 
4   EXAMPLE 1       After
              typedef int MILES, KLICKSP();
              typedef struct { double hi, lo; } range;
@@ -7120,8 +6253,7 @@ Forward references:         conditional inclusion (6.10.1), complex arithmetic
     such a structure. The object distance has a type compatible with any other int object.
 
 

-
-
+
 
5   EXAMPLE 2       After the declarations
              typedef struct s1 { int x; } t1, *tp1;
              typedef struct s2 { int x; } t2, *tp2;
@@ -7129,8 +6261,7 @@ Forward references:         conditional inclusion (6.10.1), complex arithmetic
     s1, but not compatible with the types struct s2, t2, the type pointed to by tp2, or int.
 
 

-
-
+
 
6   EXAMPLE 3       The following obscure constructions
              typedef signed int t;
              typedef int plain;
@@ -7154,8 +6285,7 @@ Forward references:         conditional inclusion (6.10.1), complex arithmetic
     int'', and an identifier t with type long int.
 
 

-
-
+
 
7   EXAMPLE 4 On the other hand, typedef names can be used to improve code readability. All three of the
     following declarations of the signal function specify exactly the same type, the first without making use
     of any typedef names.
@@ -7165,8 +6295,7 @@ Forward references:         conditional inclusion (6.10.1), complex arithmetic
              pfv signal(int, pfv);
 
 

-
-
+
 
8   EXAMPLE 5 If a typedef name denotes a variable length array type, the length of the array is fixed at the
     time the typedef name is defined, not each time it is used:
              void copyt(int n)
@@ -7180,14 +6309,12 @@ Forward references:         conditional inclusion (6.10.1), complex arithmetic
              }
 
 

-
-
+
 

 
6.7.8 [Initialization]

-

-
-
-
1            initializer:
+
+
1 Syntax
+            initializer:
                       assignment-expression
                       { initializer-list }
                       { initializer-list , }
@@ -7204,54 +6331,45 @@ Forward references:         conditional inclusion (6.10.1), complex arithmetic
                     . identifier
     Constraints
 

-
-
+
 
2   No initializer shall attempt to provide a value for an object not contained within the entity
     being initialized.
 

-
-
+
 
3   The type of the entity to be initialized shall be an array of unknown size or an object type
     that is not a variable length array type.
 

-
-
+
 
4   All the expressions in an initializer for an object that has static storage duration shall be
     constant expressions or string literals.
 

-
-
+
 
5   If the declaration of an identifier has block scope, and the identifier has external or
     internal linkage, the declaration shall have no initializer for the identifier.
 

-
-
+
 
6   If a designator has the form
              [ constant-expression ]
     then the current object (defined below) shall have array type and the expression shall be
     an integer constant expression. If the array is of unknown size, any nonnegative value is
     valid.
 

-
-
+
 
7   If a designator has the form
              . identifier
     then the current object (defined below) shall have structure or union type and the
     identifier shall be the name of a member of that type.
      Semantics
 

-
-
+
 
8    An initializer specifies the initial value stored in an object.
 

-
-
+
 
9    Except where explicitly stated otherwise, for the purposes of this subclause unnamed
      members of objects of structure and union type do not participate in initialization.
      Unnamed members of structure objects have indeterminate value even after initialization.
 

-
-
+
 
10   If an object that has automatic storage duration is not initialized explicitly, its value is
      indeterminate. If an object that has static storage duration is not initialized explicitly,
      then:
@@ -7261,55 +6379,47 @@ Forward references:         conditional inclusion (6.10.1), complex arithmetic
      -- if it is a union, the first named member is initialized (recursively) according to these
         rules.
 

-
-
+
 
11   The initializer for a scalar shall be a single expression, optionally enclosed in braces. The
      initial value of the object is that of the expression (after conversion); the same type
      constraints and conversions as for simple assignment apply, taking the type of the scalar
      to be the unqualified version of its declared type.
 

-
-
+
 
12   The rest of this subclause deals with initializers for objects that have aggregate or union
      type.
 

-
-
+
 
13   The initializer for a structure or union object that has automatic storage duration shall be
      either an initializer list as described below, or a single expression that has compatible
      structure or union type. In the latter case, the initial value of the object, including
      unnamed members, is that of the expression.
 

-
-
+
 
14   An array of character type may be initialized by a character string literal, optionally
      enclosed in braces. Successive characters of the character string literal (including the
      terminating null character if there is room or if the array is of unknown size) initialize the
      elements of the array.
 

-
-
+
 
15   An array with element type compatible with wchar_t may be initialized by a wide
      string literal, optionally enclosed in braces. Successive wide characters of the wide string
      literal (including the terminating null wide character if there is room or if the array is of
      unknown size) initialize the elements of the array.
 

-
-
+
 
16   Otherwise, the initializer for an object that has aggregate or union type shall be a brace-
      enclosed list of initializers for the elements or named members.
 

-
-
+
 
17   Each brace-enclosed initializer list has an associated current object . When no
      designations are present, subobjects of the current object are initialized in order according
      to the type of the current object: array elements in increasing subscript order, structure
-     members in declaration order, and the first named member of a union.129) In contrast, a
+     members in declaration order, and the first named member of a union.[129] In contrast, a
      designation causes the following initializer to begin initialization of the subobject
      described by the designator. Initialization then continues forward in order, beginning
-     with the next subobject after that described by the designator.130)
+     with the next subobject after that described by the designator.[130]
 

-
 
 
Footnote 129) If the initializer list for a subaggregate or contained union does not begin with a left brace, its
           subobjects are initialized as usual, but the subaggregate or contained union does not become the
@@ -7321,32 +6431,30 @@ Forward references:         conditional inclusion (6.10.1), complex arithmetic
           the next subobject of an object containing the union.
 

 
-
+
 
18   Each designator list begins its description with the current object associated with the
      closest surrounding brace pair. Each item in the designator list (in order) specifies a
      particular member of its current object and changes the current object for the next
-     designator (if any) to be that member.131) The current object that results at the end of the
+     designator (if any) to be that member.[131] The current object that results at the end of the
      designator list is the subobject to be initialized by the following initializer.
 

-
 
 
Footnote 131) Thus, a designator can only specify a strict subobject of the aggregate or union that is associated with
           the surrounding brace pair. Note, too, that each separate designator list is independent.
 

 
-
+
 
19   The initialization shall occur in initializer list order, each initializer provided for a
-     particular subobject overriding any previously listed initializer for the same subobject;132)
+     particular subobject overriding any previously listed initializer for the same subobject;[132]
      all subobjects that are not initialized explicitly shall be initialized implicitly the same as
      objects that have static storage duration.
 

-
 
 
Footnote 132) Any initializer for the subobject which is overridden and so not used to initialize that subobject might
           not be evaluated at all.
 

 
-
+
 
20   If the aggregate or union contains elements or members that are aggregates or unions,
      these rules apply recursively to the subaggregates or contained unions. If the initializer of
      a subaggregate or contained union begins with a left brace, the initializers enclosed by
@@ -7356,46 +6464,40 @@ Forward references:         conditional inclusion (6.10.1), complex arithmetic
      the contained union; any remaining initializers are left to initialize the next element or
      member of the aggregate of which the current subaggregate or contained union is a part.
 

-
-
+
 
21   If there are fewer initializers in a brace-enclosed list than there are elements or members
      of an aggregate, or fewer characters in a string literal used to initialize an array of known
      size than there are elements in the array, the remainder of the aggregate shall be
      initialized implicitly the same as objects that have static storage duration.
 

-
-
+
 
22   If an array of unknown size is initialized, its size is determined by the largest indexed
      element with an explicit initializer. At the end of its initializer list, the array no longer
      has incomplete type.
 

-
-
+
 
23   The order in which any side effects occur among the initialization list expressions is
-     unspecified.133)
+     unspecified.[133]
 

-
 
 
Footnote 133) In particular, the evaluation order need not be the same as the order of subobject initialization.
 

 
-
+
 
24   EXAMPLE 1        Provided that <complex.h> has been #included, the declarations
-              int i = 3.5;
+              int i = 3.5;
               double complex c = 5 + 3 * I;
      define and initialize i with the value 3 and c with the value 5. 0 + i 3. 0.
 
 

-
-
+
 
25   EXAMPLE 2        The declaration
               int x[] = { 1, 3, 5 };
      defines and initializes x as a one-dimensional array object that has three elements, as no size was specified
      and there are three initializers.
 
 

-
-
+
 
26   EXAMPLE 3        The declaration
               int y[4][3] =          {
                     { 1, 3,          5 },
@@ -7413,8 +6515,7 @@ Forward references:         conditional inclusion (6.10.1), complex arithmetic
      next three are taken successively for y[1] and y[2].
 
 

-
-
+
 
27   EXAMPLE 4        The declaration
               int z[4][3] = {
                     { 1 }, { 2 }, { 3 }, { 4 }
@@ -7422,15 +6523,13 @@ Forward references:         conditional inclusion (6.10.1), complex arithmetic
      initializes the first column of z as specified and initializes the rest with zeros.
 
 

-
-
+
 
28   EXAMPLE 5        The declaration
               struct { int a[3], b; } w[] = { { 1 }, 2 };
      is a definition with an inconsistently bracketed initialization. It defines an array with two element
      structures: w[0].a[0] is 1 and w[1].a[0] is 2; all the other elements are zero.
 

-
-
+
 
29   EXAMPLE 6         The declaration
                short q[4][3][2] = {
                      { 1 },
@@ -7465,14 +6564,12 @@ Forward references:         conditional inclusion (6.10.1), complex arithmetic
                };
      in a fully bracketed form.
 

-
-
+
 
30   Note that the fully bracketed and minimally bracketed forms of initialization are, in general, less likely to
      cause confusion.
 
 

-
-
+
 
31   EXAMPLE 7         One form of initialization that completes array types involves typedef names. Given the
      declaration
                typedef int A[];          // OK - declared with block scope
@@ -7482,8 +6579,7 @@ Forward references:         conditional inclusion (6.10.1), complex arithmetic
                int a[] = { 1, 2 }, b[] = { 3, 4, 5 };
      due to the rules for incomplete types.
 

-
-
+
 
32   EXAMPLE 8       The declaration
               char s[] = "abc", t[3] = "abc";
      defines ``plain'' char array objects s and t whose elements are initialized with character string literals.
@@ -7497,8 +6593,7 @@ Forward references:         conditional inclusion (6.10.1), complex arithmetic
      modify the contents of the array, the behavior is undefined.
 
 

-
-
+
 
33   EXAMPLE 9       Arrays can be initialized to correspond to the elements of an enumeration by using
      designators:
               enum { member_one,           member_two };
@@ -7508,49 +6603,42 @@ Forward references:         conditional inclusion (6.10.1), complex arithmetic
               };
 
 

-
-
+
 
34   EXAMPLE 10       Structure members can be initialized to nonzero values without depending on their order:
               div_t answer = { .quot = 2, .rem = -1 };
 
 

-
-
+
 
35   EXAMPLE 11 Designators can be used to provide explicit initialization when unadorned initializer lists
      might be misunderstood:
               struct { int a[3], b; } w[] =
                     { [0].a = {1}, [1].a[0] = 2 };
 
 

-
-
+
 
36   EXAMPLE 12       Space can be ``allocated'' from both ends of an array by using a single designator:
               int a[MAX] = {
                     1, 3, 5, 7, 9, [MAX-5] = 8, 6, 4, 2, 0
               };
 

-
-
+
 
37   In the above, if MAX is greater than ten, there will be some zero-valued elements in the middle; if it is less
      than ten, some of the values provided by the first five initializers will be overridden by the second five.
 
 

-
-
+
 
38   EXAMPLE 13       Any member of a union can be initialized:
               union { /* ... */ } u = { .any_member = 42 };
 
-     Forward references: common definitions <stddef.h> (7.17).
+     Forward references: common definitions <stddef.h> (7.17).
 
 

-
-
+
 

 
6.8 [Statements and blocks]

-

-
-
-
1            statement:
+
+
1 Syntax
+            statement:
                     labeled-statement
                     compound-statement
                     expression-statement
@@ -7559,13 +6647,11 @@ Forward references:         conditional inclusion (6.10.1), complex arithmetic
                     jump-statement
     Semantics
 

-
-
+
 
2   A statement specifies an action to be performed. Except as indicated, statements are
     executed in sequence.
 

-
-
+
 
3   A block allows a set of declarations and statements to be grouped into one syntactic unit.
     The initializers of objects that have automatic storage duration, and the variable length
     array declarators of ordinary identifiers with block scope, are evaluated and the values are
@@ -7573,55 +6659,47 @@ Forward references:         conditional inclusion (6.10.1), complex arithmetic
     initializer) each time the declaration is reached in the order of execution, as if it were a
     statement, and within each declaration in the order that declarators appear.
 

-
-
+
 
4   A full expression is an expression that is not part of another expression or of a declarator.
     Each of the following is a full expression: an initializer; the expression in an expression
     statement; the controlling expression of a selection statement (if or switch); the
     controlling expression of a while or do statement; each of the (optional) expressions of
     a for statement; the (optional) expression in a return statement. The end of a full
     expression is a sequence point.
-    Forward references: expression and null statements (6.8.3), selection statements
-    (6.8.4), iteration statements (6.8.5), the return statement (6.8.6.4).
+    Forward references: expression and null statements (6.8.3), selection statements
+    (6.8.4), iteration statements (6.8.5), the return statement (6.8.6.4).
 

-
-
+
 

 
6.8.1 [Labeled statements]

-

-
-
-
1            labeled-statement:
+
+
1 Syntax
+            labeled-statement:
                     identifier : statement
                     case constant-expression : statement
                     default : statement
     Constraints
 

-
-
+
 
2   A case or default label shall appear only in a switch statement. Further
     constraints on such labels are discussed under the switch statement.
 

-
-
+
 
3   Label names shall be unique within a function.
     Semantics
 

-
-
+
 
4   Any statement may be preceded by a prefix that declares an identifier as a label name.
     Labels in themselves do not alter the flow of control, which continues unimpeded across
     them.
-    Forward references: the goto statement (6.8.6.1), the switch statement (6.8.4.2).
+    Forward references: the goto statement (6.8.6.1), the switch statement (6.8.4.2).
 

-
-
+
 

 
6.8.2 [Compound statement]

-

-
-
-
1            compound-statement:
+
+
1 Syntax
+            compound-statement:
                    { block-item-listopt }
              block-item-list:
                      block-item
@@ -7631,36 +6709,30 @@ Forward references:         conditional inclusion (6.10.1), complex arithmetic
                      statement
     Semantics
 

-
-
+
 
2   A compound statement is a block.
 

-
-
+
 

 
6.8.3 [Expression and null statements]

-

-
-
-
1            expression-statement:
+
+
1 Syntax
+            expression-statement:
                     expressionopt ;
     Semantics
 

-
-
+
 
2   The expression in an expression statement is evaluated as a void expression for its side
-    effects.134)
+    effects.[134]
 

-
 
 
Footnote 134) Such as assignments, and function calls which have side effects.
 

 
-
+
 
3   A null statement (consisting of just a semicolon) performs no operations.
 

-
-
+
 
4   EXAMPLE 1 If a function call is evaluated as an expression statement for its side effects only, the
     discarding of its value may be made explicit by converting the expression to a void expression by means of
     a cast:
@@ -7668,8 +6740,7 @@ Forward references:         conditional inclusion (6.10.1), complex arithmetic
              /* ... */
              (void)p(0);
 

-
-
+
 
5   EXAMPLE 2       In the program fragment
              char *s;
              /* ... */
@@ -7678,8 +6749,7 @@ Forward references:         conditional inclusion (6.10.1), complex arithmetic
     a null statement is used to supply an empty loop body to the iteration statement.
 
 

-
-
+
 
6   EXAMPLE 3       A null statement may also be used to carry a label just before the closing } of a compound
     statement.
              while (loop1) {
@@ -7694,76 +6764,64 @@ Forward references:         conditional inclusion (6.10.1), complex arithmetic
              end_loop1: ;
              }
 
-    Forward references: iteration statements (6.8.5).
+    Forward references: iteration statements (6.8.5).
 

-
-
+
 

 
6.8.4 [Selection statements]

-

-
-
-
1            selection-statement:
+
+
1 Syntax
+            selection-statement:
                      if ( expression ) statement
                      if ( expression ) statement else statement
                      switch ( expression ) statement
     Semantics
 

-
-
+
 
2   A selection statement selects among a set of statements depending on the value of a
     controlling expression.
 

-
-
+
 
3   A selection statement is a block whose scope is a strict subset of the scope of its
     enclosing block. Each associated substatement is also a block whose scope is a strict
     subset of the scope of the selection statement.
 

-
-
+
 

 
6.8.4.1 [The if statement]

-

-
-
-
1   The controlling expression of an if statement shall have scalar type.
+
+
1 Constraints
+   The controlling expression of an if statement shall have scalar type.
     Semantics
 

-
-
+
 
2   In both forms, the first substatement is executed if the expression compares unequal to 0.
     In the else form, the second substatement is executed if the expression compares equal
     to 0. If the first substatement is reached via a label, the second substatement is not
     executed.
 

-
-
+
 
3   An else is associated with the lexically nearest preceding if that is allowed by the
     syntax.
 

-
-
+
 

 
6.8.4.2 [The switch statement]

-

-
-
-
1   The controlling expression of a switch statement shall have integer type.
+
+
1 Constraints
+   The controlling expression of a switch statement shall have integer type.
 

-
-
+
 
2   If a switch statement has an associated case or default label within the scope of an
     identifier with a variably modified type, the entire switch statement shall be within the
-    scope of that identifier.135)
+    scope of that identifier.[135]
 

-
 
 
Footnote 135) That is, the declaration either precedes the switch statement, or it follows the last case or
          default label associated with the switch that is in the block containing the declaration.
 

 
-
+
 
3   The expression of each case label shall be an integer constant expression and no two of
     the case constant expressions in the same switch statement shall have the same value
     after conversion. There may be at most one default label in a switch statement.
@@ -7772,15 +6830,13 @@ Forward references:         conditional inclusion (6.10.1), complex arithmetic
     switch statement.)
     Semantics
 

-
-
+
 
4   A switch statement causes control to jump to, into, or past the statement that is the
     switch body , depending on the value of a controlling expression, and on the presence of a
     default label and the values of any case labels on or in the switch body. A case or
     default label is accessible only within the closest enclosing switch statement.
 

-
-
+
 
5   The integer promotions are performed on the controlling expression. The constant
     expression in each case label is converted to the promoted type of the controlling
     expression. If a converted value matches that of the promoted controlling expression,
@@ -7790,13 +6846,11 @@ Forward references:         conditional inclusion (6.10.1), complex arithmetic
     executed.
     Implementation limits
 

-
-
-
6   As discussed in 5.2.4.1, the implementation may limit the number of case values in a
+
+
6   As discussed in 5.2.4.1, the implementation may limit the number of case values in a
     switch statement.
 

-
-
+
 
7   EXAMPLE        In the artificial program fragment
              switch (expr)
              {
@@ -7813,74 +6867,59 @@ Forward references:         conditional inclusion (6.10.1), complex arithmetic
     access an indeterminate value. Similarly, the call to the function f cannot be reached.
 
 

-
-
+
 

 
6.8.5 [Iteration statements]

-

-
-
-
1            iteration-statement:
+
+
1 Syntax
+            iteration-statement:
                      while ( expression ) statement
                      do statement while ( expression ) ;
                      for ( expressionopt ; expressionopt ; expressionopt ) statement
                      for ( declaration expressionopt ; expressionopt ) statement
     Constraints
 

-
-
+
 
2   The controlling expression of an iteration statement shall have scalar type.
 

-
-
+
 
3   The declaration part of a for statement shall only declare identifiers for objects having
     storage class auto or register.
     Semantics
 

-
-
+
 
4   An iteration statement causes a statement called the loop body to be executed repeatedly
     until the controlling expression compares equal to 0. The repetition occurs regardless of
-    whether the loop body is entered from the iteration statement or by a jump.136)
+    whether the loop body is entered from the iteration statement or by a jump.[136]
 

-
 
 
Footnote 136) Code jumped over is not executed. In particular, the controlling expression of a for or while
          statement is not evaluated before entering the loop body, nor is clause-1 of a for statement.
 

 
-
+
 
5   An iteration statement is a block whose scope is a strict subset of the scope of its
     enclosing block. The loop body is also a block whose scope is a strict subset of the scope
     of the iteration statement.
 

-
-
+
 

 
6.8.5.1 [The while statement]

-

-
-
+
 
1   The evaluation of the controlling expression takes place before each execution of the loop
     body.
 

-
-
+
 

 
6.8.5.2 [The do statement]

-

-
-
+
 
1   The evaluation of the controlling expression takes place after each execution of the loop
     body.
 

-
-
+
 

 
6.8.5.3 [The for statement]

-

-
-
+
 
1   The statement
              for ( clause-1 ; expression-2 ; expression-3 ) statement
     behaves as follows: The expression expression-2 is the controlling expression that is
@@ -7889,9 +6928,8 @@ Forward references:         conditional inclusion (6.10.1), complex arithmetic
     declaration, the scope of any identifiers it declares is the remainder of the declaration and
     the entire loop, including the other two expressions; it is reached in the order of execution
     before the first evaluation of the controlling expression. If clause-1 is an expression, it is
-    evaluated as a void expression before the first evaluation of the controlling expression.137)
+    evaluated as a void expression before the first evaluation of the controlling expression.[137]
 

-
 
 
Footnote 137) Thus, clause-1 specifies initialization for the loop, possibly declaring one or more variables for use in
          the loop; the controlling expression, expression-2, specifies an evaluation made before each iteration,
@@ -7899,47 +6937,40 @@ Forward references:         conditional inclusion (6.10.1), complex arithmetic
          specifies an operation (such as incrementing) that is performed after each iteration.
 

 
-
+
 
2   Both clause-1 and expression-3 can be omitted. An omitted expression-2 is replaced by a
     nonzero constant.
 

-
-
+
 

 
6.8.6 [Jump statements]

-

-
-
-
1            jump-statement:
+
+
1 Syntax
+            jump-statement:
                     goto identifier ;
                     continue ;
                     break ;
                     return expressionopt ;
     Semantics
 

-
-
+
 
2   A jump statement causes an unconditional jump to another place.
 

-
-
+
 

 
6.8.6.1 [The goto statement]

-

-
-
-
1   The identifier in a goto statement shall name a label located somewhere in the enclosing
+
+
1 Constraints
+   The identifier in a goto statement shall name a label located somewhere in the enclosing
     function. A goto statement shall not jump from outside the scope of an identifier having
     a variably modified type to inside the scope of that identifier.
     Semantics
 

-
-
+
 
2   A goto statement causes an unconditional jump to the statement prefixed by the named
     label in the enclosing function.
 

-
-
+
 
3   EXAMPLE 1 It is sometimes convenient to jump into the middle of a complicated set of statements. The
     following outline presents one possible approach to a problem based on these three assumptions:
       1.   The general initialization code accesses objects only visible to the current function.
@@ -7964,8 +6995,7 @@ Forward references:         conditional inclusion (6.10.1), complex arithmetic
             }
 
 

-
-
+
 
4   EXAMPLE 2 A goto statement is not allowed to jump past any declarations of objects with variably
     modified types. A jump within the scope, however, is permitted.
             goto lab3;                         // invalid: going INTO scope of VLA.
@@ -7973,27 +7003,24 @@ Forward references:         conditional inclusion (6.10.1), complex arithmetic
                   double a[n];
                   a[j] = 4.4;
             lab3:
-                  a[j] = 3.3;
+                  a[j] = 3.3;
                   goto lab4;                   // valid: going WITHIN scope of VLA.
                   a[j] = 5.5;
             lab4:
-                  a[j] = 6.6;
+                  a[j] = 6.6;
             }
             goto lab4;                         // invalid: going INTO scope of VLA.
 
 

-
-
+
 

 
6.8.6.2 [The continue statement]

-

-
-
-
1   A continue statement shall appear only in or as a loop body.
+
+
1 Constraints
+   A continue statement shall appear only in or as a loop body.
     Semantics
 

-
-
+
 
2   A continue statement causes a jump to the loop-continuation portion of the smallest
     enclosing iteration statement; that is, to the end of the loop body. More precisely, in each
     of the statements
@@ -8004,60 +7031,52 @@ Forward references:         conditional inclusion (6.10.1), complex arithmetic
     contin: ;                            contin: ;                            contin: ;
     }                                    } while (/* ... */);                 }
     unless the continue statement shown is in an enclosed iteration statement (in which
-    case it is interpreted within that statement), it is equivalent to goto contin;.138)
+    case it is interpreted within that statement), it is equivalent to goto contin;.[138]
 

-
 
 
Footnote 138) Following the contin: label is a null statement.
 

 
-
+
 

 
6.8.6.3 [The break statement]

-

-
-
-
1   A break statement shall appear only in or as a switch body or loop body.
+
+
1 Constraints
+   A break statement shall appear only in or as a switch body or loop body.
     Semantics
 

-
-
+
 
2   A break statement terminates execution of the smallest enclosing switch or iteration
     statement.
 

-
-
+
 

 
6.8.6.4 [The return statement]

-

-
-
-
1   A return statement with an expression shall not appear in a function whose return type
+
+
1 Constraints
+   A return statement with an expression shall not appear in a function whose return type
     is void. A return statement without an expression shall only appear in a function
     whose return type is void.
     Semantics
 

-
-
+
 
2   A return statement terminates execution of the current function and returns control to
     its caller. A function may have any number of return statements.
 

-
-
+
 
3   If a return statement with an expression is executed, the value of the expression is
     returned to the caller as the value of the function call expression. If the expression has a
     type different from the return type of the function in which it appears, the value is
-    converted as if by assignment to an object having the return type of the function.139)
+    converted as if by assignment to an object having the return type of the function.[139]
 

-
 
-
Footnote 139) The return statement is not an assignment. The overlap restriction of subclause 6.5.16.1 does not
+
Footnote 139) The return statement is not an assignment. The overlap restriction of subclause 6.5.16.1 does not
          apply to the case of function return. The representation of floating-point values may have wider range
          or precision and is determined by FLT_EVAL_METHOD. A cast may be used to remove this extra
          range and precision.
 

 
-
+
 
4   EXAMPLE       In:
             struct s { double i; } f(void);
             union {
@@ -8079,14 +7098,12 @@ Forward references:         conditional inclusion (6.10.1), complex arithmetic
     there is no undefined behavior, although there would be if the assignment were done directly (without using
     a function call to fetch the value).
 

-
-
+
 

 
6.9 [External definitions]

-

-
-
-
1            translation-unit:
+
+
1 Syntax
+            translation-unit:
                      external-declaration
                      translation-unit external-declaration
              external-declaration:
@@ -8094,13 +7111,11 @@ Forward references:         conditional inclusion (6.10.1), complex arithmetic
                     declaration
     Constraints
 

-
-
+
 
2   The storage-class specifiers auto and register shall not appear in the declaration
     specifiers in an external declaration.
 

-
-
+
 
3   There shall be no more than one external definition for each identifier declared with
     internal linkage in a translation unit. Moreover, if an identifier declared with internal
     linkage is used in an expression (other than as a part of the operand of a sizeof
@@ -8108,48 +7123,42 @@ Forward references:         conditional inclusion (6.10.1), complex arithmetic
     for the identifier in the translation unit.
     Semantics
 

-
-
-
4   As discussed in 5.1.1.1, the unit of program text after preprocessing is a translation unit,
+
+
4   As discussed in 5.1.1.1, the unit of program text after preprocessing is a translation unit,
     which consists of a sequence of external declarations. These are described as ``external''
-    because they appear outside any function (and hence have file scope). As discussed in 6.7,
+    because they appear outside any function (and hence have file scope). As discussed in 6.7,
     a declaration that also causes storage to be reserved for an object or a function named
     by the identifier is a definition.
 

-
-
+
 
5   An external definition is an external declaration that is also a definition of a function
     (other than an inline definition) or an object. If an identifier declared with external
     linkage is used in an expression (other than as part of the operand of a sizeof operator
     whose result is an integer constant), somewhere in the entire program there shall be
     exactly one external definition for the identifier; otherwise, there shall be no more than
-    one.140)
+    one.[140]
 

-
 
 
Footnote 140) Thus, if an identifier declared with external linkage is not used in an expression, there need be no
          external definition for it.
 

 
-
+
 

 
6.9.1 [Function definitions]

-

-
-
-
1            function-definition:
+
+
1 Syntax
+            function-definition:
                     declaration-specifiers declarator declaration-listopt compound-statement
              declaration-list:
                     declaration
                     declaration-list declaration
     Constraints
 

-
-
+
 
2   The identifier declared in a function definition (which is the name of the function) shall
-    have a function type, as specified by the declarator portion of the function definition.141)
+    have a function type, as specified by the declarator portion of the function definition.[141]
 

-
 
 
Footnote 141) The intent is that the type category in a function definition cannot be inherited from a typedef:
                   typedef int F(void);                          //   type F is ``function with no parameters
@@ -8163,83 +7172,76 @@ Forward references:         conditional inclusion (6.10.1), complex arithmetic
                   F *((e))(void) { /* ... */ }                  //   same: parentheses irrelevant
                   int (*fp)(void);                              //   fp points to a function that has type F
                   F *Fp;                                        //   Fp points to a function that has type F
+     Semantics
 

 
-
+
 
3   The return type of a function shall be void or an object type other than array type.
 

-
-
+
 
4   The storage-class specifier, if any, in the declaration specifiers shall be either extern or
     static.
 

-
-
+
 
5   If the declarator includes a parameter type list, the declaration of each parameter shall
     include an identifier, except for the special case of a parameter list consisting of a single
     parameter of type void, in which case there shall not be an identifier. No declaration list
     shall follow.
 

-
-
+
 
6   If the declarator includes an identifier list, each declaration in the declaration list shall
     have at least one declarator, those declarators shall declare only identifiers from the
     identifier list, and every identifier in the identifier list shall be declared. An identifier
     declared as a typedef name shall not be redeclared as a parameter. The declarations in the
     declaration list shall contain no storage-class specifier other than register and no
     initializations.
-     Semantics
 

-
-
+
 
7    The declarator in a function definition specifies the name of the function being defined
      and the identifiers of its parameters. If the declarator includes a parameter type list, the
      list also specifies the types of all the parameters; such a declarator also serves as a
      function prototype for later calls to the same function in the same translation unit. If the
-     declarator includes an identifier list,142) the types of the parameters shall be declared in a
+     declarator includes an identifier list,[142] the types of the parameters shall be declared in a
      following declaration list. In either case, the type of each parameter is adjusted as
-     described in 6.7.5.3 for a parameter type list; the resulting type shall be an object type.
+     described in 6.7.5.3 for a parameter type list; the resulting type shall be an object type.
 

-
 
-
Footnote 142) See ``future language directions'' (6.11.7).
+
Footnote 142) See ``future language directions'' (6.11.7).
               extern int max(a, b)
               int a, b;
               {
                     return a > b ? a : b;
               }
+     Here int a, b; is the declaration list for the parameters. The difference between these two definitions is
+     that the first form acts as a prototype declaration that forces conversion of the arguments of subsequent calls
+     to the function, whereas the second form does not.
 

 
-
+
 
8    If a function that accepts a variable number of arguments is defined without a parameter
      type list that ends with the ellipsis notation, the behavior is undefined.
 

-
-
+
 
9    Each parameter has automatic storage duration. Its identifier is an lvalue, which is in
      effect declared at the head of the compound statement that constitutes the function body
      (and therefore cannot be redeclared in the function body except in an enclosed block).
      The layout of the storage for parameters is unspecified.
 

-
-
+
 
10   On entry to the function, the size expressions of each variably modified parameter are
      evaluated and the value of each argument expression is converted to the type of the
      corresponding parameter as if by assignment. (Array expressions and function
      designators as arguments were converted to pointers before the call.)
 

-
-
+
 
11   After all parameters have been assigned, the compound statement that constitutes the
      body of the function definition is executed.
 

-
-
+
 
12   If the } that terminates a function is reached, and the value of the function call is used by
      the caller, the behavior is undefined.
 

-
-
+
 
13   EXAMPLE 1       In the following:
               extern int max(int a, int b)
               {
@@ -8250,13 +7252,9 @@ Forward references:         conditional inclusion (6.10.1), complex arithmetic
               { return a > b ? a : b; }
      is the function body. The following similar definition uses the identifier-list form for the parameter
      declarations:
-     Here int a, b; is the declaration list for the parameters. The difference between these two definitions is
-     that the first form acts as a prototype declaration that forces conversion of the arguments of subsequent calls
-     to the function, whereas the second form does not.
 
 

-
-
+
 
14   EXAMPLE 2           To pass one function to another, one might say
                           int f(void);
                           /* ... */
@@ -8274,18 +7272,15 @@ Forward references:         conditional inclusion (6.10.1), complex arithmetic
                     func(); /* or (*func)(); ...                   */
               }
 

-
-
+
 

 
6.9.2 [External object definitions]

-

-
-
-
1    If the declaration of an identifier for an object has file scope and an initializer, the
+
+
1 Semantics
+    If the declaration of an identifier for an object has file scope and an initializer, the
      declaration is an external definition for the identifier.
 

-
-
+
 
2    A declaration of an identifier for an object that has file scope without an initializer, and
      without a storage-class specifier or with the storage-class specifier static, constitutes a
      tentative definition. If a translation unit contains one or more tentative definitions for an
@@ -8294,14 +7289,12 @@ Forward references:         conditional inclusion (6.10.1), complex arithmetic
      identifier, with the composite type as of the end of the translation unit, with an initializer
      equal to 0.
 

-
-
+
 
3    If the declaration of an identifier for an object is a tentative definition and has internal
      linkage, the declared type shall not be an incomplete type.
 
 

-
-
+
 
4   EXAMPLE 1
              int i1 = 1;                    // definition, external linkage
              static int i2 = 2;             // definition, internal linkage
@@ -8309,10 +7302,10 @@ Forward references:         conditional inclusion (6.10.1), complex arithmetic
              int i4;                        // tentative definition, external linkage
              static int i5;                 // tentative definition, internal linkage
              int   i1;                      // valid tentative definition, refers to previous
-             int   i2;                      // 6.2.2 renders undefined, linkage disagreement
+             int   i2;                      // 6.2.2 renders undefined, linkage disagreement
              int   i3;                      // valid tentative definition, refers to previous
              int   i4;                      // valid tentative definition, refers to previous
-             int   i5;                      // 6.2.2 renders undefined, linkage disagreement
+             int   i5;                      // 6.2.2 renders undefined, linkage disagreement
              extern    int   i1;            // refers to previous, whose linkage is external
              extern    int   i2;            // refers to previous, whose linkage is internal
              extern    int   i3;            // refers to previous, whose linkage is external
@@ -8320,22 +7313,19 @@ Forward references:         conditional inclusion (6.10.1), complex arithmetic
              extern    int   i5;            // refers to previous, whose linkage is internal
 
 

-
-
+
 
5   EXAMPLE 2       If at the end of the translation unit containing
              int i[];
     the array i still has incomplete type, the implicit initializer causes it to have one element, which is set to
     zero on program startup.
 
 

-
-
+
 

 
6.10 [Preprocessing directives]

-

-
-
-
1            preprocessing-file:
+
+
1 Syntax
+            preprocessing-file:
                     groupopt
              group:
                       group-part
@@ -8389,31 +7379,33 @@ Forward references:         conditional inclusion (6.10.1), complex arithmetic
                     the new-line character
     Description
 

-
-
+
 
2   A preprocessing directive consists of a sequence of preprocessing tokens that satisfies the
     following constraints: The first token in the sequence is a # preprocessing token that (at
     the start of translation phase 4) is either the first character in the source file (optionally
     after white space containing no new-line characters) or that follows white space
     containing at least one new-line character. The last token in the sequence is the first new-
-    line character that follows the first token in the sequence.143) A new-line character ends
+    line character that follows the first token in the sequence.[143] A new-line character ends
     the preprocessing directive even if it occurs within what would otherwise be an
-    invocation of a function-like macro.
 

+
+
Footnote 143) Thus, preprocessing directives are commonly called ``lines''. These ``lines'' have no other syntactic
+         significance, as all white space is equivalent except in certain situations during preprocessing (see the
+         # character string literal creation operator in 6.10.3.2, for example).
+    invocation of a function-like macro.
+

 
-
+
 
3   A text line shall not begin with a # preprocessing token. A non-directive shall not begin
     with any of the directive names appearing in the syntax.
 

-
-
-
4   When in a group that is skipped (6.10.1), the directive syntax is relaxed to allow any
+
+
4   When in a group that is skipped (6.10.1), the directive syntax is relaxed to allow any
     sequence of preprocessing tokens to occur between the directive name and the following
     new-line character.
     Constraints
 

-
-
+
 
5   The only white-space characters that shall appear between preprocessing tokens within a
     preprocessing directive (from just after the introducing # preprocessing token through
     just before the terminating new-line character) are space and horizontal-tab (including
@@ -8421,19 +7413,16 @@ Forward references:         conditional inclusion (6.10.1), complex arithmetic
     translation phase 3).
     Semantics
 

-
-
+
 
6   The implementation can process and skip sections of source files conditionally, include
     other source files, and replace macros. These capabilities are called preprocessing,
     because conceptually they occur before translation of the resulting translation unit.
 

-
-
+
 
7   The preprocessing tokens within a preprocessing directive are not subject to macro
     expansion unless otherwise stated.
 

-
-
+
 
8   EXAMPLE        In:
              #define EMPTY
              EMPTY # include <file.h>
@@ -8442,45 +7431,40 @@ Forward references:         conditional inclusion (6.10.1), complex arithmetic
     replaced.
 
 

-
-
+
 

 
6.10.1 [Conditional inclusion]

-

-
-
-
1   The expression that controls conditional inclusion shall be an integer constant expression
+
+
1 Constraints
+   The expression that controls conditional inclusion shall be an integer constant expression
     except that: it shall not contain a cast; identifiers (including those lexically identical to
-    keywords) are interpreted as described below;144) and it may contain unary operator
+    keywords) are interpreted as described below;[144] and it may contain unary operator
     expressions of the form
+

+
+
Footnote 144) Because the controlling constant expression is evaluated during translation phase 4, all identifiers
+         either are or are not macro names -- there simply are no keywords, enumeration constants, etc.
+         defined identifier
     or
          defined ( identifier )
     which evaluate to 1 if the identifier is currently defined as a macro name (that is, if it is
     predefined or if it has been the subject of a #define preprocessing directive without an
     intervening #undef directive with the same subject identifier), 0 if it is not.
-

-
-
-
Footnote 144) Because the controlling constant expression is evaluated during translation phase 4, all identifiers
-         either are or are not macro names -- there simply are no keywords, enumeration constants, etc.
-         defined identifier
 

 
-
+
 
2   Each preprocessing token that remains (in the list of preprocessing tokens that will
     become the controlling expression) after all macro replacements have occurred shall be in
-    the lexical form of a token (6.4).
+    the lexical form of a token (6.4).
     Semantics
 

-
-
+
 
3   Preprocessing directives of the forms
          # if   constant-expression new-line groupopt
          # elif constant-expression new-line groupopt
     check whether the controlling constant expression evaluates to nonzero.
 

-
-
+
 
4   Prior to evaluation, macro invocations in the list of preprocessing tokens that will become
     the controlling constant expression are replaced (except for those macro names modified
     by the defined unary operator), just as in normal text. If the token defined is
@@ -8490,21 +7474,25 @@ Forward references:         conditional inclusion (6.10.1), complex arithmetic
     operator have been performed, all remaining identifiers (including those lexically
     identical to keywords) are replaced with the pp-number 0, and then each preprocessing
     token is converted into a token. The resulting tokens compose the controlling constant
-    expression which is evaluated according to the rules of 6.6. For the purposes of this
+    expression which is evaluated according to the rules of 6.6. For the purposes of this
     token conversion and evaluation, all signed integer types and all unsigned integer types
     act as if they have the same representation as, respectively, the types intmax_t and
-    uintmax_t defined in the header <stdint.h>.145) This includes interpreting
+    uintmax_t defined in the header <stdint.h>.[145] This includes interpreting
     character constants, which may involve converting escape sequences into execution
     character set members. Whether the numeric value for these character constants matches
     the value obtained when an identical character constant occurs in an expression (other
-    than within a #if or #elif directive) is implementation-defined.146) Also, whether a
+    than within a #if or #elif directive) is implementation-defined.[146] Also, whether a
     single-character character constant may have a negative value is implementation-defined.
 

-
 
 
Footnote 145) Thus, on an implementation where INT_MAX is 0x7FFF and UINT_MAX is 0xFFFF, the constant
          0x8000 is signed and positive within a #if expression even though it would be unsigned in
          translation phase 7.
+       # ifdef identifier new-line groupopt
+       # ifndef identifier new-line groupopt
+    check whether the identifier is or is not currently defined as a macro name. Their
+    conditions are equivalent to #if defined identifier and #if !defined identifier
+    respectively.
 

 
 
@@ -8514,16 +7502,10 @@ Forward references:         conditional inclusion (6.10.1), complex arithmetic
            if ('z' - 'a' == 25)
 

 
-
+
 
5   Preprocessing directives of the forms
-       # ifdef identifier new-line groupopt
-       # ifndef identifier new-line groupopt
-    check whether the identifier is or is not currently defined as a macro name. Their
-    conditions are equivalent to #if defined identifier and #if !defined identifier
-    respectively.
 

-
-
+
 
6   Each directive's condition is checked in order. If it evaluates to false (zero), the group
     that it controls is skipped: directives are processed only through the name that determines
     the directive in order to keep track of the level of nested conditionals; the rest of the
@@ -8531,39 +7513,14 @@ Forward references:         conditional inclusion (6.10.1), complex arithmetic
     group. Only the first group whose control condition evaluates to true (nonzero) is
     processed. If none of the conditions evaluates to true, and there is a #else directive, the
     group controlled by the #else is processed; lacking a #else directive, all the groups
-    until the #endif are skipped.147)
-    Forward references: macro replacement (6.10.3), source file inclusion (6.10.2), largest
-    integer types (7.18.1.5).
+    until the #endif are skipped.[147]
+    Forward references: macro replacement (6.10.3), source file inclusion (6.10.2), largest
+    integer types (7.18.1.5).
 

-
 
 
Footnote 147) As indicated by the syntax, a preprocessing token shall not follow a #else or #endif directive
          before the terminating new-line character. However, comments may appear anywhere in a source file,
          including within a preprocessing directive.
-

-
-
-

-
6.10.2 [Source file inclusion]

-

-
-
-
1   A #include directive shall identify a header or source file that can be processed by the
-    implementation.
-    Semantics
-

-
-
-
2   A preprocessing directive of the form
-       # include <h-char-sequence> new-line
-    searches a sequence of implementation-defined places for a header identified uniquely by
-    the specified sequence between the < and > delimiters, and causes the replacement of that
-    directive by the entire contents of the header. How the places are specified or the header
-    identified is implementation-defined.
-

-
-
-
3   A preprocessing directive of the form
        # include "q-char-sequence" new-line
     causes the replacement of that directive by the entire contents of the source file identified
     by the specified sequence between the " delimiters. The named source file is searched
@@ -8572,23 +7529,42 @@ Forward references:         conditional inclusion (6.10.1), complex arithmetic
        # include <h-char-sequence> new-line
     with the identical contained sequence (including > characters, if any) from the original
     directive.
-

+

 
-
+
+

+
6.10.2 [Source file inclusion]

+
+
1 Constraints
+   A #include directive shall identify a header or source file that can be processed by the
+    implementation.
+    Semantics
+

+
+
2   A preprocessing directive of the form
+       # include <h-char-sequence> new-line
+    searches a sequence of implementation-defined places for a header identified uniquely by
+    the specified sequence between the < and > delimiters, and causes the replacement of that
+    directive by the entire contents of the header. How the places are specified or the header
+    identified is implementation-defined.
+

+
+
3   A preprocessing directive of the form
+

+
 
4   A preprocessing directive of the form
        # include pp-tokens new-line
     (that does not match one of the two previous forms) is permitted. The preprocessing
     tokens after include in the directive are processed just as in normal text. (Each
     identifier currently defined as a macro name is replaced by its replacement list of
     preprocessing tokens.) The directive resulting after all replacements shall match one of
-    the two previous forms.148) The method by which a sequence of preprocessing tokens
+    the two previous forms.[148] The method by which a sequence of preprocessing tokens
     between a < and a > preprocessing token pair or a pair of " characters is combined into a
     single header name preprocessing token is implementation-defined.
 

-
 
 
Footnote 148) Note that adjacent string literals are not concatenated into a single string literal (see the translation
-         phases in 5.1.1.2); thus, an expansion that results in two string literals is an invalid directive.
+         phases in 5.1.1.2); thus, an expansion that results in two string literals is an invalid directive.
            #if VERSION == 1
                   #define INCFILE        "vers1.h"
            #elif VERSION == 2
@@ -8597,47 +7573,40 @@ Forward references:         conditional inclusion (6.10.1), complex arithmetic
                   #define INCFILE        "versN.h"
            #endif
            #include INCFILE
+    Forward references: macro replacement (6.10.3).
 

 
-
+
 
5   The implementation shall provide unique mappings for sequences consisting of one or
-    more nondigits or digits (6.4.2.1) followed by a period (.) and a single nondigit. The
+    more nondigits or digits (6.4.2.1) followed by a period (.) and a single nondigit. The
     first character shall not be a digit. The implementation may ignore distinctions of
     alphabetical case and restrict the mapping to eight significant characters before the
     period.
 

-
-
+
 
6   A #include preprocessing directive may appear in a source file that has been read
     because of a #include directive in another file, up to an implementation-defined
-    nesting limit (see 5.2.4.1).
+    nesting limit (see 5.2.4.1).
 

-
-
+
 
7   EXAMPLE 1       The most common uses of #include preprocessing directives are as in the following:
              #include <stdio.h>
              #include "myprog.h"
 
 

-
-
+
 
8   EXAMPLE 2       This illustrates macro-replaced #include directives:
-
-    Forward references: macro replacement (6.10.3).
 

-
-
+
 

 
6.10.3 [Macro replacement]

-

-
-
-
1   Two replacement lists are identical if and only if the preprocessing tokens in both have
+
+
1 Constraints
+   Two replacement lists are identical if and only if the preprocessing tokens in both have
     the same number, ordering, spelling, and white-space separation, where all white-space
     separations are considered identical.
 

-
-
+
 
2   An identifier currently defined as an object-like macro shall not be redefined by another
     #define preprocessing directive unless the second definition is an object-like macro
     definition and the two replacement lists are identical. Likewise, an identifier currently
@@ -8646,13 +7615,11 @@ Forward references:         conditional inclusion (6.10.1), complex arithmetic
     that has the same number and spelling of parameters, and the two replacement lists are
     identical.
 

-
-
+
 
3   There shall be white-space between the identifier and the replacement list in the definition
     of an object-like macro.
 

-
-
+
 
4   If the identifier-list in the macro definition does not end with an ellipsis, the number of
     arguments (including those arguments consisting of no preprocessing tokens) in an
     invocation of a function-like macro shall equal the number of parameters in the macro
@@ -8660,46 +7627,40 @@ Forward references:         conditional inclusion (6.10.1), complex arithmetic
     parameters in the macro definition (excluding the ...). There shall exist a )
     preprocessing token that terminates the invocation.
 

-
-
+
 
5   The identifier _ _VA_ARGS_ _ shall occur only in the replacement-list of a function-like
     macro that uses the ellipsis notation in the parameters.
 

-
-
+
 
6   A parameter identifier in a function-like macro shall be uniquely declared within its
     scope.
     Semantics
 

-
-
+
 
7   The identifier immediately following the define is called the macro name. There is one
     name space for macro names. Any white-space characters preceding or following the
     replacement list of preprocessing tokens are not considered part of the replacement list
     for either form of macro.
 

-
-
+
 
8    If a # preprocessing token, followed by an identifier, occurs lexically at the point at which
      a preprocessing directive could begin, the identifier is not subject to macro replacement.
 

-
-
+
 
9    A preprocessing directive of the form
         # define identifier replacement-list new-line
-     defines an object-like macro that causes each subsequent instance of the macro name149)
+     defines an object-like macro that causes each subsequent instance of the macro name[149]
      to be replaced by the replacement list of preprocessing tokens that constitute the
      remainder of the directive. The replacement list is then rescanned for more macro names
      as specified below.
 

-
 
 
Footnote 149) Since, by macro-replacement time, all character constants and string literals are preprocessing tokens,
-          not sequences possibly containing identifier-like subsequences (see 5.1.1.2, translation phases), they
+          not sequences possibly containing identifier-like subsequences (see 5.1.1.2, translation phases), they
           are never scanned for macro names or parameters.
 

 
-
+
 
10   A preprocessing directive of the form
         # define identifier lparen identifier-listopt ) replacement-list new-line
         # define identifier lparen ... ) replacement-list new-line
@@ -8716,34 +7677,29 @@ Forward references:         conditional inclusion (6.10.1), complex arithmetic
      tokens making up an invocation of a function-like macro, new-line is considered a normal
      white-space character.
 

-
-
+
 
11   The sequence of preprocessing tokens bounded by the outside-most matching parentheses
      forms the list of arguments for the function-like macro. The individual arguments within
      the list are separated by comma preprocessing tokens, but comma preprocessing tokens
      between matching inner parentheses do not separate arguments. If there are sequences of
      preprocessing tokens within the list of arguments that would otherwise act as
-     preprocessing directives,150) the behavior is undefined.
+     preprocessing directives,[150] the behavior is undefined.
 

-
 
 
Footnote 150) Despite the name, a non-directive is a preprocessing directive.
+    merger, the number of arguments is one more than the number of parameters in the macro
+    definition (excluding the ...).
 

 
-
+
 
12   If there is a ... in the identifier-list in the macro definition, then the trailing arguments,
      including any separating comma preprocessing tokens, are merged to form a single item:
      the variable arguments. The number of arguments so combined is such that, following
-    merger, the number of arguments is one more than the number of parameters in the macro
-    definition (excluding the ...).
 

-
-
+
 

 
6.10.3.1 [Argument substitution]

-

-
-
+
 
1   After the arguments for the invocation of a function-like macro have been identified,
     argument substitution takes place. A parameter in the replacement list, unless preceded
     by a # or ## preprocessing token or followed by a ## preprocessing token (see below), is
@@ -8752,25 +7708,21 @@ Forward references:         conditional inclusion (6.10.1), complex arithmetic
     completely macro replaced as if they formed the rest of the preprocessing file; no other
     preprocessing tokens are available.
 

-
-
+
 
2   An identifier _ _VA_ARGS_ _ that occurs in the replacement list shall be treated as if it
     were a parameter, and the variable arguments shall form the preprocessing tokens used to
     replace it.
 

-
-
+
 

 
6.10.3.2 [The # operator]

-

-
-
-
1   Each # preprocessing token in the replacement list for a function-like macro shall be
+
+
1 Constraints
+   Each # preprocessing token in the replacement list for a function-like macro shall be
     followed by a parameter as the next preprocessing token in the replacement list.
     Semantics
 

-
-
+
 
2   If, in the replacement list, a parameter is immediately preceded by a # preprocessing
     token, both are replaced by a single character string literal preprocessing token that
     contains the spelling of the preprocessing token sequence for the corresponding
@@ -8788,32 +7740,28 @@ Forward references:         conditional inclusion (6.10.1), complex arithmetic
     ## operators is unspecified.
 
 

-
-
+
 

 
6.10.3.3 [The ## operator]

-

-
-
-
1   A ## preprocessing token shall not occur at the beginning or at the end of a replacement
+
+
1 Constraints
+   A ## preprocessing token shall not occur at the beginning or at the end of a replacement
     list for either form of macro definition.
     Semantics
 

-
-
+
 
2   If, in the replacement list of a function-like macro, a parameter is immediately preceded
     or followed by a ## preprocessing token, the parameter is replaced by the corresponding
     argument's preprocessing token sequence; however, if an argument consists of no
     preprocessing tokens, the parameter is replaced by a placemarker preprocessing token
-    instead.151)
+    instead.[151]
 

-
 
 
Footnote 151) Placemarker preprocessing tokens do not appear in the syntax because they are temporary entities that
          exist only within translation phase 4.
 

 
-
+
 
3   For both object-like and function-like macro invocations, before the replacement list is
     reexamined for more macro names to replace, each instance of a ## preprocessing token
     in the replacement list (not from an argument) is deleted and the preceding preprocessing
@@ -8825,8 +7773,7 @@ Forward references:         conditional inclusion (6.10.1), complex arithmetic
     token is available for further macro replacement. The order of evaluation of ## operators
     is unspecified.
 

-
-
+
 
4   EXAMPLE       In the following fragment:
             #define     hash_hash # ## #
             #define     mkstr(a) # a
@@ -8843,20 +7790,16 @@ Forward references:         conditional inclusion (6.10.1), complex arithmetic
     In other words, expanding hash_hash produces a new token, consisting of two adjacent sharp signs, but
     this new token is not the ## operator.
 

-
-
+
 

 
6.10.3.4 [Rescanning and further replacement]

-

-
-
+
 
1   After all parameters in the replacement list have been substituted and # and ##
     processing has taken place, all placemarker preprocessing tokens are removed. Then, the
     resulting preprocessing token sequence is rescanned, along with all subsequent
     preprocessing tokens of the source file, for more macro names to replace.
 

-
-
+
 
2   If the name of the macro being replaced is found during this scan of the replacement list
     (not including the rest of the source file's preprocessing tokens), it is not replaced.
     Furthermore, if any nested replacements encounter the name of the macro being replaced,
@@ -8864,39 +7807,32 @@ Forward references:         conditional inclusion (6.10.1), complex arithmetic
     available for further replacement even if they are later (re)examined in contexts in which
     that macro name preprocessing token would otherwise have been replaced.
 

-
-
+
 
3   The resulting completely macro-replaced preprocessing token sequence is not processed
     as a preprocessing directive even if it resembles one, but all pragma unary operator
-    expressions within it are then processed as specified in 6.10.9 below.
+    expressions within it are then processed as specified in 6.10.9 below.
 

-
-
+
 

 
6.10.3.5 [Scope of macro definitions]

-

-
-
+
 
1   A macro definition lasts (independent of block structure) until a corresponding #undef
     directive is encountered or (if none is encountered) until the end of the preprocessing
     translation unit. Macro definitions have no significance after translation phase 4.
 

-
-
+
 
2   A preprocessing directive of the form
        # undef identifier new-line
     causes the specified identifier no longer to be defined as a macro name. It is ignored if
     the specified identifier is not currently defined as a macro name.
 

-
-
+
 
3   EXAMPLE 1      The simplest use of this facility is to define a ``manifest constant'', as in
             #define TABSIZE 100
             int table[TABSIZE];
 
 

-
-
+
 
4   EXAMPLE 2 The following defines a function-like macro whose value is the maximum of its arguments.
     It has the advantages of working for any compatible types of the arguments and of generating in-line code
     without the overhead of function calling. It has the disadvantages of evaluating one or the other of its
@@ -8906,8 +7842,7 @@ Forward references:         conditional inclusion (6.10.1), complex arithmetic
     The parentheses ensure that the arguments and the resulting expression are bound properly.
 
 

-
-
+
 
5   EXAMPLE 3     To illustrate the rules for redefinition and reexamination, the sequence
              #define   x         3
              #define   f(a)      f(x * (a))
@@ -8935,8 +7870,7 @@ Forward references:         conditional inclusion (6.10.1), complex arithmetic
              char c[2][6] = { "hello", "" };
 
 

-
-
+
 
6   EXAMPLE 4     To illustrate the rules for creating character string literals and concatenating tokens, the
     sequence
              #define str(s)      # s
@@ -8974,8 +7908,7 @@ Forward references:         conditional inclusion (6.10.1), complex arithmetic
     Space around the # and ## tokens in the macro definition is optional.
 
 

-
-
+
 
7   EXAMPLE 5        To illustrate the rules for placemarker preprocessing tokens, the sequence
              #define t(x,y,z) x ## y ## z
              int j[] = { t(1,2,3), t(,4,5), t(6,,7), t(8,9,),
@@ -8985,8 +7918,7 @@ Forward references:         conditional inclusion (6.10.1), complex arithmetic
                          10, 11, 12, };
 
 

-
-
+
 
8   EXAMPLE 6        To demonstrate the redefinition rules, the following sequence is valid.
              #define      OBJ_LIKE      (1-1)
              #define      OBJ_LIKE      /* white space */ (1-1) /* other */
@@ -9001,8 +7933,7 @@ Forward references:         conditional inclusion (6.10.1), complex arithmetic
              #define      FUNC_LIKE(b) ( b ) // different parameter spelling
 
 

-
-
+
 
9   EXAMPLE 7        Finally, to show the variable argument list macro facilities:
              #define debug(...)       fprintf(stderr, _ _VA_ARGS_ _)
              #define showlist(...)    puts(#_ _VA_ARGS_ _)
@@ -9020,39 +7951,33 @@ Forward references:         conditional inclusion (6.10.1), complex arithmetic
                          printf("x is %d but y is %d", x, y));
 
 

-
-
+
 

 
6.10.4 [Line control]

-

-
-
-
1   The string literal of a #line directive, if present, shall be a character string literal.
+
+
1 Constraints
+   The string literal of a #line directive, if present, shall be a character string literal.
     Semantics
 

-
-
+
 
2   The line number of the current source line is one greater than the number of new-line
-    characters read or introduced in translation phase 1 (5.1.1.2) while processing the source
+    characters read or introduced in translation phase 1 (5.1.1.2) while processing the source
     file to the current token.
 

-
-
+
 
3   A preprocessing directive of the form
        # line digit-sequence new-line
     causes the implementation to behave as if the following sequence of source lines begins
     with a source line that has a line number as specified by the digit sequence (interpreted as
     a decimal integer). The digit sequence shall not specify zero, nor a number greater than 2147483647.
 

-
-
+
 
4   A preprocessing directive of the form
        # line digit-sequence "s-char-sequenceopt" new-line
     sets the presumed line number similarly and changes the presumed name of the source
     file to be the contents of the character string literal.
 

-
-
+
 
5   A preprocessing directive of the form
        # line pp-tokens new-line
     (that does not match one of the two previous forms) is permitted. The preprocessing
@@ -9062,34 +7987,29 @@ Forward references:         conditional inclusion (6.10.1), complex arithmetic
     previous forms and is then processed as appropriate.
 
 

-
-
+
 

 
6.10.5 [Error directive]

-

-
-
-
1   A preprocessing directive of the form
+
+
1 Semantics
+   A preprocessing directive of the form
        # error pp-tokensopt new-line
     causes the implementation to produce a diagnostic message that includes the specified
     sequence of preprocessing tokens.
 

-
-
+
 

 
6.10.6 [Pragma directive]

-

-
-
-
1   A preprocessing directive of the form
+
+
1 Semantics
+   A preprocessing directive of the form
        # pragma pp-tokensopt new-line
     where the preprocessing token STDC does not immediately follow pragma in the
-    directive (prior to any macro replacement)152) causes the implementation to behave in an
+    directive (prior to any macro replacement)[152] causes the implementation to behave in an
     implementation-defined manner. The behavior might cause translation to fail or cause the
     translator or the resulting program to behave in a non-conforming manner. Any such
     pragma that is not recognized by the implementation is ignored.
 

-
 
 
Footnote 152) An implementation is not required to perform macro replacement in pragmas, but it is permitted
          except for in standard pragmas (where STDC immediately follows pragma). If the result of macro
@@ -9098,51 +8018,46 @@ Forward references:         conditional inclusion (6.10.1), complex arithmetic
          but is not required to.
 

 
-
+
 
2   If the preprocessing token STDC does immediately follow pragma in the directive (prior
     to any macro replacement), then no macro replacement is performed on the directive, and
-    the directive shall have one of the following forms153) whose meanings are described
+    the directive shall have one of the following forms[153] whose meanings are described
     elsewhere:
        #pragma STDC FP_CONTRACT on-off-switch
        #pragma STDC FENV_ACCESS on-off-switch
        #pragma STDC CX_LIMITED_RANGE on-off-switch
        on-off-switch: one of
                    ON     OFF           DEFAULT
-    Forward references: the FP_CONTRACT pragma (7.12.2), the FENV_ACCESS pragma
-    (7.6.1), the CX_LIMITED_RANGE pragma (7.3.4).
+    Forward references: the FP_CONTRACT pragma (7.12.2), the FENV_ACCESS pragma
+    (7.6.1), the CX_LIMITED_RANGE pragma (7.3.4).
 

-
 
-
Footnote 153) See ``future language directions'' (6.11.8).
+
Footnote 153) See ``future language directions'' (6.11.8).
 

 
-
+
 

 
6.10.7 [Null directive]

-

-
-
-
1   A preprocessing directive of the form
+
+
1 Semantics
+   A preprocessing directive of the form
        # new-line
     has no effect.
 

-
-
+
 

 
6.10.8 [Predefined macro names]

-

-
-
-
1   The following macro names154) shall be defined by the implementation:
+
+
1   The following macro names[154] shall be defined by the implementation:
     _ _DATE_ _ The date of translation of the preprocessing translation unit: a character
                string literal of the form "Mmm dd yyyy", where the names of the
                months are the same as those generated by the asctime function, and the
                first character of dd is a space character if the value is less than 10. If the
                date of translation is not available, an implementation-defined valid date
                shall be supplied.
-    _ _FILE_ _ The presumed name of the current source file (a character string literal).155)
+    _ _FILE_ _ The presumed name of the current source file (a character string literal).[155]
     _ _LINE_ _ The presumed line number (within the current source file) of the current
-               source line (an integer constant).155)
+               source line (an integer constant).[155]
     _ _STDC_ _ The integer constant 1, intended to indicate a conforming implementation.
     _ _STDC_HOSTED_ _ The integer constant 1 if the implementation is a hosted
               implementation or the integer constant 0 if it is not.
@@ -9150,15 +8065,14 @@ Forward references:         conditional inclusion (6.10.1), complex arithmetic
               the encoding for wchar_t, a member of the basic character set need not
               have a code value equal to its value when used as the lone character in an
               integer character constant.
-    _ _STDC_VERSION_ _ The integer constant 199901L.156)
+    _ _STDC_VERSION_ _ The integer constant 199901L.[156]
     _ _TIME_ _ The time of translation of the preprocessing translation unit: a character
                string literal of the form "hh:mm:ss" as in the time generated by the
                asctime function. If the time of translation is not available, an
                implementation-defined valid time shall be supplied.
 

-
 
-
Footnote 154) See ``future language directions'' (6.11.9).
+
Footnote 154) See ``future language directions'' (6.11.9).
 

 
 
@@ -9175,7 +8089,7 @@ Forward references:         conditional inclusion (6.10.1), complex arithmetic
          int that is increased with each revision of this International Standard.
 

 
-
+
 
2   The following macro names are conditionally defined by the implementation:
     _ _STDC_IEC_559_ _ The integer constant 1, intended to indicate conformance to the
               specifications in annex F (IEC 60559 floating-point arithmetic).
@@ -9190,32 +8104,27 @@ Forward references:         conditional inclusion (6.10.1), complex arithmetic
               all amendments and technical corrigenda, as of the specified year and
               month.
 

-
-
+
 
3   The values of the predefined macros (except for _ _FILE_ _ and _ _LINE_ _) remain
     constant throughout the translation unit.
 

-
-
+
 
4   None of these macro names, nor the identifier defined, shall be the subject of a
     #define or a #undef preprocessing directive. Any other predefined macro names
     shall begin with a leading underscore followed by an uppercase letter or a second
     underscore.
 

-
-
+
 
5   The implementation shall not predefine the macro _ _cplusplus, nor shall it define it
     in any standard header.
-    Forward references: the asctime function (7.23.3.1), standard headers (7.1.2).
+    Forward references: the asctime function (7.23.3.1), standard headers (7.1.2).
 

-
-
+
 

 
6.10.9 [Pragma operator]

-

-
-
-
1   A unary operator expression of the form:
+
+
1 Semantics
+   A unary operator expression of the form:
        _Pragma ( string-literal )
     is processed as follows: The string literal is destringized by deleting the L prefix, if
     present, deleting the leading and trailing double-quotes, replacing each escape sequence
@@ -9225,8 +8134,7 @@ Forward references:         conditional inclusion (6.10.1), complex arithmetic
     directive. The original four preprocessing tokens in the unary operator expression are
     removed.
 

-
-
+
 
2   EXAMPLE       A directive of the form:
              #pragma listing on "..\listing.dir"
     can also be expressed as:
@@ -9238,121 +8146,81 @@ replacement, as in:
         LISTING ( ..\listing.dir )
 
 

-
-
+
 

 
6.11 [Future language directions]

-
 Future language directions
-

-
-
+
 

 
6.11.1 [Floating types]

-

-
-
+
 
1   Future standardization may include additional floating-point types, including those with
     greater range, precision, or both than long double.
 

-
-
+
 

 
6.11.2 [Linkages of identifiers]

-

-
-
+
 
1   Declaring an identifier with internal linkage at file scope without the static storage-
     class specifier is an obsolescent feature.
 

-
-
+
 

 
6.11.3 [External names]

-

-
-
+
 
1   Restriction of the significance of an external name to fewer than 255 characters
     (considering each universal character name or extended source character as a single
     character) is an obsolescent feature that is a concession to existing implementations.
 

-
-
+
 

 
6.11.4 [Character escape sequences]

-

-
-
+
 
1   Lowercase letters as escape sequences are reserved for future standardization. Other
     characters may be used in extensions.
 

-
-
+
 

 
6.11.5 [Storage-class specifiers]

-

-
-
+
 
1   The placement of a storage-class specifier other than at the beginning of the declaration
     specifiers in a declaration is an obsolescent feature.
 

-
-
+
 

 
6.11.6 [Function declarators]

-

-
-
+
 
1   The use of function declarators with empty parentheses (not prototype-format parameter
     type declarators) is an obsolescent feature.
 

-
-
+
 

 
6.11.7 [Function definitions]

-

-
-
+
 
1   The use of function definitions with separate parameter identifier and declaration lists
     (not prototype-format parameter type and identifier declarators) is an obsolescent feature.
 

-
-
+
 

 
6.11.8 [Pragma directives]

-

-
-
+
 
1   Pragmas whose first preprocessing token is STDC are reserved for future standardization.
 

-
-
+
 

 
6.11.9 [Predefined macro names]

-

-
-
+
 
1   Macro names beginning with _ _STDC_ are reserved for future standardization.
 

-
-
+
 

 
7. [Library]

-
 Library
-
-

-
-
+
 

 
7.1 [Introduction]

-
 Introduction
-

-
-
+
 

 
7.1.1 [Definitions of terms]

-

-
-
+
 
1   A string is a contiguous sequence of characters terminated by and including the first null
     character. The term multibyte string is sometimes used instead to emphasize special
     processing given to multibyte characters contained in the string or to avoid confusion
@@ -9360,39 +8228,34 @@ replacement, as in:
     character. The length of a string is the number of bytes preceding the null character and
     the value of a string is the sequence of the values of the contained characters, in order.
 

-
-
+
 
2   The decimal-point character is the character used by functions that convert floating-point
     numbers to or from character sequences to denote the beginning of the fractional part of
-    such character sequences.157) It is represented in the text and examples by a period, but
+    such character sequences.[157] It is represented in the text and examples by a period, but
     may be changed by the setlocale function.
 

-
 
 
Footnote 157) The functions that make use of the decimal-point character are the numeric conversion functions
-         (7.20.1, 7.24.4.1) and the formatted input/output functions (7.19.6, 7.24.2).
+         (7.20.1, 7.24.4.1) and the formatted input/output functions (7.19.6, 7.24.2).
 

 
-
+
 
3   A null wide character is a wide character with code value zero.
 

-
-
+
 
4   A wide string is a contiguous sequence of wide characters terminated by and including
     the first null wide character. A pointer to a wide string is a pointer to its initial (lowest
     addressed) wide character. The length of a wide string is the number of wide characters
     preceding the null wide character and the value of a wide string is the sequence of code
     values of the contained wide characters, in order.
 

-
-
+
 
5   A shift sequence is a contiguous sequence of bytes within a multibyte string that
-    (potentially) causes a change in shift state (see 5.2.1.2). A shift sequence shall not have a
+    (potentially) causes a change in shift state (see 5.2.1.2). A shift sequence shall not have a
     corresponding wide character; it is instead taken to be an adjunct to an adjacent multibyte
-    character.158)
-    Forward references: character handling (7.4), the setlocale function (7.11.1.1).
+    character.[158]
+    Forward references: character handling (7.4), the setlocale function (7.11.1.1).
 

-
 
 
Footnote 158) For state-dependent encodings, the values for MB_CUR_MAX and MB_LEN_MAX shall thus be large
          enough to count all the bytes in any complete multibyte character plus at least one adjacent shift
@@ -9400,25 +8263,22 @@ replacement, as in:
          implementation's choice.
 

 
-
+
 

 
7.1.2 [Standard headers]

-

-
-
-
1   Each library function is declared, with a type that includes a prototype, in a header ,159)
+
+
1   Each library function is declared, with a type that includes a prototype, in a header ,[159]
     whose contents are made available by the #include preprocessing directive. The
     header declares a set of related functions, plus any necessary types and additional macros
     needed to facilitate their use. Declarations of types described in this clause shall not
     include type qualifiers, unless explicitly stated otherwise.
 

-
 
 
Footnote 159) A header is not necessarily a source file, nor are the < and > delimited sequences in header names
          necessarily valid source file names.
 

 
-
+
 
2   The standard headers are
            <assert.h>              <inttypes.h>            <signal.h>              <stdlib.h>
            <complex.h>             <iso646.h>              <stdarg.h>              <string.h>
@@ -9427,17 +8287,15 @@ replacement, as in:
            <fenv.h>                <math.h>                <stdint.h>              <wchar.h>
            <float.h>               <setjmp.h>              <stdio.h>               <wctype.h>
 

-
-
+
 
3   If a file with the same name as one of the above < and > delimited sequences, not
     provided as part of the implementation, is placed in any of the standard places that are
     searched for included source files, the behavior is undefined.
 

-
-
+
 
4   Standard headers may be included in any order; each may be included more than once in
     a given scope, with no effect different from being included only once, except that the
-    effect of including <assert.h> depends on the definition of NDEBUG (see 7.2). If
+    effect of including <assert.h> depends on the definition of NDEBUG (see 7.2). If
     used, a header shall be included outside of any external declaration or definition, and it
     shall first be included before the first reference to any of the functions or objects it
     declares, or to any of the types or macros it defines. However, if an identifier is declared
@@ -9446,28 +8304,22 @@ replacement, as in:
     macros with names lexically identical to keywords currently defined prior to the
     inclusion.
 

-
-
+
 
5   Any definition of an object-like macro described in this clause shall expand to code that is
     fully protected by parentheses where necessary, so that it groups in an arbitrary
     expression as if it were a single identifier.
 

-
-
+
 
6   Any declaration of a library function shall have external linkage.
 

-
-
+
 
7   A summary of the contents of the standard headers is given in annex B.
-    Forward references: diagnostics (7.2).
+    Forward references: diagnostics (7.2).
 

-
-
+
 

 
7.1.3 [Reserved identifiers]

-

-
-
+
 
1   Each header declares or defines all identifiers listed in its associated subclause, and
     optionally declares or defines identifiers listed in its associated future library directions
     subclause and identifiers which are always reserved either for any use or for use as file
@@ -9478,47 +8330,17 @@ replacement, as in:
        with file scope in both the ordinary and tag name spaces.
     -- Each macro name in any of the following subclauses (including the future library
        directions) is reserved for use as specified if any of its associated headers is included;
-       unless explicitly stated otherwise (see 7.1.4).
+       unless explicitly stated otherwise (see 7.1.4).
     -- All identifiers with external linkage in any of the following subclauses (including the
        future library directions) are always reserved for use as identifiers with external
-       linkage.160)
+       linkage.[160]
     -- Each identifier with file scope listed in any of the following subclauses (including the
        future library directions) is reserved for use as a macro name and as an identifier with
        file scope in the same name space if any of its associated headers is included.
 

-
 
 
Footnote 160) The list of reserved identifiers with external linkage includes errno, math_errhandling,
          setjmp, and va_end.
-

-
-
-
2   No other identifiers are reserved. If the program declares or defines an identifier in a
-    context in which it is reserved (other than as allowed by 7.1.4), or defines a reserved
-    identifier as a macro name, the behavior is undefined.
-

-
-
-
3   If the program removes (with #undef) any macro definition of an identifier in the first
-    group listed above, the behavior is undefined.
-

-
-
-

-
7.1.4 [Use of library functions]

-

-
-
-
1   Each of the following statements applies unless explicitly stated otherwise in the detailed
-    descriptions that follow: If an argument to a function has an invalid value (such as a value
-    outside the domain of the function, or a pointer outside the address space of the program,
-    or a null pointer, or a pointer to non-modifiable storage when the corresponding
-    parameter is not const-qualified) or a type (after promotion) not expected by a function
-    with variable number of arguments, the behavior is undefined. If a function argument is
-    described as being an array, the pointer actually passed to the function shall have a value
-    such that all address computations and accesses to objects (that would be valid if the
-    pointer did point to the first element of such an array) are in fact valid. Any function
-    declared in a header may be additionally implemented as a function-like macro defined in
     the header, so if a library function is declared explicitly when its header is included, one
     of the techniques shown below can be used to ensure the declaration is not affected by
     such a macro. Any macro definition of a function can be suppressed locally by enclosing
@@ -9534,52 +8356,49 @@ replacement, as in:
     compatible return type could be called.163) All object-like macros listed as expanding to
     integer constant expressions shall additionally be suitable for use in #if preprocessing
     directives.
+

+
+
+
2   No other identifiers are reserved. If the program declares or defines an identifier in a
+    context in which it is reserved (other than as allowed by 7.1.4), or defines a reserved
+    identifier as a macro name, the behavior is undefined.
 

-
-
-
Footnote 161) This means that an implementation shall provide an actual function for each library function, even if it
-         also provides a macro for that function.
-

-
-
-
Footnote 162) Such macros might not contain the sequence points that the corresponding function calls do.
-

-
-
-
Footnote 163) Because external identifiers and some macro names beginning with an underscore are reserved,
-         implementations may provide special semantics for such names. For example, the identifier
-         _BUILTIN_abs could be used to indicate generation of in-line code for the abs function. Thus, the
-         appropriate header could specify
-                  #define abs(x) _BUILTIN_abs(x)
-         for a compiler whose code generator will accept it.
-         In this manner, a user desiring to guarantee that a given library function such as abs will be a genuine
-         function may write
-                  #undef abs
-         whether the implementation's header provides a macro implementation of abs or a built-in
-         implementation. The prototype for the function, which precedes and is hidden by any macro
-         definition, is thereby revealed also.
-

-
-
+
+
3   If the program removes (with #undef) any macro definition of an identifier in the first
+    group listed above, the behavior is undefined.
+

+
+

+
7.1.4 [Use of library functions]

+
+
1   Each of the following statements applies unless explicitly stated otherwise in the detailed
+    descriptions that follow: If an argument to a function has an invalid value (such as a value
+    outside the domain of the function, or a pointer outside the address space of the program,
+    or a null pointer, or a pointer to non-modifiable storage when the corresponding
+    parameter is not const-qualified) or a type (after promotion) not expected by a function
+    with variable number of arguments, the behavior is undefined. If a function argument is
+    described as being an array, the pointer actually passed to the function shall have a value
+    such that all address computations and accesses to objects (that would be valid if the
+    pointer did point to the first element of such an array) are in fact valid. Any function
+    declared in a header may be additionally implemented as a function-like macro defined in
+

+
 
2   Provided that a library function can be declared without reference to any type defined in a
     header, it is also permissible to declare the function and use it without including its
     associated header.
 

-
-
+
 
3   There is a sequence point immediately before a library function returns.
 

-
-
+
 
4   The functions in the standard library are not guaranteed to be reentrant and may modify
-    objects with static storage duration.164)
+    objects with static storage duration.[164]
 

-
 
 
Footnote 164) Thus, a signal handler cannot, in general, call standard library functions.
 

 
-
+
 
5   EXAMPLE        The function atoi may be used in any of several ways:
     -- by use of its associated header (possibly generating a macro expansion)
                 #include <stdlib.h>
@@ -9604,13 +8423,10 @@ replacement, as in:
                 i = atoi(str);
 
 

-
-
+
 

-
7.2 [Diagnostics ]

-

-
-
+
7.2 [Diagnostics <assert.h>]

+
 
1   The header <assert.h> defines the assert macro and refers to another macro,
             NDEBUG
     which is not defined by <assert.h>. If NDEBUG is defined as a macro name at the
@@ -9620,132 +8436,108 @@ replacement, as in:
     The assert macro is redefined according to the current state of NDEBUG each time that
     <assert.h> is included.
 

-
-
+
 
2   The assert macro shall be implemented as a macro, not as an actual function. If the
     macro definition is suppressed in order to access an actual function, the behavior is
     undefined.
 

-
-
+
 

 
7.2.1 [Program diagnostics]

-
 Program diagnostics
-

-
-
+
 

 
7.2.1.1 [The assert macro]

-

-
-
-
1           #include <assert.h>
+
+
1 Synopsis
+           #include <assert.h>
             void assert(scalar expression);
     Description
 

-
-
+
 
2   The assert macro puts diagnostic tests into programs; it expands to a void expression.
     When it is executed, if expression (which shall have a scalar type) is false (that is,
     compares equal to 0), the assert macro writes information about the particular call that
     failed (including the text of the argument, the name of the source file, the source line
     number, and the name of the enclosing function -- the latter are respectively the values of
     the preprocessing macros _ _FILE_ _ and _ _LINE_ _ and of the identifier
-    _ _func_ _) on the standard error stream in an implementation-defined format.165) It
+    _ _func_ _) on the standard error stream in an implementation-defined format.[165] It
     then calls the abort function.
     Returns
 

-
 
 
Footnote 165) The message written might be of the form:
          Assertion failed: expression, function abc, file xyz, line nnn.
 

 
-
+
 
3   The assert macro returns no value.
-    Forward references: the abort function (7.20.4.1).
+    Forward references: the abort function (7.20.4.1).
 

-
-
+
 

-
7.3 [Complex arithmetic ]

-
 Complex arithmetic 
-

-
-
+
7.3 [Complex arithmetic <complex.h>]

+
 

 
7.3.1 [Introduction]

-

-
-
+
 
1   The header <complex.h> defines macros and declares functions that support complex
-    arithmetic.166) Each synopsis specifies a family of functions consisting of a principal
+    arithmetic.[166] Each synopsis specifies a family of functions consisting of a principal
     function with one or more double complex parameters and a double complex or
     double return value; and other functions with the same name but with f and l suffixes
     which are corresponding functions with float and long double parameters and
     return values.
 

-
 
-
Footnote 166) See ``future library directions'' (7.26.1).
+
Footnote 166) See ``future library directions'' (7.26.1).
 

 
-
+
 
2   The macro
              complex
     expands to _Complex; the macro
              _Complex_I
     expands to a constant expression of type const float _Complex, with the value of
-    the imaginary unit.167)
+    the imaginary unit.[167]
 

-
 
 
Footnote 167) The imaginary unit is a number i such that i 2   = -1.
 

 
-
+
 
3   The macros
              imaginary
     and
              _Imaginary_I
-    are defined if and only if the implementation supports imaginary types;168) if defined,
+    are defined if and only if the implementation supports imaginary types;[168] if defined,
     they expand to _Imaginary and a constant expression of type const float
     _Imaginary with the value of the imaginary unit.
 

-
 
 
Footnote 168) A specification for imaginary types is in informative annex G.
 

 
-
+
 
4   The macro
              I
     expands to either _Imaginary_I or _Complex_I. If _Imaginary_I is not
     defined, I shall expand to _Complex_I.
 

-
-
-
5   Notwithstanding the provisions of 7.1.3, a program may undefine and perhaps then
+
+
5   Notwithstanding the provisions of 7.1.3, a program may undefine and perhaps then
     redefine the macros complex, imaginary, and I.
     Forward references: IEC 60559-compatible complex arithmetic (annex G).
 

-
-
+
 

 
7.3.2 [Conventions]

-

-
-
+
 
1   Values are interpreted as radians, not degrees. An implementation may set errno but is
     not required to.
 

-
-
+
 

 
7.3.3 [Branch cuts]

-

-
-
+
 
1   Some of the functions below have branch cuts, across which the function is
     discontinuous. For implementations with a signed zero (including all IEC 60559
     implementations) that follow the specifications of annex G, the sign of zero distinguishes
@@ -9755,8 +8547,7 @@ replacement, as in:
     imaginary part +0, maps to the positive imaginary axis, and the bottom of the cut, with
     imaginary part -0, maps to the negative imaginary axis.
 

-
-
+
 
2   Implementations that do not support a signed zero (see annex F) cannot distinguish the
     sides of branch cuts. These implementations shall map a cut so the function is continuous
     as the cut is approached coming around the finite endpoint of the cut in a counter
@@ -9765,25 +8556,29 @@ replacement, as in:
     the finite endpoint of the cut along the negative real axis approaches the cut from above,
     so the cut maps to the positive imaginary axis.
 

-
-
+
 

 
7.3.4 [The CX_LIMITED_RANGE pragma]

-

-
-
-
1            #include <complex.h>
+
+
1 Synopsis
+            #include <complex.h>
              #pragma STDC CX_LIMITED_RANGE on-off-switch
     Description
 

-
-
+
 
2   The usual mathematical formulas for complex multiply, divide, and absolute value are
     problematic because of their treatment of infinities and because of undue overflow and
     underflow. The CX_LIMITED_RANGE pragma can be used to inform the
     implementation that (where the state is ``on'') the usual mathematical formulas are
-    acceptable.169) The pragma can occur either outside external declarations or preceding all
+    acceptable.[169] The pragma can occur either outside external declarations or preceding all
     explicit declarations and statements inside a compound statement. When outside external
+

+
+
Footnote 169) The purpose of the pragma is to allow the implementation to use the formulas:
+             ( x + iy ) \xD7 (u + iv ) = ( xu - yv ) + i ( yu + xv )
+             ( x + iy ) / (u + iv ) = [( xu + yv ) + i ( yu - xv )]/(u2 + v 2 )
+             | x + iy | =  x 2 + y2
+         where the programmer can determine they are safe.
     declarations, the pragma takes effect from its occurrence until another
     CX_LIMITED_RANGE pragma is encountered, or until the end of the translation unit.
     When inside a compound statement, the pragma takes effect from its occurrence until
@@ -9792,534 +8587,429 @@ replacement, as in:
     compound statement the state for the pragma is restored to its condition just before the
     compound statement. If this pragma is used in any other context, the behavior is
     undefined. The default state for the pragma is ``off''.
-

-
-
-
Footnote 169) The purpose of the pragma is to allow the implementation to use the formulas:
-             ( x + iy ) × (u + iv ) = ( xu - yv ) + i ( yu + xv )
-             ( x + iy ) / (u + iv ) = [( xu + yv ) + i ( yu - xv )]/(u2 + v 2 )
-             | x + iy | =  x 2 + y2
-         where the programmer can determine they are safe.
 

 
-
+
 

 
7.3.5 [Trigonometric functions]

-
 Trigonometric functions
-

-
-
+
 

 
7.3.5.1 [The cacos functions]

-

-
-
-
1          #include <complex.h>
+
+
1 Synopsis
+          #include <complex.h>
            double complex cacos(double complex z);
            float complex cacosf(float complex z);
            long double complex cacosl(long double complex z);
     Description
 

-
-
+
 
2   The cacos functions compute the complex arc cosine of z, with branch cuts outside the
     interval [-1, +1] along the real axis.
     Returns
 

-
-
+
 
3   The cacos functions return the complex arc cosine value, in the range of a strip
     mathematically unbounded along the imaginary axis and in the interval [0,  ] along the
     real axis.
 

-
-
+
 

 
7.3.5.2 [The casin functions]

-

-
-
-
1          #include <complex.h>
+
+
1 Synopsis
+          #include <complex.h>
            double complex casin(double complex z);
            float complex casinf(float complex z);
            long double complex casinl(long double complex z);
     Description
 

-
-
+
 
2   The casin functions compute the complex arc sine of z, with branch cuts outside the
     interval [-1, +1] along the real axis.
     Returns
 

-
-
+
 
3   The casin functions return the complex arc sine value, in the range of a strip
     mathematically unbounded along the imaginary axis and in the interval [- /2, + /2]
     along the real axis.
 

-
-
+
 

 
7.3.5.3 [The catan functions]

-

-
-
-
1          #include <complex.h>
+
+
1 Synopsis
+          #include <complex.h>
            double complex catan(double complex z);
            float complex catanf(float complex z);
            long double complex catanl(long double complex z);
     Description
 

-
-
+
 
2   The catan functions compute the complex arc tangent of z, with branch cuts outside the
     interval [-i , +i ] along the imaginary axis.
     Returns
 

-
-
+
 
3   The catan functions return the complex arc tangent value, in the range of a strip
     mathematically unbounded along the imaginary axis and in the interval [- /2, + /2]
     along the real axis.
 

-
-
+
 

 
7.3.5.4 [The ccos functions]

-

-
-
-
1          #include <complex.h>
+
+
1 Synopsis
+          #include <complex.h>
            double complex ccos(double complex z);
            float complex ccosf(float complex z);
            long double complex ccosl(long double complex z);
     Description
 

-
-
+
 
2   The ccos functions compute the complex cosine of z.
     Returns
 

-
-
+
 
3   The ccos functions return the complex cosine value.
 

-
-
+
 

 
7.3.5.5 [The csin functions]

-

-
-
-
1          #include <complex.h>
+
+
1 Synopsis
+          #include <complex.h>
            double complex csin(double complex z);
            float complex csinf(float complex z);
            long double complex csinl(long double complex z);
     Description
 

-
-
+
 
2   The csin functions compute the complex sine of z.
     Returns
 

-
-
+
 
3   The csin functions return the complex sine value.
 

-
-
+
 

 
7.3.5.6 [The ctan functions]

-

-
-
-
1          #include <complex.h>
+
+
1 Synopsis
+          #include <complex.h>
            double complex ctan(double complex z);
            float complex ctanf(float complex z);
            long double complex ctanl(long double complex z);
     Description
 

-
-
+
 
2   The ctan functions compute the complex tangent of z.
     Returns
 

-
-
+
 
3   The ctan functions return the complex tangent value.
 

-
-
+
 

 
7.3.6 [Hyperbolic functions]

-
 Hyperbolic functions
-

-
-
+
 

 
7.3.6.1 [The cacosh functions]

-

-
-
-
1          #include <complex.h>
+
+
1 Synopsis
+          #include <complex.h>
            double complex cacosh(double complex z);
            float complex cacoshf(float complex z);
            long double complex cacoshl(long double complex z);
     Description
 

-
-
+
 
2   The cacosh functions compute the complex arc hyperbolic cosine of z, with a branch
     cut at values less than 1 along the real axis.
     Returns
 

-
-
+
 
3   The cacosh functions return the complex arc hyperbolic cosine value, in the range of a
     half-strip of non-negative values along the real axis and in the interval [-i , +i ] along
     the imaginary axis.
 

-
-
+
 

 
7.3.6.2 [The casinh functions]

-

-
-
-
1          #include <complex.h>
+
+
1 Synopsis
+          #include <complex.h>
            double complex casinh(double complex z);
            float complex casinhf(float complex z);
            long double complex casinhl(long double complex z);
     Description
 

-
-
+
 
2   The casinh functions compute the complex arc hyperbolic sine of z, with branch cuts
     outside the interval [-i , +i ] along the imaginary axis.
     Returns
 

-
-
+
 
3   The casinh functions return the complex arc hyperbolic sine value, in the range of a
     strip mathematically unbounded along the real axis and in the interval [-i /2, +i /2]
     along the imaginary axis.
 

-
-
+
 

 
7.3.6.3 [The catanh functions]

-

-
-
-
1          #include <complex.h>
+
+
1 Synopsis
+          #include <complex.h>
            double complex catanh(double complex z);
            float complex catanhf(float complex z);
            long double complex catanhl(long double complex z);
     Description
 

-
-
+
 
2   The catanh functions compute the complex arc hyperbolic tangent of z, with branch
     cuts outside the interval [-1, +1] along the real axis.
     Returns
 

-
-
+
 
3   The catanh functions return the complex arc hyperbolic tangent value, in the range of a
     strip mathematically unbounded along the real axis and in the interval [-i /2, +i /2]
     along the imaginary axis.
 

-
-
+
 

 
7.3.6.4 [The ccosh functions]

-

-
-
-
1          #include <complex.h>
+
+
1 Synopsis
+          #include <complex.h>
            double complex ccosh(double complex z);
            float complex ccoshf(float complex z);
            long double complex ccoshl(long double complex z);
     Description
 

-
-
+
 
2   The ccosh functions compute the complex hyperbolic cosine of z.
     Returns
 

-
-
+
 
3   The ccosh functions return the complex hyperbolic cosine value.
 

-
-
+
 

 
7.3.6.5 [The csinh functions]

-

-
-
-
1          #include <complex.h>
+
+
1 Synopsis
+          #include <complex.h>
            double complex csinh(double complex z);
            float complex csinhf(float complex z);
            long double complex csinhl(long double complex z);
     Description
 

-
-
+
 
2   The csinh functions compute the complex hyperbolic sine of z.
     Returns
 

-
-
+
 
3   The csinh functions return the complex hyperbolic sine value.
 

-
-
+
 

 
7.3.6.6 [The ctanh functions]

-

-
-
-
1          #include <complex.h>
+
+
1 Synopsis
+          #include <complex.h>
            double complex ctanh(double complex z);
            float complex ctanhf(float complex z);
            long double complex ctanhl(long double complex z);
     Description
 

-
-
+
 
2   The ctanh functions compute the complex hyperbolic tangent of z.
     Returns
 

-
-
+
 
3   The ctanh functions return the complex hyperbolic tangent value.
 

-
-
+
 

 
7.3.7 [Exponential and logarithmic functions]

-
 Exponential and logarithmic functions
-

-
-
+
 

 
7.3.7.1 [The cexp functions]

-

-
-
-
1          #include <complex.h>
+
+
1 Synopsis
+          #include <complex.h>
            double complex cexp(double complex z);
            float complex cexpf(float complex z);
            long double complex cexpl(long double complex z);
     Description
 

-
-
+
 
2   The cexp functions compute the complex base-e exponential of z.
     Returns
 

-
-
+
 
3   The cexp functions return the complex base-e exponential value.
 

-
-
+
 

 
7.3.7.2 [The clog functions]

-

-
-
-
1          #include <complex.h>
+
+
1 Synopsis
+          #include <complex.h>
            double complex clog(double complex z);
            float complex clogf(float complex z);
            long double complex clogl(long double complex z);
     Description
 

-
-
+
 
2   The clog functions compute the complex natural (base-e) logarithm of z, with a branch
     cut along the negative real axis.
     Returns
 

-
-
+
 
3   The clog functions return the complex natural logarithm value, in the range of a strip
     mathematically unbounded along the real axis and in the interval [-i , +i ] along the
     imaginary axis.
 

-
-
+
 

 
7.3.8 [Power and absolute-value functions]

-
 Power and absolute-value functions
-

-
-
+
 

 
7.3.8.1 [The cabs functions]

-

-
-
-
1          #include <complex.h>
+
+
1 Synopsis
+          #include <complex.h>
            double cabs(double complex z);
            float cabsf(float complex z);
            long double cabsl(long double complex z);
     Description
 

-
-
+
 
2   The cabs functions compute the complex absolute value (also called norm, modulus, or
     magnitude) of z.
     Returns
 

-
-
+
 
3   The cabs functions return the complex absolute value.
 

-
-
+
 

 
7.3.8.2 [The cpow functions]

-

-
-
-
1          #include <complex.h>
+
+
1 Synopsis
+          #include <complex.h>
            double complex cpow(double complex x, double complex y);
            float complex cpowf(float complex x, float complex y);
            long double complex cpowl(long double complex x,
                 long double complex y);
     Description
 

-
-
+
 
2   The cpow functions compute the complex power function xy , with a branch cut for the
     first parameter along the negative real axis.
     Returns
 

-
-
+
 
3   The cpow functions return the complex power function value.
 
 

-
-
+
 

 
7.3.8.3 [The csqrt functions]

-

-
-
-
1          #include <complex.h>
+
+
1 Synopsis
+          #include <complex.h>
            double complex csqrt(double complex z);
            float complex csqrtf(float complex z);
            long double complex csqrtl(long double complex z);
     Description
 

-
-
+
 
2   The csqrt functions compute the complex square root of z, with a branch cut along the
     negative real axis.
     Returns
 

-
-
+
 
3   The csqrt functions return the complex square root value, in the range of the right half-
     plane (including the imaginary axis).
 

-
-
+
 

 
7.3.9 [Manipulation functions]

-
 Manipulation functions
-

-
-
+
 

 
7.3.9.1 [The carg functions]

-

-
-
-
1          #include <complex.h>
+
+
1 Synopsis
+          #include <complex.h>
            double carg(double complex z);
            float cargf(float complex z);
            long double cargl(long double complex z);
     Description
 

-
-
+
 
2   The carg functions compute the argument (also called phase angle) of z, with a branch
     cut along the negative real axis.
     Returns
 

-
-
+
 
3   The carg functions return the value of the argument in the interval [- , + ].
 

-
-
+
 

 
7.3.9.2 [The cimag functions]

-

-
-
-
1          #include <complex.h>
+
+
1 Synopsis
+          #include <complex.h>
            double cimag(double complex z);
            float cimagf(float complex z);
            long double cimagl(long double complex z);
 
     Description
 

-
-
-
2   The cimag functions compute the imaginary part of z.170)
+
+
2   The cimag functions compute the imaginary part of z.[170]
     Returns
 

-
 
 
Footnote 170) For a variable z of complex type, z == creal(z) + cimag(z)*I.
 

 
-
+
 
3   The cimag functions return the imaginary part value (as a real).
 

-
-
+
 

 
7.3.9.3 [The conj functions]

-

-
-
-
1          #include <complex.h>
+
+
1 Synopsis
+          #include <complex.h>
            double complex conj(double complex z);
            float complex conjf(float complex z);
            long double complex conjl(long double complex z);
     Description
 

-
-
+
 
2   The conj functions compute the complex conjugate of z, by reversing the sign of its
     imaginary part.
     Returns
 

-
-
+
 
3   The conj functions return the complex conjugate value.
 

-
-
+
 

 
7.3.9.4 [The cproj functions]

-

-
-
-
1          #include <complex.h>
+
+
1 Synopsis
+          #include <complex.h>
            double complex cproj(double complex z);
            float complex cprojf(float complex z);
            long double complex cprojl(long double complex z);
     Description
 

-
-
+
 
2   The cproj functions compute a projection of z onto the Riemann sphere: z projects to
     z except that all complex infinities (even those with one infinite part and one NaN part)
     project to positive infinity on the real axis. If z has an infinite part, then cproj(z) is
@@ -10327,352 +9017,282 @@ replacement, as in:
            INFINITY + I * copysign(0.0, cimag(z))
     Returns
 

-
-
+
 
3   The cproj functions return the value of the projection onto the Riemann sphere.
 

-
-
+
 

 
7.3.9.5 [The creal functions]

-

-
-
-
1          #include <complex.h>
+
+
1 Synopsis
+          #include <complex.h>
            double creal(double complex z);
            float crealf(float complex z);
            long double creall(long double complex z);
     Description
 

-
-
-
2   The creal functions compute the real part of z.171)
+
+
2   The creal functions compute the real part of z.[171]
     Returns
 

-
 
 
Footnote 171) For a variable z of complex type, z == creal(z) + cimag(z)*I.
 

 
-
+
 
3   The creal functions return the real part value.
 

-
-
+
 

-
7.4 [Character handling ]

-

-
-
+
7.4 [Character handling <ctype.h>]

+
 
1   The header <ctype.h> declares several functions useful for classifying and mapping
-    characters.172) In all cases the argument is an int, the value of which shall be
+    characters.[172] In all cases the argument is an int, the value of which shall be
     representable as an unsigned char or shall equal the value of the macro EOF. If the
     argument has any other value, the behavior is undefined.
 

-
 
-
Footnote 172) See ``future library directions'' (7.26.2).
+
Footnote 172) See ``future library directions'' (7.26.2).
 

 
-
+
 
2   The behavior of these functions is affected by the current locale. Those functions that
     have locale-specific aspects only when not in the "C" locale are noted below.
 

-
-
+
 
3   The term printing character refers to a member of a locale-specific set of characters, each
     of which occupies one printing position on a display device; the term control character
     refers to a member of a locale-specific set of characters that are not printing
-    characters.173) All letters and digits are printing characters.
-    Forward references: EOF (7.19.1), localization (7.11).
+    characters.[173] All letters and digits are printing characters.
+    Forward references: EOF (7.19.1), localization (7.11).
 

-
 
 
Footnote 173) In an implementation that uses the seven-bit US ASCII character set, the printing characters are those
          whose values lie from 0x20 (space) through 0x7E (tilde); the control characters are those whose
          values lie from 0 (NUL) through 0x1F (US), and the character 0x7F (DEL).
+    none of iscntrl, isdigit, ispunct, or isspace is true.174) In the "C" locale,
+    isalpha returns true only for the characters for which isupper or islower is true.
 

 
-
+
 

 
7.4.1 [Character classification functions]

-

-
-
+
 
1   The functions in this subclause return nonzero (true) if and only if the value of the
     argument c conforms to that in the description of the function.
 

-
-
+
 

 
7.4.1.1 [The isalnum function]

-

-
-
-
1            #include <ctype.h>
+
+
1 Synopsis
+            #include <ctype.h>
              int isalnum(int c);
     Description
 

-
-
+
 
2   The isalnum function tests for any character for which isalpha or isdigit is true.
 

-
-
+
 

 
7.4.1.2 [The isalpha function]

-

-
-
-
1            #include <ctype.h>
+
+
1 Synopsis
+            #include <ctype.h>
              int isalpha(int c);
     Description
 

-
-
+
 
2   The isalpha function tests for any character for which isupper or islower is true,
     or any character that is one of a locale-specific set of alphabetic characters for which
-    none of iscntrl, isdigit, ispunct, or isspace is true.174) In the "C" locale,
-    isalpha returns true only for the characters for which isupper or islower is true.
 

-
-
-
Footnote 174) The functions islower and isupper test true or false separately for each of these additional
-         characters; all four combinations are possible.
-

-
-
+
 

 
7.4.1.3 [The isblank function]

-

-
-
-
1           #include <ctype.h>
+
+
1 Synopsis
+           #include <ctype.h>
             int isblank(int c);
     Description
 

-
-
+
 
2   The isblank function tests for any character that is a standard blank character or is one
     of a locale-specific set of characters for which isspace is true and that is used to
     separate words within a line of text. The standard blank characters are the following:
     space (' '), and horizontal tab ('\t'). In the "C" locale, isblank returns true only
     for the standard blank characters.
 

-
-
+
 

 
7.4.1.4 [The iscntrl function]

-

-
-
-
1           #include <ctype.h>
+
+
1 Synopsis
+           #include <ctype.h>
             int iscntrl(int c);
     Description
 

-
-
+
 
2   The iscntrl function tests for any control character.
 

-
-
+
 

 
7.4.1.5 [The isdigit function]

-

-
-
-
1           #include <ctype.h>
+
+
1 Synopsis
+           #include <ctype.h>
             int isdigit(int c);
     Description
 

-
-
-
2   The isdigit function tests for any decimal-digit character (as defined in 5.2.1).
+
+
2   The isdigit function tests for any decimal-digit character (as defined in 5.2.1).
 

-
-
+
 

 
7.4.1.6 [The isgraph function]

-

-
-
-
1           #include <ctype.h>
+
+
1 Synopsis
+           #include <ctype.h>
             int isgraph(int c);
-    Description
 

-
-
+
 
2   The isgraph function tests for any printing character except space (' ').
 

-
-
+
 

 
7.4.1.7 [The islower function]

-

-
-
-
1          #include <ctype.h>
+
+
1 Synopsis
+          #include <ctype.h>
            int islower(int c);
     Description
 

-
-
+
 
2   The islower function tests for any character that is a lowercase letter or is one of a
     locale-specific set of characters for which none of iscntrl, isdigit, ispunct, or
     isspace is true. In the "C" locale, islower returns true only for the lowercase
-    letters (as defined in 5.2.1).
+    letters (as defined in 5.2.1).
 

-
-
+
 

 
7.4.1.8 [The isprint function]

-

-
-
-
1          #include <ctype.h>
+
+
1 Synopsis
+          #include <ctype.h>
            int isprint(int c);
     Description
 

-
-
+
 
2   The isprint function tests for any printing character including space (' ').
 

-
-
+
 

 
7.4.1.9 [The ispunct function]

-

-
-
-
1          #include <ctype.h>
+
+
1 Synopsis
+          #include <ctype.h>
            int ispunct(int c);
     Description
 

-
-
+
 
2   The ispunct function tests for any printing character that is one of a locale-specific set
     of punctuation characters for which neither isspace nor isalnum is true. In the "C"
     locale, ispunct returns true for every printing character for which neither isspace
     nor isalnum is true.
 

-
-
+
 

 
7.4.1.10 [The isspace function]

-

-
-
-
1          #include <ctype.h>
+
+
1 Synopsis
+          #include <ctype.h>
            int isspace(int c);
     Description
 

-
-
+
 
2   The isspace function tests for any character that is a standard white-space character or
     is one of a locale-specific set of characters for which isalnum is false. The standard
     white-space characters are the following: space (' '), form feed ('\f'), new-line
     ('\n'), carriage return ('\r'), horizontal tab ('\t'), and vertical tab ('\v'). In the
     "C" locale, isspace returns true only for the standard white-space characters.
 

-
-
+
 

 
7.4.1.11 [The isupper function]

-

-
-
-
1          #include <ctype.h>
+
+
1 Synopsis
+          #include <ctype.h>
            int isupper(int c);
     Description
 

-
-
+
 
2   The isupper function tests for any character that is an uppercase letter or is one of a
     locale-specific set of characters for which none of iscntrl, isdigit, ispunct, or
     isspace is true. In the "C" locale, isupper returns true only for the uppercase
-    letters (as defined in 5.2.1).
+    letters (as defined in 5.2.1).
 

-
-
+
 

 
7.4.1.12 [The isxdigit function]

-

-
-
-
1          #include <ctype.h>
+
+
1 Synopsis
+          #include <ctype.h>
            int isxdigit(int c);
     Description
 

-
-
-
2   The isxdigit function tests for any hexadecimal-digit character (as defined in 6.4.4.1).
+
+
2   The isxdigit function tests for any hexadecimal-digit character (as defined in 6.4.4.1).
 

-
-
+
 

 
7.4.2 [Character case mapping functions]

-
 Character case mapping functions
-

-
-
+
 

 
7.4.2.1 [The tolower function]

-

-
-
-
1          #include <ctype.h>
+
+
1 Synopsis
+          #include <ctype.h>
            int tolower(int c);
     Description
 

-
-
+
 
2   The tolower function converts an uppercase letter to a corresponding lowercase letter.
     Returns
 

-
-
+
 
3   If the argument is a character for which isupper is true and there are one or more
     corresponding characters, as specified by the current locale, for which islower is true,
     the tolower function returns one of the corresponding characters (always the same one
     for any given locale); otherwise, the argument is returned unchanged.
 
 

-
-
+
 

 
7.4.2.2 [The toupper function]

-

-
-
-
1          #include <ctype.h>
+
+
1 Synopsis
+          #include <ctype.h>
            int toupper(int c);
     Description
 

-
-
+
 
2   The toupper function converts a lowercase letter to a corresponding uppercase letter.
     Returns
 

-
-
+
 
3   If the argument is a character for which islower is true and there are one or more
     corresponding characters, as specified by the current locale, for which isupper is true,
     the toupper function returns one of the corresponding characters (always the same one
     for any given locale); otherwise, the argument is returned unchanged.
 
 

-
-
+
 

-
7.5 [Errors ]

-

-
-
+
7.5 [Errors <errno.h>]

+
 
1   The header <errno.h> defines several macros, all relating to the reporting of error
     conditions.
 

-
-
+
 
2   The macros are
              EDOM
              EILSEQ
@@ -10680,25 +9300,23 @@ replacement, as in:
     which expand to integer constant expressions with type int, distinct positive values, and
     which are suitable for use in #if preprocessing directives; and
              errno
-    which expands to a modifiable lvalue175) that has type int, the value of which is set to a
+    which expands to a modifiable lvalue[175] that has type int, the value of which is set to a
     positive error number by several library functions. It is unspecified whether errno is a
     macro or an identifier declared with external linkage. If a macro definition is suppressed
     in order to access an actual object, or a program defines an identifier with the name
     errno, the behavior is undefined.
 

-
 
 
Footnote 175) The macro errno need not be the identifier of an object. It might expand to a modifiable lvalue
          resulting from a function call (for example, *errno()).
 

 
-
+
 
3   The value of errno is zero at program startup, but is never set to zero by any library
-    function.176) The value of errno may be set to nonzero by a library function call
+    function.[176] The value of errno may be set to nonzero by a library function call
     whether or not there is an error, provided the use of errno is not documented in the
     description of the function in this International Standard.
 

-
 
 
Footnote 176) Thus, a program that uses errno for error checking should set it to zero before a library function call,
          then inspect it before a subsequent library function call. Of course, a library function can save the
@@ -10706,31 +9324,27 @@ replacement, as in:
          value is still zero just before the return.
 

 
-
+
 
4   Additional macro definitions, beginning with E and a digit or E and an uppercase
-    letter,177) may also be specified by the implementation.
+    letter,[177] may also be specified by the implementation.
 

-
 
-
Footnote 177) See ``future library directions'' (7.26.3).
+
Footnote 177) See ``future library directions'' (7.26.3).
 

 
-
+
 

-
7.6 [Floating-point environment ]

-

-
-
+
7.6 [Floating-point environment <fenv.h>]

+
 
1   The header <fenv.h> declares two types and several macros and functions to provide
     access to the floating-point environment. The floating-point environment refers
     collectively to any floating-point status flags and control modes supported by the
-    implementation.178) A floating-point status flag is a system variable whose value is set
+    implementation.[178] A floating-point status flag is a system variable whose value is set
     (but never cleared) when a floating-point exception is raised, which occurs as a side effect
-    of exceptional floating-point arithmetic to provide auxiliary information.179) A floating-
+    of exceptional floating-point arithmetic to provide auxiliary information.[179] A floating-
     point control mode is a system variable whose value may be set by the user to affect the
     subsequent behavior of floating-point arithmetic.
 

-
 
 
Footnote 178) This header is designed to support the floating-point exception status flags and directed-rounding
          control modes required by IEC 60559, and other similar floating-point state information. Also it is
@@ -10741,9 +9355,9 @@ replacement, as in:
 
Footnote 179) A floating-point status flag is not an object and can be set more than once within an expression.
 

 
-
+
 
2   Certain programming conventions support the intended model of use for the floating-
-    point environment:180)
+    point environment:[180]
     -- a function call does not alter its caller's floating-point control modes, clear its caller's
        floating-point status flags, nor depend on the state of its caller's floating-point status
        flags unless the function is so documented;
@@ -10752,27 +9366,24 @@ replacement, as in:
     -- a function call is assumed to have the potential for raising floating-point exceptions,
        unless its documentation promises otherwise.
 

-
 
 
Footnote 180) With these conventions, a programmer can safely assume default floating-point control modes (or be
          unaware of them). The responsibilities associated with accessing the floating-point environment fall
          on the programmer or program that does so explicitly.
 

 
-
+
 
3   The type
              fenv_t
     represents the entire floating-point environment.
 

-
-
+
 
4   The type
              fexcept_t
     represents the floating-point status flags collectively, including any status the
     implementation associates with the flags.
 

-
-
+
 
5   Each of the macros
             FE_DIVBYZERO
             FE_INEXACT
@@ -10780,17 +9391,16 @@ replacement, as in:
             FE_OVERFLOW
             FE_UNDERFLOW
     is defined if and only if the implementation supports the floating-point exception by
-    means of the functions in 7.6.2.181) Additional implementation-defined floating-point
+    means of the functions in 7.6.2.[181] Additional implementation-defined floating-point
     exceptions, with macro definitions beginning with FE_ and an uppercase letter, may also
     be specified by the implementation. The defined macros expand to integer constant
     expressions with values such that bitwise ORs of all combinations of the macros result in
     distinct values, and furthermore, bitwise ANDs of all combinations of the macros result in
-    zero.182)
+    zero.[182]
 

-
 
 
Footnote 181) The implementation supports an exception if there are circumstances where a call to at least one of the
-         functions in 7.6.2, using the macro as the appropriate argument, will succeed. It is not necessary for
+         functions in 7.6.2, using the macro as the appropriate argument, will succeed. It is not necessary for
          all the functions to succeed all the time.
 

 
@@ -10798,14 +9408,13 @@ replacement, as in:
 
Footnote 182) The macros should be distinct powers of two.
 

 
-
+
 
6   The macro
             FE_ALL_EXCEPT
     is simply the bitwise OR of all floating-point exception macros defined by the
     implementation. If no such macros are defined, FE_ALL_EXCEPT shall be defined as 0.
 

-
-
+
 
7   Each of the macros
             FE_DOWNWARD
             FE_TONEAREST
@@ -10816,43 +9425,38 @@ replacement, as in:
     Additional implementation-defined rounding directions, with macro definitions beginning
     with FE_ and an uppercase letter, may also be specified by the implementation. The
     defined macros expand to integer constant expressions whose values are distinct
-    nonnegative values.183)
+    nonnegative values.[183]
 

-
 
 
Footnote 183) Even though the rounding direction macros may expand to constants corresponding to the values of
          FLT_ROUNDS, they are not required to do so.
              FE_DFL_ENV
-

-
-
-
8   The macro
     represents the default floating-point environment -- the one installed at program startup
     -- and has type ``pointer to const-qualified fenv_t''. It can be used as an argument to
     <fenv.h> functions that manage the floating-point environment.
-

+

 
-
+
+
8   The macro
+

+
 
9   Additional implementation-defined environments, with macro definitions beginning with
     FE_ and an uppercase letter, and having type ``pointer to const-qualified fenv_t'', may
     also be specified by the implementation.
 

-
-
+
 

 
7.6.1 [The FENV_ACCESS pragma]

-

-
-
-
1            #include <fenv.h>
+
+
1 Synopsis
+            #include <fenv.h>
              #pragma STDC FENV_ACCESS on-off-switch
     Description
 

-
-
+
 
2   The FENV_ACCESS pragma provides a means to inform the implementation when a
     program might access the floating-point environment to test floating-point status flags or
-    run under non-default floating-point control modes.184) The pragma shall occur either
+    run under non-default floating-point control modes.[184] The pragma shall occur either
     outside external declarations or preceding all explicit declarations and statements inside a
     compound statement. When outside external declarations, the pragma takes effect from
     its occurrence until another FENV_ACCESS pragma is encountered, or until the end of
@@ -10869,7 +9473,6 @@ replacement, as in:
     FENV_ACCESS ``on'', the state of the floating-point status flags is unspecified and the
     floating-point control modes have their default settings.)
 

-
 
 
Footnote 184) The purpose of the FENV_ACCESS pragma is to allow certain optimizations that could subvert flag
          tests and mode changes (e.g., global common subexpression elimination, code motion, and constant
@@ -10877,7 +9480,7 @@ replacement, as in:
          modes are in effect and the flags are not tested.
 

 
-
+
 
3   EXAMPLE
             #include <fenv.h>
             void f(double x)
@@ -10891,33 +9494,28 @@ replacement, as in:
                   /* ... */
             }
 

-
-
+
 
4   If the function g might depend on status flags set as a side effect of the first x + 1, or if the second
     x + 1 might depend on control modes set as a side effect of the call to function g, then the program shall
-    contain an appropriately placed invocation of #pragma STDC FENV_ACCESS ON.185)
+    contain an appropriately placed invocation of #pragma STDC FENV_ACCESS ON.[185]
 
 

-
 
 
Footnote 185) The side effects impose a temporal ordering that requires two evaluations of x + 1. On the other
          hand, without the #pragma STDC FENV_ACCESS ON pragma, and assuming the default state is
          ``off'', just one evaluation of x + 1 would suffice.
 

 
-
+
 

 
7.6.2 [Floating-point exceptions]

-

-
-
-
1   The following functions provide access to the floating-point status flags.186) The int
+
+
1   The following functions provide access to the floating-point status flags.[186] The int
     input argument for the functions represents a subset of floating-point exceptions, and can
     be zero or the bitwise OR of one or more floating-point exception macros, for example
     FE_OVERFLOW | FE_INEXACT. For other argument values the behavior of these
     functions is undefined.
 

-
 
 
Footnote 186) The functions fetestexcept, feraiseexcept, and feclearexcept support the basic
          abstraction of flags that are either set or clear. An implementation may endow floating-point status
@@ -10926,96 +9524,82 @@ replacement, as in:
          content of flags.
 

 
-
+
 

 
7.6.2.1 [The feclearexcept function]

-

-
-
-
1           #include <fenv.h>
+
+
1 Synopsis
+           #include <fenv.h>
             int feclearexcept(int excepts);
     Description
 

-
-
+
 
2   The feclearexcept function attempts to clear the supported floating-point exceptions
     represented by its argument.
     Returns
 

-
-
+
 
3   The feclearexcept function returns zero if the excepts argument is zero or if all
     the specified exceptions were successfully cleared. Otherwise, it returns a nonzero value.
 

-
-
+
 

 
7.6.2.2 [The fegetexceptflag function]

-

-
-
-
1            #include <fenv.h>
+
+
1 Synopsis
+            #include <fenv.h>
              int fegetexceptflag(fexcept_t *flagp,
                   int excepts);
     Description
 

-
-
+
 
2   The fegetexceptflag function attempts to store an implementation-defined
     representation of the states of the floating-point status flags indicated by the argument
     excepts in the object pointed to by the argument flagp.
     Returns
 

-
-
+
 
3   The fegetexceptflag function returns zero if the representation was successfully
     stored. Otherwise, it returns a nonzero value.
 

-
-
+
 

 
7.6.2.3 [The feraiseexcept function]

-

-
-
-
1            #include <fenv.h>
+
+
1 Synopsis
+            #include <fenv.h>
              int feraiseexcept(int excepts);
     Description
 

-
-
+
 
2   The feraiseexcept function attempts to raise the supported floating-point exceptions
-    represented by its argument.187) The order in which these floating-point exceptions are
-    raised is unspecified, except as stated in F.7.6. Whether the feraiseexcept function
+    represented by its argument.[187] The order in which these floating-point exceptions are
+    raised is unspecified, except as stated in F.7.6. Whether the feraiseexcept function
     additionally raises the ``inexact'' floating-point exception whenever it raises the
     ``overflow'' or ``underflow'' floating-point exception is implementation-defined.
     Returns
 

-
 
 
Footnote 187) The effect is intended to be similar to that of floating-point exceptions raised by arithmetic operations.
          Hence, enabled traps for floating-point exceptions raised by this function are taken. The specification
-         in F.7.6 is in the same spirit.
+         in F.7.6 is in the same spirit.
 

 
-
+
 
3   The feraiseexcept function returns zero if the excepts argument is zero or if all
     the specified exceptions were successfully raised. Otherwise, it returns a nonzero value.
 

-
-
+
 

 
7.6.2.4 [The fesetexceptflag function]

-

-
-
-
1            #include <fenv.h>
+
+
1 Synopsis
+            #include <fenv.h>
              int fesetexceptflag(const fexcept_t *flagp,
                   int excepts);
     Description
 

-
-
+
 
2   The fesetexceptflag function attempts to set the floating-point status flags
     indicated by the argument excepts to the states stored in the object pointed to by
     flagp. The value of *flagp shall have been set by a previous call to
@@ -11024,31 +9608,26 @@ replacement, as in:
     point exceptions, but only sets the state of the flags.
     Returns
 

-
-
+
 
3   The fesetexceptflag function returns zero if the excepts argument is zero or if
     all the specified flags were successfully set to the appropriate state. Otherwise, it returns
     a nonzero value.
 

-
-
+
 

 
7.6.2.5 [The fetestexcept function]

-

-
-
-
1            #include <fenv.h>
+
+
1 Synopsis
+            #include <fenv.h>
              int fetestexcept(int excepts);
     Description
 

-
-
+
 
2   The fetestexcept function determines which of a specified subset of the floating-
     point exception flags are currently set. The excepts argument specifies the floating-
-    point status flags to be queried.188)
+    point status flags to be queried.[188]
     Returns
 

-
 
 
Footnote 188) This mechanism allows testing several floating-point exceptions with just one function call.
            #include <fenv.h>
@@ -11065,73 +9644,60 @@ replacement, as in:
            }
 

 
-
+
 
3   The fetestexcept function returns the value of the bitwise OR of the floating-point
     exception macros corresponding to the currently set floating-point exceptions included in
     excepts.
 

-
-
+
 
4   EXAMPLE       Call f if ``invalid'' is set, then g if ``overflow'' is set:
 
 

-
-
+
 

 
7.6.3 [Rounding]

-

-
-
+
 
1   The fegetround and fesetround functions provide control of rounding direction
     modes.
 

-
-
+
 

 
7.6.3.1 [The fegetround function]

-

-
-
-
1          #include <fenv.h>
+
+
1 Synopsis
+          #include <fenv.h>
            int fegetround(void);
     Description
 

-
-
+
 
2   The fegetround function gets the current rounding direction.
     Returns
 

-
-
+
 
3   The fegetround function returns the value of the rounding direction macro
     representing the current rounding direction or a negative value if there is no such
     rounding direction macro or the current rounding direction is not determinable.
 

-
-
+
 

 
7.6.3.2 [The fesetround function]

-

-
-
-
1          #include <fenv.h>
+
+
1 Synopsis
+          #include <fenv.h>
            int fesetround(int round);
     Description
 

-
-
+
 
2   The fesetround function establishes the rounding direction represented by its
     argument round. If the argument is not equal to the value of a rounding direction macro,
     the rounding direction is not changed.
     Returns
 

-
-
+
 
3   The fesetround function returns zero if and only if the requested rounding direction
     was established.
 

-
-
+
 
4   EXAMPLE Save, set, and restore the rounding direction. Report an error and abort if setting the
     rounding direction fails.
            #include <fenv.h>
@@ -11150,58 +9716,47 @@ replacement, as in:
            }
 
 

-
-
+
 

 
7.6.4 [Environment]

-

-
-
+
 
1   The functions in this section manage the floating-point environment -- status flags and
     control modes -- as one entity.
 

-
-
+
 

 
7.6.4.1 [The fegetenv function]

-

-
-
-
1          #include <fenv.h>
+
+
1 Synopsis
+          #include <fenv.h>
            int fegetenv(fenv_t *envp);
     Description
 

-
-
+
 
2   The fegetenv function attempts to store the current floating-point environment in the
     object pointed to by envp.
     Returns
 

-
-
+
 
3   The fegetenv function returns zero if the environment was successfully stored.
     Otherwise, it returns a nonzero value.
 

-
-
+
 

 
7.6.4.2 [The feholdexcept function]

-

-
-
-
1          #include <fenv.h>
+
+
1 Synopsis
+          #include <fenv.h>
            int feholdexcept(fenv_t *envp);
     Description
 

-
-
+
 
2   The feholdexcept function saves the current floating-point environment in the object
     pointed to by envp, clears the floating-point status flags, and then installs a non-stop
     (continue on floating-point exceptions) mode, if available, for all floating-point
-    exceptions.189)
+    exceptions.[189]
     Returns
 

-
 
 
Footnote 189) IEC 60559 systems have a default non-stop mode, and typically at least one other mode for trap
          handling or aborting; if the system provides only the non-stop mode then installing it is trivial. For
@@ -11209,23 +9764,20 @@ replacement, as in:
          function to write routines that hide spurious floating-point exceptions from their callers.
 

 
-
+
 
3   The feholdexcept function returns zero if and only if non-stop floating-point
     exception handling was successfully installed.
 

-
-
+
 

 
7.6.4.3 [The fesetenv function]

-

-
-
-
1           #include <fenv.h>
+
+
1 Synopsis
+           #include <fenv.h>
             int fesetenv(const fenv_t *envp);
     Description
 

-
-
+
 
2   The fesetenv function attempts to establish the floating-point environment represented
     by the object pointed to by envp. The argument envp shall point to an object set by a
     call to fegetenv or feholdexcept, or equal a floating-point environment macro.
@@ -11233,24 +9785,20 @@ replacement, as in:
     represented through its argument, and does not raise these floating-point exceptions.
     Returns
 

-
-
+
 
3   The fesetenv function returns zero if the environment was successfully established.
     Otherwise, it returns a nonzero value.
 

-
-
+
 

 
7.6.4.4 [The feupdateenv function]

-

-
-
-
1           #include <fenv.h>
+
+
1 Synopsis
+           #include <fenv.h>
             int feupdateenv(const fenv_t *envp);
     Description
 

-
-
+
 
2   The feupdateenv function attempts to save the currently raised floating-point
     exceptions in its automatic storage, install the floating-point environment represented by
     the object pointed to by envp, and then raise the saved floating-point exceptions. The
@@ -11258,13 +9806,11 @@ replacement, as in:
     or equal a floating-point environment macro.
     Returns
 

-
-
+
 
3   The feupdateenv function returns zero if all the actions were successfully carried out.
     Otherwise, it returns a nonzero value.
 

-
-
+
 
4   EXAMPLE   Hide spurious underflow floating-point exceptions:
           #include <fenv.h>
           double f(double x)
@@ -11284,65 +9830,53 @@ replacement, as in:
           }
 
 

-
-
+
 

-
7.7 [Characteristics of floating types ]

-

-
-
+
7.7 [Characteristics of floating types <float.h>]

+
 
1   The header <float.h> defines several macros that expand to various limits and
     parameters of the standard floating-point types.
 

-
-
+
 
2   The macros, their meanings, and the constraints (or restrictions) on their values are listed
-    in 5.2.4.2.2.
+    in 5.2.4.2.2.
 
 

-
-
+
 

-
7.8 [Format conversion of integer types ]

-

-
-
+
7.8 [Format conversion of integer types <inttypes.h>]

+
 
1   The header <inttypes.h> includes the header <stdint.h> and extends it with
     additional facilities provided by hosted implementations.
 

-
-
+
 
2   It declares functions for manipulating greatest-width integers and converting numeric
     character strings to greatest-width integers, and it declares the type
              imaxdiv_t
     which is a structure type that is the type of the value returned by the imaxdiv function.
     For each type declared in <stdint.h>, it defines corresponding macros for conversion
-    specifiers for use with the formatted input/output functions.190)
-    Forward references: integer types <stdint.h> (7.18), formatted input/output
-    functions (7.19.6), formatted wide character input/output functions (7.24.2).
+    specifiers for use with the formatted input/output functions.[190]
+    Forward references: integer types <stdint.h> (7.18), formatted input/output
+    functions (7.19.6), formatted wide character input/output functions (7.24.2).
 

-
 
-
Footnote 190) See ``future library directions'' (7.26.4).
+
Footnote 190) See ``future library directions'' (7.26.4).
 

 
-
+
 

 
7.8.1 [Macros for format specifiers]

-

-
-
-
1   Each of the following object-like macros191) expands to a character string literal
+
+
1   Each of the following object-like macros[191] expands to a character string literal
     containing a conversion specifier, possibly modified by a length modifier, suitable for use
     within the format argument of a formatted input/output function when converting the
     corresponding integer type. These macro names have the general form of PRI (character
     string literals for the fprintf and fwprintf family) or SCN (character string literals
-    for the fscanf and fwscanf family),192) followed by the conversion specifier,
-    followed by a name corresponding to a similar type name in 7.18.1. In these names, N
-    represents the width of the type as described in 7.18.1. For example, PRIdFAST32 can
+    for the fscanf and fwscanf family),[192] followed by the conversion specifier,
+    followed by a name corresponding to a similar type name in 7.18.1. In these names, N
+    represents the width of the type as described in 7.18.1. For example, PRIdFAST32 can
     be used in a format string to print the value of an integer of type int_fast32_t.
 

-
 
 
Footnote 191) C++ implementations should define these macros only when _ _STDC_FORMAT_MACROS is defined
          before <inttypes.h> is included.
@@ -11354,41 +9888,36 @@ replacement, as in:
          same.
 

 
-
+
 
2   The fprintf macros for signed integers are:
            PRIdN             PRIdLEASTN                PRIdFASTN          PRIdMAX             PRIdPTR
            PRIiN             PRIiLEASTN                PRIiFASTN          PRIiMAX             PRIiPTR
 

-
-
+
 
3   The fprintf macros for unsigned integers are:
            PRIoN           PRIoLEASTN               PRIoFASTN              PRIoMAX             PRIoPTR
            PRIuN           PRIuLEASTN               PRIuFASTN              PRIuMAX             PRIuPTR
            PRIxN           PRIxLEASTN               PRIxFASTN              PRIxMAX             PRIxPTR
            PRIXN           PRIXLEASTN               PRIXFASTN              PRIXMAX             PRIXPTR
 

-
-
+
 
4   The fscanf macros for signed integers are:
            SCNdN           SCNdLEASTN               SCNdFASTN              SCNdMAX             SCNdPTR
            SCNiN           SCNiLEASTN               SCNiFASTN              SCNiMAX             SCNiPTR
 

-
-
+
 
5   The fscanf macros for unsigned integers are:
            SCNoN           SCNoLEASTN               SCNoFASTN              SCNoMAX             SCNoPTR
            SCNuN           SCNuLEASTN               SCNuFASTN              SCNuMAX             SCNuPTR
            SCNxN           SCNxLEASTN               SCNxFASTN              SCNxMAX             SCNxPTR
 

-
-
+
 
6   For each type that the implementation provides in <stdint.h>, the corresponding
     fprintf macros shall be defined and the corresponding fscanf macros shall be
     defined unless the implementation does not have a suitable fscanf length modifier for
     the type.
 

-
-
+
 
7   EXAMPLE
             #include <inttypes.h>
             #include <wchar.h>
@@ -11401,100 +9930,83 @@ replacement, as in:
             }
 
 

-
-
+
 

 
7.8.2 [Functions for greatest-width integer types]

-
 Functions for greatest-width integer types
-

-
-
+
 

 
7.8.2.1 [The imaxabs function]

-

-
-
-
1           #include <inttypes.h>
+
+
1 Synopsis
+           #include <inttypes.h>
             intmax_t imaxabs(intmax_t j);
     Description
 

-
-
+
 
2   The imaxabs function computes the absolute value of an integer j. If the result cannot
-    be represented, the behavior is undefined.193)
-    Returns
+    be represented, the behavior is undefined.[193]
 

-
 
 
Footnote 193) The absolute value of the most negative number cannot be represented in two's complement.
+    Returns
 

 
-
+
 
3   The imaxabs function returns the absolute value.
 

-
-
+
 

 
7.8.2.2 [The imaxdiv function]

-

-
-
-
1              #include <inttypes.h>
+
+
1 Synopsis
+              #include <inttypes.h>
                imaxdiv_t imaxdiv(intmax_t numer, intmax_t denom);
     Description
 

-
-
+
 
2   The imaxdiv function computes numer / denom and numer % denom in a single
     operation.
     Returns
 

-
-
+
 
3   The imaxdiv function returns a structure of type imaxdiv_t comprising both the
     quotient and the remainder. The structure shall contain (in either order) the members
     quot (the quotient) and rem (the remainder), each of which has type intmax_t. If
     either part of the result cannot be represented, the behavior is undefined.
 

-
-
+
 

 
7.8.2.3 [The strtoimax and strtoumax functions]

-

-
-
-
1          #include <inttypes.h>
+
+
1 Synopsis
+          #include <inttypes.h>
            intmax_t strtoimax(const char * restrict nptr,
                 char ** restrict endptr, int base);
            uintmax_t strtoumax(const char * restrict nptr,
                 char ** restrict endptr, int base);
     Description
 

-
-
+
 
2   The strtoimax and strtoumax functions are equivalent to the strtol, strtoll,
     strtoul, and strtoull functions, except that the initial portion of the string is
     converted to intmax_t and uintmax_t representation, respectively.
     Returns
 

-
-
+
 
3   The strtoimax and strtoumax functions return the converted value, if any. If no
     conversion could be performed, zero is returned. If the correct value is outside the range
     of representable values, INTMAX_MAX, INTMAX_MIN, or UINTMAX_MAX is returned
     (according to the return type and sign of the value, if any), and the value of the macro
     ERANGE is stored in errno.
     Forward references: the strtol, strtoll, strtoul, and strtoull functions
-    (7.20.1.4).
+    (7.20.1.4).
 

-
-
+
 

 
7.8.2.4 [The wcstoimax and wcstoumax functions]

-

-
-
-
1          #include <stddef.h>           // for wchar_t
+
+
1 Synopsis
+          #include <stddef.h>           // for wchar_t
            #include <inttypes.h>
            intmax_t wcstoimax(const wchar_t * restrict nptr,
                 wchar_t ** restrict endptr, int base);
@@ -11502,31 +10014,26 @@ replacement, as in:
                 wchar_t ** restrict endptr, int base);
     Description
 

-
-
+
 
2   The wcstoimax and wcstoumax functions are equivalent to the wcstol, wcstoll,
     wcstoul, and wcstoull functions except that the initial portion of the wide string is
     converted to intmax_t and uintmax_t representation, respectively.
     Returns
 

-
-
+
 
3   The wcstoimax function returns the converted value, if any. If no conversion could be
     performed, zero is returned. If the correct value is outside the range of representable
     values, INTMAX_MAX, INTMAX_MIN, or UINTMAX_MAX is returned (according to the
     return type and sign of the value, if any), and the value of the macro ERANGE is stored in
     errno.
     Forward references: the wcstol, wcstoll, wcstoul, and wcstoull functions
-    (7.24.4.1.2).
+    (7.24.4.1.2).
 
 

-
-
+
 

-
7.9 [Alternative spellings ]

-

-
-
+
7.9 [Alternative spellings <iso646.h>]

+
 
1   The header <iso646.h> defines the following eleven macros (on the left) that expand
     to the corresponding tokens (on the right):
           and          &&
@@ -11542,38 +10049,30 @@ replacement, as in:
           xor_eq       ^=
 
 

-
-
+
 

-
7.10 [Sizes of integer types ]

-

-
-
+
7.10 [Sizes of integer types <limits.h>]

+
 
1   The header <limits.h> defines several macros that expand to various limits and
     parameters of the standard integer types.
 

-
-
+
 
2   The macros, their meanings, and the constraints (or restrictions) on their values are listed
-    in 5.2.4.2.1.
+    in 5.2.4.2.1.
 
 

-
-
+
 

-
7.11 [Localization ]

-

-
-
+
7.11 [Localization <locale.h>]

+
 
1   The header <locale.h> declares two functions, one type, and defines several macros.
 

-
-
+
 
2   The type is
            struct lconv
     which contains members related to the formatting of numeric values. The structure shall
     contain at least the following members, in any order. The semantics of the members and
-    their normal ranges are explained in 7.11.2.1. In the "C" locale, the members shall have
+    their normal ranges are explained in 7.11.2.1. In the "C" locale, the members shall have
     the values specified in the comments.
            char   *decimal_point;                 //   "."
            char   *thousands_sep;                 //   ""
@@ -11601,9 +10100,8 @@ replacement, as in:
            char   int_n_sign_posn;                //   CHAR_MAX
 
 

-
-
-
3   The macros defined are NULL (described in 7.17); and
+
+
3   The macros defined are NULL (described in 7.17); and
              LC_ALL
              LC_COLLATE
              LC_CTYPE
@@ -11611,129 +10109,77 @@ replacement, as in:
              LC_NUMERIC
              LC_TIME
     which expand to integer constant expressions with distinct values, suitable for use as the
-    first argument to the setlocale function.194) Additional macro definitions, beginning
-    with the characters LC_ and an uppercase letter,195) may also be specified by the
+    first argument to the setlocale function.[194] Additional macro definitions, beginning
+    with the characters LC_ and an uppercase letter,[195] may also be specified by the
     implementation.
 

-
 
 
Footnote 194) ISO/IEC 9945-2 specifies locale and charmap formats that may be used to specify locales for C.
 

 
 
-
Footnote 195) See ``future library directions'' (7.26.5).
+
Footnote 195) See ``future library directions'' (7.26.5).
 

 
-
+
 

 
7.11.1 [Locale control]

-
 Locale control
-

-
-
+
 

 
7.11.1.1 [The setlocale function]

-

-
-
-
1            #include <locale.h>
+
+
1 Synopsis
+            #include <locale.h>
              char *setlocale(int category, const char *locale);
     Description
 

-
-
+
 
2   The setlocale function selects the appropriate portion of the program's locale as
     specified by the category and locale arguments. The setlocale function may be
     used to change or query the program's entire current locale or portions thereof. The value
     LC_ALL for category names the program's entire locale; the other values for
     category name only a portion of the program's locale. LC_COLLATE affects the
     behavior of the strcoll and strxfrm functions. LC_CTYPE affects the behavior of
-    the character handling functions196) and the multibyte and wide character functions.
+    the character handling functions[196] and the multibyte and wide character functions.
     LC_MONETARY affects the monetary formatting information returned by the
     localeconv function. LC_NUMERIC affects the decimal-point character for the
     formatted input/output functions and the string conversion functions, as well as the
     nonmonetary formatting information returned by the localeconv function. LC_TIME
     affects the behavior of the strftime and wcsftime functions.
 

-
 
-
Footnote 196) The only functions in 7.4 whose behavior is not affected by the current locale are isdigit and
+
Footnote 196) The only functions in 7.4 whose behavior is not affected by the current locale are isdigit and
          isxdigit.
 

 
-
+
 
3   A value of "C" for locale specifies the minimal environment for C translation; a value
     of "" for locale specifies the locale-specific native environment. Other
     implementation-defined strings may be passed as the second argument to setlocale.
 

-
-
+
 
4   At program startup, the equivalent of
             setlocale(LC_ALL, "C");
     is executed.
 

-
-
+
 
5   The implementation shall behave as if no library function calls the setlocale function.
     Returns
 

-
-
+
 
6   If a pointer to a string is given for locale and the selection can be honored, the
     setlocale function returns a pointer to the string associated with the specified
     category for the new locale. If the selection cannot be honored, the setlocale
     function returns a null pointer and the program's locale is not changed.
 

-
-
+
 
7   A null pointer for locale causes the setlocale function to return a pointer to the
     string associated with the category for the program's current locale; the program's
-    locale is not changed.197)
+    locale is not changed.[197]
 

-
 
 
Footnote 197) The implementation shall arrange to encode in a string the various categories due to a heterogeneous
          locale when category has the value LC_ALL.
-

-
-
-
8   The pointer to string returned by the setlocale function is such that a subsequent call
-    with that string value and its associated category will restore that part of the program's
-    locale. The string pointed to shall not be modified by the program, but may be
-    overwritten by a subsequent call to the setlocale function.
-    Forward references: formatted input/output functions (7.19.6), multibyte/wide
-    character conversion functions (7.20.7), multibyte/wide string conversion functions
-    (7.20.8), numeric conversion functions (7.20.1), the strcoll function (7.21.4.3), the
-    strftime function (7.23.3.5), the strxfrm function (7.21.4.5).
-

-
-
-

-
7.11.2 [Numeric formatting convention inquiry]

-
 Numeric formatting convention inquiry
-

-
-
-

-
7.11.2.1 [The localeconv function]

-

-
-
-
1           #include <locale.h>
-            struct lconv *localeconv(void);
-    Description
-

-
-
-
2   The localeconv function sets the components of an object with type struct lconv
-    with values appropriate for the formatting of numeric quantities (monetary and otherwise)
-    according to the rules of the current locale.
-

-
-
-
3   The members of the structure with type char * are pointers to strings, any of which
-    (except decimal_point) can point to "", to indicate that the value is not available in
-    the current locale or is of zero length. Apart from grouping and mon_grouping, the
 strings shall start and end in the initial shift state. The members with type char are
 nonnegative numbers, any of which can be CHAR_MAX to indicate that the value is not
 available in the current locale. The members include the following:
@@ -11804,7 +10250,6 @@ char int_p_sep_by_space
           Set to a value indicating the separation of the int_curr_symbol, the
           sign string, and the value for a nonnegative internationally formatted
           monetary quantity.
-
     char int_n_sep_by_space
               Set to a value indicating the separation of the int_curr_symbol, the
               sign string, and the value for a negative internationally formatted monetary
@@ -11815,9 +10260,41 @@ char int_p_sep_by_space
     char int_n_sign_posn
               Set to a value indicating the positioning of the negative_sign for a
               negative internationally formatted monetary quantity.
-

+

 
-
+
+
8   The pointer to string returned by the setlocale function is such that a subsequent call
+    with that string value and its associated category will restore that part of the program's
+    locale. The string pointed to shall not be modified by the program, but may be
+    overwritten by a subsequent call to the setlocale function.
+    Forward references: formatted input/output functions (7.19.6), multibyte/wide
+    character conversion functions (7.20.7), multibyte/wide string conversion functions
+    (7.20.8), numeric conversion functions (7.20.1), the strcoll function (7.21.4.3), the
+    strftime function (7.23.3.5), the strxfrm function (7.21.4.5).
+

+
+

+
7.11.2 [Numeric formatting convention inquiry]

+
+

+
7.11.2.1 [The localeconv function]

+
+
1 Synopsis
+           #include <locale.h>
+            struct lconv *localeconv(void);
+    Description
+

+
+
2   The localeconv function sets the components of an object with type struct lconv
+    with values appropriate for the formatting of numeric quantities (monetary and otherwise)
+    according to the rules of the current locale.
+

+
+
3   The members of the structure with type char * are pointers to strings, any of which
+    (except decimal_point) can point to "", to indicate that the value is not available in
+    the current locale or is of zero length. Apart from grouping and mon_grouping, the
+

+
 
4   The elements of grouping and mon_grouping are interpreted according to the
     following:
     CHAR_MAX      No further grouping is to be performed.
@@ -11827,8 +10304,7 @@ char int_p_sep_by_space
                   The next element is examined to determine the size of the next group of
                   digits before the current group.
 

-
-
+
 
5   The values of p_sep_by_space, n_sep_by_space, int_p_sep_by_space,
     and int_n_sep_by_space are interpreted according to the following:
     0   No space separates the currency symbol and value.
@@ -11839,8 +10315,7 @@ char int_p_sep_by_space
     For int_p_sep_by_space and int_n_sep_by_space, the fourth character of
     int_curr_symbol is used instead of a space.
 

-
-
+
 
6   The values of p_sign_posn, n_sign_posn, int_p_sign_posn,                            and
     int_n_sign_posn are interpreted according to the following:
     0   Parentheses surround the quantity and currency symbol.
@@ -11849,22 +10324,19 @@ char int_p_sep_by_space
     3   The sign string immediately precedes the currency symbol.
     4   The sign string immediately succeeds the currency symbol.
 

-
-
+
 
7    The implementation shall behave as if no library function calls the localeconv
      function.
      Returns
 

-
-
+
 
8    The localeconv function returns a pointer to the filled-in object. The structure
      pointed to by the return value shall not be modified by the program, but may be
      overwritten by a subsequent call to the localeconv function. In addition, calls to the
      setlocale function with categories LC_ALL, LC_MONETARY, or LC_NUMERIC may
      overwrite the contents of the structure.
 

-
-
+
 
9    EXAMPLE 1 The following table illustrates rules which may well be used by four countries to format
      monetary quantities.
                                    Local format                                     International format
@@ -11876,8 +10348,7 @@ char int_p_sep_by_space
      Country3      1.234,56                -1.234,56                    NLG   1.234,56         NLG -1.234,56
      Country4     SFrs.1,234.56           SFrs.1,234.56C                CHF   1,234.56         CHF 1,234.56C
 

-
-
+
 
10   For these four countries, the respective values for the monetary members of the structure returned by
      localeconv could be:
                                        Country1              Country2              Country3            Country4
@@ -11905,8 +10376,7 @@ char int_p_sep_by_space
      int_n_sign_posn                   4                     1                    4                   2
 
 

-
-
+
 
11   EXAMPLE 2 The following table illustrates how the cs_precedes, sep_by_space, and sign_posn members
      affect the formatted value.
                                                                    p_sep_by_space
@@ -11926,27 +10396,23 @@ char int_p_sep_by_space
                                           4         $+1.25             $+ 1.25             $ +1.25
 
 

-
-
+
 

-
7.12 [Mathematics ]

-

-
-
+
7.12 [Mathematics <math.h>]

+
 
1   The header <math.h> declares two types and many mathematical functions and defines
     several macros. Most synopses specify a family of functions consisting of a principal
     function with one or more double parameters, a double return value, or both; and
     other functions with the same name but with f and l suffixes, which are corresponding
-    functions with float and long double parameters, return values, or both.198)
+    functions with float and long double parameters, return values, or both.[198]
     Integer arithmetic functions and conversion functions are discussed later.
 

-
 
 
Footnote 198) Particularly on systems with wide expression evaluation, a <math.h> function might pass arguments
          and return values in wider format than the synopsis prototype indicates.
 

 
-
+
 
2   The types
             float_t
             double_t
@@ -11955,50 +10421,42 @@ char int_p_sep_by_space
     float_t and double_t are float and double, respectively; if
     FLT_EVAL_METHOD equals 1, they are both double; if FLT_EVAL_METHOD equals
     2, they are both long double; and for other values of FLT_EVAL_METHOD, they are
-    otherwise implementation-defined.199)
+    otherwise implementation-defined.[199]
 

-
 
 
Footnote 199) The types float_t and double_t are intended to be the implementation's most efficient types at
          least as wide as float and double, respectively. For FLT_EVAL_METHOD equal 0, 1, or 2, the
          type float_t is the narrowest type used by the implementation to evaluate floating expressions.
 

 
-
+
 
3   The macro
             HUGE_VAL
     expands to a positive double constant expression, not necessarily representable as a
     float. The macros
             HUGE_VALF
             HUGE_VALL
-    are respectively float and long double analogs of HUGE_VAL.200)
+    are respectively float and long double analogs of HUGE_VAL.[200]
 

-
 
 
Footnote 200) HUGE_VAL, HUGE_VALF, and HUGE_VALL can be positive infinities in an implementation that
          supports infinities.
+    translation time.201)
 

 
-
+
 
4   The macro
             INFINITY
     expands to a constant expression of type float representing positive or unsigned
     infinity, if available; else to a positive constant of type float that overflows at
-    translation time.201)
 

-
-
-
Footnote 201) In this case, using INFINITY will violate the constraint in 6.4.4 and thus require a diagnostic.
-

-
-
+
 
5   The macro
              NAN
     is defined if and only if the implementation supports quiet NaNs for the float type. It
     expands to a constant expression of type float representing a quiet NaN.
 

-
-
+
 
6   The number classification macros
              FP_INFINITE
              FP_NAN
@@ -12010,26 +10468,24 @@ char int_p_sep_by_space
     point classifications, with macro definitions beginning with FP_ and an uppercase letter,
     may also be specified by the implementation.
 

-
-
+
 
7   The macro
              FP_FAST_FMA
     is optionally defined. If defined, it indicates that the fma function generally executes
-    about as fast as, or faster than, a multiply and an add of double operands.202) The
+    about as fast as, or faster than, a multiply and an add of double operands.[202] The
     macros
              FP_FAST_FMAF
              FP_FAST_FMAL
     are, respectively, float and long double analogs of FP_FAST_FMA. If defined,
     these macros expand to the integer constant 1.
 

-
 
 
Footnote 202) Typically, the FP_FAST_FMA macro is defined if and only if the fma function is implemented
          directly with a hardware multiply-add instruction. Software implementations are expected to be
          substantially slower.
 

 
-
+
 
8   The macros
              FP_ILOGB0
              FP_ILOGBNAN
@@ -12037,8 +10493,7 @@ char int_p_sep_by_space
     zero or NaN, respectively. The value of FP_ILOGB0 shall be either INT_MIN or
     -INT_MAX. The value of FP_ILOGBNAN shall be either INT_MAX or INT_MIN.
 

-
-
+
 
9   The macros
             MATH_ERRNO
             MATH_ERREXCEPT
@@ -12054,58 +10509,51 @@ char int_p_sep_by_space
     shall define the macros FE_DIVBYZERO, FE_INVALID, and FE_OVERFLOW in
     <fenv.h>.
 

-
-
+
 

 
7.12.1 [Treatment of error conditions]

-

-
-
+
 
1   The behavior of each of the functions in <math.h> is specified for all representable
     values of its input arguments, except where stated otherwise. Each function shall execute
     as if it were a single operation without generating any externally visible exceptional
     conditions.
 

-
-
+
 
2   For all functions, a domain error occurs if an input argument is outside the domain over
     which the mathematical function is defined. The description of each function lists any
     required domain errors; an implementation may define additional domain errors, provided
-    that such errors are consistent with the mathematical definition of the function.203) On a
+    that such errors are consistent with the mathematical definition of the function.[203] On a
     domain error, the function returns an implementation-defined value; if the integer
     expression math_errhandling & MATH_ERRNO is nonzero, the integer expression
     errno acquires the value EDOM; if the integer expression math_errhandling &
     MATH_ERREXCEPT is nonzero, the ``invalid'' floating-point exception is raised.
 

-
 
 
Footnote 203) In an implementation that supports infinities, this allows an infinity as an argument to be a domain
          error if the mathematical domain of the function does not include the infinity.
-

-
-
-
3   Similarly, a range error occurs if the mathematical result of the function cannot be
-    represented in an object of the specified type, due to extreme magnitude.
-

-
-
-
4   A floating result overflows if the magnitude of the mathematical result is finite but so
-    large that the mathematical result cannot be represented without extraordinary roundoff
-    error in an object of the specified type. If a floating result overflows and default rounding
-    is in effect, or if the mathematical result is an exact infinity from finite arguments (for
-    example log(0.0)), then the function returns the value of the macro HUGE_VAL,
     HUGE_VALF, or HUGE_VALL according to the return type, with the same sign as the
     correct value of the function; if the integer expression math_errhandling &
     MATH_ERRNO is nonzero, the integer expression errno acquires the value ERANGE; if
     the integer expression math_errhandling & MATH_ERREXCEPT is nonzero, the
     ``divide-by-zero'' floating-point exception is raised if the mathematical result is an exact
     infinity and the ``overflow'' floating-point exception is raised otherwise.
-

+

 
-
+
+
3   Similarly, a range error occurs if the mathematical result of the function cannot be
+    represented in an object of the specified type, due to extreme magnitude.
+

+
+
4   A floating result overflows if the magnitude of the mathematical result is finite but so
+    large that the mathematical result cannot be represented without extraordinary roundoff
+    error in an object of the specified type. If a floating result overflows and default rounding
+    is in effect, or if the mathematical result is an exact infinity from finite arguments (for
+    example log(0.0)), then the function returns the value of the macro HUGE_VAL,
+

+
 
5   The result underflows if the magnitude of the mathematical result is so small that the
     mathematical result cannot be represented, without extraordinary roundoff error, in an
-    object of the specified type.204) If the result underflows, the function returns an
+    object of the specified type.[204] If the result underflows, the function returns an
     implementation-defined value whose magnitude is no greater than the smallest
     normalized positive number in the specified type; if the integer expression
     math_errhandling & MATH_ERRNO is nonzero, whether errno acquires the
@@ -12113,26 +10561,23 @@ char int_p_sep_by_space
     math_errhandling & MATH_ERREXCEPT is nonzero, whether the ``underflow''
     floating-point exception is raised is implementation-defined.
 

-
 
 
Footnote 204) The term underflow here is intended to encompass both ``gradual underflow'' as in IEC 60559 and
          also ``flush-to-zero'' underflow.
 

 
-
+
 

 
7.12.2 [The FP_CONTRACT pragma]

-

-
-
-
1           #include <math.h>
+
+
1 Synopsis
+           #include <math.h>
             #pragma STDC FP_CONTRACT on-off-switch
     Description
 

-
-
+
 
2   The FP_CONTRACT pragma can be used to allow (if the state is ``on'') or disallow (if the
-    state is ``off'') the implementation to contract expressions (6.5). Each pragma can occur
+    state is ``off'') the implementation to contract expressions (6.5). Each pragma can occur
     either outside external declarations or preceding all explicit declarations and statements
     inside a compound statement. When outside external declarations, the pragma takes
     effect from its occurrence until another FP_CONTRACT pragma is encountered, or until
@@ -12144,48 +10589,41 @@ char int_p_sep_by_space
     context, the behavior is undefined. The default state (``on'' or ``off'') for the pragma is
     implementation-defined.
 

-
-
+
 

 
7.12.3 [Classification macros]

-

-
-
+
 
1   In the synopses in this subclause, real-floating indicates that the argument shall be an
     expression of real floating type.
 

-
-
+
 

 
7.12.3.1 [The fpclassify macro]

-

-
-
-
1            #include <math.h>
+
+
1 Synopsis
+            #include <math.h>
              int fpclassify(real-floating x);
     Description
 

-
-
+
 
2   The fpclassify macro classifies its argument value as NaN, infinite, normal,
     subnormal, zero, or into another implementation-defined category. First, an argument
     represented in a format wider than its semantic type is converted to its semantic type.
-    Then classification is based on the type of the argument.205)
+    Then classification is based on the type of the argument.[205]
     Returns
 

-
 
 
Footnote 205) Since an expression can be evaluated with more range and precision than its type has, it is important to
          know the type that classification is based on. For example, a normal long double value might
          become subnormal when converted to double, and zero when converted to float.
+    Returns
 

 
-
+
 
3   The fpclassify macro returns the value of the number classification macro
     appropriate to the value of its argument.
 

-
-
+
 
4   EXAMPLE        The fpclassify macro might be implemented in terms of ordinary functions as
              #define fpclassify(x) \
                    ((sizeof (x) == sizeof (float)) ? _ _fpclassifyf(x) : \
@@ -12193,756 +10631,626 @@ char int_p_sep_by_space
                                                       _ _fpclassifyl(x))
 
 

-
-
+
 

 
7.12.3.2 [The isfinite macro]

-

-
-
-
1            #include <math.h>
+
+
1 Synopsis
+            #include <math.h>
              int isfinite(real-floating x);
     Description
 

-
-
+
 
2   The isfinite macro determines whether its argument has a finite value (zero,
     subnormal, or normal, and not infinite or NaN). First, an argument represented in a
     format wider than its semantic type is converted to its semantic type. Then determination
     is based on the type of the argument.
-    Returns
 

-
-
+
 
3   The isfinite macro returns a nonzero value if and only if its argument has a finite
     value.
 

-
-
+
 

 
7.12.3.3 [The isinf macro]

-

-
-
-
1           #include <math.h>
+
+
1 Synopsis
+           #include <math.h>
             int isinf(real-floating x);
     Description
 

-
-
+
 
2   The isinf macro determines whether its argument value is an infinity (positive or
     negative). First, an argument represented in a format wider than its semantic type is
     converted to its semantic type. Then determination is based on the type of the argument.
     Returns
 

-
-
+
 
3   The isinf macro returns a nonzero value if and only if its argument has an infinite
     value.
 

-
-
+
 

 
7.12.3.4 [The isnan macro]

-

-
-
-
1           #include <math.h>
+
+
1 Synopsis
+           #include <math.h>
             int isnan(real-floating x);
     Description
 

-
-
+
 
2   The isnan macro determines whether its argument value is a NaN. First, an argument
     represented in a format wider than its semantic type is converted to its semantic type.
-    Then determination is based on the type of the argument.206)
+    Then determination is based on the type of the argument.[206]
     Returns
 

-
 
 
Footnote 206) For the isnan macro, the type for determination does not matter unless the implementation supports
          NaNs in the evaluation type but not in the semantic type.
+    Description
 

 
-
+
 
3   The isnan macro returns a nonzero value if and only if its argument has a NaN value.
 

-
-
+
 

 
7.12.3.5 [The isnormal macro]

-

-
-
-
1           #include <math.h>
+
+
1 Synopsis
+           #include <math.h>
             int isnormal(real-floating x);
-    Description
 

-
-
+
 
2   The isnormal macro determines whether its argument value is normal (neither zero,
     subnormal, infinite, nor NaN). First, an argument represented in a format wider than its
     semantic type is converted to its semantic type. Then determination is based on the type
     of the argument.
     Returns
 

-
-
+
 
3   The isnormal macro returns a nonzero value if and only if its argument has a normal
     value.
 

-
-
+
 

 
7.12.3.6 [The signbit macro]

-

-
-
-
1           #include <math.h>
+
+
1 Synopsis
+           #include <math.h>
             int signbit(real-floating x);
     Description
 

-
-
-
2   The signbit macro determines whether the sign of its argument value is negative.207)
+
+
2   The signbit macro determines whether the sign of its argument value is negative.[207]
     Returns
 

-
 
 
Footnote 207) The signbit macro reports the sign of all values, including infinities, zeros, and NaNs. If zero is
          unsigned, it is treated as positive.
 

 
-
+
 
3   The signbit macro returns a nonzero value if and only if the sign of its argument value
     is negative.
 

-
-
+
 

 
7.12.4 [Trigonometric functions]

-
 Trigonometric functions
-

-
-
+
 

 
7.12.4.1 [The acos functions]

-

-
-
-
1           #include <math.h>
+
+
1 Synopsis
+           #include <math.h>
             double acos(double x);
             float acosf(float x);
             long double acosl(long double x);
     Description
 

-
-
+
 
2   The acos functions compute the principal value of the arc cosine of x. A domain error
     occurs for arguments not in the interval [-1, +1].
     Returns
 

-
-
+
 
3   The acos functions return arccos x in the interval [0,  ] radians.
 

-
-
+
 

 
7.12.4.2 [The asin functions]

-

-
-
-
1          #include <math.h>
+
+
1 Synopsis
+          #include <math.h>
            double asin(double x);
            float asinf(float x);
            long double asinl(long double x);
     Description
 

-
-
+
 
2   The asin functions compute the principal value of the arc sine of x. A domain error
     occurs for arguments not in the interval [-1, +1].
     Returns
 

-
-
+
 
3   The asin functions return arcsin x in the interval [- /2, + /2] radians.
 

-
-
+
 

 
7.12.4.3 [The atan functions]

-

-
-
-
1          #include <math.h>
+
+
1 Synopsis
+          #include <math.h>
            double atan(double x);
            float atanf(float x);
            long double atanl(long double x);
     Description
 

-
-
+
 
2   The atan functions compute the principal value of the arc tangent of x.
     Returns
 

-
-
+
 
3   The atan functions return arctan x in the interval [- /2, + /2] radians.
 

-
-
+
 

 
7.12.4.4 [The atan2 functions]

-

-
-
-
1          #include <math.h>
+
+
1 Synopsis
+          #include <math.h>
            double atan2(double y, double x);
            float atan2f(float y, float x);
            long double atan2l(long double y, long double x);
     Description
 

-
-
+
 
2   The atan2 functions compute the value of the arc tangent of y/x, using the signs of both
     arguments to determine the quadrant of the return value. A domain error may occur if
     both arguments are zero.
     Returns
 

-
-
+
 
3   The atan2 functions return arctan y/x in the interval [- , + ] radians.
 

-
-
+
 

 
7.12.4.5 [The cos functions]

-

-
-
-
1          #include <math.h>
+
+
1 Synopsis
+          #include <math.h>
            double cos(double x);
            float cosf(float x);
            long double cosl(long double x);
     Description
 

-
-
+
 
2   The cos functions compute the cosine of x (measured in radians).
     Returns
 

-
-
+
 
3   The cos functions return cos x.
 

-
-
+
 

 
7.12.4.6 [The sin functions]

-

-
-
-
1          #include <math.h>
+
+
1 Synopsis
+          #include <math.h>
            double sin(double x);
            float sinf(float x);
            long double sinl(long double x);
     Description
 

-
-
+
 
2   The sin functions compute the sine of x (measured in radians).
     Returns
 

-
-
+
 
3   The sin functions return sin x.
 

-
-
+
 

 
7.12.4.7 [The tan functions]

-

-
-
-
1          #include <math.h>
+
+
1 Synopsis
+          #include <math.h>
            double tan(double x);
            float tanf(float x);
            long double tanl(long double x);
     Description
 

-
-
+
 
2   The tan functions return the tangent of x (measured in radians).
     Returns
 

-
-
+
 
3   The tan functions return tan x.
 
 

-
-
+
 

 
7.12.5 [Hyperbolic functions]

-
 Hyperbolic functions
-

-
-
+
 

 
7.12.5.1 [The acosh functions]

-

-
-
-
1          #include <math.h>
+
+
1 Synopsis
+          #include <math.h>
            double acosh(double x);
            float acoshf(float x);
            long double acoshl(long double x);
     Description
 

-
-
+
 
2   The acosh functions compute the (nonnegative) arc hyperbolic cosine of x. A domain
     error occurs for arguments less than 1.
     Returns
 

-
-
+
 
3   The acosh functions return arcosh x in the interval [0, +].
 

-
-
+
 

 
7.12.5.2 [The asinh functions]

-

-
-
-
1          #include <math.h>
+
+
1 Synopsis
+          #include <math.h>
            double asinh(double x);
            float asinhf(float x);
            long double asinhl(long double x);
     Description
 

-
-
+
 
2   The asinh functions compute the arc hyperbolic sine of x.
     Returns
 

-
-
+
 
3   The asinh functions return arsinh x.
 

-
-
+
 

 
7.12.5.3 [The atanh functions]

-

-
-
-
1          #include <math.h>
+
+
1 Synopsis
+          #include <math.h>
            double atanh(double x);
            float atanhf(float x);
            long double atanhl(long double x);
     Description
 

-
-
+
 
2   The atanh functions compute the arc hyperbolic tangent of x. A domain error occurs
     for arguments not in the interval [-1, +1]. A range error may occur if the argument
     equals -1 or +1.
     Returns
 

-
-
+
 
3   The atanh functions return artanh x.
 

-
-
+
 

 
7.12.5.4 [The cosh functions]

-

-
-
-
1          #include <math.h>
+
+
1 Synopsis
+          #include <math.h>
            double cosh(double x);
            float coshf(float x);
            long double coshl(long double x);
     Description
 

-
-
+
 
2   The cosh functions compute the hyperbolic cosine of x. A range error occurs if the
     magnitude of x is too large.
     Returns
 

-
-
+
 
3   The cosh functions return cosh x.
 

-
-
+
 

 
7.12.5.5 [The sinh functions]

-

-
-
-
1          #include <math.h>
+
+
1 Synopsis
+          #include <math.h>
            double sinh(double x);
            float sinhf(float x);
            long double sinhl(long double x);
     Description
 

-
-
+
 
2   The sinh functions compute the hyperbolic sine of x. A range error occurs if the
     magnitude of x is too large.
     Returns
 

-
-
+
 
3   The sinh functions return sinh x.
 

-
-
+
 

 
7.12.5.6 [The tanh functions]

-

-
-
-
1          #include <math.h>
+
+
1 Synopsis
+          #include <math.h>
            double tanh(double x);
            float tanhf(float x);
            long double tanhl(long double x);
     Description
 

-
-
+
 
2   The tanh functions compute the hyperbolic tangent of x.
     Returns
 

-
-
+
 
3   The tanh functions return tanh x.
 

-
-
+
 

 
7.12.6 [Exponential and logarithmic functions]

-
 Exponential and logarithmic functions
-

-
-
+
 

 
7.12.6.1 [The exp functions]

-

-
-
-
1          #include <math.h>
+
+
1 Synopsis
+          #include <math.h>
            double exp(double x);
            float expf(float x);
            long double expl(long double x);
     Description
 

-
-
+
 
2   The exp functions compute the base-e exponential of x. A range error occurs if the
     magnitude of x is too large.
     Returns
 

-
-
+
 
3   The exp functions return ex .
 

-
-
+
 

 
7.12.6.2 [The exp2 functions]

-

-
-
-
1          #include <math.h>
+
+
1 Synopsis
+          #include <math.h>
            double exp2(double x);
            float exp2f(float x);
            long double exp2l(long double x);
     Description
 

-
-
+
 
2   The exp2 functions compute the base-2 exponential of x. A range error occurs if the
     magnitude of x is too large.
     Returns
 

-
-
+
 
3   The exp2 functions return 2x .
 

-
-
+
 

 
7.12.6.3 [The expm1 functions]

-

-
-
-
1          #include <math.h>
+
+
1 Synopsis
+          #include <math.h>
            double expm1(double x);
            float expm1f(float x);
            long double expm1l(long double x);
 
     Description
 

-
-
+
 
2   The expm1 functions compute the base-e exponential of the argument, minus 1. A range
-    error occurs if x is too large.208)
+    error occurs if x is too large.[208]
     Returns
 

-
 
 
Footnote 208) For small magnitude x, expm1(x) is expected to be more accurate than exp(x) - 1.
+    Returns
 

 
-
+
 
3   The expm1 functions return ex - 1.
 

-
-
+
 

 
7.12.6.4 [The frexp functions]

-

-
-
-
1           #include <math.h>
+
+
1 Synopsis
+           #include <math.h>
             double frexp(double value, int *exp);
             float frexpf(float value, int *exp);
             long double frexpl(long double value, int *exp);
     Description
 

-
-
+
 
2   The frexp functions break a floating-point number into a normalized fraction and an
     integral power of 2. They store the integer in the int object pointed to by exp.
     Returns
 

-
-
+
 
3   If value is not a floating-point number, the results are unspecified. Otherwise, the
-    frexp functions return the value x, such that x has a magnitude in the interval [1/2, 1) or
-    zero, and value equals x × 2*exp . If value is zero, both parts of the result are zero.
+    frexp functions return the value x, such that x has a magnitude in the interval [1/2, [1] or
+    zero, and value equals x \xD7 2*exp . If value is zero, both parts of the result are zero.
 

-
 
 
Footnote 1) This International Standard is designed to promote the portability of C programs among a variety of
          data-processing systems. It is intended for use by implementors and programmers.
+    -- all minimal requirements of a data-processing system that is capable of supporting a
+       conforming implementation.
 

 
-
+
 

 
7.12.6.5 [The ilogb functions]

-

-
-
-
1           #include <math.h>
+
+
1 Synopsis
+           #include <math.h>
             int ilogb(double x);
             int ilogbf(float x);
             int ilogbl(long double x);
     Description
 

-
-
+
 
2   The ilogb functions extract the exponent of x as a signed int value. If x is zero they
     compute the value FP_ILOGB0; if x is infinite they compute the value INT_MAX; if x is
     a NaN they compute the value FP_ILOGBNAN; otherwise, they are equivalent to calling
     the corresponding logb function and casting the returned value to type int. A domain
     error or range error may occur if x is zero, infinite, or NaN. If the correct value is outside
     the range of the return type, the numeric result is unspecified.
-    Returns
 

-
-
+
 
3   The ilogb functions return the exponent of x as a signed int value.
-    Forward references: the logb functions (7.12.6.11).
+    Forward references: the logb functions (7.12.6.11).
 

-
-
+
 

 
7.12.6.6 [The ldexp functions]

-

-
-
-
1          #include <math.h>
+
+
1 Synopsis
+          #include <math.h>
            double ldexp(double x, int exp);
            float ldexpf(float x, int exp);
            long double ldexpl(long double x, int exp);
     Description
 

-
-
+
 
2   The ldexp functions multiply a floating-point number by an integral power of 2. A
     range error may occur.
     Returns
 

-
-
-
3   The ldexp functions return x × 2exp .
+
+
3   The ldexp functions return x \xD7 2exp .
 

-
-
+
 

 
7.12.6.7 [The log functions]

-

-
-
-
1          #include <math.h>
+
+
1 Synopsis
+          #include <math.h>
            double log(double x);
            float logf(float x);
            long double logl(long double x);
     Description
 

-
-
+
 
2   The log functions compute the base-e (natural) logarithm of x. A domain error occurs if
     the argument is negative. A range error may occur if the argument is zero.
     Returns
 

-
-
+
 
3   The log functions return loge x.
 

-
-
+
 

 
7.12.6.8 [The log10 functions]

-

-
-
-
1          #include <math.h>
+
+
1 Synopsis
+          #include <math.h>
            double log10(double x);
            float log10f(float x);
            long double log10l(long double x);
 
     Description
 

-
-
+
 
2   The log10 functions compute the base-10 (common) logarithm of x. A domain error
     occurs if the argument is negative. A range error may occur if the argument is zero.
     Returns
 

-
-
+
 
3   The log10 functions return log10 x.
 

-
-
+
 

 
7.12.6.9 [The log1p functions]

-

-
-
-
1           #include <math.h>
+
+
1 Synopsis
+           #include <math.h>
             double log1p(double x);
             float log1pf(float x);
             long double log1pl(long double x);
     Description
 

-
-
-
2   The log1p functions compute the base-e (natural) logarithm of 1 plus the argument.209)
+
+
2   The log1p functions compute the base-e (natural) logarithm of 1 plus the argument.[209]
     A domain error occurs if the argument is less than -1. A range error may occur if the
     argument equals -1.
     Returns
 

-
 
 
Footnote 209) For small magnitude x, log1p(x) is expected to be more accurate than log(1 + x).
 

 
-
+
 
3   The log1p functions return loge (1 + x).
 

-
-
+
 

 
7.12.6.10 [The log2 functions]

-

-
-
-
1           #include <math.h>
+
+
1 Synopsis
+           #include <math.h>
             double log2(double x);
             float log2f(float x);
             long double log2l(long double x);
     Description
 

-
-
+
 
2   The log2 functions compute the base-2 logarithm of x. A domain error occurs if the
     argument is less than zero. A range error may occur if the argument is zero.
     Returns
 

-
-
+
 
3   The log2 functions return log2 x.
 

-
-
+
 

 
7.12.6.11 [The logb functions]

-

-
-
-
1          #include <math.h>
+
+
1 Synopsis
+          #include <math.h>
            double logb(double x);
            float logbf(float x);
            long double logbl(long double x);
     Description
 

-
-
+
 
2   The logb functions extract the exponent of x, as a signed integer value in floating-point
     format. If x is subnormal it is treated as though it were normalized; thus, for positive
     finite x,
-          1  x × FLT_RADIX-logb(x) < FLT_RADIX
+          1  x \xD7 FLT_RADIX-logb(x) < FLT_RADIX
     A domain error or range error may occur if the argument is zero.
     Returns
 

-
-
+
 
3   The logb functions return the signed exponent of x.
 

-
-
+
 

 
7.12.6.12 [The modf functions]

-

-
-
-
1          #include <math.h>
+
+
1 Synopsis
+          #include <math.h>
            double modf(double value, double *iptr);
            float modff(float value, float *iptr);
            long double modfl(long double value, long double *iptr);
     Description
 

-
-
+
 
2   The modf functions break the argument value into integral and fractional parts, each of
     which has the same type and sign as the argument. They store the integral part (in
     floating-point format) in the object pointed to by iptr.
     Returns
 

-
-
+
 
3   The modf functions return the signed fractional part of value.
 
 

-
-
+
 

 
7.12.6.13 [The scalbn and scalbln functions]

-

-
-
-
1          #include <math.h>
+
+
1 Synopsis
+          #include <math.h>
            double scalbn(double x, int n);
            float scalbnf(float x, int n);
            long double scalbnl(long double x, int n);
@@ -12951,357 +11259,291 @@ char int_p_sep_by_space
            long double scalblnl(long double x, long int n);
     Description
 

-
-
-
2   The scalbn and scalbln functions compute x × FLT_RADIXn efficiently, not
+
+
2   The scalbn and scalbln functions compute x \xD7 FLT_RADIXn efficiently, not
     normally by computing FLT_RADIXn explicitly. A range error may occur.
     Returns
 

-
-
-
3   The scalbn and scalbln functions return x × FLT_RADIXn .
+
+
3   The scalbn and scalbln functions return x \xD7 FLT_RADIXn .
 

-
-
+
 

 
7.12.7 [Power and absolute-value functions]

-
 Power and absolute-value functions
-

-
-
+
 

 
7.12.7.1 [The cbrt functions]

-

-
-
-
1          #include <math.h>
+
+
1 Synopsis
+          #include <math.h>
            double cbrt(double x);
            float cbrtf(float x);
            long double cbrtl(long double x);
     Description
 

-
-
+
 
2   The cbrt functions compute the real cube root of x.
     Returns
 

-
-
+
 
3   The cbrt functions return x1/3 .
 

-
-
+
 

 
7.12.7.2 [The fabs functions]

-

-
-
-
1          #include <math.h>
+
+
1 Synopsis
+          #include <math.h>
            double fabs(double x);
            float fabsf(float x);
            long double fabsl(long double x);
     Description
 

-
-
+
 
2   The fabs functions compute the absolute value of a floating-point number x.
     Returns
 

-
-
+
 
3   The fabs functions return | x |.
 

-
-
+
 

 
7.12.7.3 [The hypot functions]

-

-
-
-
1          #include <math.h>
+
+
1 Synopsis
+          #include <math.h>
            double hypot(double x, double y);
            float hypotf(float x, float y);
            long double hypotl(long double x, long double y);
     Description
 

-
-
+
 
2   The hypot functions compute the square root of the sum of the squares of x and y,
     without undue overflow or underflow. A range error may occur.
 

-
-
+
 
3   Returns
 

-
-
+
 
4   The hypot functions return  x2 + y2 .
 

-
-
+
 

 
7.12.7.4 [The pow functions]

-

-
-
-
1          #include <math.h>
+
+
1 Synopsis
+          #include <math.h>
            double pow(double x, double y);
            float powf(float x, float y);
            long double powl(long double x, long double y);
     Description
 

-
-
+
 
2   The pow functions compute x raised to the power y. A domain error occurs if x is finite
     and negative and y is finite and not an integer value. A range error may occur. A domain
     error may occur if x is zero and y is zero. A domain error or range error may occur if x
     is zero and y is less than zero.
     Returns
 

-
-
+
 
3   The pow functions return xy .
 

-
-
+
 

 
7.12.7.5 [The sqrt functions]

-

-
-
-
1          #include <math.h>
+
+
1 Synopsis
+          #include <math.h>
            double sqrt(double x);
            float sqrtf(float x);
            long double sqrtl(long double x);
 
     Description
 

-
-
+
 
2   The sqrt functions compute the nonnegative square root of x. A domain error occurs if
     the argument is less than zero.
     Returns
 

-
-
+
 
3   The sqrt functions return x.
-                              
+
 

-
-
+
 

 
7.12.8 [Error and gamma functions]

-
 Error and gamma functions
-

-
-
+
 

 
7.12.8.1 [The erf functions]

-

-
-
-
1          #include <math.h>
+
+
1 Synopsis
+          #include <math.h>
            double erf(double x);
            float erff(float x);
            long double erfl(long double x);
     Description
 

-
-
+
 
2   The erf functions compute the error function of x.
     Returns
                                        2      x
-                                           
+
 

-
-
+
 
3     The erf functions return erf x =              e-t dt .
                                                      2
                                            0
 
 

-
-
+
 

 
7.12.8.2 [The erfc functions]

-

-
-
-
1          #include <math.h>
+
+
1 Synopsis
+          #include <math.h>
            double erfc(double x);
            float erfcf(float x);
            long double erfcl(long double x);
     Description
 

-
-
+
 
2   The erfc functions compute the complementary error function of x. A range error
     occurs if x is too large.
     Returns
-                                                             2      
-                                                                 
+                                                             2
+
 

-
-
+
 
3     The erfc functions return erfc x = 1 - erf x =                     e-t dt .
                                                                           2
                                                                  x
 
 

-
-
+
 

 
7.12.8.3 [The lgamma functions]

-

-
-
-
1          #include <math.h>
+
+
1 Synopsis
+          #include <math.h>
            double lgamma(double x);
            float lgammaf(float x);
            long double lgammal(long double x);
     Description
 

-
-
+
 
2   The lgamma functions compute the natural logarithm of the absolute value of gamma of
     x. A range error occurs if x is too large. A range error may occur if x is a negative
     integer or zero.
     Returns
 

-
-
+
 
3   The lgamma functions return loge | (x) |.
 

-
-
+
 

 
7.12.8.4 [The tgamma functions]

-

-
-
-
1          #include <math.h>
+
+
1 Synopsis
+          #include <math.h>
            double tgamma(double x);
            float tgammaf(float x);
            long double tgammal(long double x);
     Description
 

-
-
+
 
2   The tgamma functions compute the gamma function of x. A domain error or range error
     may occur if x is a negative integer or zero. A range error may occur if the magnitude of
     x is too large or too small.
     Returns
 

-
-
+
 
3   The tgamma functions return (x).
 

-
-
+
 

 
7.12.9 [Nearest integer functions]

-
 Nearest integer functions
-

-
-
+
 

 
7.12.9.1 [The ceil functions]

-

-
-
-
1          #include <math.h>
+
+
1 Synopsis
+          #include <math.h>
            double ceil(double x);
            float ceilf(float x);
            long double ceill(long double x);
     Description
 

-
-
+
 
2   The ceil functions compute the smallest integer value not less than x.
     Returns
 

-
-
+
 
3   The ceil functions return x, expressed as a floating-point number.
 

-
-
+
 

 
7.12.9.2 [The floor functions]

-

-
-
-
1          #include <math.h>
+
+
1 Synopsis
+          #include <math.h>
            double floor(double x);
            float floorf(float x);
            long double floorl(long double x);
     Description
 

-
-
+
 
2   The floor functions compute the largest integer value not greater than x.
     Returns
 

-
-
+
 
3   The floor functions return x, expressed as a floating-point number.
 

-
-
+
 

 
7.12.9.3 [The nearbyint functions]

-

-
-
-
1          #include <math.h>
+
+
1 Synopsis
+          #include <math.h>
            double nearbyint(double x);
            float nearbyintf(float x);
            long double nearbyintl(long double x);
     Description
 

-
-
+
 
2   The nearbyint functions round their argument to an integer value in floating-point
     format, using the current rounding direction and without raising the ``inexact'' floating-
     point exception.
     Returns
 

-
-
+
 
3   The nearbyint functions return the rounded integer value.
 

-
-
+
 

 
7.12.9.4 [The rint functions]

-

-
-
-
1          #include <math.h>
+
+
1 Synopsis
+          #include <math.h>
            double rint(double x);
            float rintf(float x);
            long double rintl(long double x);
     Description
 

-
-
-
2   The rint functions differ from the nearbyint functions (7.12.9.3) only in that the
+
+
2   The rint functions differ from the nearbyint functions (7.12.9.3) only in that the
     rint functions may raise the ``inexact'' floating-point exception if the result differs in
     value from the argument.
     Returns
 

-
-
+
 
3   The rint functions return the rounded integer value.
 

-
-
+
 

 
7.12.9.5 [The lrint and llrint functions]

-

-
-
-
1          #include <math.h>
+
+
1 Synopsis
+          #include <math.h>
            long int lrint(double x);
            long int lrintf(float x);
            long int lrintl(long double x);
@@ -13310,51 +11552,43 @@ char int_p_sep_by_space
            long long int llrintl(long double x);
     Description
 

-
-
+
 
2   The lrint and llrint functions round their argument to the nearest integer value,
     rounding according to the current rounding direction. If the rounded value is outside the
     range of the return type, the numeric result is unspecified and a domain error or range
-    error may occur.                                                                          
+    error may occur.
     Returns
 

-
-
+
 
3   The lrint and llrint functions return the rounded integer value.
 

-
-
+
 

 
7.12.9.6 [The round functions]

-

-
-
-
1          #include <math.h>
+
+
1 Synopsis
+          #include <math.h>
            double round(double x);
            float roundf(float x);
            long double roundl(long double x);
     Description
 

-
-
+
 
2   The round functions round their argument to the nearest integer value in floating-point
     format, rounding halfway cases away from zero, regardless of the current rounding
     direction.
     Returns
 

-
-
+
 
3   The round functions return the rounded integer value.
 
 

-
-
+
 

 
7.12.9.7 [The lround and llround functions]

-

-
-
-
1          #include <math.h>
+
+
1 Synopsis
+          #include <math.h>
            long int lround(double x);
            long int lroundf(float x);
            long int lroundl(long double x);
@@ -13363,92 +11597,75 @@ char int_p_sep_by_space
            long long int llroundl(long double x);
     Description
 

-
-
+
 
2   The lround and llround functions round their argument to the nearest integer value,
     rounding halfway cases away from zero, regardless of the current rounding direction. If
     the rounded value is outside the range of the return type, the numeric result is unspecified
     and a domain error or range error may occur.
     Returns
 

-
-
+
 
3   The lround and llround functions return the rounded integer value.
 

-
-
+
 

 
7.12.9.8 [The trunc functions]

-

-
-
-
1          #include <math.h>
+
+
1 Synopsis
+          #include <math.h>
            double trunc(double x);
            float truncf(float x);
            long double truncl(long double x);
     Description
 

-
-
+
 
2   The trunc functions round their argument to the integer value, in floating format,
     nearest to but no larger in magnitude than the argument.
     Returns
 

-
-
+
 
3   The trunc functions return the truncated integer value.
 
 

-
-
+
 

 
7.12.10 [Remainder functions]

-
 Remainder functions
-

-
-
+
 

 
7.12.10.1 [The fmod functions]

-

-
-
-
1            #include <math.h>
+
+
1 Synopsis
+            #include <math.h>
              double fmod(double x, double y);
              float fmodf(float x, float y);
              long double fmodl(long double x, long double y);
     Description
 

-
-
+
 
2   The fmod functions compute the floating-point remainder of x/y.
     Returns
 

-
-
+
 
3   The fmod functions return the value x - ny, for some integer n such that, if y is nonzero,
     the result has the same sign as x and magnitude less than the magnitude of y. If y is zero,
     whether a domain error occurs or the fmod functions return zero is implementation-
     defined.
 

-
-
+
 

 
7.12.10.2 [The remainder functions]

-

-
-
-
1            #include <math.h>
+
+
1 Synopsis
+            #include <math.h>
              double remainder(double x, double y);
              float remainderf(float x, float y);
              long double remainderl(long double x, long double y);
     Description
 

-
-
-
2   The remainder functions compute the remainder x REM y required by IEC 60559.210)
+
+
2   The remainder functions compute the remainder x REM y required by IEC 60559.[210]
     Returns
 

-
 
 
Footnote 210) ``When y  0, the remainder r = x REM y is defined regardless of the rounding mode by the
          mathematical relation r = x - ny , where n is the integer nearest the exact value of x / y ; whenever
@@ -13456,85 +11673,71 @@ char int_p_sep_by_space
          x .'' This definition is applicable for all implementations.
 

 
-
+
 
3   The remainder functions return x REM y. If y is zero, whether a domain error occurs
     or the functions return zero is implementation defined.
 

-
-
+
 

 
7.12.10.3 [The remquo functions]

-

-
-
-
1          #include <math.h>
+
+
1 Synopsis
+          #include <math.h>
            double remquo(double x, double y, int *quo);
            float remquof(float x, float y, int *quo);
            long double remquol(long double x, long double y,
                 int *quo);
     Description
 

-
-
+
 
2   The remquo functions compute the same remainder as the remainder functions. In
     the object pointed to by quo they store a value whose sign is the sign of x/y and whose
     magnitude is congruent modulo 2n to the magnitude of the integral quotient of x/y, where
     n is an implementation-defined integer greater than or equal to 3.
     Returns
 

-
-
+
 
3   The remquo functions return x REM y. If y is zero, the value stored in the object
     pointed to by quo is unspecified and whether a domain error occurs or the functions
     return zero is implementation defined.
 

-
-
+
 

 
7.12.11 [Manipulation functions]

-
 Manipulation functions
-

-
-
+
 

 
7.12.11.1 [The copysign functions]

-

-
-
-
1          #include <math.h>
+
+
1 Synopsis
+          #include <math.h>
            double copysign(double x, double y);
            float copysignf(float x, float y);
            long double copysignl(long double x, long double y);
     Description
 

-
-
+
 
2   The copysign functions produce a value with the magnitude of x and the sign of y.
     They produce a NaN (with the sign of y) if x is a NaN. On implementations that
     represent a signed zero but do not treat negative zero consistently in arithmetic
     operations, the copysign functions regard the sign of zero as positive.
     Returns
 

-
-
+
 
3   The copysign functions return a value with the magnitude of x and the sign of y.
 
 

-
-
+
 

 
7.12.11.2 [The nan functions]

-

-
-
-
1           #include <math.h>
+
+
1 Synopsis
+           #include <math.h>
             double nan(const char *tagp);
             float nanf(const char *tagp);
             long double nanl(const char *tagp);
     Description
 

-
-
+
 
2   The call nan("n-char-sequence") is equivalent to strtod("NAN(n-char-
     sequence)",     (char**)       NULL); the call nan("") is equivalent to
     strtod("NAN()", (char**) NULL). If tagp does not point to an n-char
@@ -13543,313 +11746,261 @@ char int_p_sep_by_space
     and strtold.
     Returns
 

-
-
+
 
3   The nan functions return a quiet NaN, if available, with content indicated through tagp.
     If the implementation does not support quiet NaNs, the functions return zero.
-    Forward references: the strtod, strtof, and strtold functions (7.20.1.3).
+    Forward references: the strtod, strtof, and strtold functions (7.20.1.3).
 

-
-
+
 

 
7.12.11.3 [The nextafter functions]

-

-
-
-
1           #include <math.h>
+
+
1 Synopsis
+           #include <math.h>
             double nextafter(double x, double y);
             float nextafterf(float x, float y);
             long double nextafterl(long double x, long double y);
     Description
 

-
-
+
 
2   The nextafter functions determine the next representable value, in the type of the
     function, after x in the direction of y, where x and y are first converted to the type of the
-    function.211) The nextafter functions return y if x equals y. A range error may occur
+    function.[211] The nextafter functions return y if x equals y. A range error may occur
     if the magnitude of x is the largest finite value representable in the type and the result is
     infinite or not representable in the type.
     Returns
 

-
 
 
Footnote 211) The argument values are converted to the type of the function, even by a macro implementation of the
          function.
 

 
-
+
 
3   The nextafter functions return the next representable value in the specified format
     after x in the direction of y.
 

-
-
+
 

 
7.12.11.4 [The nexttoward functions]

-

-
-
-
1           #include <math.h>
+
+
1 Synopsis
+           #include <math.h>
             double nexttoward(double x, long double y);
             float nexttowardf(float x, long double y);
             long double nexttowardl(long double x, long double y);
     Description
 

-
-
+
 
2   The nexttoward functions are equivalent to the nextafter functions except that the
     second parameter has type long double and the functions return y converted to the
-    type of the function if x equals y.212)
+    type of the function if x equals y.[212]
 

-
 
 
Footnote 212) The result of the nexttoward functions is determined in the type of the function, without loss of
          range or precision in a floating second argument.
+    Description
 

 
-
+
 

 
7.12.12 [Maximum, minimum, and positive difference functions]

-
 Maximum, minimum, and positive difference functions
-

-
-
+
 

 
7.12.12.1 [The fdim functions]

-

-
-
-
1           #include <math.h>
+
+
1 Synopsis
+           #include <math.h>
             double fdim(double x, double y);
             float fdimf(float x, float y);
             long double fdiml(long double x, long double y);
     Description
 

-
-
+
 
2   The fdim functions determine the positive difference between their arguments:
           x - y if x > y
-          
+
           +0      if x  y
     A range error may occur.
     Returns
 

-
-
+
 
3   The fdim functions return the positive difference value.
 

-
-
+
 

 
7.12.12.2 [The fmax functions]

-

-
-
-
1           #include <math.h>
+
+
1 Synopsis
+           #include <math.h>
             double fmax(double x, double y);
             float fmaxf(float x, float y);
             long double fmaxl(long double x, long double y);
-    Description
 

-
-
-
2   The fmax functions determine the maximum numeric value of their arguments.213)
+
+
2   The fmax functions determine the maximum numeric value of their arguments.[213]
     Returns
 

-
 
 
Footnote 213) NaN arguments are treated as missing data: if one argument is a NaN and the other numeric, then the
-         fmax functions choose the numeric value. See F.9.9.2.
+         fmax functions choose the numeric value. See F.9.9.2.
 

 
-
+
 
3   The fmax functions return the maximum numeric value of their arguments.
 

-
-
+
 

 
7.12.12.3 [The fmin functions]

-

-
-
-
1           #include <math.h>
+
+
1 Synopsis
+           #include <math.h>
             double fmin(double x, double y);
             float fminf(float x, float y);
             long double fminl(long double x, long double y);
     Description
 

-
-
-
2   The fmin functions determine the minimum numeric value of their arguments.214)
+
+
2   The fmin functions determine the minimum numeric value of their arguments.[214]
     Returns
 

-
 
 
Footnote 214) The fmin functions are analogous to the fmax functions in their treatment of NaNs.
 

 
-
+
 
3   The fmin functions return the minimum numeric value of their arguments.
 

-
-
+
 

 
7.12.13 [Floating multiply-add]

-
 Floating multiply-add
-

-
-
+
 

 
7.12.13.1 [The fma functions]

-

-
-
-
1           #include <math.h>
+
+
1 Synopsis
+           #include <math.h>
             double fma(double x, double y, double z);
             float fmaf(float x, float y, float z);
             long double fmal(long double x, long double y,
                  long double z);
     Description
 

-
-
-
2   The fma functions compute (x × y) + z, rounded as one ternary operation: they compute
+
+
2   The fma functions compute (x \xD7 y) + z, rounded as one ternary operation: they compute
     the value (as if) to infinite precision and round once to the result format, according to the
     current rounding mode. A range error may occur.
     Returns
 

-
-
-
3   The fma functions return (x × y) + z, rounded as one ternary operation.
+
+
3   The fma functions return (x \xD7 y) + z, rounded as one ternary operation.
 

-
-
+
 

 
7.12.14 [Comparison macros]

-

-
-
+
 
1   The relational and equality operators support the usual mathematical relationships
     between numeric values. For any ordered pair of numeric values exactly one of the
     relationships -- less, greater , and equal -- is true. Relational operators may raise the
     ``invalid'' floating-point exception when argument values are NaNs. For a NaN and a
-    numeric value, or for two NaNs, just the unordered relationship is true.215) The following
+    numeric value, or for two NaNs, just the unordered relationship is true.[215] The following
     subclauses provide macros that are quiet (non floating-point exception raising) versions
     of the relational operators, and other comparison macros that facilitate writing efficient
     code that accounts for NaNs without suffering the ``invalid'' floating-point exception. In
     the synopses in this subclause, real-floating indicates that the argument shall be an
     expression of real floating type.
 

-
 
 
Footnote 215) IEC 60559 requires that the built-in relational operators raise the ``invalid'' floating-point exception if
          the operands compare unordered, as an error indicator for programs written without consideration of
          NaNs; the result in these cases is false.
+    Returns
 

 
-
+
 

 
7.12.14.1 [The isgreater macro]

-

-
-
-
1            #include <math.h>
+
+
1 Synopsis
+            #include <math.h>
              int isgreater(real-floating x, real-floating y);
     Description
 

-
-
+
 
2   The isgreater macro determines whether its first argument is greater than its second
     argument. The value of isgreater(x, y) is always equal to (x) > (y); however,
     unlike (x) > (y), isgreater(x, y) does not raise the ``invalid'' floating-point
     exception when x and y are unordered.
     Returns
 

-
-
+
 
3   The isgreater macro returns the value of (x) > (y).
 

-
-
+
 

 
7.12.14.2 [The isgreaterequal macro]

-

-
-
-
1            #include <math.h>
+
+
1 Synopsis
+            #include <math.h>
              int isgreaterequal(real-floating x, real-floating y);
     Description
 

-
-
+
 
2   The isgreaterequal macro determines whether its first argument is greater than or
     equal to its second argument. The value of isgreaterequal(x, y) is always equal
     to (x) >= (y); however, unlike (x) >= (y), isgreaterequal(x, y) does
     not raise the ``invalid'' floating-point exception when x and y are unordered.
-    Returns
 

-
-
+
 
3   The isgreaterequal macro returns the value of (x) >= (y).
 

-
-
+
 

 
7.12.14.3 [The isless macro]

-

-
-
-
1          #include <math.h>
+
+
1 Synopsis
+          #include <math.h>
            int isless(real-floating x, real-floating y);
     Description
 

-
-
+
 
2   The isless macro determines whether its first argument is less than its second
     argument. The value of isless(x, y) is always equal to (x) < (y); however,
     unlike (x) < (y), isless(x, y) does not raise the ``invalid'' floating-point
     exception when x and y are unordered.
     Returns
 

-
-
+
 
3   The isless macro returns the value of (x) < (y).
 

-
-
+
 

 
7.12.14.4 [The islessequal macro]

-

-
-
-
1          #include <math.h>
+
+
1 Synopsis
+          #include <math.h>
            int islessequal(real-floating x, real-floating y);
     Description
 

-
-
+
 
2   The islessequal macro determines whether its first argument is less than or equal to
     its second argument. The value of islessequal(x, y) is always equal to
     (x) <= (y); however, unlike (x) <= (y), islessequal(x, y) does not raise
     the ``invalid'' floating-point exception when x and y are unordered.
     Returns
 

-
-
+
 
3   The islessequal macro returns the value of (x) <= (y).
 

-
-
+
 

 
7.12.14.5 [The islessgreater macro]

-

-
-
-
1          #include <math.h>
+
+
1 Synopsis
+          #include <math.h>
            int islessgreater(real-floating x, real-floating y);
     Description
 

-
-
+
 
2   The islessgreater macro determines whether its first argument is less than or
     greater than its second argument. The islessgreater(x, y) macro is similar to
     (x) < (y) || (x) > (y); however, islessgreater(x, y) does not raise
@@ -13857,49 +12008,43 @@ char int_p_sep_by_space
     and y twice).
     Returns
 

-
-
+
 
3   The islessgreater macro returns the value of (x) < (y) || (x) > (y).
 

-
-
+
 

 
7.12.14.6 [The isunordered macro]

-

-
-
-
1         #include <math.h>
+
+
1 Synopsis
+         #include <math.h>
           int isunordered(real-floating x, real-floating y);
     Description
 

-
-
+
 
2   The isunordered macro determines whether its arguments are unordered.
     Returns
 

-
-
+
 
3   The isunordered macro returns 1 if its arguments are unordered and 0 otherwise.
 
 

-
-
+
 

-
7.13 [Nonlocal jumps ]

-

-
-
+
7.13 [Nonlocal jumps <setjmp.h>]

+
 
1   The header <setjmp.h> defines the macro setjmp, and declares one function and
-    one type, for bypassing the normal function call and return discipline.216)
+    one type, for bypassing the normal function call and return discipline.[216]
 

-
 
 
Footnote 216) These functions are useful for dealing with unusual conditions encountered in a low-level function of
          a program.
         expression of a selection or iteration statement;
+    -- the operand of a unary ! operator with the resulting expression being the entire
+       controlling expression of a selection or iteration statement; or
+    -- the entire expression of an expression statement (possibly cast to void).
 

 
-
+
 
2   The type declared is
             jmp_buf
     which is an array type suitable for holding the information needed to restore a calling
@@ -13909,90 +12054,70 @@ char int_p_sep_by_space
     floating-point status flags, of open files, or of any other component of the abstract
     machine.
 

-
-
+
 
3   It is unspecified whether setjmp is a macro or an identifier declared with external
     linkage. If a macro definition is suppressed in order to access an actual function, or a
     program defines an external identifier with the name setjmp, the behavior is undefined.
 

-
-
+
 

 
7.13.1 [Save calling environment]

-
 Save calling environment
-

-
-
+
 

 
7.13.1.1 [The setjmp macro]

-

-
-
-
1           #include <setjmp.h>
+
+
1 Synopsis
+           #include <setjmp.h>
             int setjmp(jmp_buf env);
     Description
 

-
-
+
 
2   The setjmp macro saves its calling environment in its jmp_buf argument for later use
     by the longjmp function.
     Returns
 

-
-
+
 
3   If the return is from a direct invocation, the setjmp macro returns the value zero. If the
     return is from a call to the longjmp function, the setjmp macro returns a nonzero
     value.
     Environmental limits
 

-
-
+
 
4   An invocation of the setjmp macro shall appear only in one of the following contexts:
     -- the entire controlling expression of a selection or iteration statement;
     -- one operand of a relational or equality operator with the other operand an integer
        constant expression, with the resulting expression being the entire controlling
-    -- the operand of a unary ! operator with the resulting expression being the entire
-       controlling expression of a selection or iteration statement; or
-    -- the entire expression of an expression statement (possibly cast to void).
 

-
-
+
 
5   If the invocation appears in any other context, the behavior is undefined.
 

-
-
+
 

 
7.13.2 [Restore calling environment]

-
 Restore calling environment
-

-
-
+
 

 
7.13.2.1 [The longjmp function]

-

-
-
-
1            #include <setjmp.h>
+
+
1 Synopsis
+            #include <setjmp.h>
              void longjmp(jmp_buf env, int val);
     Description
 

-
-
+
 
2   The longjmp function restores the environment saved by the most recent invocation of
     the setjmp macro in the same invocation of the program with the corresponding
     jmp_buf argument. If there has been no such invocation, or if the function containing
-    the invocation of the setjmp macro has terminated execution217) in the interim, or if the
+    the invocation of the setjmp macro has terminated execution[217] in the interim, or if the
     invocation of the setjmp macro was within the scope of an identifier with variably
     modified type and execution has left that scope in the interim, the behavior is undefined.
 

-
 
 
Footnote 217) For example, by executing a return statement or because another longjmp call has caused a
          transfer to a setjmp invocation in a function earlier in the set of nested calls.
 

 
-
-
3   All accessible objects have values, and all other components of the abstract machine218)
+
+
3   All accessible objects have values, and all other components of the abstract machine[218]
     have state, as of the time the longjmp function was called, except that the values of
     objects of automatic storage duration that are local to the function containing the
     invocation of the corresponding setjmp macro that do not have volatile-qualified type
@@ -14000,21 +12125,8 @@ char int_p_sep_by_space
     indeterminate.
     Returns
 

-
 
 
Footnote 218) This includes, but is not limited to, the floating-point status flags and the state of open files.
-

-
-
-
4   After longjmp is completed, program execution continues as if the corresponding
-    invocation of the setjmp macro had just returned the value specified by val. The
-    longjmp function cannot cause the setjmp macro to return the value 0; if val is 0,
-    the setjmp macro returns the value 1.
-

-
-
-
5   EXAMPLE The longjmp function that returns control back to the point of the setjmp invocation
-    might cause memory associated with a variable length array object to be squandered.
        #include <setjmp.h>
        jmp_buf buf;
        void g(int n);
@@ -14036,27 +12148,33 @@ char int_p_sep_by_space
              int b[n];          // b may remain allocated
              longjmp(buf, 2);   // might cause memory loss
        }
+

+
+
+
4   After longjmp is completed, program execution continues as if the corresponding
+    invocation of the setjmp macro had just returned the value specified by val. The
+    longjmp function cannot cause the setjmp macro to return the value 0; if val is 0,
+    the setjmp macro returns the value 1.
+

+
+
5   EXAMPLE The longjmp function that returns control back to the point of the setjmp invocation
+    might cause memory associated with a variable length array object to be squandered.
 
 

-
-
+
 

-
7.14 [Signal handling ]

-

-
-
+
7.14 [Signal handling <signal.h>]

+
 
1   The header <signal.h> declares a type and two functions and defines several macros,
     for handling various signals (conditions that may be reported during program execution).
 

-
-
+
 
2   The type defined is
              sig_atomic_t
     which is the (possibly volatile-qualified) integer type of an object that can be accessed as
     an atomic entity, even in the presence of asynchronous interrupts.
 

-
-
+
 
3   The macros defined are
              SIG_DFL
              SIG_ERR
@@ -14074,40 +12192,33 @@ char int_p_sep_by_space
              SIGSEGV an invalid access to storage
              SIGTERM a termination request sent to the program
 

-
-
+
 
4   An implementation need not generate any of these signals, except as a result of explicit
     calls to the raise function. Additional signals and pointers to undeclarable functions,
     with macro definitions beginning, respectively, with the letters SIG and an uppercase
-    letter or with SIG_ and an uppercase letter,219) may also be specified by the
+    letter or with SIG_ and an uppercase letter,[219] may also be specified by the
     implementation. The complete set of signals, their semantics, and their default handling
     is implementation-defined; all signal numbers shall be positive.
 

-
 
-
Footnote 219) See ``future library directions'' (7.26.9). The names of the signal numbers reflect the following terms
+
Footnote 219) See ``future library directions'' (7.26.9). The names of the signal numbers reflect the following terms
          (respectively): abort, floating-point exception, illegal instruction, interrupt, segmentation violation,
          and termination.
 

 
-
+
 

 
7.14.1 [Specify signal handling]

-
 Specify signal handling
-

-
-
+
 

 
7.14.1.1 [The signal function]

-

-
-
-
1            #include <signal.h>
+
+
1 Synopsis
+            #include <signal.h>
              void (*signal(int sig, void (*func)(int)))(int);
     Description
 

-
-
+
 
2   The signal function chooses one of three ways in which receipt of the signal number
     sig is to be subsequently handled. If the value of func is SIG_DFL, default handling
     for that signal will occur. If the value of func is SIG_IGN, the signal will be ignored.
@@ -14116,8 +12227,7 @@ char int_p_sep_by_space
     called by that invocation (other than functions in the standard library), is called a signal
     handler .
 

-
-
+
 
3   When a signal occurs and func points to a function, it is implementation-defined
     whether the equivalent of signal(sig, SIG_DFL); is executed or the
     implementation prevents some implementation-defined set of signals (at least including
@@ -14128,13 +12238,11 @@ char int_p_sep_by_space
     value corresponding to a computational exception, the behavior is undefined; otherwise
     the program will resume execution at the point it was interrupted.
 

-
-
+
 
4   If the signal occurs as the result of calling the abort or raise function, the signal
     handler shall not call the raise function.
 

-
-
+
 
5   If the signal occurs other than as the result of calling the abort or raise function, the
     behavior is undefined if the signal handler refers to any object with static storage duration
     other than by assigning a value to an object declared as volatile sig_atomic_t, or
@@ -14142,83 +12250,68 @@ char int_p_sep_by_space
     function, the _Exit function, or the signal function with the first argument equal to
     the signal number corresponding to the signal that caused the invocation of the handler.
     Furthermore, if such a call to the signal function results in a SIG_ERR return, the
-    value of errno is indeterminate.220)
+    value of errno is indeterminate.[220]
 

-
 
 
Footnote 220) If any signal is generated by an asynchronous signal handler, the behavior is undefined.
-

-
-
-
6   At program startup, the equivalent of
-             signal(sig, SIG_IGN);
     may be executed for some signals selected in an implementation-defined manner; the
     equivalent of
            signal(sig, SIG_DFL);
     is executed for all other signals defined by the implementation.
-

+

 
-
+
+
6   At program startup, the equivalent of
+             signal(sig, SIG_IGN);
+

+
 
7   The implementation shall behave as if no library function calls the signal function.
     Returns
 

-
-
+
 
8   If the request can be honored, the signal function returns the value of func for the
     most recent successful call to signal for the specified signal sig. Otherwise, a value of
     SIG_ERR is returned and a positive value is stored in errno.
-    Forward references: the abort function (7.20.4.1), the exit function (7.20.4.3), the
-    _Exit function (7.20.4.4).
+    Forward references: the abort function (7.20.4.1), the exit function (7.20.4.3), the
+    _Exit function (7.20.4.4).
 

-
-
+
 

 
7.14.2 [Send signal]

-
 Send signal
-

-
-
+
 

 
7.14.2.1 [The raise function]

-

-
-
-
1          #include <signal.h>
+
+
1 Synopsis
+          #include <signal.h>
            int raise(int sig);
     Description
 

-
-
-
2   The raise function carries out the actions described in 7.14.1.1 for the signal sig. If a
+
+
2   The raise function carries out the actions described in 7.14.1.1 for the signal sig. If a
     signal handler is called, the raise function shall not return until after the signal handler
     does.
     Returns
 

-
-
+
 
3   The raise function returns zero if successful, nonzero if unsuccessful.
 
 

-
-
+
 

-
7.15 [Variable arguments ]

-

-
-
+
7.15 [Variable arguments <stdarg.h>]

+
 
1   The header <stdarg.h> declares a type and defines four macros, for advancing
     through a list of arguments whose number and types are not known to the called function
     when it is translated.
 

-
-
+
 
2   A function may be called with a variable number of arguments of varying types. As
-    described in 6.9.1, its parameter list contains one or more parameters. The rightmost
+    described in 6.9.1, its parameter list contains one or more parameters. The rightmost
     parameter plays a special role in the access mechanism, and will be designated parmN in
     this description.
 

-
-
+
 
3   The type declared is
             va_list
     which is an object type suitable for holding information needed by the macros
@@ -14227,44 +12320,11 @@ char int_p_sep_by_space
     subclause) having type va_list. The object ap may be passed as an argument to
     another function; if that function invokes the va_arg macro with parameter ap, the
     value of ap in the calling function is indeterminate and shall be passed to the va_end
-    macro prior to any further reference to ap.221)
+    macro prior to any further reference to ap.[221]
 

-
 
 
Footnote 221) It is permitted to create a pointer to a va_list and pass that pointer to another function, in which
          case the original function may make further use of the original list after the other function returns.
-

-
-
-

-
7.15.1 [Variable argument list access macros]

-

-
-
-
1   The va_start and va_arg macros described in this subclause shall be implemented
-    as macros, not functions. It is unspecified whether va_copy and va_end are macros or
-    identifiers declared with external linkage. If a macro definition is suppressed in order to
-    access an actual function, or a program defines an external identifier with the same name,
-    the behavior is undefined. Each invocation of the va_start and va_copy macros
-    shall be matched by a corresponding invocation of the va_end macro in the same
-    function.
-

-
-
-

-
7.15.1.1 [The va_arg macro]

-

-
-
-
1           #include <stdarg.h>
-            type va_arg(va_list ap, type);
-    Description
-

-
-
-
2   The va_arg macro expands to an expression that has the specified type and the value of
-    the next argument in the call. The parameter ap shall have been initialized by the
-    va_start or va_copy macro (without an intervening invocation of the va_end
     macro for the same ap). Each invocation of the va_arg macro modifies ap so that the
     values of successive arguments are returned in turn. The parameter type shall be a type
     name specified such that the type of a pointer to an object that has the specified type can
@@ -14276,26 +12336,49 @@ char int_p_sep_by_space
        type, and the value is representable in both types;
     -- one type is pointer to void and the other is a pointer to a character type.
     Returns
-

+

 
-
+
+

+
7.15.1 [Variable argument list access macros]

+
+
1   The va_start and va_arg macros described in this subclause shall be implemented
+    as macros, not functions. It is unspecified whether va_copy and va_end are macros or
+    identifiers declared with external linkage. If a macro definition is suppressed in order to
+    access an actual function, or a program defines an external identifier with the same name,
+    the behavior is undefined. Each invocation of the va_start and va_copy macros
+    shall be matched by a corresponding invocation of the va_end macro in the same
+    function.
+

+
+

+
7.15.1.1 [The va_arg macro]

+
+
1 Synopsis
+           #include <stdarg.h>
+            type va_arg(va_list ap, type);
+    Description
+

+
+
2   The va_arg macro expands to an expression that has the specified type and the value of
+    the next argument in the call. The parameter ap shall have been initialized by the
+    va_start or va_copy macro (without an intervening invocation of the va_end
+

+
 
3   The first invocation of the va_arg macro after that of the va_start macro returns the
     value of the argument after that specified by parmN . Successive invocations return the
     values of the remaining arguments in succession.
 

-
-
+
 

 
7.15.1.2 [The va_copy macro]

-

-
-
-
1          #include <stdarg.h>
+
+
1 Synopsis
+          #include <stdarg.h>
            void va_copy(va_list dest, va_list src);
     Description
 

-
-
+
 
2   The va_copy macro initializes dest as a copy of src, as if the va_start macro had
     been applied to dest followed by the same sequence of uses of the va_arg macro as
     had previously been used to reach the present state of src. Neither the va_copy nor
@@ -14303,23 +12386,19 @@ char int_p_sep_by_space
     invocation of the va_end macro for the same dest.
     Returns
 

-
-
+
 
3   The va_copy macro returns no value.
 

-
-
+
 

 
7.15.1.3 [The va_end macro]

-

-
-
-
1          #include <stdarg.h>
+
+
1 Synopsis
+          #include <stdarg.h>
            void va_end(va_list ap);
     Description
 

-
-
+
 
2   The va_end macro facilitates a normal return from the function whose variable
     argument list was referred to by the expansion of the va_start macro, or the function
     containing the expansion of the va_copy macro, that initialized the va_list ap. The
@@ -14329,33 +12408,27 @@ char int_p_sep_by_space
     return, the behavior is undefined.
     Returns
 

-
-
+
 
3   The va_end macro returns no value.
 

-
-
+
 

 
7.15.1.4 [The va_start macro]

-

-
-
-
1           #include <stdarg.h>
+
+
1 Synopsis
+           #include <stdarg.h>
             void va_start(va_list ap, parmN);
     Description
 

-
-
+
 
2   The va_start macro shall be invoked before any access to the unnamed arguments.
 

-
-
+
 
3   The va_start macro initializes ap for subsequent use by the va_arg and va_end
     macros. Neither the va_start nor va_copy macro shall be invoked to reinitialize ap
     without an intervening invocation of the va_end macro for the same ap.
 

-
-
+
 
4   The parameter parmN is the identifier of the rightmost parameter in the variable
     parameter list in the function definition (the one just before the , ...). If the parameter
     parmN is declared with the register storage class, with a function or array type, or
@@ -14363,12 +12436,10 @@ char int_p_sep_by_space
     argument promotions, the behavior is undefined.
     Returns
 

-
-
+
 
5   The va_start macro returns no value.
 

-
-
+
 
6   EXAMPLE 1 The function f1 gathers into an array a list of arguments that are pointers to strings (but not
     more than MAXARGS arguments), then passes the array as a single argument to function f2. The number of
     pointers is specified by the first argument to f1.
@@ -14392,8 +12463,7 @@ char int_p_sep_by_space
              void f1(int, ...);
 
 

-
-
+
 
7   EXAMPLE 2 The function f3 is similar, but saves the status of the variable argument list after the
     indicated number of arguments; after f2 has been called once with the whole list, the trailing part of the list
     is gathered again and passed to function f4.
@@ -14424,23 +12494,18 @@ char int_p_sep_by_space
              }
 
 

-
-
+
 

-
7.16 [Boolean type and values ]

-

-
-
+
7.16 [Boolean type and values <stdbool.h>]

+
 
1   The header <stdbool.h> defines four macros.
 

-
-
+
 
2   The macro
              bool
     expands to _Bool.
 

-
-
+
 
3   The remaining three macros are suitable for use in #if preprocessing directives. They
     are
              true
@@ -14450,27 +12515,22 @@ char int_p_sep_by_space
              _ _bool_true_false_are_defined
     which expands to the integer constant 1.
 

-
-
-
4   Notwithstanding the provisions of 7.1.3, a program may undefine and perhaps then
-    redefine the macros bool, true, and false.222)
+
+
4   Notwithstanding the provisions of 7.1.3, a program may undefine and perhaps then
+    redefine the macros bool, true, and false.[222]
 

-
 
-
Footnote 222) See ``future library directions'' (7.26.7).
+
Footnote 222) See ``future library directions'' (7.26.7).
 

 
-
+
 

-
7.17 [Common definitions ]

-

-
-
+
7.17 [Common definitions <stddef.h>]

+
 
1   The following types and macros are defined in the standard header <stddef.h>. Some
     are also defined in other headers, as noted in their respective subclauses.
 

-
-
+
 
2   The types are
            ptrdiff_t
     which is the signed integer type of the result of subtracting two pointers;
@@ -14484,8 +12544,7 @@ char int_p_sep_by_space
     character      constant     if     an      implementation      does      not      define
     _ _STDC_MB_MIGHT_NEQ_WC_ _.
 

-
-
+
 
3   The macros are
            NULL
     which expands to an implementation-defined null pointer constant; and
@@ -14499,31 +12558,26 @@ char int_p_sep_by_space
     specified member is a bit-field, the behavior is undefined.)
     Recommended practice
 

-
-
+
 
4   The types used for size_t and ptrdiff_t should not have an integer conversion rank
     greater than that of signed long int unless the implementation supports objects
     large enough to make this necessary.
-    Forward references: localization (7.11).
+    Forward references: localization (7.11).
 
 

-
-
+
 

-
7.18 [Integer types ]

-

-
-
+
7.18 [Integer types <stdint.h>]

+
 
1   The header <stdint.h> declares sets of integer types having specified widths, and
-    defines corresponding sets of macros.223) It also defines macros that specify limits of
+    defines corresponding sets of macros.[223] It also defines macros that specify limits of
     integer types corresponding to types defined in other standard headers.
 

-
 
-
Footnote 223) See ``future library directions'' (7.26.8).
+
Footnote 223) See ``future library directions'' (7.26.8).
 

 
-
+
 
2   Types are defined in the following categories:
     -- integer types having certain exact widths;
     -- integer types having at least certain specified widths;
@@ -14532,82 +12586,66 @@ char int_p_sep_by_space
     -- integer types having greatest width.
     (Some of these types may denote the same type.)
 

-
-
+
 
3   Corresponding macros specify limits of the declared types and construct suitable
     constants.
 

-
-
-
4   For each type described herein that the implementation provides,224) <stdint.h> shall
+
+
4   For each type described herein that the implementation provides,[224] <stdint.h> shall
     declare that typedef name and define the associated macros. Conversely, for each type
     described herein that the implementation does not provide, <stdint.h> shall not
     declare that typedef name nor shall it define the associated macros. An implementation
     shall provide those types described as ``required'', but need not provide any of the others
     (described as ``optional'').
 

-
 
 
Footnote 224) Some of these types may denote implementation-defined extended integer types.
 

 
-
+
 

 
7.18.1 [Integer types]

-

-
-
+
 
1   When typedef names differing only in the absence or presence of the initial u are defined,
-    they shall denote corresponding signed and unsigned types as described in 6.2.5; an
+    they shall denote corresponding signed and unsigned types as described in 6.2.5; an
     implementation providing one of these corresponding types shall also provide the other.
 

-
-
+
 
2   In the following descriptions, the symbol N represents an unsigned decimal integer with
     no leading zeros (e.g., 8 or 24, but not 04 or 048).
 

-
-
+
 

 
7.18.1.1 [Exact-width integer types]

-

-
-
+
 
1   The typedef name intN_t designates a signed integer type with width N , no padding
     bits, and a two's complement representation. Thus, int8_t denotes a signed integer
     type with a width of exactly 8 bits.
 

-
-
+
 
2   The typedef name uintN_t designates an unsigned integer type with width N . Thus,
     uint24_t denotes an unsigned integer type with a width of exactly 24 bits.
 

-
-
+
 
3   These types are optional. However, if an implementation provides integer types with
     widths of 8, 16, 32, or 64 bits, no padding bits, and (for the signed types) that have a
     two's complement representation, it shall define the corresponding typedef names.
 

-
-
+
 

 
7.18.1.2 [Minimum-width integer types]

-

-
-
+
 
1   The typedef name int_leastN_t designates a signed integer type with a width of at
     least N , such that no signed integer type with lesser size has at least the specified width.
     Thus, int_least32_t denotes a signed integer type with a width of at least 32 bits.
 

-
-
+
 
2   The typedef name uint_leastN_t designates an unsigned integer type with a width
     of at least N , such that no unsigned integer type with lesser size has at least the specified
     width. Thus, uint_least16_t denotes an unsigned integer type with a width of at
     least 16 bits.
 

-
-
+
 
3   The following types are required:
              int_least8_t                                      uint_least8_t
              int_least16_t                                     uint_least16_t
@@ -14615,30 +12653,25 @@ char int_p_sep_by_space
              int_least64_t                                     uint_least64_t
     All other types of this form are optional.
 

-
-
+
 

 
7.18.1.3 [Fastest minimum-width integer types]

-

-
-
-
1   Each of the following types designates an integer type that is usually fastest225) to operate
+
+
1   Each of the following types designates an integer type that is usually fastest[225] to operate
     with among all integer types that have at least the specified width.
 

-
 
 
Footnote 225) The designated type is not guaranteed to be fastest for all purposes; if the implementation has no clear
          grounds for choosing one type over another, it will simply pick some integer type satisfying the
          signedness and width requirements.
 

 
-
+
 
2   The typedef name int_fastN_t designates the fastest signed integer type with a width
     of at least N . The typedef name uint_fastN_t designates the fastest unsigned integer
     type with a width of at least N .
 

-
-
+
 
3   The following types are required:
            int_fast8_t                                 uint_fast8_t
            int_fast16_t                                uint_fast16_t
@@ -14646,13 +12679,10 @@ char int_p_sep_by_space
            int_fast64_t                                uint_fast64_t
     All other types of this form are optional.
 

-
-
+
 

 
7.18.1.4 [Integer types capable of holding object pointers]

-

-
-
+
 
1   The following type designates a signed integer type with the property that any valid
     pointer to void can be converted to this type, then converted back to pointer to void,
     and the result will compare equal to the original pointer:
@@ -14663,13 +12693,10 @@ char int_p_sep_by_space
            uintptr_t
     These types are optional.
 

-
-
+
 

 
7.18.1.5 [Greatest-width integer types]

-

-
-
+
 
1   The following type designates a signed integer type capable of representing any value of
     any signed integer type:
            intmax_t
@@ -14678,37 +12705,30 @@ char int_p_sep_by_space
            uintmax_t
     These types are required.
 

-
-
+
 

 
7.18.2 [Limits of specified-width integer types]

-

-
-
-
1   The following object-like macros226) specify the minimum and maximum limits of the
-    types declared in <stdint.h>. Each macro name corresponds to a similar type name in 7.18.1.
+
+
1   The following object-like macros[226] specify the minimum and maximum limits of the
+    types declared in <stdint.h>. Each macro name corresponds to a similar type name in 7.18.1.
 

-
 
 
Footnote 226) C++ implementations should define these macros only when _ _STDC_LIMIT_MACROS is defined
          before <stdint.h> is included.
-

-
-
-
2   Each instance of any defined macro shall be replaced by a constant expression suitable
-    for use in #if preprocessing directives, and this expression shall have the same type as
-    would an expression that is an object of the corresponding type converted according to
     the integer promotions. Its implementation-defined value shall be equal to or greater in
     magnitude (absolute value) than the corresponding value given below, with the same sign,
     except where stated to be exactly the given value.
-

+

 
-
+
+
2   Each instance of any defined macro shall be replaced by a constant expression suitable
+    for use in #if preprocessing directives, and this expression shall have the same type as
+    would an expression that is an object of the corresponding type converted according to
+

+
 

 
7.18.2.1 [Limits of exact-width integer types]

-

-
-
+
 
1   -- minimum values of exact-width signed integer types
        INTN_MIN                                    exactly -(2 N -1 )
     -- maximum values of exact-width signed integer types
@@ -14716,13 +12736,10 @@ char int_p_sep_by_space
     -- maximum values of exact-width unsigned integer types
        UINTN_MAX                                   exactly 2 N - 1
 

-
-
+
 

 
7.18.2.2 [Limits of minimum-width integer types]

-

-
-
+
 
1   -- minimum values of minimum-width signed integer types
        INT_LEASTN_MIN                                       -(2 N -1 - 1)
     -- maximum values of minimum-width signed integer types
@@ -14730,13 +12747,10 @@ char int_p_sep_by_space
     -- maximum values of minimum-width unsigned integer types
        UINT_LEASTN_MAX                                      2N - 1
 

-
-
+
 

 
7.18.2.3 [Limits of fastest minimum-width integer types]

-

-
-
+
 
1   -- minimum values of fastest minimum-width signed integer types
        INT_FASTN_MIN                                        -(2 N -1 - 1)
     -- maximum values of fastest minimum-width signed integer types
@@ -14744,13 +12758,10 @@ char int_p_sep_by_space
     -- maximum values of fastest minimum-width unsigned integer types
        UINT_FASTN_MAX                                       2N - 1
 

-
-
+
 

 
7.18.2.4 [Limits of integer types capable of holding object pointers]

-

-
-
+
 
1   -- minimum value of pointer-holding signed integer type
           INTPTR_MIN                                        -(215 - 1)
     -- maximum value of pointer-holding signed integer type
@@ -14758,13 +12769,10 @@ char int_p_sep_by_space
     -- maximum value of pointer-holding unsigned integer type
         UINTPTR_MAX                                                   216 - 1
 

-
-
+
 

 
7.18.2.5 [Limits of greatest-width integer types]

-

-
-
+
 
1   -- minimum value of greatest-width signed integer type
         INTMAX_MIN                                                    -(263 - 1)
     -- maximum value of greatest-width signed integer type
@@ -14772,30 +12780,26 @@ char int_p_sep_by_space
     -- maximum value of greatest-width unsigned integer type
         UINTMAX_MAX                                                   264 - 1
 

-
-
+
 

 
7.18.3 [Limits of other integer types]

-

-
-
-
1   The following object-like macros227) specify the minimum and maximum limits of
+
+
1   The following object-like macros[227] specify the minimum and maximum limits of
     integer types corresponding to types defined in other standard headers.
 

-
 
 
Footnote 227) C++ implementations should define these macros only when _ _STDC_LIMIT_MACROS is defined
          before <stdint.h> is included.
 

 
-
+
 
2   Each instance of these macros shall be replaced by a constant expression suitable for use
     in #if preprocessing directives, and this expression shall have the same type as would an
     expression that is an object of the corresponding type converted according to the integer
     promotions. Its implementation-defined value shall be equal to or greater in magnitude
     (absolute value) than the corresponding value given below, with the same sign. An
     implementation shall define only the macros corresponding to those typedef names it
-    actually provides.228)
+    actually provides.[228]
     -- limits of ptrdiff_t
         PTRDIFF_MIN                                                 -65535
         PTRDIFF_MAX                                                 +65535
@@ -14805,91 +12809,77 @@ char int_p_sep_by_space
     -- limit of size_t
         SIZE_MAX                                                      65535
     -- limits of wchar_t
+

+
+
Footnote 228) A freestanding implementation need not provide all of these types.
        WCHAR_MIN                                              see below
        WCHAR_MAX                                              see below
     -- limits of wint_t
        WINT_MIN                                               see below
        WINT_MAX                                               see below
-

-
-
-
Footnote 228) A freestanding implementation need not provide all of these types.
 

 
-
-
3   If sig_atomic_t (see 7.14) is defined as a signed integer type, the value of
+
+
3   If sig_atomic_t (see 7.14) is defined as a signed integer type, the value of
     SIG_ATOMIC_MIN shall be no greater than -127 and the value of SIG_ATOMIC_MAX
     shall be no less than 127; otherwise, sig_atomic_t is defined as an unsigned integer
     type, and the value of SIG_ATOMIC_MIN shall be 0 and the value of
     SIG_ATOMIC_MAX shall be no less than 255.
 

-
-
-
4   If wchar_t (see 7.17) is defined as a signed integer type, the value of WCHAR_MIN
+
+
4   If wchar_t (see 7.17) is defined as a signed integer type, the value of WCHAR_MIN
     shall be no greater than -127 and the value of WCHAR_MAX shall be no less than 127;
     otherwise, wchar_t is defined as an unsigned integer type, and the value of
-    WCHAR_MIN shall be 0 and the value of WCHAR_MAX shall be no less than 255.229)
+    WCHAR_MIN shall be 0 and the value of WCHAR_MAX shall be no less than 255.[229]
 

-
 
 
Footnote 229) The values WCHAR_MIN and WCHAR_MAX do not necessarily correspond to members of the extended
          character set.
 

 
-
-
5   If wint_t (see 7.24) is defined as a signed integer type, the value of WINT_MIN shall
+
+
5   If wint_t (see 7.24) is defined as a signed integer type, the value of WINT_MIN shall
     be no greater than -32767 and the value of WINT_MAX shall be no less than 32767;
     otherwise, wint_t is defined as an unsigned integer type, and the value of WINT_MIN
     shall be 0 and the value of WINT_MAX shall be no less than 65535.
 

-
-
+
 

 
7.18.4 [Macros for integer constants]

-

-
-
-
1   The following function-like macros230) expand to integer constants suitable for
+
+
1   The following function-like macros[230] expand to integer constants suitable for
     initializing objects that have integer types corresponding to types defined in
-    <stdint.h>. Each macro name corresponds to a similar type name in 7.18.1.2 or 7.18.1.5.
+    <stdint.h>. Each macro name corresponds to a similar type name in 7.18.1.2 or 7.18.1.5.
 

-
 
 
Footnote 230) C++ implementations should define these macros only when _ _STDC_CONSTANT_MACROS is
          defined before <stdint.h> is included.
 

 
-
+
 
2   The argument in any instance of these macros shall be an unsuffixed integer constant (as
-    defined in 6.4.4.1) with a value that does not exceed the limits for the corresponding type.
+    defined in 6.4.4.1) with a value that does not exceed the limits for the corresponding type.
 

-
-
+
 
3   Each invocation of one of these macros shall expand to an integer constant expression
     suitable for use in #if preprocessing directives. The type of the expression shall have
     the same type as would an expression of the corresponding type converted according to
     the integer promotions. The value of the expression shall be that of the argument.
 

-
-
+
 

 
7.18.4.1 [Macros for minimum-width integer constants]

-

-
-
+
 
1   The macro INTN_C(value) shall expand to an integer constant expression
     corresponding to the type int_leastN_t. The macro UINTN_C(value) shall expand
     to an integer constant expression corresponding to the type uint_leastN_t. For
     example, if uint_least64_t is a name for the type unsigned long long int,
     then UINT64_C(0x123) might expand to the integer constant 0x123ULL.
 

-
-
+
 

 
7.18.4.2 [Macros for greatest-width integer constants]

-

-
-
+
 
1   The following macro expands to an integer constant expression having the value specified
     by its argument and the type intmax_t:
            INTMAX_C(value)
@@ -14898,25 +12888,18 @@ char int_p_sep_by_space
            UINTMAX_C(value)
 
 

-
-
+
 

-
7.19 [Input/output ]

-
 Input/output 
-

-
-
+
7.19 [Input/output <stdio.h>]

+
 

 
7.19.1 [Introduction]

-

-
-
+
 
1   The header <stdio.h> declares three types, several macros, and many functions for
     performing input and output.
 

-
-
-
2   The types declared are size_t (described in 7.17);
+
+
2   The types declared are size_t (described in 7.17);
            FILE
     which is an object type capable of recording all the information needed to control a
     stream, including its file position indicator, a pointer to its associated buffer (if any), an
@@ -14926,9 +12909,8 @@ char int_p_sep_by_space
     which is an object type other than an array type capable of recording all the information
     needed to specify uniquely every position within a file.
 

-
-
-
3   The macros are NULL (described in 7.17);
+
+
3   The macros are NULL (described in 7.17);
            _IOFBF
            _IOLBF
            _IONBF
@@ -14947,7 +12929,7 @@ char int_p_sep_by_space
            FILENAME_MAX
     which expands to an integer constant expression that is the size needed for an array of
     char large enough to hold the longest file name string that the implementation
-    guarantees can be opened;231)
+    guarantees can be opened;[231]
              L_tmpnam
     which expands to an integer constant expression that is the size needed for an array of
     char large enough to hold a temporary file name string generated by the tmpnam
@@ -14966,61 +12948,59 @@ char int_p_sep_by_space
     which are expressions of type ``pointer to FILE'' that point to the FILE objects
     associated, respectively, with the standard error, input, and output streams.
 

-
 
 
Footnote 231) If the implementation imposes no practical limit on the length of file name strings, the value of
          FILENAME_MAX should instead be the recommended size of an array intended to hold a file name
          string. Of course, file name string contents are subject to other system-specific constraints; therefore
          all possible strings of length FILENAME_MAX cannot be expected to be opened successfully.
-

-
-
-
4   The header <wchar.h> declares a number of functions useful for wide character input
-    and output. The wide character input/output functions described in that subclause
-    provide operations analogous to most of those described here, except that the
-    fundamental units internal to the program are wide characters. The external
-    representation (in the file) is a sequence of ``generalized'' multibyte characters, as
-    described further in 7.19.3.
-

-
-
-
5   The input/output functions are given the following collective terms:
-    -- The wide character input functions -- those functions described in 7.24 that perform
-       input into wide characters and wide strings: fgetwc, fgetws, getwc, getwchar,
-       fwscanf, wscanf, vfwscanf, and vwscanf.
-    -- The wide character output functions -- those functions described in 7.24 that perform
-       output from wide characters and wide strings: fputwc, fputws, putwc,
-       putwchar, fwprintf, wprintf, vfwprintf, and vwprintf.
     -- The wide character input/output functions -- the union of the ungetwc function, the
        wide character input functions, and the wide character output functions.
     -- The byte input/output functions -- those functions described in this subclause that
        perform input/output: fgetc, fgets, fprintf, fputc, fputs, fread,
        fscanf, fwrite, getc, getchar, gets, printf, putc, putchar, puts,
        scanf, ungetc, vfprintf, vfscanf, vprintf, and vscanf.
-    Forward references: files (7.19.3), the fseek function (7.19.9.2), streams (7.19.2), the
-    tmpnam function (7.19.4.4), <wchar.h> (7.24).
-

+    Forward references: files (7.19.3), the fseek function (7.19.9.2), streams (7.19.2), the
+    tmpnam function (7.19.4.4), <wchar.h> (7.24).
+

 
-
+
+
4   The header <wchar.h> declares a number of functions useful for wide character input
+    and output. The wide character input/output functions described in that subclause
+    provide operations analogous to most of those described here, except that the
+    fundamental units internal to the program are wide characters. The external
+    representation (in the file) is a sequence of ``generalized'' multibyte characters, as
+    described further in 7.19.3.
+

+
+
5   The input/output functions are given the following collective terms:
+    -- The wide character input functions -- those functions described in 7.24 that perform
+       input into wide characters and wide strings: fgetwc, fgetws, getwc, getwchar,
+       fwscanf, wscanf, vfwscanf, and vwscanf.
+    -- The wide character output functions -- those functions described in 7.24 that perform
+       output from wide characters and wide strings: fputwc, fputws, putwc,
+       putwchar, fwprintf, wprintf, vfwprintf, and vwprintf.
+

+
 

 
7.19.2 [Streams]

-

-
-
+
 
1   Input and output, whether to or from physical devices such as terminals and tape drives,
     or whether to or from files supported on structured storage devices, are mapped into
     logical data streams, whose properties are more uniform than their various inputs and
     outputs. Two forms of mapping are supported, for text streams and for binary
-    streams.232)
+    streams.[232]
 

-
 
 
Footnote 232) An implementation need not distinguish between text streams and binary streams. In such an
          implementation, there need be no new-line characters in a text stream nor any limit to the length of a
          line.
+    stream becomes a wide-oriented stream . Similarly, once a byte input/output function has
+    been applied to a stream without orientation, the stream becomes a byte-oriented stream .
+    Only a call to the freopen function or the fwide function can otherwise alter the
+    orientation of a stream. (A successful call to freopen removes any orientation.)233)
 

 
-
+
 
2   A text stream is an ordered sequence of characters composed into lines, each line
     consisting of zero or more characters plus a terminating new-line character. Whether the
     last line requires a terminating new-line character is implementation-defined. Characters
@@ -15034,30 +13014,19 @@ char int_p_sep_by_space
     Whether space characters that are written out immediately before a new-line character
     appear when read in is implementation-defined.
 

-
-
+
 
3   A binary stream is an ordered sequence of characters that can transparently record
     internal data. Data read in from a binary stream shall compare equal to the data that were
     earlier written out to that stream, under the same implementation. Such a stream may,
     however, have an implementation-defined number of null characters appended to the end
     of the stream.
 

-
-
+
 
4   Each stream has an orientation. After a stream is associated with an external file, but
     before any operations are performed on it, the stream is without orientation. Once a wide
     character input/output function has been applied to a stream without orientation, the
-    stream becomes a wide-oriented stream . Similarly, once a byte input/output function has
-    been applied to a stream without orientation, the stream becomes a byte-oriented stream .
-    Only a call to the freopen function or the fwide function can otherwise alter the
-    orientation of a stream. (A successful call to freopen removes any orientation.)233)
 

-
-
-
Footnote 233) The three predefined streams stdin, stdout, and stderr are unoriented at program startup.
-

-
-
+
 
5   Byte input/output functions shall not be applied to a wide-oriented stream and wide
     character input/output functions shall not be applied to a byte-oriented stream. The
     remaining stream operations do not affect, and are not affected by, a stream's orientation,
@@ -15069,8 +13038,7 @@ char int_p_sep_by_space
        function can overwrite a partial multibyte character; any file contents beyond the
        byte(s) written are henceforth indeterminate.
 

-
-
+
 
6   Each wide-oriented stream has an associated mbstate_t object that stores the current
     parse state of the stream. A successful call to fgetpos stores a representation of the
     value of this mbstate_t object as part of the value of the fpos_t object. A later
@@ -15078,22 +13046,18 @@ char int_p_sep_by_space
     the associated mbstate_t object as well as the position within the controlled stream.
     Environmental limits
 

-
-
+
 
7   An implementation shall support text files with lines containing at least 254 characters,
     including the terminating new-line character. The value of the macro BUFSIZ shall be at
     least 256.
-    Forward references: the freopen function (7.19.5.4), the fwide function (7.24.3.5),
-    mbstate_t (7.25.1), the fgetpos function (7.19.9.1), the fsetpos function
-    (7.19.9.3).
+    Forward references: the freopen function (7.19.5.4), the fwide function (7.24.3.5),
+    mbstate_t (7.25.1), the fgetpos function (7.19.9.1), the fsetpos function
+    (7.19.9.3).
 

-
-
+
 

 
7.19.3 [Files]

-

-
-
+
 
1   A stream is associated with an external file (which may be a physical device) by opening
     a file, which may involve creating a new file. Creating an existing file causes its former
     contents to be discarded, if necessary. If a file can support positioning requests (such as a
@@ -15104,14 +13068,12 @@ char int_p_sep_by_space
     position indicator is maintained by subsequent reads, writes, and positioning requests, to
     facilitate an orderly progression through the file.
 

-
-
-
2   Binary files are not truncated, except as defined in 7.19.5.3. Whether a write on a text
+
+
2   Binary files are not truncated, except as defined in 7.19.5.3. Whether a write on a text
     stream causes the associated file to be truncated beyond that point is implementation-
     defined.
 

-
-
+
 
3   When a stream is unbuffered , characters are intended to appear from the source or at the
     destination as soon as possible. Otherwise characters may be accumulated and
     transmitted to or from the host environment as a block. When a stream is fully buffered ,
@@ -15124,8 +13086,7 @@ char int_p_sep_by_space
     characters from the host environment. Support for these characteristics is
     implementation-defined, and may be affected via the setbuf and setvbuf functions.
 

-
-
+
 
4   A file may be disassociated from a controlling stream by closing the file. Output streams
     are flushed (any unwritten buffer contents are transmitted to the host environment) before
     the stream is disassociated from the file. The value of a pointer to a FILE object is
@@ -15133,8 +13094,7 @@ char int_p_sep_by_space
     Whether a file of zero length (on which no characters have been written by an output
     stream) actually exists is implementation-defined.
 

-
-
+
 
5   The file may be subsequently reopened, by the same or another program execution, and
     its contents reclaimed or modified (if it can be repositioned at its start). If the main
     function returns to its original caller, or if the exit function is called, all open files are
@@ -15142,13 +13102,11 @@ char int_p_sep_by_space
     program termination, such as calling the abort function, need not close all files
     properly.
 

-
-
+
 
6   The address of the FILE object used to control a stream may be significant; a copy of a
     FILE object need not serve in place of the original.
 

-
-
+
 
7    At program startup, three text streams are predefined and need not be opened explicitly
      -- standard input (for reading conventional input), standard output (for writing
      conventional output), and standard error (for writing diagnostic output). As initially
@@ -15156,116 +13114,98 @@ char int_p_sep_by_space
      output streams are fully buffered if and only if the stream can be determined not to refer
      to an interactive device.
 

-
-
+
 
8    Functions that open additional (nontemporary) files require a file name, which is a string.
      The rules for composing valid file names are implementation-defined. Whether the same
      file can be simultaneously open multiple times is also implementation-defined.
 

-
-
+
 
9    Although both text and binary wide-oriented streams are conceptually sequences of wide
      characters, the external file associated with a wide-oriented stream is a sequence of
      multibyte characters, generalized as follows:
      -- Multibyte encodings within files may contain embedded null bytes (unlike multibyte
         encodings valid for use internal to the program).
-     -- A file need not begin nor end in the initial shift state.234)
+     -- A file need not begin nor end in the initial shift state.[234]
 

-
 
 
Footnote 234) Setting the file position indicator to end-of-file, as with fseek(file, 0, SEEK_END), has
           undefined behavior for a binary stream (because of possible trailing null characters) or for any stream
           with state-dependent encoding that does not assuredly end in the initial shift state.
+     multibyte character. The wide character input/output functions and the byte input/output
+     functions store the value of the macro EILSEQ in errno if and only if an encoding error
+     occurs.
+     Environmental limits
 

 
-
+
 
10   Moreover, the encodings used for multibyte characters may differ among files. Both the
      nature and choice of such encodings are implementation-defined.
 

-
-
+
 
11   The wide character input functions read multibyte characters from the stream and convert
      them to wide characters as if they were read by successive calls to the fgetwc function.
      Each conversion occurs as if by a call to the mbrtowc function, with the conversion state
      described by the stream's own mbstate_t object. The byte input functions read
      characters from the stream as if by successive calls to the fgetc function.
 

-
-
+
 
12   The wide character output functions convert wide characters to multibyte characters and
      write them to the stream as if they were written by successive calls to the fputwc
      function. Each conversion occurs as if by a call to the wcrtomb function, with the
      conversion state described by the stream's own mbstate_t object. The byte output
      functions write characters to the stream as if by successive calls to the fputc function.
 

-
-
+
 
13   In some cases, some of the byte input/output functions also perform conversions between
      multibyte characters and wide characters. These conversions also occur as if by calls to
      the mbrtowc and wcrtomb functions.
 

-
-
+
 
14   An encoding error occurs if the character sequence presented to the underlying
      mbrtowc function does not form a valid (generalized) multibyte character, or if the code
      value passed to the underlying wcrtomb does not correspond to a valid (generalized)
-     multibyte character. The wide character input/output functions and the byte input/output
-     functions store the value of the macro EILSEQ in errno if and only if an encoding error
-     occurs.
-     Environmental limits
 

-
-
+
 
15   The value of FOPEN_MAX shall be at least eight, including the three standard text
      streams.
-     Forward references: the exit function (7.20.4.3), the fgetc function (7.19.7.1), the
-     fopen function (7.19.5.3), the fputc function (7.19.7.3), the setbuf function
-     (7.19.5.5), the setvbuf function (7.19.5.6), the fgetwc function (7.24.3.1), the
-     fputwc function (7.24.3.3), conversion state (7.24.6), the mbrtowc function
-     (7.24.6.3.2), the wcrtomb function (7.24.6.3.3).
+     Forward references: the exit function (7.20.4.3), the fgetc function (7.19.7.1), the
+     fopen function (7.19.5.3), the fputc function (7.19.7.3), the setbuf function
+     (7.19.5.5), the setvbuf function (7.19.5.6), the fgetwc function (7.24.3.1), the
+     fputwc function (7.24.3.3), conversion state (7.24.6), the mbrtowc function
+     (7.24.6.3.2), the wcrtomb function (7.24.6.3.3).
 

-
-
+
 

 
7.19.4 [Operations on files]

-
 Operations on files
-

-
-
+
 

 
7.19.4.1 [The remove function]

-

-
-
-
1           #include <stdio.h>
+
+
1 Synopsis
+           #include <stdio.h>
             int remove(const char *filename);
      Description
 

-
-
+
 
2    The remove function causes the file whose name is the string pointed to by filename
      to be no longer accessible by that name. A subsequent attempt to open that file using that
      name will fail, unless it is created anew. If the file is open, the behavior of the remove
      function is implementation-defined.
      Returns
 

-
-
+
 
3    The remove function returns zero if the operation succeeds, nonzero if it fails.
 

-
-
+
 

 
7.19.4.2 [The rename function]

-

-
-
-
1           #include <stdio.h>
+
+
1 Synopsis
+           #include <stdio.h>
             int rename(const char *old, const char *new);
      Description
 

-
-
+
 
2    The rename function causes the file whose name is the string pointed to by old to be
      henceforth known by the name given by the string pointed to by new. The file named
      old is no longer accessible by that name. If a file named by the string pointed to by new
@@ -15273,85 +13213,73 @@ char int_p_sep_by_space
 
     Returns
 

-
-
-
3   The rename function returns zero if the operation succeeds, nonzero if it fails,235) in
+
+
3   The rename function returns zero if the operation succeeds, nonzero if it fails,[235] in
     which case if the file existed previously it is still known by its original name.
 

-
 
 
Footnote 235) Among the reasons the implementation may cause the rename function to fail are that the file is open
          or that it is necessary to copy its contents to effectuate its renaming.
 

 
-
+
 

 
7.19.4.3 [The tmpfile function]

-

-
-
-
1           #include <stdio.h>
+
+
1 Synopsis
+           #include <stdio.h>
             FILE *tmpfile(void);
     Description
 

-
-
+
 
2   The tmpfile function creates a temporary binary file that is different from any other
     existing file and that will automatically be removed when it is closed or at program
     termination. If the program terminates abnormally, whether an open temporary file is
     removed is implementation-defined. The file is opened for update with "wb+" mode.
     Recommended practice
 

-
-
+
 
3   It should be possible to open at least TMP_MAX temporary files during the lifetime of the
     program (this limit may be shared with tmpnam) and there should be no limit on the
     number simultaneously open other than this limit and any limit on the number of open
     files (FOPEN_MAX).
     Returns
 

-
-
+
 
4   The tmpfile function returns a pointer to the stream of the file that it created. If the file
     cannot be created, the tmpfile function returns a null pointer.
-    Forward references: the fopen function (7.19.5.3).
+    Forward references: the fopen function (7.19.5.3).
 

-
-
+
 

 
7.19.4.4 [The tmpnam function]

-

-
-
-
1           #include <stdio.h>
+
+
1 Synopsis
+           #include <stdio.h>
             char *tmpnam(char *s);
     Description
 

-
-
+
 
2   The tmpnam function generates a string that is a valid file name and that is not the same
-    as the name of an existing file.236) The function is potentially capable of generating
-    TMP_MAX different strings, but any or all of them may already be in use by existing files
-    and thus not be suitable return values.
+    as the name of an existing file.[236] The function is potentially capable of generating
 

-
 
 
Footnote 236) Files created using strings generated by the tmpnam function are temporary only in the sense that
          their names should not collide with those generated by conventional naming rules for the
          implementation. It is still necessary to use the remove function to remove such files when their use
          is ended, and before program termination.
+    TMP_MAX different strings, but any or all of them may already be in use by existing files
+    and thus not be suitable return values.
 

 
-
+
 
3   The tmpnam function generates a different string each time it is called.
 

-
-
+
 
4   The implementation shall behave as if no library function calls the tmpnam function.
     Returns
 

-
-
+
 
5   If no suitable string can be generated, the tmpnam function returns a null pointer.
     Otherwise, if the argument is a null pointer, the tmpnam function leaves its result in an
     internal static object and returns a pointer to that object (subsequent calls to the tmpnam
@@ -15360,29 +13288,22 @@ char int_p_sep_by_space
     in that array and returns the argument as its value.
     Environmental limits
 

-
-
+
 
6   The value of the macro TMP_MAX shall be at least 25.
 

-
-
+
 

 
7.19.5 [File access functions]

-
 File access functions
-

-
-
+
 

 
7.19.5.1 [The fclose function]

-

-
-
-
1          #include <stdio.h>
+
+
1 Synopsis
+          #include <stdio.h>
            int fclose(FILE *stream);
     Description
 

-
-
+
 
2   A successful call to the fclose function causes the stream pointed to by stream to be
     flushed and the associated file to be closed. Any unwritten buffered data for the stream
     are delivered to the host environment to be written to the file; any unread buffered data
@@ -15391,63 +13312,53 @@ char int_p_sep_by_space
     (and deallocated if it was automatically allocated).
     Returns
 

-
-
+
 
3   The fclose function returns zero if the stream was successfully closed, or EOF if any
     errors were detected.
 

-
-
+
 

 
7.19.5.2 [The fflush function]

-

-
-
-
1          #include <stdio.h>
+
+
1 Synopsis
+          #include <stdio.h>
            int fflush(FILE *stream);
 
     Description
 

-
-
+
 
2   If stream points to an output stream or an update stream in which the most recent
     operation was not input, the fflush function causes any unwritten data for that stream
     to be delivered to the host environment to be written to the file; otherwise, the behavior is
     undefined.
 

-
-
+
 
3   If stream is a null pointer, the fflush function performs this flushing action on all
     streams for which the behavior is defined above.
     Returns
 

-
-
+
 
4   The fflush function sets the error indicator for the stream and returns EOF if a write
     error occurs, otherwise it returns zero.
-    Forward references: the fopen function (7.19.5.3).
+    Forward references: the fopen function (7.19.5.3).
 

-
-
+
 

 
7.19.5.3 [The fopen function]

-

-
-
-
1           #include <stdio.h>
+
+
1 Synopsis
+           #include <stdio.h>
             FILE *fopen(const char * restrict filename,
                  const char * restrict mode);
     Description
 

-
-
+
 
2   The fopen function opens the file whose name is the string pointed to by filename,
     and associates a stream with it.
 

-
-
+
 
3   The argument mode points to a string. If the string is one of the following, the file is
-    open in the indicated mode. Otherwise, the behavior is undefined.237)
+    open in the indicated mode. Otherwise, the behavior is undefined.[237]
     r                open text file for reading
     w                truncate to zero length or create text file for writing
     a                append; open or create text file for writing at end-of-file
@@ -15457,23 +13368,21 @@ char int_p_sep_by_space
     r+               open text file for update (reading and writing)
     w+               truncate to zero length or create text file for update
     a+               append; open or create text file for update, writing at end-of-file
-    r+b or rb+ open binary file for update (reading and writing)
-    w+b or wb+ truncate to zero length or create binary file for update
-    a+b or ab+ append; open or create binary file for update, writing at end-of-file
 

-
 
 
Footnote 237) If the string begins with one of the above sequences, the implementation might choose to ignore the
          remaining characters, or it might use them to select different kinds of a file (some of which might not
-         conform to the properties in 7.19.2).
+         conform to the properties in 7.19.2).
+    r+b or rb+ open binary file for update (reading and writing)
+    w+b or wb+ truncate to zero length or create binary file for update
+    a+b or ab+ append; open or create binary file for update, writing at end-of-file
 

 
-
+
 
4   Opening a file with read mode ('r' as the first character in the mode argument) fails if
     the file does not exist or cannot be read.
 

-
-
+
 
5   Opening a file with append mode ('a' as the first character in the mode argument)
     causes all subsequent writes to the file to be forced to the then current end-of-file,
     regardless of intervening calls to the fseek function. In some implementations, opening
@@ -15481,8 +13390,7 @@ char int_p_sep_by_space
     mode argument values) may initially position the file position indicator for the stream
     beyond the last data written, because of null character padding.
 

-
-
+
 
6   When a file is opened with update mode ('+' as the second or third character in the
     above list of mode argument values), both input and output may be performed on the
     associated stream. However, output shall not be directly followed by input without an
@@ -15492,152 +13400,133 @@ char int_p_sep_by_space
     of-file. Opening (or creating) a text file with update mode may instead open (or create) a
     binary stream in some implementations.
 

-
-
+
 
7   When opened, a stream is fully buffered if and only if it can be determined not to refer to
     an interactive device. The error and end-of-file indicators for the stream are cleared.
     Returns
 

-
-
+
 
8   The fopen function returns a pointer to the object controlling the stream. If the open
     operation fails, fopen returns a null pointer.
-    Forward references: file positioning functions (7.19.9).
+    Forward references: file positioning functions (7.19.9).
 

-
-
+
 

 
7.19.5.4 [The freopen function]

-

-
-
-
1          #include <stdio.h>
+
+
1 Synopsis
+          #include <stdio.h>
            FILE *freopen(const char * restrict filename,
                 const char * restrict mode,
                 FILE * restrict stream);
     Description
 

-
-
+
 
2   The freopen function opens the file whose name is the string pointed to by filename
     and associates the stream pointed to by stream with it. The mode argument is used just
 
-    as in the fopen function.238)
+    as in the fopen function.[238]
 

-
 
 
Footnote 238) The primary use of the freopen function is to change the file associated with a standard text stream
          (stderr, stdin, or stdout), as those identifiers need not be modifiable lvalues to which the value
          returned by the fopen function may be assigned.
+    Description
 

 
-
+
 
3   If filename is a null pointer, the freopen function attempts to change the mode of
     the stream to that specified by mode, as if the name of the file currently associated with
     the stream had been used. It is implementation-defined which changes of mode are
     permitted (if any), and under what circumstances.
 

-
-
+
 
4   The freopen function first attempts to close any file that is associated with the specified
     stream. Failure to close the file is ignored. The error and end-of-file indicators for the
     stream are cleared.
     Returns
 

-
-
+
 
5   The freopen function returns a null pointer if the open operation fails. Otherwise,
     freopen returns the value of stream.
 

-
-
+
 

 
7.19.5.5 [The setbuf function]

-

-
-
-
1           #include <stdio.h>
+
+
1 Synopsis
+           #include <stdio.h>
             void setbuf(FILE * restrict stream,
                  char * restrict buf);
     Description
 

-
-
+
 
2   Except that it returns no value, the setbuf function is equivalent to the setvbuf
     function invoked with the values _IOFBF for mode and BUFSIZ for size, or (if buf
     is a null pointer), with the value _IONBF for mode.
     Returns
 

-
-
+
 
3   The setbuf function returns no value.
-    Forward references: the setvbuf function (7.19.5.6).
+    Forward references: the setvbuf function (7.19.5.6).
 

-
-
+
 

 
7.19.5.6 [The setvbuf function]

-

-
-
-
1           #include <stdio.h>
+
+
1 Synopsis
+           #include <stdio.h>
             int setvbuf(FILE * restrict stream,
                  char * restrict buf,
                  int mode, size_t size);
-    Description
 

-
-
+
 
2   The setvbuf function may be used only after the stream pointed to by stream has
     been associated with an open file and before any other operation (other than an
     unsuccessful call to setvbuf) is performed on the stream. The argument mode
     determines how stream will be buffered, as follows: _IOFBF causes input/output to be
     fully buffered; _IOLBF causes input/output to be line buffered; _IONBF causes
     input/output to be unbuffered. If buf is not a null pointer, the array it points to may be
-    used instead of a buffer allocated by the setvbuf function239) and the argument size
+    used instead of a buffer allocated by the setvbuf function[239] and the argument size
     specifies the size of the array; otherwise, size may determine the size of a buffer
     allocated by the setvbuf function. The contents of the array at any time are
     indeterminate.
     Returns
 

-
 
 
Footnote 239) The buffer has to have a lifetime at least as great as the open stream, so the stream should be closed
          before a buffer that has automatic storage duration is deallocated upon block exit.
 

 
-
+
 
3   The setvbuf function returns zero on success, or nonzero if an invalid value is given
     for mode or if the request cannot be honored.
 

-
-
+
 

 
7.19.6 [Formatted input/output functions]

-

-
-
+
 
1   The formatted input/output functions shall behave as if there is a sequence point after the
-    actions associated with each specifier.240)
+    actions associated with each specifier.[240]
 

-
 
 
Footnote 240) The fprintf functions perform writes to memory for the %n specifier.
+    specifications, each of which results in fetching zero or more subsequent arguments,
+    converting them, if applicable, according to the corresponding conversion specifier, and
+    then writing the result to the output stream.
 

 
-
+
 

 
7.19.6.1 [The fprintf function]

-

-
-
-
1           #include <stdio.h>
+
+
1 Synopsis
+           #include <stdio.h>
             int fprintf(FILE * restrict stream,
                  const char * restrict format, ...);
     Description
 

-
-
+
 
2   The fprintf function writes output to the stream pointed to by stream, under control
     of the string pointed to by format that specifies how subsequent arguments are
     converted for output. If there are insufficient arguments for the format, the behavior is
@@ -15645,17 +13534,12 @@ char int_p_sep_by_space
     evaluated (as always) but are otherwise ignored. The fprintf function returns when
     the end of the format string is encountered.
 

-
-
+
 
3   The format shall be a multibyte character sequence, beginning and ending in its initial
     shift state. The format is composed of zero or more directives: ordinary multibyte
     characters (not %), which are copied unchanged to the output stream; and conversion
-    specifications, each of which results in fetching zero or more subsequent arguments,
-    converting them, if applicable, according to the corresponding conversion specifier, and
-    then writing the result to the output stream.
 

-
-
+
 
4   Each conversion specification is introduced by the character %. After the %, the following
     appear in sequence:
     -- Zero or more flags (in any order) that modify the meaning of the conversion
@@ -15663,7 +13547,7 @@ char int_p_sep_by_space
     -- An optional minimum field width. If the converted value has fewer characters than the
        field width, it is padded with spaces (by default) on the left (or right, if the left
        adjustment flag, described later, has been given) to the field width. The field width
-       takes the form of an asterisk * (described later) or a nonnegative decimal integer.241)
+       takes the form of an asterisk * (described later) or a nonnegative decimal integer.[241]
     -- An optional precision that gives the minimum number of digits to appear for the d, i,
        o, u, x, and X conversions, the number of digits to appear after the decimal-point
        character for a, A, e, E, f, and F conversions, the maximum number of significant
@@ -15675,27 +13559,9 @@ char int_p_sep_by_space
     -- An optional length modifier that specifies the size of the argument.
     -- A conversion specifier character that specifies the type of conversion to be applied.
 

-
 
 
Footnote 241) Note that 0 is taken as a flag, not as the beginning of a field width.
               specified.)242)
-

-
-
-
5   As noted above, a field width, or precision, or both, may be indicated by an asterisk. In
-    this case, an int argument supplies the field width or precision. The arguments
-    specifying field width, or precision, or both, shall appear (in that order) before the
-    argument (if any) to be converted. A negative field width argument is taken as a - flag
-    followed by a positive field width. A negative precision argument is taken as if the
-    precision were omitted.
-

-
-
-
6   The flag characters and their meanings are:
-    -        The result of the conversion is left-justified within the field. (It is right-justified if
-             this flag is not specified.)
-    +        The result of a signed conversion always begins with a plus or minus sign. (It
-             begins with a sign only when a negative value is converted if this flag is not
     space If the first character of a signed conversion is not a sign, or if a signed conversion
           results in no characters, a space is prefixed to the result. If the space and + flags
           both appear, the space flag is ignored.
@@ -15714,9 +13580,24 @@ char int_p_sep_by_space
               0 and - flags both appear, the 0 flag is ignored. For d, i, o, u, x, and X
               conversions, if a precision is specified, the 0 flag is ignored. For other
               conversions, the behavior is undefined.
-

+

 
-
+
+
5   As noted above, a field width, or precision, or both, may be indicated by an asterisk. In
+    this case, an int argument supplies the field width or precision. The arguments
+    specifying field width, or precision, or both, shall appear (in that order) before the
+    argument (if any) to be converted. A negative field width argument is taken as a - flag
+    followed by a positive field width. A negative precision argument is taken as if the
+    precision were omitted.
+

+
+
6   The flag characters and their meanings are:
+    -        The result of the conversion is left-justified within the field. (It is right-justified if
+             this flag is not specified.)
+    +        The result of a signed conversion always begins with a plus or minus sign. (It
+             begins with a sign only when a negative value is converted if this flag is not
+

+
 
7   The length modifiers and their meanings are:
     hh             Specifies that a following d, i, o, u, x, or X conversion specifier applies to a
                    signed char or unsigned char argument (the argument will have
@@ -15733,28 +13614,8 @@ char int_p_sep_by_space
     l (ell)        Specifies that a following d, i, o, u, x, or X conversion specifier applies to a
                    long int or unsigned long int argument; that a following n
                    conversion specifier applies to a pointer to a long int argument; that a
-    ll (ell-ell) Specifies that a following d, i, o, u, x, or X conversion specifier applies to a
-                 long long int or unsigned long long int argument; or that a
-                 following n conversion specifier applies to a pointer to a long long int
-                 argument.
-    j            Specifies that a following d, i, o, u, x, or X conversion specifier applies to
-                 an intmax_t or uintmax_t argument; or that a following n conversion
-                 specifier applies to a pointer to an intmax_t argument.
-    z            Specifies that a following d, i, o, u, x, or X conversion specifier applies to a
-                 size_t or the corresponding signed integer type argument; or that a
-                 following n conversion specifier applies to a pointer to a signed integer type
-                 corresponding to size_t argument.
-    t            Specifies that a following d, i, o, u, x, or X conversion specifier applies to a
-                 ptrdiff_t or the corresponding unsigned integer type argument; or that a
-                 following n conversion specifier applies to a pointer to a ptrdiff_t
-                 argument.
-    L            Specifies that a following a, A, e, E, f, F, g, or G conversion specifier
-                 applies to a long double argument.
-    If a length modifier appears with any conversion specifier other than as specified above,
-    the behavior is undefined.
 

-
-
+
 
8   The conversion specifiers and their meanings are:
     d,i         The int argument is converted to signed decimal in the style [-]dddd. The
                 precision specifies the minimum number of digits to appear; if the value
@@ -15781,9 +13642,9 @@ char int_p_sep_by_space
                   [-]nan or [-]nan(n-char-sequence) -- which style, and the meaning of
                   any n-char-sequence, is implementation-defined. The F conversion specifier
                   produces INF, INFINITY, or NAN instead of inf, infinity, or nan,
-                  respectively.243)
+                  respectively.[243]
     e,E           A double argument representing a floating-point number is converted in the
-                  style [-]d.ddd e±dd, where there is one digit (which is nonzero if the
+                  style [-]d.ddd e\xB1dd, where there is one digit (which is nonzero if the
                   argument is nonzero) before the decimal-point character and the number of
                   digits after it is equal to the precision; if the precision is missing, it is taken as
                   6; if the precision is zero and the # flag is not specified, no decimal-point
@@ -15803,8 +13664,16 @@ char int_p_sep_by_space
                      P - ( X + 1).
                   -- otherwise, the conversion is with style e (or E) and precision P - 1.
                   Finally, unless the # flag is used, any trailing zeros are removed from the
+

+
+
Footnote 243) When applied to infinite and NaN values, the -, +, and space flag characters have their usual meaning;
+         the # and 0 flag characters have no effect.
+                  fractional portion of the result and the decimal-point character is removed if
+                  there is no fractional portion remaining.
+                  A double argument representing an infinity or NaN is converted in the style
+                  of an f or F conversion specifier.
     a,A           A double argument representing a floating-point number is converted in the
-                  style [-]0xh.hhhh p±d, where there is one hexadecimal digit (which is
+                  style [-]0xh.hhhh p\xB1d, where there is one hexadecimal digit (which is
                   nonzero if the argument is a normalized floating-point number and is
                   otherwise unspecified) before the decimal-point character244) and the number
                   of hexadecimal digits after it is equal to the precision; if the precision is
@@ -15829,83 +13698,36 @@ char int_p_sep_by_space
                   second a null wide character.
     s             If no l length modifier is present, the argument shall be a pointer to the initial
                   element of an array of character type.246) Characters from the array are
-     p              The argument shall be a pointer to void. The value of the pointer is
-                    converted to a sequence of printing characters, in an implementation-defined
-                    manner.
-     n              The argument shall be a pointer to signed integer into which is written the
-                    number of characters written to the output stream so far by this call to
-                    fprintf. No argument is converted, but one is consumed. If the conversion
-                    specification includes any flags, a field width, or a precision, the behavior is
-                    undefined.
-     %              A % character is written. No argument is converted. The complete
-                    conversion specification shall be %%.
-

-
-
-
Footnote 244) Binary implementations can choose the hexadecimal digit to the left of the decimal-point character so
-         that subsequent digits align to nibble (4-bit) boundaries.
 

 
-
-
Footnote 245) The precision p is sufficient to distinguish values of the source type if 16 p-1 > b n where b is
-         FLT_RADIX and n is the number of base-b digits in the significand of the source type. A smaller p
-         might suffice depending on the implementation's scheme for determining the digit to the left of the
-         decimal-point character.
-

-
-
-
Footnote 246) No special provisions are made for multibyte characters.
-                    written up to (but not including) the terminating null character. If the
-                    precision is specified, no more than that many bytes are written. If the
-                    precision is not specified or is greater than the size of the array, the array shall
-                    contain a null character.
-                    If an l length modifier is present, the argument shall be a pointer to the initial
-                    element of an array of wchar_t type. Wide characters from the array are
-                    converted to multibyte characters (each as if by a call to the wcrtomb
-                    function, with the conversion state described by an mbstate_t object
-                    initialized to zero before the first wide character is converted) up to and
-                    including a terminating null wide character. The resulting multibyte
-                    characters are written up to (but not including) the terminating null character
-                    (byte). If no precision is specified, the array shall contain a null wide
-                    character. If a precision is specified, no more than that many bytes are
-                    written (including shift sequences, if any), and the array shall contain a null
-                    wide character if, to equal the multibyte character sequence length given by
-                    the precision, the function would need to access a wide character one past the
-                    end of the array. In no case is a partial multibyte character written.247)
-

-
-
-
9    If a conversion specification is invalid, the behavior is undefined.248) If any argument is
+
+
9    If a conversion specification is invalid, the behavior is undefined.[248] If any argument is
      not the correct type for the corresponding conversion specification, the behavior is
      undefined.
 

-
 
-
Footnote 248) See ``future library directions'' (7.26.9).
+
Footnote 248) See ``future library directions'' (7.26.9).
 

 
-
+
 
10   In no case does a nonexistent or small field width cause truncation of a field; if the result
      of a conversion is wider than the field width, the field is expanded to contain the
      conversion result.
 

-
-
+
 
11   For a and A conversions, if FLT_RADIX is a power of 2, the value is correctly rounded
      to a hexadecimal floating number with the given precision.
      Recommended practice
 

-
-
+
 
12   For a and A conversions, if FLT_RADIX is not a power of 2 and the result is not exactly
      representable in the given precision, the result should be one of the two adjacent numbers
      in hexadecimal floating style with the given precision, with the extra stipulation that the
      error should have a correct sign for the current rounding direction.
 

-
-
+
 
13   For e, E, f, F, g, and G conversions, if the number of significant decimal digits is at most
-     DECIMAL_DIG, then the result should be correctly rounded.249) If the number of
+     DECIMAL_DIG, then the result should be correctly rounded.[249] If the number of
      significant decimal digits is more than DECIMAL_DIG but the source value is exactly
      representable with DECIMAL_DIG digits, then the result should be an exact
      representation with trailing zeros. Otherwise, the source value is bounded by two
@@ -15914,25 +13736,22 @@ char int_p_sep_by_space
      the error should have a correct sign for the current rounding direction.
      Returns
 

-
 
 
Footnote 249) For binary-to-decimal conversion, the result format's values are the numbers representable with the
           given format specifier. The number of significant digits is determined by the format specifier, and in
           the case of fixed-point conversion by the source value as well.
 

 
-
+
 
14   The fprintf function returns the number of characters transmitted, or a negative value
      if an output or encoding error occurred.
      Environmental limits
 

-
-
+
 
15   The number of characters that can be produced by any single conversion shall be at least
      4095.
 

-
-
+
 
16   EXAMPLE 1       To print a date and time in the form ``Sunday, July 3, 10:02'' followed by  to five decimal
      places:
              #include <math.h>
@@ -15945,14 +13764,12 @@ char int_p_sep_by_space
              fprintf(stdout, "pi = %.5f\n", 4 * atan(1.0));
 
 

-
-
+
 
17   EXAMPLE 2 In this example, multibyte characters do not have a state-dependent encoding, and the
      members of the extended character set that consist of more than one byte each consist of exactly two bytes,
      the first of which is denoted here by a and the second by an uppercase letter.
 

-
-
+
 
18   Given the following wide string with length seven,
               static wchar_t wstr[] = L" X Yabc Z W";
      the seven calls
@@ -15972,22 +13789,19 @@ char int_p_sep_by_space
               |      abc Z W|
               |            Z|
 
-     Forward references: conversion state (7.24.6), the wcrtomb function (7.24.6.3.3).
+     Forward references: conversion state (7.24.6), the wcrtomb function (7.24.6.3.3).
 

-
-
+
 

 
7.19.6.2 [The fscanf function]

-

-
-
-
1             #include <stdio.h>
+
+
1 Synopsis
+             #include <stdio.h>
               int fscanf(FILE * restrict stream,
                    const char * restrict format, ...);
      Description
 

-
-
+
 
2    The fscanf function reads input from the stream pointed to by stream, under control
      of the string pointed to by format that specifies the admissible input sequences and how
      they are to be converted for assignment, using subsequent arguments as pointers to the
@@ -15995,8 +13809,7 @@ char int_p_sep_by_space
      the behavior is undefined. If the format is exhausted while arguments remain, the excess
      arguments are evaluated (as always) but are otherwise ignored.
 

-
-
+
 
3    The format shall be a multibyte character sequence, beginning and ending in its initial
      shift state. The format is composed of zero or more directives: one or more white-space
      characters, an ordinary multibyte character (neither % nor a white-space character), or a
@@ -16008,59 +13821,53 @@ char int_p_sep_by_space
      -- An optional length modifier that specifies the size of the receiving object.
      -- A conversion specifier character that specifies the type of conversion to be applied.
 

-
-
+
 
4    The fscanf function executes each directive of the format in turn. If a directive fails, as
      detailed below, the function returns. Failures are described as input failures (due to the
      occurrence of an encoding error or the unavailability of input characters), or matching
      failures (due to inappropriate input).
 

-
-
+
 
5    A directive composed of white-space character(s) is executed by reading input up to the
      first non-white-space character (which remains unread), or until no more characters can
      be read.
 

-
-
+
 
6    A directive that is an ordinary multibyte character is executed by reading the next
      characters of the stream. If any of those characters differ from the ones composing the
      directive, the directive fails and the differing and subsequent characters remain unread.
      Similarly, if end-of-file, an encoding error, or a read error prevents a character from being
      read, the directive fails.
 

-
-
+
 
7    A directive that is a conversion specification defines a set of matching input sequences, as
      described below for each specifier. A conversion specification is executed in the
      following steps:
 

-
-
+
 
8    Input white-space characters (as specified by the isspace function) are skipped, unless
-     the specification includes a [, c, or n specifier.250)
+     the specification includes a [, c, or n specifier.[250]
 

-
 
 
Footnote 250) These white-space characters are not counted against a specified field width.
 

 
-
+
 
9    An input item is read from the stream, unless the specification includes an n specifier. An
      input item is defined as the longest sequence of input characters which does not exceed
-     any specified field width and which is, or is a prefix of, a matching input sequence.251)
+     any specified field width and which is, or is a prefix of, a matching input sequence.[251]
      The first character, if any, after the input item remains unread. If the length of the input
      item is zero, the execution of the directive fails; this condition is a matching failure unless
      end-of-file, an encoding error, or a read error prevented input from the stream, in which
      case it is an input failure.
 

-
 
 
Footnote 251) fscanf pushes back at most one input character onto the input stream. Therefore, some sequences
           that are acceptable to strtod, strtol, etc., are unacceptable to fscanf.
+     in the object, the behavior is undefined.
 

 
-
+
 
10   Except in the case of a % specifier, the input item (or, in the case of a %n directive, the
      count of input characters) is converted to a type appropriate to the conversion specifier. If
      the input item is not a matching sequence, the execution of the directive fails: this
@@ -16068,10 +13875,8 @@ char int_p_sep_by_space
      result of the conversion is placed in the object pointed to by the first argument following
      the format argument that has not already received a conversion result. If this object
      does not have an appropriate type, or if the result of the conversion cannot be represented
-     in the object, the behavior is undefined.
 

-
-
+
 
11   The length modifiers and their meanings are:
      hh           Specifies that a following d, i, o, u, x, X, or n conversion specifier applies
                   to an argument with type pointer to signed char or unsigned char.
@@ -16099,8 +13904,7 @@ char int_p_sep_by_space
      If a length modifier appears with any conversion specifier other than as specified above,
      the behavior is undefined.
 

-
-
+
 
12   The conversion specifiers and their meanings are:
      d           Matches an optionally signed decimal integer, whose format is the same as
                  expected for the subject sequence of the strtol function with the value 10
@@ -16126,7 +13930,7 @@ char int_p_sep_by_space
             format is the same as expected for the subject sequence of the strtod
             function. The corresponding argument shall be a pointer to floating.
     c             Matches a sequence of characters of exactly the number specified by the field
-                  width (1 if no field width is present in the directive).252)
+                  width (1 if no field width is present in the directive).[252]
                   If no l length modifier is present, the corresponding argument shall be a
                   pointer to the initial element of a character array large enough to accept the
                   sequence. No null character is added.
@@ -16138,11 +13942,23 @@ char int_p_sep_by_space
                   corresponding argument shall be a pointer to the initial element of an array of
                   wchar_t large enough to accept the resulting sequence of wide characters.
                   No null wide character is added.
-    s             Matches a sequence of non-white-space characters.252)
+    s             Matches a sequence of non-white-space characters.[252]
                   If no l length modifier is present, the corresponding argument shall be a
                   pointer to the initial element of a character array large enough to accept the
                   sequence and a terminating null character, which will be added automatically.
                   If an l length modifier is present, the input shall be a sequence of multibyte
+

+
+
Footnote 252) No special provisions are made for multibyte characters in the matching rules used by the c, s, and [
+         conversion specifiers -- the extent of the input field is determined on a byte-by-byte basis. The
+         resulting field is nevertheless a sequence of multibyte characters that begins in the initial shift state.
+             characters that begins in the initial shift state. Each multibyte character is
+             converted to a wide character as if by a call to the mbrtowc function, with
+             the conversion state described by an mbstate_t object initialized to zero
+             before the first multibyte character is converted. The corresponding argument
+             shall be a pointer to the initial element of an array of wchar_t large enough
+             to accept the sequence and the terminating null wide character, which will be
+             added automatically.
     [        Matches a nonempty sequence of characters from a set of expected characters
              (the scanset ).252)
              If no l length modifier is present, the corresponding argument shall be a
@@ -16184,76 +14000,89 @@ char int_p_sep_by_space
                     suppressing character or a field width, the behavior is undefined.
      %              Matches a single % character; no conversion or assignment occurs. The
                     complete conversion specification shall be %%.
+

+
+
+
Footnote 252) No special provisions are made for multibyte characters in the matching rules used by the c, s, and [
+         conversion specifiers -- the extent of the input field is determined on a byte-by-byte basis. The
+         resulting field is nevertheless a sequence of multibyte characters that begins in the initial shift state.
+             characters that begins in the initial shift state. Each multibyte character is
+             converted to a wide character as if by a call to the mbrtowc function, with
+             the conversion state described by an mbstate_t object initialized to zero
+             before the first multibyte character is converted. The corresponding argument
+             shall be a pointer to the initial element of an array of wchar_t large enough
+             to accept the sequence and the terminating null wide character, which will be
+             added automatically.
+    [        Matches a nonempty sequence of characters from a set of expected characters
+             (the scanset ).252)
+             If no l length modifier is present, the corresponding argument shall be a
+             pointer to the initial element of a character array large enough to accept the
+             sequence and a terminating null character, which will be added automatically.
+             If an l length modifier is present, the input shall be a sequence of multibyte
+             characters that begins in the initial shift state. Each multibyte character is
+             converted to a wide character as if by a call to the mbrtowc function, with
+             the conversion state described by an mbstate_t object initialized to zero
+             before the first multibyte character is converted. The corresponding argument
+             shall be a pointer to the initial element of an array of wchar_t large enough
+             to accept the sequence and the terminating null wide character, which will be
+             added automatically.
+             The conversion specifier includes all subsequent characters in the format
+             string, up to and including the matching right bracket (]). The characters
+             between the brackets (the scanlist ) compose the scanset, unless the character
+             after the left bracket is a circumflex (^), in which case the scanset contains all
+             characters that do not appear in the scanlist between the circumflex and the
+             right bracket. If the conversion specifier begins with [] or [^], the right
+             bracket character is in the scanlist and the next following right bracket
+             character is the matching right bracket that ends the specification; otherwise
+             the first following right bracket character is the one that ends the
+             specification. If a - character is in the scanlist and is not the first, nor the
+             second where the first character is a ^, nor the last character, the behavior is
+             implementation-defined.
+    p        Matches an implementation-defined set of sequences, which should be the
+             same as the set of sequences that may be produced by the %p conversion of
+             the fprintf function. The corresponding argument shall be a pointer to a
+             pointer to void. The input item is converted to a pointer value in an
+             implementation-defined manner. If the input item is a value converted earlier
+             during the same program execution, the pointer that results shall compare
+             equal to that value; otherwise the behavior of the %p conversion is undefined.
+     n              No input is consumed. The corresponding argument shall be a pointer to
+                    signed integer into which is to be written the number of characters read from
+                    the input stream so far by this call to the fscanf function. Execution of a
+                    %n directive does not increment the assignment count returned at the
+                    completion of execution of the fscanf function. No argument is converted,
+                    but one is consumed. If the conversion specification includes an assignment-
+                    suppressing character or a field width, the behavior is undefined.
+     %              Matches a single % character; no conversion or assignment occurs. The
+                    complete conversion specification shall be %%.
+

+
+
+
13   If a conversion specification is invalid, the behavior is undefined.[253]
 

-
-
-
Footnote 252) No special provisions are made for multibyte characters in the matching rules used by the c, s, and [
-         conversion specifiers -- the extent of the input field is determined on a byte-by-byte basis. The
-         resulting field is nevertheless a sequence of multibyte characters that begins in the initial shift state.
-             characters that begins in the initial shift state. Each multibyte character is
-             converted to a wide character as if by a call to the mbrtowc function, with
-             the conversion state described by an mbstate_t object initialized to zero
-             before the first multibyte character is converted. The corresponding argument
-             shall be a pointer to the initial element of an array of wchar_t large enough
-             to accept the sequence and the terminating null wide character, which will be
-             added automatically.
-

-
-
-
Footnote 252) No special provisions are made for multibyte characters in the matching rules used by the c, s, and [
-         conversion specifiers -- the extent of the input field is determined on a byte-by-byte basis. The
-         resulting field is nevertheless a sequence of multibyte characters that begins in the initial shift state.
-             characters that begins in the initial shift state. Each multibyte character is
-             converted to a wide character as if by a call to the mbrtowc function, with
-             the conversion state described by an mbstate_t object initialized to zero
-             before the first multibyte character is converted. The corresponding argument
-             shall be a pointer to the initial element of an array of wchar_t large enough
-             to accept the sequence and the terminating null wide character, which will be
-             added automatically.
-

-
-
-
Footnote 252) No special provisions are made for multibyte characters in the matching rules used by the c, s, and [
-         conversion specifiers -- the extent of the input field is determined on a byte-by-byte basis. The
-         resulting field is nevertheless a sequence of multibyte characters that begins in the initial shift state.
-             characters that begins in the initial shift state. Each multibyte character is
-             converted to a wide character as if by a call to the mbrtowc function, with
-             the conversion state described by an mbstate_t object initialized to zero
-             before the first multibyte character is converted. The corresponding argument
-             shall be a pointer to the initial element of an array of wchar_t large enough
-             to accept the sequence and the terminating null wide character, which will be
-             added automatically.
-

-
-
-
13   If a conversion specification is invalid, the behavior is undefined.253)
-

-
 
-
Footnote 253) See ``future library directions'' (7.26.9).
+
Footnote 253) See ``future library directions'' (7.26.9).
               56789 0123 56a72
+     will assign to i the value 56 and to x the value 789.0, will skip 0123, and will assign to name the
+     sequence 56\0. The next character read from the input stream will be a.
 

 
-
+
 
14   The conversion specifiers A, E, F, G, and X are also valid and behave the same as,
      respectively, a, e, f, g, and x.
 

-
-
+
 
15   Trailing white space (including new-line characters) is left unread unless matched by a
      directive. The success of literal matches and suppressed assignments is not directly
      determinable other than via the %n directive.
      Returns
 

-
-
+
 
16   The fscanf function returns the value of the macro EOF if an input failure occurs
      before any conversion. Otherwise, the function returns the number of input items
      assigned, which can be fewer than provided for, or even zero, in the event of an early
      matching failure.
 

-
-
+
 
17   EXAMPLE 1        The call:
               #include <stdio.h>
               /* ... */
@@ -16265,20 +14094,16 @@ char int_p_sep_by_space
      thompson\0.
 
 

-
-
+
 
18   EXAMPLE 2        The call:
               #include <stdio.h>
               /* ... */
               int i; float x; char name[50];
               fscanf(stdin, "%2d%f%*d %[0123456789]", &i, &x, name);
      with input:
-     will assign to i the value 56 and to x the value 789.0, will skip 0123, and will assign to name the
-     sequence 56\0. The next character read from the input stream will be a.
 
 

-
-
+
 
19   EXAMPLE 3         To accept repeatedly from stdin a quantity, a unit of measure, and an item name:
               #include <stdio.h>
               /* ... */
@@ -16288,8 +14113,7 @@ char int_p_sep_by_space
                       fscanf(stdin,"%*[^\n]");
               } while (!feof(stdin) && !ferror(stdin));
 

-
-
+
 
20   If the stdin stream contains the following lines:
               2 quarts of oil
               -12.8degrees Celsius
@@ -16309,8 +14133,7 @@ char int_p_sep_by_space
               count     =    EOF;
 
 

-
-
+
 
21   EXAMPLE 4         In:
               #include <stdio.h>
               /* ... */
@@ -16320,16 +14143,14 @@ char int_p_sep_by_space
      of 3 is also assigned to n2. The value of d2 is not affected. The value 1 is assigned to i.
 
 

-
-
+
 
22   EXAMPLE 5 In these examples, multibyte characters do have a state-dependent encoding, and the
      members of the extended character set that consist of more than one byte each consist of exactly two bytes,
      the first of which is denoted here by a and the second by an uppercase letter, but are only recognized as
      such when in the alternate shift state. The shift sequences are denoted by  and , in which the first causes
      entry into the alternate shift state.
 

-
-
+
 
23   After the call:
 
                #include <stdio.h>
@@ -16341,8 +14162,7 @@ char int_p_sep_by_space
      str will contain  X Y\0 assuming that none of the bytes of the shift sequences (or of the multibyte
      characters, in the more general case) appears to be a single-byte white-space character.
 

-
-
+
 
24   In contrast, after the call:
                #include <stdio.h>
                #include <stddef.h>
@@ -16352,8 +14172,7 @@ char int_p_sep_by_space
      with the same input line, wstr will contain the two wide characters that correspond to X and Y and a
      terminating null wide character.
 

-
-
+
 
25   However, the call:
                #include <stdio.h>
                #include <stddef.h>
@@ -16363,8 +14182,7 @@ char int_p_sep_by_space
      with the same input line will return zero due to a matching failure against the  sequence in the format
      string.
 

-
-
+
 
26   Assuming that the first byte of the multibyte character X is the same as the first byte of the multibyte
      character Y, after the call:
                #include <stdio.h>
@@ -16375,71 +14193,60 @@ char int_p_sep_by_space
      with the same input line, zero will again be returned, but stdin will be left with a partially consumed
      multibyte character.
 
-     Forward references: the strtod, strtof, and strtold functions (7.20.1.3), the
-     strtol, strtoll, strtoul, and strtoull functions (7.20.1.4), conversion state
-     (7.24.6), the wcrtomb function (7.24.6.3.3).
+     Forward references: the strtod, strtof, and strtold functions (7.20.1.3), the
+     strtol, strtoll, strtoul, and strtoull functions (7.20.1.4), conversion state
+     (7.24.6), the wcrtomb function (7.24.6.3.3).
 
 

-
-
+
 

 
7.19.6.3 [The printf function]

-

-
-
-
1          #include <stdio.h>
+
+
1 Synopsis
+          #include <stdio.h>
            int printf(const char * restrict format, ...);
     Description
 

-
-
+
 
2   The printf function is equivalent to fprintf with the argument stdout interposed
     before the arguments to printf.
     Returns
 

-
-
+
 
3   The printf function returns the number of characters transmitted, or a negative value if
     an output or encoding error occurred.
 

-
-
+
 

 
7.19.6.4 [The scanf function]

-

-
-
-
1          #include <stdio.h>
+
+
1 Synopsis
+          #include <stdio.h>
            int scanf(const char * restrict format, ...);
     Description
 

-
-
+
 
2   The scanf function is equivalent to fscanf with the argument stdin interposed
     before the arguments to scanf.
     Returns
 

-
-
+
 
3   The scanf function returns the value of the macro EOF if an input failure occurs before
     any conversion. Otherwise, the scanf function returns the number of input items
     assigned, which can be fewer than provided for, or even zero, in the event of an early
     matching failure.
 

-
-
+
 

 
7.19.6.5 [The snprintf function]

-

-
-
-
1          #include <stdio.h>
+
+
1 Synopsis
+          #include <stdio.h>
            int snprintf(char * restrict s, size_t n,
                 const char * restrict format, ...);
     Description
 

-
-
+
 
2   The snprintf function is equivalent to fprintf, except that the output is written into
     an array (specified by argument s) rather than to a stream. If n is zero, nothing is written,
     and s may be a null pointer. Otherwise, output characters beyond the n-1st are
@@ -16448,100 +14255,86 @@ char int_p_sep_by_space
     that overlap, the behavior is undefined.
     Returns
 

-
-
+
 
3   The snprintf function returns the number of characters that would have been written
     had n been sufficiently large, not counting the terminating null character, or a negative
     value if an encoding error occurred. Thus, the null-terminated output has been
     completely written if and only if the returned value is nonnegative and less than n.
 

-
-
+
 

 
7.19.6.6 [The sprintf function]

-

-
-
-
1          #include <stdio.h>
+
+
1 Synopsis
+          #include <stdio.h>
            int sprintf(char * restrict s,
                 const char * restrict format, ...);
     Description
 

-
-
+
 
2   The sprintf function is equivalent to fprintf, except that the output is written into
     an array (specified by the argument s) rather than to a stream. A null character is written
     at the end of the characters written; it is not counted as part of the returned value. If
     copying takes place between objects that overlap, the behavior is undefined.
     Returns
 

-
-
+
 
3   The sprintf function returns the number of characters written in the array, not
     counting the terminating null character, or a negative value if an encoding error occurred.
 

-
-
+
 

 
7.19.6.7 [The sscanf function]

-

-
-
-
1          #include <stdio.h>
+
+
1 Synopsis
+          #include <stdio.h>
            int sscanf(const char * restrict s,
                 const char * restrict format, ...);
     Description
 

-
-
+
 
2   The sscanf function is equivalent to fscanf, except that input is obtained from a
     string (specified by the argument s) rather than from a stream. Reaching the end of the
     string is equivalent to encountering end-of-file for the fscanf function. If copying
     takes place between objects that overlap, the behavior is undefined.
     Returns
 

-
-
+
 
3   The sscanf function returns the value of the macro EOF if an input failure occurs
     before any conversion. Otherwise, the sscanf function returns the number of input
     items assigned, which can be fewer than provided for, or even zero, in the event of an
     early matching failure.
 
 

-
-
+
 

 
7.19.6.8 [The vfprintf function]

-

-
-
-
1          #include <stdarg.h>
+
+
1 Synopsis
+          #include <stdarg.h>
            #include <stdio.h>
            int vfprintf(FILE * restrict stream,
                 const char * restrict format,
                 va_list arg);
     Description
 

-
-
+
 
2   The vfprintf function is equivalent to fprintf, with the variable argument list
     replaced by arg, which shall have been initialized by the va_start macro (and
     possibly subsequent va_arg calls). The vfprintf function does not invoke the
-    va_end macro.254)
+    va_end macro.[254]
     Returns
 

-
 
 
Footnote 254) As the functions vfprintf, vfscanf, vprintf, vscanf, vsnprintf, vsprintf, and
          vsscanf invoke the va_arg macro, the value of arg after the return is indeterminate.
 

 
-
+
 
3   The vfprintf function returns the number of characters transmitted, or a negative
     value if an output or encoding error occurred.
 

-
-
+
 
4   EXAMPLE       The following shows the use of the vfprintf function in a general error-reporting routine.
            #include <stdarg.h>
            #include <stdio.h>
@@ -16556,286 +14349,248 @@ char int_p_sep_by_space
                     va_end(args);
            }
 

-
-
+
 

 
7.19.6.9 [The vfscanf function]

-

-
-
-
1          #include <stdarg.h>
+
+
1 Synopsis
+          #include <stdarg.h>
            #include <stdio.h>
            int vfscanf(FILE * restrict stream,
                 const char * restrict format,
                 va_list arg);
     Description
 

-
-
+
 
2   The vfscanf function is equivalent to fscanf, with the variable argument list
     replaced by arg, which shall have been initialized by the va_start macro (and
     possibly subsequent va_arg calls). The vfscanf function does not invoke the
-    va_end macro.254)
+    va_end macro.[254]
     Returns
 

-
 
 
Footnote 254) As the functions vfprintf, vfscanf, vprintf, vscanf, vsnprintf, vsprintf, and
          vsscanf invoke the va_arg macro, the value of arg after the return is indeterminate.
 

 
-
+
 
3   The vfscanf function returns the value of the macro EOF if an input failure occurs
     before any conversion. Otherwise, the vfscanf function returns the number of input
     items assigned, which can be fewer than provided for, or even zero, in the event of an
     early matching failure.
 

-
-
+
 

 
7.19.6.10 [The vprintf function]

-

-
-
-
1          #include <stdarg.h>
+
+
1 Synopsis
+          #include <stdarg.h>
            #include <stdio.h>
            int vprintf(const char * restrict format,
                 va_list arg);
     Description
 

-
-
+
 
2   The vprintf function is equivalent to printf, with the variable argument list
     replaced by arg, which shall have been initialized by the va_start macro (and
     possibly subsequent va_arg calls). The vprintf function does not invoke the
-    va_end macro.254)
+    va_end macro.[254]
     Returns
 

-
 
 
Footnote 254) As the functions vfprintf, vfscanf, vprintf, vscanf, vsnprintf, vsprintf, and
          vsscanf invoke the va_arg macro, the value of arg after the return is indeterminate.
 

 
-
+
 
3   The vprintf function returns the number of characters transmitted, or a negative value
     if an output or encoding error occurred.
 
 

-
-
+
 

 
7.19.6.11 [The vscanf function]

-

-
-
-
1          #include <stdarg.h>
+
+
1 Synopsis
+          #include <stdarg.h>
            #include <stdio.h>
            int vscanf(const char * restrict format,
                 va_list arg);
     Description
 

-
-
+
 
2   The vscanf function is equivalent to scanf, with the variable argument list replaced
     by arg, which shall have been initialized by the va_start macro (and possibly
     subsequent va_arg calls). The vscanf function does not invoke the va_end
-    macro.254)
+    macro.[254]
     Returns
 

-
 
 
Footnote 254) As the functions vfprintf, vfscanf, vprintf, vscanf, vsnprintf, vsprintf, and
          vsscanf invoke the va_arg macro, the value of arg after the return is indeterminate.
 

 
-
+
 
3   The vscanf function returns the value of the macro EOF if an input failure occurs
     before any conversion. Otherwise, the vscanf function returns the number of input
     items assigned, which can be fewer than provided for, or even zero, in the event of an
     early matching failure.
 

-
-
+
 

 
7.19.6.12 [The vsnprintf function]

-

-
-
-
1          #include <stdarg.h>
+
+
1 Synopsis
+          #include <stdarg.h>
            #include <stdio.h>
            int vsnprintf(char * restrict s, size_t n,
                 const char * restrict format,
                 va_list arg);
     Description
 

-
-
+
 
2   The vsnprintf function is equivalent to snprintf, with the variable argument list
     replaced by arg, which shall have been initialized by the va_start macro (and
     possibly subsequent va_arg calls). The vsnprintf function does not invoke the
-    va_end macro.254) If copying takes place between objects that overlap, the behavior is
+    va_end macro.[254] If copying takes place between objects that overlap, the behavior is
     undefined.
     Returns
 

-
 
 
Footnote 254) As the functions vfprintf, vfscanf, vprintf, vscanf, vsnprintf, vsprintf, and
          vsscanf invoke the va_arg macro, the value of arg after the return is indeterminate.
 

 
-
+
 
3   The vsnprintf function returns the number of characters that would have been written
     had n been sufficiently large, not counting the terminating null character, or a negative
     value if an encoding error occurred. Thus, the null-terminated output has been
     completely written if and only if the returned value is nonnegative and less than n.
 
 

-
-
+
 

 
7.19.6.13 [The vsprintf function]

-

-
-
-
1          #include <stdarg.h>
+
+
1 Synopsis
+          #include <stdarg.h>
            #include <stdio.h>
            int vsprintf(char * restrict s,
                 const char * restrict format,
                 va_list arg);
     Description
 

-
-
+
 
2   The vsprintf function is equivalent to sprintf, with the variable argument list
     replaced by arg, which shall have been initialized by the va_start macro (and
     possibly subsequent va_arg calls). The vsprintf function does not invoke the
-    va_end macro.254) If copying takes place between objects that overlap, the behavior is
+    va_end macro.[254] If copying takes place between objects that overlap, the behavior is
     undefined.
     Returns
 

-
 
 
Footnote 254) As the functions vfprintf, vfscanf, vprintf, vscanf, vsnprintf, vsprintf, and
          vsscanf invoke the va_arg macro, the value of arg after the return is indeterminate.
 

 
-
+
 
3   The vsprintf function returns the number of characters written in the array, not
     counting the terminating null character, or a negative value if an encoding error occurred.
 

-
-
+
 

 
7.19.6.14 [The vsscanf function]

-

-
-
-
1          #include <stdarg.h>
+
+
1 Synopsis
+          #include <stdarg.h>
            #include <stdio.h>
            int vsscanf(const char * restrict s,
                 const char * restrict format,
                 va_list arg);
     Description
 

-
-
+
 
2   The vsscanf function is equivalent to sscanf, with the variable argument list
     replaced by arg, which shall have been initialized by the va_start macro (and
     possibly subsequent va_arg calls). The vsscanf function does not invoke the
-    va_end macro.254)
+    va_end macro.[254]
     Returns
 

-
 
 
Footnote 254) As the functions vfprintf, vfscanf, vprintf, vscanf, vsnprintf, vsprintf, and
          vsscanf invoke the va_arg macro, the value of arg after the return is indeterminate.
 

 
-
+
 
3   The vsscanf function returns the value of the macro EOF if an input failure occurs
     before any conversion. Otherwise, the vsscanf function returns the number of input
     items assigned, which can be fewer than provided for, or even zero, in the event of an
     early matching failure.
 
 

-
-
+
 

 
7.19.7 [Character input/output functions]

-
 Character input/output functions
-

-
-
+
 

 
7.19.7.1 [The fgetc function]

-

-
-
-
1           #include <stdio.h>
+
+
1 Synopsis
+           #include <stdio.h>
             int fgetc(FILE *stream);
     Description
 

-
-
+
 
2   If the end-of-file indicator for the input stream pointed to by stream is not set and a
     next character is present, the fgetc function obtains that character as an unsigned
     char converted to an int and advances the associated file position indicator for the
     stream (if defined).
     Returns
 

-
-
+
 
3   If the end-of-file indicator for the stream is set, or if the stream is at end-of-file, the end-
     of-file indicator for the stream is set and the fgetc function returns EOF. Otherwise, the
     fgetc function returns the next character from the input stream pointed to by stream.
     If a read error occurs, the error indicator for the stream is set and the fgetc function
-    returns EOF.255)
+    returns EOF.[255]
 

-
 
 
Footnote 255) An end-of-file and a read error can be distinguished by use of the feof and ferror functions.
 

 
-
+
 

 
7.19.7.2 [The fgets function]

-

-
-
-
1           #include <stdio.h>
+
+
1 Synopsis
+           #include <stdio.h>
             char *fgets(char * restrict s, int n,
                  FILE * restrict stream);
     Description
 

-
-
+
 
2   The fgets function reads at most one less than the number of characters specified by n
     from the stream pointed to by stream into the array pointed to by s. No additional
     characters are read after a new-line character (which is retained) or after end-of-file. A
     null character is written immediately after the last character read into the array.
     Returns
 

-
-
+
 
3   The fgets function returns s if successful. If end-of-file is encountered and no
     characters have been read into the array, the contents of the array remain unchanged and a
     null pointer is returned. If a read error occurs during the operation, the array contents are
     indeterminate and a null pointer is returned.
 

-
-
+
 

 
7.19.7.3 [The fputc function]

-

-
-
-
1          #include <stdio.h>
+
+
1 Synopsis
+          #include <stdio.h>
            int fputc(int c, FILE *stream);
     Description
 

-
-
+
 
2   The fputc function writes the character specified by c (converted to an unsigned
     char) to the output stream pointed to by stream, at the position indicated by the
     associated file position indicator for the stream (if defined), and advances the indicator
@@ -16843,192 +14598,160 @@ char int_p_sep_by_space
     with append mode, the character is appended to the output stream.
     Returns
 

-
-
+
 
3   The fputc function returns the character written. If a write error occurs, the error
     indicator for the stream is set and fputc returns EOF.
 

-
-
+
 

 
7.19.7.4 [The fputs function]

-

-
-
-
1          #include <stdio.h>
+
+
1 Synopsis
+          #include <stdio.h>
            int fputs(const char * restrict s,
                 FILE * restrict stream);
     Description
 

-
-
+
 
2   The fputs function writes the string pointed to by s to the stream pointed to by
     stream. The terminating null character is not written.
     Returns
 

-
-
+
 
3   The fputs function returns EOF if a write error occurs; otherwise it returns a
     nonnegative value.
 

-
-
+
 

 
7.19.7.5 [The getc function]

-

-
-
-
1          #include <stdio.h>
+
+
1 Synopsis
+          #include <stdio.h>
            int getc(FILE *stream);
     Description
 

-
-
+
 
2   The getc function is equivalent to fgetc, except that if it is implemented as a macro, it
     may evaluate stream more than once, so the argument should never be an expression
     with side effects.
 
     Returns
 

-
-
+
 
3   The getc function returns the next character from the input stream pointed to by
     stream. If the stream is at end-of-file, the end-of-file indicator for the stream is set and
     getc returns EOF. If a read error occurs, the error indicator for the stream is set and
     getc returns EOF.
 

-
-
+
 

 
7.19.7.6 [The getchar function]

-

-
-
-
1          #include <stdio.h>
+
+
1 Synopsis
+          #include <stdio.h>
            int getchar(void);
     Description
 

-
-
+
 
2   The getchar function is equivalent to getc with the argument stdin.
     Returns
 

-
-
+
 
3   The getchar function returns the next character from the input stream pointed to by
     stdin. If the stream is at end-of-file, the end-of-file indicator for the stream is set and
     getchar returns EOF. If a read error occurs, the error indicator for the stream is set and
     getchar returns EOF.
 

-
-
+
 

 
7.19.7.7 [The gets function]

-

-
-
-
1          #include <stdio.h>
+
+
1 Synopsis
+          #include <stdio.h>
            char *gets(char *s);
     Description
 

-
-
+
 
2   The gets function reads characters from the input stream pointed to by stdin, into the
     array pointed to by s, until end-of-file is encountered or a new-line character is read.
     Any new-line character is discarded, and a null character is written immediately after the
     last character read into the array.
     Returns
 

-
-
+
 
3   The gets function returns s if successful. If end-of-file is encountered and no
     characters have been read into the array, the contents of the array remain unchanged and a
     null pointer is returned. If a read error occurs during the operation, the array contents are
     indeterminate and a null pointer is returned.
-    Forward references: future library directions (7.26.9).
+    Forward references: future library directions (7.26.9).
 
 

-
-
+
 

 
7.19.7.8 [The putc function]

-

-
-
-
1          #include <stdio.h>
+
+
1 Synopsis
+          #include <stdio.h>
            int putc(int c, FILE *stream);
     Description
 

-
-
+
 
2   The putc function is equivalent to fputc, except that if it is implemented as a macro, it
     may evaluate stream more than once, so that argument should never be an expression
     with side effects.
     Returns
 

-
-
+
 
3   The putc function returns the character written. If a write error occurs, the error
     indicator for the stream is set and putc returns EOF.
 

-
-
+
 

 
7.19.7.9 [The putchar function]

-

-
-
-
1          #include <stdio.h>
+
+
1 Synopsis
+          #include <stdio.h>
            int putchar(int c);
     Description
 

-
-
+
 
2   The putchar function is equivalent to putc with the second argument stdout.
     Returns
 

-
-
+
 
3   The putchar function returns the character written. If a write error occurs, the error
     indicator for the stream is set and putchar returns EOF.
 

-
-
+
 

 
7.19.7.10 [The puts function]

-

-
-
-
1          #include <stdio.h>
+
+
1 Synopsis
+          #include <stdio.h>
            int puts(const char *s);
     Description
 

-
-
+
 
2   The puts function writes the string pointed to by s to the stream pointed to by stdout,
     and appends a new-line character to the output. The terminating null character is not
     written.
     Returns
 

-
-
+
 
3   The puts function returns EOF if a write error occurs; otherwise it returns a nonnegative
     value.
 
 

-
-
+
 

 
7.19.7.11 [The ungetc function]

-

-
-
-
1            #include <stdio.h>
+
+
1 Synopsis
+            #include <stdio.h>
              int ungetc(int c, FILE *stream);
     Description
 

-
-
+
 
2   The ungetc function pushes the character specified by c (converted to an unsigned
     char) back onto the input stream pointed to by stream. Pushed-back characters will be
     returned by subsequent reads on that stream in the reverse order of their pushing. A
@@ -17036,19 +14759,16 @@ char int_p_sep_by_space
     function (fseek, fsetpos, or rewind) discards any pushed-back characters for the
     stream. The external storage corresponding to the stream is unchanged.
 

-
-
+
 
3   One character of pushback is guaranteed. If the ungetc function is called too many
     times on the same stream without an intervening read or file positioning operation on that
     stream, the operation may fail.
 

-
-
+
 
4   If the value of c equals that of the macro EOF, the operation fails and the input stream is
     unchanged.
 

-
-
+
 
5   A successful call to the ungetc function clears the end-of-file indicator for the stream.
     The value of the file position indicator for the stream after reading or discarding all
     pushed-back characters shall be the same as it was before the characters were pushed
@@ -17056,40 +14776,33 @@ char int_p_sep_by_space
     ungetc function is unspecified until all pushed-back characters are read or discarded.
     For a binary stream, its file position indicator is decremented by each successful call to
     the ungetc function; if its value was zero before a call, it is indeterminate after the
-    call.256)
+    call.[256]
     Returns
 

-
 
-
Footnote 256) See ``future library directions'' (7.26.9).
+
Footnote 256) See ``future library directions'' (7.26.9).
 

 
-
+
 
6   The ungetc function returns the character pushed back after conversion, or EOF if the
     operation fails.
-    Forward references: file positioning functions (7.19.9).
+    Forward references: file positioning functions (7.19.9).
 

-
-
+
 

 
7.19.8 [Direct input/output functions]

-
 Direct input/output functions
-

-
-
+
 

 
7.19.8.1 [The fread function]

-

-
-
-
1          #include <stdio.h>
+
+
1 Synopsis
+          #include <stdio.h>
            size_t fread(void * restrict ptr,
                 size_t size, size_t nmemb,
                 FILE * restrict stream);
     Description
 

-
-
+
 
2   The fread function reads, into the array pointed to by ptr, up to nmemb elements
     whose size is specified by size, from the stream pointed to by stream. For each
     object, size calls are made to the fgetc function and the results stored, in the order
@@ -17099,28 +14812,24 @@ char int_p_sep_by_space
     indeterminate. If a partial element is read, its value is indeterminate.
     Returns
 

-
-
+
 
3   The fread function returns the number of elements successfully read, which may be
     less than nmemb if a read error or end-of-file is encountered. If size or nmemb is zero,
     fread returns zero and the contents of the array and the state of the stream remain
     unchanged.
 

-
-
+
 

 
7.19.8.2 [The fwrite function]

-

-
-
-
1          #include <stdio.h>
+
+
1 Synopsis
+          #include <stdio.h>
            size_t fwrite(const void * restrict ptr,
                 size_t size, size_t nmemb,
                 FILE * restrict stream);
     Description
 

-
-
+
 
2   The fwrite function writes, from the array pointed to by ptr, up to nmemb elements
     whose size is specified by size, to the stream pointed to by stream. For each object,
     size calls are made to the fputc function, taking the values (in order) from an array of
@@ -17131,132 +14840,109 @@ char int_p_sep_by_space
 
     Returns
 

-
-
+
 
3   The fwrite function returns the number of elements successfully written, which will be
     less than nmemb only if a write error is encountered. If size or nmemb is zero,
     fwrite returns zero and the state of the stream remains unchanged.
 

-
-
+
 

 
7.19.9 [File positioning functions]

-
 File positioning functions
-

-
-
+
 

 
7.19.9.1 [The fgetpos function]

-

-
-
-
1          #include <stdio.h>
+
+
1 Synopsis
+          #include <stdio.h>
            int fgetpos(FILE * restrict stream,
                 fpos_t * restrict pos);
     Description
 

-
-
+
 
2   The fgetpos function stores the current values of the parse state (if any) and file
     position indicator for the stream pointed to by stream in the object pointed to by pos.
     The values stored contain unspecified information usable by the fsetpos function for
     repositioning the stream to its position at the time of the call to the fgetpos function.
     Returns
 

-
-
+
 
3   If successful, the fgetpos function returns zero; on failure, the fgetpos function
     returns nonzero and stores an implementation-defined positive value in errno.
-    Forward references: the fsetpos function (7.19.9.3).
+    Forward references: the fsetpos function (7.19.9.3).
 

-
-
+
 

 
7.19.9.2 [The fseek function]

-

-
-
-
1          #include <stdio.h>
+
+
1 Synopsis
+          #include <stdio.h>
            int fseek(FILE *stream, long int offset, int whence);
     Description
 

-
-
+
 
2   The fseek function sets the file position indicator for the stream pointed to by stream.
     If a read or write error occurs, the error indicator for the stream is set and fseek fails.
 

-
-
+
 
3   For a binary stream, the new position, measured in characters from the beginning of the
     file, is obtained by adding offset to the position specified by whence. The specified
     position is the beginning of the file if whence is SEEK_SET, the current value of the file
     position indicator if SEEK_CUR, or end-of-file if SEEK_END. A binary stream need not
     meaningfully support fseek calls with a whence value of SEEK_END.
 

-
-
+
 
4   For a text stream, either offset shall be zero, or offset shall be a value returned by
     an earlier successful call to the ftell function on a stream associated with the same file
     and whence shall be SEEK_SET.
 

-
-
+
 
5   After determining the new position, a successful call to the fseek function undoes any
     effects of the ungetc function on the stream, clears the end-of-file indicator for the
     stream, and then establishes the new position. After a successful fseek call, the next
     operation on an update stream may be either input or output.
     Returns
 

-
-
+
 
6   The fseek function returns nonzero only for a request that cannot be satisfied.
-    Forward references: the ftell function (7.19.9.4).
+    Forward references: the ftell function (7.19.9.4).
 

-
-
+
 

 
7.19.9.3 [The fsetpos function]

-

-
-
-
1          #include <stdio.h>
+
+
1 Synopsis
+          #include <stdio.h>
            int fsetpos(FILE *stream, const fpos_t *pos);
     Description
 

-
-
+
 
2   The fsetpos function sets the mbstate_t object (if any) and file position indicator
     for the stream pointed to by stream according to the value of the object pointed to by
     pos, which shall be a value obtained from an earlier successful call to the fgetpos
     function on a stream associated with the same file. If a read or write error occurs, the
     error indicator for the stream is set and fsetpos fails.
 

-
-
+
 
3   A successful call to the fsetpos function undoes any effects of the ungetc function
     on the stream, clears the end-of-file indicator for the stream, and then establishes the new
     parse state and position. After a successful fsetpos call, the next operation on an
     update stream may be either input or output.
     Returns
 

-
-
+
 
4   If successful, the fsetpos function returns zero; on failure, the fsetpos function
     returns nonzero and stores an implementation-defined positive value in errno.
 

-
-
+
 

 
7.19.9.4 [The ftell function]

-

-
-
-
1          #include <stdio.h>
+
+
1 Synopsis
+          #include <stdio.h>
            long int ftell(FILE *stream);
     Description
 

-
-
+
 
2   The ftell function obtains the current value of the file position indicator for the stream
     pointed to by stream. For a binary stream, the value is the number of characters from
     the beginning of the file. For a text stream, its file position indicator contains unspecified
@@ -17266,118 +14952,95 @@ char int_p_sep_by_space
     or read.
     Returns
 

-
-
+
 
3   If successful, the ftell function returns the current value of the file position indicator
     for the stream. On failure, the ftell function returns -1L and stores an
     implementation-defined positive value in errno.
 

-
-
+
 

 
7.19.9.5 [The rewind function]

-

-
-
-
1          #include <stdio.h>
+
+
1 Synopsis
+          #include <stdio.h>
            void rewind(FILE *stream);
     Description
 

-
-
+
 
2   The rewind function sets the file position indicator for the stream pointed to by
     stream to the beginning of the file. It is equivalent to
            (void)fseek(stream, 0L, SEEK_SET)
     except that the error indicator for the stream is also cleared.
     Returns
 

-
-
+
 
3   The rewind function returns no value.
 

-
-
+
 

 
7.19.10 [Error-handling functions]

-
 Error-handling functions
-

-
-
+
 

 
7.19.10.1 [The clearerr function]

-

-
-
-
1          #include <stdio.h>
+
+
1 Synopsis
+          #include <stdio.h>
            void clearerr(FILE *stream);
     Description
 

-
-
+
 
2   The clearerr function clears the end-of-file and error indicators for the stream pointed
     to by stream.
     Returns
 

-
-
+
 
3   The clearerr function returns no value.
 
 

-
-
+
 

 
7.19.10.2 [The feof function]

-

-
-
-
1          #include <stdio.h>
+
+
1 Synopsis
+          #include <stdio.h>
            int feof(FILE *stream);
     Description
 

-
-
+
 
2   The feof function tests the end-of-file indicator for the stream pointed to by stream.
     Returns
 

-
-
+
 
3   The feof function returns nonzero if and only if the end-of-file indicator is set for
     stream.
 

-
-
+
 

 
7.19.10.3 [The ferror function]

-

-
-
-
1          #include <stdio.h>
+
+
1 Synopsis
+          #include <stdio.h>
            int ferror(FILE *stream);
     Description
 

-
-
+
 
2   The ferror function tests the error indicator for the stream pointed to by stream.
     Returns
 

-
-
+
 
3   The ferror function returns nonzero if and only if the error indicator is set for
     stream.
 

-
-
+
 

 
7.19.10.4 [The perror function]

-

-
-
-
1          #include <stdio.h>
+
+
1 Synopsis
+          #include <stdio.h>
            void perror(const char *s);
     Description
 

-
-
+
 
2   The perror function maps the error number in the integer expression errno to an
     error message. It writes a sequence of characters to the standard error stream thus: first
     (if s is not a null pointer and the character pointed to by s is not the null character), the
@@ -17386,28 +15049,23 @@ char int_p_sep_by_space
     strings are the same as those returned by the strerror function with argument errno.
     Returns
 

-
-
+
 
3   The perror function returns no value.
-    Forward references: the strerror function (7.21.6.2).
+    Forward references: the strerror function (7.21.6.2).
 

-
-
+
 

-
7.20 [General utilities ]

-

-
-
+
7.20 [General utilities <stdlib.h>]

+
 
1   The header <stdlib.h> declares five types and several functions of general utility, and
-    defines several macros.257)
+    defines several macros.[257]
 

-
 
-
Footnote 257) See ``future library directions'' (7.26.10).
+
Footnote 257) See ``future library directions'' (7.26.10).
 

 
-
-
2   The types declared are size_t and wchar_t (both described in 7.17),
+
+
2   The types declared are size_t and wchar_t (both described in 7.17),
              div_t
     which is a structure type that is the type of the value returned by the div function,
              ldiv_t
@@ -17415,9 +15073,8 @@ char int_p_sep_by_space
              lldiv_t
     which is a structure type that is the type of the value returned by the lldiv function.
 

-
-
-
3   The macros defined are NULL (described in 7.17);
+
+
3   The macros defined are NULL (described in 7.17);
              EXIT_FAILURE
     and
              EXIT_SUCCESS
@@ -17432,55 +15089,45 @@ char int_p_sep_by_space
     number of bytes in a multibyte character for the extended character set specified by the
     current locale (category LC_CTYPE), which is never greater than MB_LEN_MAX.
 

-
-
+
 

 
7.20.1 [Numeric conversion functions]

-

-
-
+
 
1   The functions atof, atoi, atol, and atoll need not affect the value of the integer
     expression errno on an error. If the value of the result cannot be represented, the
     behavior is undefined.
 

-
-
+
 

 
7.20.1.1 [The atof function]

-

-
-
-
1          #include <stdlib.h>
+
+
1 Synopsis
+          #include <stdlib.h>
            double atof(const char *nptr);
     Description
 

-
-
+
 
2   The atof function converts the initial portion of the string pointed to by nptr to
     double representation. Except for the behavior on error, it is equivalent to
            strtod(nptr, (char **)NULL)
     Returns
 

-
-
+
 
3   The atof function returns the converted value.
-    Forward references: the strtod, strtof, and strtold functions (7.20.1.3).
+    Forward references: the strtod, strtof, and strtold functions (7.20.1.3).
 

-
-
+
 

 
7.20.1.2 [The atoi, atol, and atoll functions]

-

-
-
-
1          #include <stdlib.h>
+
+
1 Synopsis
+          #include <stdlib.h>
            int atoi(const char *nptr);
            long int atol(const char *nptr);
            long long int atoll(const char *nptr);
     Description
 

-
-
+
 
2   The atoi, atol, and atoll functions convert the initial portion of the string pointed
     to by nptr to int, long int, and long long int representation, respectively.
     Except for the behavior on error, they are equivalent to
@@ -17489,20 +15136,17 @@ char int_p_sep_by_space
            atoll: strtoll(nptr, (char **)NULL, 10)
     Returns
 

-
-
+
 
3   The atoi, atol, and atoll functions return the converted value.
     Forward references: the strtol, strtoll, strtoul, and strtoull functions
-    (7.20.1.4).
+    (7.20.1.4).
 

-
-
+
 

 
7.20.1.3 [The strtod, strtof, and strtold functions]

-

-
-
-
1          #include <stdlib.h>
+
+
1 Synopsis
+          #include <stdlib.h>
            double strtod(const char * restrict nptr,
                 char ** restrict endptr);
            float strtof(const char * restrict nptr,
@@ -17511,8 +15155,7 @@ char int_p_sep_by_space
                 char ** restrict endptr);
     Description
 

-
-
+
 
2   The strtod, strtof, and strtold functions convert the initial portion of the string
     pointed to by nptr to double, float, and long double representation,
     respectively. First, they decompose the input string into three parts: an initial, possibly
@@ -17522,14 +15165,13 @@ char int_p_sep_by_space
     character of the input string. Then, they attempt to convert the subject sequence to a
     floating-point number, and return the result.
 

-
-
+
 
3   The expected form of the subject sequence is an optional plus or minus sign, then one of
     the following:
     -- a nonempty sequence of decimal digits optionally containing a decimal-point
-       character, then an optional exponent part as defined in 6.4.4.2;
+       character, then an optional exponent part as defined in 6.4.4.2;
     -- a 0x or 0X, then a nonempty sequence of hexadecimal digits optionally containing a
-       decimal-point character, then an optional binary exponent part as defined in 6.4.4.2;
+       decimal-point character, then an optional binary exponent part as defined in 6.4.4.2;
     -- INF or INFINITY, ignoring case
     -- NAN or NAN(n-char-sequenceopt), ignoring case in the NAN part, where:
                n-char-sequence:
@@ -17541,28 +15183,26 @@ char int_p_sep_by_space
     starting with the first non-white-space character, that is of the expected form. The subject
     sequence contains no characters if the input string is not of the expected form.
 

-
-
+
 
4   If the subject sequence has the expected form for a floating-point number, the sequence of
     characters starting with the first digit or the decimal-point character (whichever occurs
-    first) is interpreted as a floating constant according to the rules of 6.4.4.2, except that the
+    first) is interpreted as a floating constant according to the rules of 6.4.4.2, except that the
     decimal-point character is used in place of a period, and that if neither an exponent part
     nor a decimal-point character appears in a decimal floating point number, or if a binary
     exponent part does not appear in a hexadecimal floating point number, an exponent part
     of the appropriate type with value zero is assumed to follow the last digit in the string. If
-    the subject sequence begins with a minus sign, the sequence is interpreted as negated.258)
+    the subject sequence begins with a minus sign, the sequence is interpreted as negated.[258]
     A character sequence INF or INFINITY is interpreted as an infinity, if representable in
     the return type, else like a floating constant that is too large for the range of the return
     type. A character sequence NAN or NAN(n-char-sequenceopt), is interpreted as a quiet
     NaN, if supported in the return type, else like a subject sequence part that does not have
-    the expected form; the meaning of the n-char sequences is implementation-defined.259) A
+    the expected form; the meaning of the n-char sequences is implementation-defined.[259] A
     pointer to the final string is stored in the object pointed to by endptr, provided that
     endptr is not a null pointer.
 

-
 
 
Footnote 258) It is unspecified whether a minus-signed sequence is converted to a negative number directly or by
-         negating the value resulting from converting the corresponding unsigned sequence (see F.5); the two
+         negating the value resulting from converting the corresponding unsigned sequence (see F.5); the two
          methods may yield different results if rounding is toward positive or negative infinity. In either case,
          the functions honor the sign of zero if floating-point arithmetic supports signed zeros.
 

@@ -17570,34 +15210,33 @@ char int_p_sep_by_space
 
 
Footnote 259) An implementation may use the n-char sequence to determine extra information to be represented in
          the NaN's significand.
+     stipulation that the error with respect to D should have a correct sign for the current
+     rounding direction.260)
+     Returns
 

 
-
+
 
5   If the subject sequence has the hexadecimal form and FLT_RADIX is a power of 2, the
     value resulting from the conversion is correctly rounded.
 

-
-
+
 
6   In other than the "C" locale, additional locale-specific subject sequence forms may be
     accepted.
 

-
-
+
 
7   If the subject sequence is empty or does not have the expected form, no conversion is
     performed; the value of nptr is stored in the object pointed to by endptr, provided
     that endptr is not a null pointer.
     Recommended practice
 

-
-
+
 
8   If the subject sequence has the hexadecimal form, FLT_RADIX is not a power of 2, and
     the result is not exactly representable, the result should be one of the two numbers in the
     appropriate internal format that are adjacent to the hexadecimal floating source value,
     with the extra stipulation that the error should have a correct sign for the current rounding
     direction.
 

-
-
+
 
9   If the subject sequence has the decimal form and at most DECIMAL_DIG (defined in
     <float.h>) significant digits, the result should be correctly rounded. If the subject
     sequence D has the decimal form and more than DECIMAL_DIG significant digits,
@@ -17605,33 +15244,22 @@ char int_p_sep_by_space
     DECIMAL_DIG significant digits, such that the values of L , D, and U satisfy L  D  U .
     The result should be one of the (equal or adjacent) values that would be obtained by
     correctly rounding L and U according to the current rounding direction, with the extra
-     stipulation that the error with respect to D should have a correct sign for the current
-     rounding direction.260)
-     Returns
 

-
-
-
Footnote 260) DECIMAL_DIG, defined in <float.h>, should be sufficiently large that L and U will usually round
-          to the same internal floating value, but if not will round to adjacent values.
-

-
-
+
 
10   The functions return the converted value, if any. If no conversion could be performed,
      zero is returned. If the correct value is outside the range of representable values, plus or
      minus HUGE_VAL, HUGE_VALF, or HUGE_VALL is returned (according to the return
      type and sign of the value), and the value of the macro ERANGE is stored in errno. If
-     the result underflows (7.12.1), the functions return a value whose magnitude is no greater
+     the result underflows (7.12.1), the functions return a value whose magnitude is no greater
      than the smallest normalized positive number in the return type; whether errno acquires
      the value ERANGE is implementation-defined.
 

-
-
+
 

 
7.20.1.4 [The strtol, strtoll, strtoul, and strtoull functions]

-

-
-
-
1            #include <stdlib.h>
+
+
1 Synopsis
+            #include <stdlib.h>
              long int strtol(
                   const char * restrict nptr,
                   char ** restrict endptr,
@@ -17650,22 +15278,16 @@ char int_p_sep_by_space
                   int base);
      Description
 

-
-
+
 
2    The strtol, strtoll, strtoul, and strtoull functions convert the initial
      portion of the string pointed to by nptr to long int, long long int, unsigned
      long int, and unsigned long long int representation, respectively. First,
      they decompose the input string into three parts: an initial, possibly empty, sequence of
      white-space characters (as specified by the isspace function), a subject sequence
-    resembling an integer represented in some radix determined by the value of base, and a
-    final string of one or more unrecognized characters, including the terminating null
-    character of the input string. Then, they attempt to convert the subject sequence to an
-    integer, and return the result.
 

-
-
+
 
3   If the value of base is zero, the expected form of the subject sequence is that of an
-    integer constant as described in 6.4.4.1, optionally preceded by a plus or minus sign, but
+    integer constant as described in 6.4.4.1, optionally preceded by a plus or minus sign, but
     not including an integer suffix. If the value of base is between 2 and 36 (inclusive), the
     expected form of the subject sequence is a sequence of letters and digits representing an
     integer with the radix specified by base, optionally preceded by a plus or minus sign,
@@ -17674,38 +15296,33 @@ char int_p_sep_by_space
     than that of base are permitted. If the value of base is 16, the characters 0x or 0X may
     optionally precede the sequence of letters and digits, following the sign if present.
 

-
-
+
 
4   The subject sequence is defined as the longest initial subsequence of the input string,
     starting with the first non-white-space character, that is of the expected form. The subject
     sequence contains no characters if the input string is empty or consists entirely of white
     space, or if the first non-white-space character is other than a sign or a permissible letter
     or digit.
 

-
-
+
 
5   If the subject sequence has the expected form and the value of base is zero, the sequence
     of characters starting with the first digit is interpreted as an integer constant according to
-    the rules of 6.4.4.1. If the subject sequence has the expected form and the value of base
+    the rules of 6.4.4.1. If the subject sequence has the expected form and the value of base
     is between 2 and 36, it is used as the base for conversion, ascribing to each letter its value
     as given above. If the subject sequence begins with a minus sign, the value resulting from
     the conversion is negated (in the return type). A pointer to the final string is stored in the
     object pointed to by endptr, provided that endptr is not a null pointer.
 

-
-
+
 
6   In other than the "C" locale, additional locale-specific subject sequence forms may be
     accepted.
 

-
-
+
 
7   If the subject sequence is empty or does not have the expected form, no conversion is
     performed; the value of nptr is stored in the object pointed to by endptr, provided
     that endptr is not a null pointer.
     Returns
 

-
-
+
 
8   The strtol, strtoll, strtoul, and strtoull functions return the converted
     value, if any. If no conversion could be performed, zero is returned. If the correct value
     is outside the range of representable values, LONG_MIN, LONG_MAX, LLONG_MIN,
@@ -17713,72 +15330,57 @@ char int_p_sep_by_space
     and sign of the value, if any), and the value of the macro ERANGE is stored in errno.
 
 

-
-
+
 

 
7.20.2 [Pseudo-random sequence generation functions]

-
 Pseudo-random sequence generation functions
-

-
-
+
 

 
7.20.2.1 [The rand function]

-

-
-
-
1          #include <stdlib.h>
+
+
1 Synopsis
+          #include <stdlib.h>
            int rand(void);
     Description
 

-
-
+
 
2   The rand function computes a sequence of pseudo-random integers in the range 0 to
     RAND_MAX.
 

-
-
+
 
3   The implementation shall behave as if no library function calls the rand function.
     Returns
 

-
-
+
 
4   The rand function returns a pseudo-random integer.
     Environmental limits
 

-
-
+
 
5   The value of the RAND_MAX macro shall be at least 32767.
 

-
-
+
 

 
7.20.2.2 [The srand function]

-

-
-
-
1          #include <stdlib.h>
+
+
1 Synopsis
+          #include <stdlib.h>
            void srand(unsigned int seed);
     Description
 

-
-
+
 
2   The srand function uses the argument as a seed for a new sequence of pseudo-random
     numbers to be returned by subsequent calls to rand. If srand is then called with the
     same seed value, the sequence of pseudo-random numbers shall be repeated. If rand is
     called before any calls to srand have been made, the same sequence shall be generated
     as when srand is first called with a seed value of 1.
 

-
-
+
 
3   The implementation shall behave as if no library function calls the srand function.
     Returns
 

-
-
+
 
4   The srand function returns no value.
 

-
-
+
 
5   EXAMPLE       The following functions define a portable implementation of rand and srand.
            static unsigned long int next = 1;
            int rand(void)   // RAND_MAX assumed to be 32767
@@ -17792,13 +15394,10 @@ char int_p_sep_by_space
             }
 
 

-
-
+
 

 
7.20.3 [Memory management functions]

-

-
-
+
 
1   The order and contiguity of storage allocated by successive calls to the calloc,
     malloc, and realloc functions is unspecified. The pointer returned if the allocation
     succeeds is suitably aligned so that it may be assigned to a pointer to any type of object
@@ -17811,98 +15410,82 @@ char int_p_sep_by_space
     defined: either a null pointer is returned, or the behavior is as if the size were some
     nonzero value, except that the returned pointer shall not be used to access an object.
 

-
-
+
 

 
7.20.3.1 [The calloc function]

-

-
-
-
1           #include <stdlib.h>
+
+
1 Synopsis
+           #include <stdlib.h>
             void *calloc(size_t nmemb, size_t size);
     Description
 

-
-
+
 
2   The calloc function allocates space for an array of nmemb objects, each of whose size
-    is size. The space is initialized to all bits zero.261)
+    is size. The space is initialized to all bits zero.[261]
     Returns
 

-
 
 
Footnote 261) Note that this need not be the same as the representation of floating-point zero or a null pointer
          constant.
-

-
-
-
3   The calloc function returns either a null pointer or a pointer to the allocated space.
-

-
-
-

-
7.20.3.2 [The free function]

-

-
-
-
1           #include <stdlib.h>
-            void free(void *ptr);
-    Description
-

-
-
-
2   The free function causes the space pointed to by ptr to be deallocated, that is, made
-    available for further allocation. If ptr is a null pointer, no action occurs. Otherwise, if
-    the argument does not match a pointer earlier returned by the calloc, malloc, or
     realloc function, or if the space has been deallocated by a call to free or realloc,
     the behavior is undefined.
     Returns
-

+

 
-
+
+
3   The calloc function returns either a null pointer or a pointer to the allocated space.
+

+
+

+
7.20.3.2 [The free function]

+
+
1 Synopsis
+           #include <stdlib.h>
+            void free(void *ptr);
+    Description
+

+
+
2   The free function causes the space pointed to by ptr to be deallocated, that is, made
+    available for further allocation. If ptr is a null pointer, no action occurs. Otherwise, if
+    the argument does not match a pointer earlier returned by the calloc, malloc, or
+

+
 
3   The free function returns no value.
 

-
-
+
 

 
7.20.3.3 [The malloc function]

-

-
-
-
1          #include <stdlib.h>
+
+
1 Synopsis
+          #include <stdlib.h>
            void *malloc(size_t size);
     Description
 

-
-
+
 
2   The malloc function allocates space for an object whose size is specified by size and
     whose value is indeterminate.
     Returns
 

-
-
+
 
3   The malloc function returns either a null pointer or a pointer to the allocated space.
 

-
-
+
 

 
7.20.3.4 [The realloc function]

-

-
-
-
1          #include <stdlib.h>
+
+
1 Synopsis
+          #include <stdlib.h>
            void *realloc(void *ptr, size_t size);
     Description
 

-
-
+
 
2   The realloc function deallocates the old object pointed to by ptr and returns a
     pointer to a new object that has the size specified by size. The contents of the new
     object shall be the same as that of the old object prior to deallocation, up to the lesser of
     the new and old sizes. Any bytes in the new object beyond the size of the old object have
     indeterminate values.
 

-
-
+
 
3   If ptr is a null pointer, the realloc function behaves like the malloc function for the
     specified size. Otherwise, if ptr does not match a pointer earlier returned by the
     calloc, malloc, or realloc function, or if the space has been deallocated by a call
@@ -17910,32 +15493,25 @@ char int_p_sep_by_space
     object cannot be allocated, the old object is not deallocated and its value is unchanged.
     Returns
 

-
-
+
 
4   The realloc function returns a pointer to the new object (which may have the same
     value as a pointer to the old object), or a null pointer if the new object could not be
     allocated.
 
 

-
-
+
 

 
7.20.4 [Communication with the environment]

-
 Communication with the environment
-

-
-
+
 

 
7.20.4.1 [The abort function]

-

-
-
-
1          #include <stdlib.h>
+
+
1 Synopsis
+          #include <stdlib.h>
            void abort(void);
     Description
 

-
-
+
 
2   The abort function causes abnormal program termination to occur, unless the signal
     SIGABRT is being caught and the signal handler does not return. Whether open streams
     with unwritten buffered data are flushed, open streams are closed, or temporary files are
@@ -17944,73 +15520,61 @@ char int_p_sep_by_space
     call raise(SIGABRT).
     Returns
 

-
-
+
 
3   The abort function does not return to its caller.
 

-
-
+
 

 
7.20.4.2 [The atexit function]

-

-
-
-
1          #include <stdlib.h>
+
+
1 Synopsis
+          #include <stdlib.h>
            int atexit(void (*func)(void));
     Description
 

-
-
+
 
2   The atexit function registers the function pointed to by func, to be called without
     arguments at normal program termination.
     Environmental limits
 

-
-
+
 
3   The implementation shall support the registration of at least 32 functions.
     Returns
 

-
-
+
 
4   The atexit function returns zero if the registration succeeds, nonzero if it fails.
-    Forward references: the exit function (7.20.4.3).
+    Forward references: the exit function (7.20.4.3).
 

-
-
+
 

 
7.20.4.3 [The exit function]

-

-
-
-
1          #include <stdlib.h>
+
+
1 Synopsis
+          #include <stdlib.h>
            void exit(int status);
     Description
 

-
-
+
 
2   The exit function causes normal program termination to occur. If more than one call to
     the exit function is executed by a program, the behavior is undefined.
 

-
-
+
 
3   First, all functions registered by the atexit function are called, in the reverse order of
-    their registration,262) except that a function is called after any previously registered
+    their registration,[262] except that a function is called after any previously registered
     functions that had already been called at the time it was registered. If, during the call to
     any such function, a call to the longjmp function is made that would terminate the call
     to the registered function, the behavior is undefined.
 

-
 
 
Footnote 262) Each function is called as many times as it was registered, and in the correct order with respect to
          other registered functions.
 

 
-
+
 
4   Next, all open streams with unwritten buffered data are flushed, all open streams are
     closed, and all files created by the tmpfile function are removed.
 

-
-
+
 
5   Finally, control is returned to the host environment. If the value of status is zero or
     EXIT_SUCCESS, an implementation-defined form of the status successful termination is
     returned. If the value of status is EXIT_FAILURE, an implementation-defined form
@@ -18018,77 +15582,64 @@ char int_p_sep_by_space
     implementation-defined.
     Returns
 

-
-
+
 
6   The exit function cannot return to its caller.
 

-
-
+
 

 
7.20.4.4 [The _Exit function]

-

-
-
-
1           #include <stdlib.h>
+
+
1 Synopsis
+           #include <stdlib.h>
             void _Exit(int status);
     Description
 

-
-
+
 
2   The _Exit function causes normal program termination to occur and control to be
     returned to the host environment. No functions registered by the atexit function or
     signal handlers registered by the signal function are called. The status returned to the
-    host environment is determined in the same way as for the exit function (7.20.4.3).
+    host environment is determined in the same way as for the exit function (7.20.4.3).
     Whether open streams with unwritten buffered data are flushed, open streams are closed,
     or temporary files are removed is implementation-defined.
     Returns
 

-
-
+
 
3   The _Exit function cannot return to its caller.
 

-
-
+
 

 
7.20.4.5 [The getenv function]

-

-
-
-
1          #include <stdlib.h>
+
+
1 Synopsis
+          #include <stdlib.h>
            char *getenv(const char *name);
     Description
 

-
-
+
 
2   The getenv function searches an environment list , provided by the host environment,
     for a string that matches the string pointed to by name. The set of environment names
     and the method for altering the environment list are implementation-defined.
 

-
-
+
 
3   The implementation shall behave as if no library function calls the getenv function.
     Returns
 

-
-
+
 
4   The getenv function returns a pointer to a string associated with the matched list
     member. The string pointed to shall not be modified by the program, but may be
     overwritten by a subsequent call to the getenv function. If the specified name cannot
     be found, a null pointer is returned.
 

-
-
+
 

 
7.20.4.6 [The system function]

-

-
-
-
1          #include <stdlib.h>
+
+
1 Synopsis
+          #include <stdlib.h>
            int system(const char *string);
     Description
 

-
-
+
 
2   If string is a null pointer, the system function determines whether the host
     environment has a command processor . If string is not a null pointer, the system
     function passes the string pointed to by string to that command processor to be
@@ -18096,263 +15647,222 @@ char int_p_sep_by_space
     program calling system to behave in a non-conforming manner or to terminate.
     Returns
 

-
-
+
 
3   If the argument is a null pointer, the system function returns nonzero only if a
     command processor is available. If the argument is not a null pointer, and the system
     function does return, it returns an implementation-defined value.
 
 

-
-
+
 

 
7.20.5 [Searching and sorting utilities]

-

-
-
+
 
1   These utilities make use of a comparison function to search or sort arrays of unspecified
     type. Where an argument declared as size_t nmemb specifies the length of the array
     for a function, nmemb can have the value zero on a call to that function; the comparison
     function is not called, a search finds no matching element, and sorting performs no
     rearrangement. Pointer arguments on such a call shall still have valid values, as described
-    in 7.1.4.
+    in 7.1.4.
 

-
-
+
 
2   The implementation shall ensure that the second argument of the comparison function
     (when called from bsearch), or both arguments (when called from qsort), are
-    pointers to elements of the array.263) The first argument when called from bsearch
+    pointers to elements of the array.[263] The first argument when called from bsearch
     shall equal key.
 

-
 
 
Footnote 263) That is, if the value passed is p, then the following expressions are always nonzero:
                   ((char *)p - (char *)base) % size == 0
                   (char *)p >= (char *)base
                   (char *)p < (char *)base + nmemb * size
+    size of each element of the array is specified by size.
 

 
-
+
 
3   The comparison function shall not alter the contents of the array. The implementation
     may reorder elements of the array between calls to the comparison function, but shall not
     alter the contents of any individual element.
 

-
-
+
 
4   When the same objects (consisting of size bytes, irrespective of their current positions
     in the array) are passed more than once to the comparison function, the results shall be
     consistent with one another. That is, for qsort they shall define a total ordering on the
     array, and for bsearch the same object shall always compare the same way with the
     key.
 

-
-
+
 
5   A sequence point occurs immediately before and immediately after each call to the
     comparison function, and also between any call to the comparison function and any
     movement of the objects passed as arguments to that call.
 

-
-
+
 

 
7.20.5.1 [The bsearch function]

-

-
-
-
1            #include <stdlib.h>
+
+
1 Synopsis
+            #include <stdlib.h>
              void *bsearch(const void *key, const void *base,
                   size_t nmemb, size_t size,
                   int (*compar)(const void *, const void *));
     Description
 

-
-
+
 
2   The bsearch function searches an array of nmemb objects, the initial element of which
     is pointed to by base, for an element that matches the object pointed to by key. The
-    size of each element of the array is specified by size.
 

-
-
+
 
3   The comparison function pointed to by compar is called with two arguments that point
     to the key object and to an array element, in that order. The function shall return an
     integer less than, equal to, or greater than zero if the key object is considered,
     respectively, to be less than, to match, or to be greater than the array element. The array
     shall consist of: all the elements that compare less than, all the elements that compare
-    equal to, and all the elements that compare greater than the key object, in that order.264)
+    equal to, and all the elements that compare greater than the key object, in that order.[264]
     Returns
 

-
 
 
Footnote 264) In practice, the entire array is sorted according to the comparison function.
 

 
-
+
 
4   The bsearch function returns a pointer to a matching element of the array, or a null
     pointer if no match is found. If two elements compare as equal, which element is
     matched is unspecified.
 

-
-
+
 

 
7.20.5.2 [The qsort function]

-

-
-
-
1            #include <stdlib.h>
+
+
1 Synopsis
+            #include <stdlib.h>
              void qsort(void *base, size_t nmemb, size_t size,
                   int (*compar)(const void *, const void *));
     Description
 

-
-
+
 
2   The qsort function sorts an array of nmemb objects, the initial element of which is
     pointed to by base. The size of each object is specified by size.
 

-
-
+
 
3   The contents of the array are sorted into ascending order according to a comparison
     function pointed to by compar, which is called with two arguments that point to the
     objects being compared. The function shall return an integer less than, equal to, or
     greater than zero if the first argument is considered to be respectively less than, equal to,
     or greater than the second.
 

-
-
+
 
4   If two elements compare as equal, their order in the resulting sorted array is unspecified.
     Returns
 

-
-
+
 
5   The qsort function returns no value.
 

-
-
+
 

 
7.20.6 [Integer arithmetic functions]

-
 Integer arithmetic functions
-

-
-
+
 

 
7.20.6.1 [The abs, labs and llabs functions]

-

-
-
-
1           #include <stdlib.h>
+
+
1 Synopsis
+           #include <stdlib.h>
             int abs(int j);
             long int labs(long int j);
             long long int llabs(long long int j);
     Description
 

-
-
+
 
2   The abs, labs, and llabs functions compute the absolute value of an integer j. If the
-    result cannot be represented, the behavior is undefined.265)
+    result cannot be represented, the behavior is undefined.[265]
     Returns
 

-
 
 
Footnote 265) The absolute value of the most negative number cannot be represented in two's complement.
 

 
-
+
 
3   The abs, labs, and llabs, functions return the absolute value.
 

-
-
+
 

 
7.20.6.2 [The div, ldiv, and lldiv functions]

-

-
-
-
1           #include <stdlib.h>
+
+
1 Synopsis
+           #include <stdlib.h>
             div_t div(int numer, int denom);
             ldiv_t ldiv(long int numer, long int denom);
             lldiv_t lldiv(long long int numer, long long int denom);
     Description
 

-
-
+
 
2   The div, ldiv, and lldiv, functions compute numer / denom and numer %
     denom in a single operation.
     Returns
 

-
-
+
 
3   The div, ldiv, and lldiv functions return a structure of type div_t, ldiv_t, and
     lldiv_t, respectively, comprising both the quotient and the remainder. The structures
     shall contain (in either order) the members quot (the quotient) and rem (the remainder),
     each of which has the same type as the arguments numer and denom. If either part of
     the result cannot be represented, the behavior is undefined.
 

-
-
+
 

 
7.20.7 [Multibyte/wide character conversion functions]

-

-
-
+
 
1   The behavior of the multibyte character functions is affected by the LC_CTYPE category
     of the current locale. For a state-dependent encoding, each function is placed into its
     initial conversion state by a call for which its character pointer argument, s, is a null
     pointer. Subsequent calls with s as other than a null pointer cause the internal conversion
     state of the function to be altered as necessary. A call with s as a null pointer causes
     these functions to return a nonzero value if encodings have state dependency, and zero
-    otherwise.266) Changing the LC_CTYPE category causes the conversion state of these
+    otherwise.[266] Changing the LC_CTYPE category causes the conversion state of these
     functions to be indeterminate.
 

-
 
 
Footnote 266) If the locale employs special bytes to change the shift state, these bytes do not produce separate wide
          character codes, but are grouped with an adjacent multibyte character.
 

 
-
+
 

 
7.20.7.1 [The mblen function]

-

-
-
-
1           #include <stdlib.h>
+
+
1 Synopsis
+           #include <stdlib.h>
             int mblen(const char *s, size_t n);
     Description
 

-
-
+
 
2   If s is not a null pointer, the mblen function determines the number of bytes contained
     in the multibyte character pointed to by s. Except that the conversion state of the
     mbtowc function is not affected, it is equivalent to
             mbtowc((wchar_t *)0, s, n);
 

-
-
+
 
3   The implementation shall behave as if no library function calls the mblen function.
     Returns
 

-
-
+
 
4   If s is a null pointer, the mblen function returns a nonzero or zero value, if multibyte
     character encodings, respectively, do or do not have state-dependent encodings. If s is
     not a null pointer, the mblen function either returns 0 (if s points to the null character),
     or returns the number of bytes that are contained in the multibyte character (if the next n
     or fewer bytes form a valid multibyte character), or returns -1 (if they do not form a valid
     multibyte character).
-    Forward references: the mbtowc function (7.20.7.2).
+    Forward references: the mbtowc function (7.20.7.2).
 

-
-
+
 

 
7.20.7.2 [The mbtowc function]

-

-
-
-
1          #include <stdlib.h>
+
+
1 Synopsis
+          #include <stdlib.h>
            int mbtowc(wchar_t * restrict pwc,
                 const char * restrict s,
                 size_t n);
     Description
 

-
-
+
 
2   If s is not a null pointer, the mbtowc function inspects at most n bytes beginning with
     the byte pointed to by s to determine the number of bytes needed to complete the next
     multibyte character (including any shift sequences). If the function determines that the
@@ -18361,13 +15871,11 @@ char int_p_sep_by_space
     the object pointed to by pwc. If the corresponding wide character is the null wide
     character, the function is left in the initial conversion state.
 

-
-
+
 
3   The implementation shall behave as if no library function calls the mbtowc function.
     Returns
 

-
-
+
 
4   If s is a null pointer, the mbtowc function returns a nonzero or zero value, if multibyte
     character encodings, respectively, do or do not have state-dependent encodings. If s is
     not a null pointer, the mbtowc function either returns 0 (if s points to the null character),
@@ -18375,24 +15883,20 @@ char int_p_sep_by_space
     the next n or fewer bytes form a valid multibyte character), or returns -1 (if they do not
     form a valid multibyte character).
 

-
-
+
 
5   In no case will the value returned be greater than n or the value of the MB_CUR_MAX
     macro.
 

-
-
+
 

 
7.20.7.3 [The wctomb function]

-

-
-
-
1          #include <stdlib.h>
+
+
1 Synopsis
+          #include <stdlib.h>
            int wctomb(char *s, wchar_t wc);
     Description
 

-
-
+
 
2   The wctomb function determines the number of bytes needed to represent the multibyte
     character corresponding to the wide character given by wc (including any shift
     sequences), and stores the multibyte character representation in the array whose first
@@ -18401,48 +15905,39 @@ char int_p_sep_by_space
     sequence needed to restore the initial shift state, and the function is left in the initial
     conversion state.
 

-
-
+
 
3   The implementation shall behave as if no library function calls the wctomb function.
     Returns
 

-
-
+
 
4   If s is a null pointer, the wctomb function returns a nonzero or zero value, if multibyte
     character encodings, respectively, do or do not have state-dependent encodings. If s is
     not a null pointer, the wctomb function returns -1 if the value of wc does not correspond
     to a valid multibyte character, or returns the number of bytes that are contained in the
     multibyte character corresponding to the value of wc.
 

-
-
+
 
5   In no case will the value returned be greater than the value of the MB_CUR_MAX macro.
 

-
-
+
 

 
7.20.8 [Multibyte/wide string conversion functions]

-

-
-
+
 
1   The behavior of the multibyte string functions is affected by the LC_CTYPE category of
     the current locale.
 

-
-
+
 

 
7.20.8.1 [The mbstowcs function]

-

-
-
-
1            #include <stdlib.h>
+
+
1 Synopsis
+            #include <stdlib.h>
              size_t mbstowcs(wchar_t * restrict pwcs,
                   const char * restrict s,
                   size_t n);
     Description
 

-
-
+
 
2   The mbstowcs function converts a sequence of multibyte characters that begins in the
     initial shift state from the array pointed to by s into a sequence of corresponding wide
     characters and stores not more than n wide characters into the array pointed to by pwcs.
@@ -18451,37 +15946,32 @@ char int_p_sep_by_space
     a call to the mbtowc function, except that the conversion state of the mbtowc function is
     not affected.
 

-
-
+
 
3   No more than n elements will be modified in the array pointed to by pwcs. If copying
     takes place between objects that overlap, the behavior is undefined.
     Returns
 

-
-
+
 
4   If an invalid multibyte character is encountered, the mbstowcs function returns
     (size_t)(-1). Otherwise, the mbstowcs function returns the number of array
-    elements modified, not including a terminating null wide character, if any.267)
+    elements modified, not including a terminating null wide character, if any.[267]
 

-
 
 
Footnote 267) The array will not be null-terminated if the value returned is n.
 

 
-
+
 

 
7.20.8.2 [The wcstombs function]

-

-
-
-
1          #include <stdlib.h>
+
+
1 Synopsis
+          #include <stdlib.h>
            size_t wcstombs(char * restrict s,
                 const wchar_t * restrict pwcs,
                 size_t n);
     Description
 

-
-
+
 
2   The wcstombs function converts a sequence of wide characters from the array pointed
     to by pwcs into a sequence of corresponding multibyte characters that begins in the
     initial shift state, and stores these multibyte characters into the array pointed to by s,
@@ -18489,107 +15979,87 @@ char int_p_sep_by_space
     character is stored. Each wide character is converted as if by a call to the wctomb
     function, except that the conversion state of the wctomb function is not affected.
 

-
-
+
 
3   No more than n bytes will be modified in the array pointed to by s. If copying takes place
     between objects that overlap, the behavior is undefined.
     Returns
 

-
-
+
 
4   If a wide character is encountered that does not correspond to a valid multibyte character,
     the wcstombs function returns (size_t)(-1). Otherwise, the wcstombs function
     returns the number of bytes modified, not including a terminating null character, if
-    any.267)
+    any.[267]
 
 

-
 
 
Footnote 267) The array will not be null-terminated if the value returned is n.
 

 
-
+
 

-
7.21 [String handling ]

-
 String handling 
-

-
-
+
7.21 [String handling <string.h>]

+
 

 
7.21.1 [String function conventions]

-

-
-
+
 
1   The header <string.h> declares one type and several functions, and defines one
     macro useful for manipulating arrays of character type and other objects treated as arrays
-    of character type.268) The type is size_t and the macro is NULL (both described in 7.17). 
+    of character type.[268] The type is size_t and the macro is NULL (both described in 7.17).
     Various methods are used for determining the lengths of the arrays, but in all cases
     a char * or void * argument points to the initial (lowest addressed) character of the
     array. If an array is accessed beyond the end of an object, the behavior is undefined.
 

-
 
-
Footnote 268) See ``future library directions'' (7.26.11).
+
Footnote 268) See ``future library directions'' (7.26.11).
 

 
-
+
 
2   Where an argument declared as size_t n specifies the length of the array for a
     function, n can have the value zero on a call to that function. Unless explicitly stated
     otherwise in the description of a particular function in this subclause, pointer arguments
-    on such a call shall still have valid values, as described in 7.1.4. On such a call, a
+    on such a call shall still have valid values, as described in 7.1.4. On such a call, a
     function that locates a character finds no occurrence, a function that compares two
     character sequences returns zero, and a function that copies characters copies zero
     characters.
 

-
-
+
 
3   For all functions in this subclause, each character shall be interpreted as if it had the type
     unsigned char (and therefore every possible object representation is valid and has a
     different value).
 

-
-
+
 

 
7.21.2 [Copying functions]

-
 Copying functions
-

-
-
+
 

 
7.21.2.1 [The memcpy function]

-

-
-
-
1            #include <string.h>
+
+
1 Synopsis
+            #include <string.h>
              void *memcpy(void * restrict s1,
                   const void * restrict s2,
                   size_t n);
     Description
 

-
-
+
 
2   The memcpy function copies n characters from the object pointed to by s2 into the
     object pointed to by s1. If copying takes place between objects that overlap, the behavior
     is undefined.
     Returns
 

-
-
+
 
3   The memcpy function returns the value of s1.
 

-
-
+
 

 
7.21.2.2 [The memmove function]

-

-
-
-
1          #include <string.h>
+
+
1 Synopsis
+          #include <string.h>
            void *memmove(void *s1, const void *s2, size_t n);
     Description
 

-
-
+
 
2   The memmove function copies n characters from the object pointed to by s2 into the
     object pointed to by s1. Copying takes place as if the n characters from the object
     pointed to by s2 are first copied into a temporary array of n characters that does not
@@ -18597,257 +16067,214 @@ char int_p_sep_by_space
     temporary array are copied into the object pointed to by s1.
     Returns
 

-
-
+
 
3   The memmove function returns the value of s1.
 

-
-
+
 

 
7.21.2.3 [The strcpy function]

-

-
-
-
1          #include <string.h>
+
+
1 Synopsis
+          #include <string.h>
            char *strcpy(char * restrict s1,
                 const char * restrict s2);
     Description
 

-
-
+
 
2   The strcpy function copies the string pointed to by s2 (including the terminating null
     character) into the array pointed to by s1. If copying takes place between objects that
     overlap, the behavior is undefined.
     Returns
 

-
-
+
 
3   The strcpy function returns the value of s1.
 

-
-
+
 

 
7.21.2.4 [The strncpy function]

-

-
-
-
1          #include <string.h>
+
+
1 Synopsis
+          #include <string.h>
            char *strncpy(char * restrict s1,
                 const char * restrict s2,
                 size_t n);
     Description
 

-
-
+
 
2   The strncpy function copies not more than n characters (characters that follow a null
     character are not copied) from the array pointed to by s2 to the array pointed to by
 
-    s1.269) If copying takes place between objects that overlap, the behavior is undefined.
+    s1.[269] If copying takes place between objects that overlap, the behavior is undefined.
 

-
 
 
Footnote 269) Thus, if there is no null character in the first n characters of the array pointed to by s2, the result will
          not be null-terminated.
 

 
-
+
 
3   If the array pointed to by s2 is a string that is shorter than n characters, null characters
     are appended to the copy in the array pointed to by s1, until n characters in all have been
     written.
     Returns
 

-
-
+
 
4   The strncpy function returns the value of s1.
 

-
-
+
 

 
7.21.3 [Concatenation functions]

-
 Concatenation functions
-

-
-
+
 

 
7.21.3.1 [The strcat function]

-

-
-
-
1            #include <string.h>
+
+
1 Synopsis
+            #include <string.h>
              char *strcat(char * restrict s1,
                   const char * restrict s2);
     Description
 

-
-
+
 
2   The strcat function appends a copy of the string pointed to by s2 (including the
     terminating null character) to the end of the string pointed to by s1. The initial character
     of s2 overwrites the null character at the end of s1. If copying takes place between
     objects that overlap, the behavior is undefined.
     Returns
 

-
-
+
 
3   The strcat function returns the value of s1.
 

-
-
+
 

 
7.21.3.2 [The strncat function]

-

-
-
-
1            #include <string.h>
+
+
1 Synopsis
+            #include <string.h>
              char *strncat(char * restrict s1,
                   const char * restrict s2,
                   size_t n);
     Description
 

-
-
+
 
2   The strncat function appends not more than n characters (a null character and
     characters that follow it are not appended) from the array pointed to by s2 to the end of
     the string pointed to by s1. The initial character of s2 overwrites the null character at the
-    end of s1. A terminating null character is always appended to the result.270) If copying
-    takes place between objects that overlap, the behavior is undefined.
-    Returns
+    end of s1. A terminating null character is always appended to the result.[270] If copying
 

-
 
 
Footnote 270) Thus, the maximum number of characters that can end up in the array pointed to by s1 is
          strlen(s1)+n+1.
+    takes place between objects that overlap, the behavior is undefined.
+    Returns
 

 
-
+
 
3   The strncat function returns the value of s1.
-    Forward references: the strlen function (7.21.6.3).
+    Forward references: the strlen function (7.21.6.3).
 

-
-
+
 

 
7.21.4 [Comparison functions]

-

-
-
+
 
1   The sign of a nonzero value returned by the comparison functions memcmp, strcmp,
     and strncmp is determined by the sign of the difference between the values of the first
     pair of characters (both interpreted as unsigned char) that differ in the objects being
     compared.
 

-
-
+
 

 
7.21.4.1 [The memcmp function]

-

-
-
-
1           #include <string.h>
+
+
1 Synopsis
+           #include <string.h>
             int memcmp(const void *s1, const void *s2, size_t n);
     Description
 

-
-
+
 
2   The memcmp function compares the first n characters of the object pointed to by s1 to
-    the first n characters of the object pointed to by s2.271)
+    the first n characters of the object pointed to by s2.[271]
     Returns
 

-
 
 
Footnote 271) The contents of ``holes'' used as padding for purposes of alignment within structure objects are
          indeterminate. Strings shorter than their allocated space and unions may also cause problems in
          comparison.
+    pointed to by s2.
 

 
-
+
 
3   The memcmp function returns an integer greater than, equal to, or less than zero,
     accordingly as the object pointed to by s1 is greater than, equal to, or less than the object
     pointed to by s2.
 

-
-
+
 

 
7.21.4.2 [The strcmp function]

-

-
-
-
1           #include <string.h>
+
+
1 Synopsis
+           #include <string.h>
             int strcmp(const char *s1, const char *s2);
     Description
 

-
-
+
 
2   The strcmp function compares the string pointed to by s1 to the string pointed to by
     s2.
     Returns
 

-
-
+
 
3   The strcmp function returns an integer greater than, equal to, or less than zero,
     accordingly as the string pointed to by s1 is greater than, equal to, or less than the string
-    pointed to by s2.
 

-
-
+
 

 
7.21.4.3 [The strcoll function]

-

-
-
-
1          #include <string.h>
+
+
1 Synopsis
+          #include <string.h>
            int strcoll(const char *s1, const char *s2);
     Description
 

-
-
+
 
2   The strcoll function compares the string pointed to by s1 to the string pointed to by
     s2, both interpreted as appropriate to the LC_COLLATE category of the current locale.
     Returns
 

-
-
+
 
3   The strcoll function returns an integer greater than, equal to, or less than zero,
     accordingly as the string pointed to by s1 is greater than, equal to, or less than the string
     pointed to by s2 when both are interpreted as appropriate to the current locale.
 

-
-
+
 

 
7.21.4.4 [The strncmp function]

-

-
-
-
1          #include <string.h>
+
+
1 Synopsis
+          #include <string.h>
            int strncmp(const char *s1, const char *s2, size_t n);
     Description
 

-
-
+
 
2   The strncmp function compares not more than n characters (characters that follow a
     null character are not compared) from the array pointed to by s1 to the array pointed to
     by s2.
     Returns
 

-
-
+
 
3   The strncmp function returns an integer greater than, equal to, or less than zero,
     accordingly as the possibly null-terminated array pointed to by s1 is greater than, equal
     to, or less than the possibly null-terminated array pointed to by s2.
 

-
-
+
 

 
7.21.4.5 [The strxfrm function]

-

-
-
-
1          #include <string.h>
+
+
1 Synopsis
+          #include <string.h>
            size_t strxfrm(char * restrict s1,
                 const char * restrict s2,
                 size_t n);
     Description
 

-
-
+
 
2   The strxfrm function transforms the string pointed to by s2 and places the resulting
     string into the array pointed to by s1. The transformation is such that if the strcmp
     function is applied to two transformed strings, it returns a value greater than, equal to, or
@@ -18858,212 +16285,174 @@ char int_p_sep_by_space
     undefined.
     Returns
 

-
-
+
 
3   The strxfrm function returns the length of the transformed string (not including the
     terminating null character). If the value returned is n or more, the contents of the array
     pointed to by s1 are indeterminate.
 

-
-
+
 
4   EXAMPLE The value of the following expression is the size of the array needed to hold the
     transformation of the string pointed to by s.
            1 + strxfrm(NULL, s, 0)
 
 

-
-
+
 

 
7.21.5 [Search functions]

-
 Search functions
-

-
-
+
 

 
7.21.5.1 [The memchr function]

-

-
-
-
1          #include <string.h>
+
+
1 Synopsis
+          #include <string.h>
            void *memchr(const void *s, int c, size_t n);
     Description
 

-
-
+
 
2   The memchr function locates the first occurrence of c (converted to an unsigned
     char) in the initial n characters (each interpreted as unsigned char) of the object
     pointed to by s.
     Returns
 

-
-
+
 
3   The memchr function returns a pointer to the located character, or a null pointer if the
     character does not occur in the object.
 

-
-
+
 

 
7.21.5.2 [The strchr function]

-

-
-
-
1          #include <string.h>
+
+
1 Synopsis
+          #include <string.h>
            char *strchr(const char *s, int c);
     Description
 

-
-
+
 
2   The strchr function locates the first occurrence of c (converted to a char) in the
     string pointed to by s. The terminating null character is considered to be part of the
     string.
     Returns
 

-
-
+
 
3   The strchr function returns a pointer to the located character, or a null pointer if the
     character does not occur in the string.
 

-
-
+
 

 
7.21.5.3 [The strcspn function]

-

-
-
-
1          #include <string.h>
+
+
1 Synopsis
+          #include <string.h>
            size_t strcspn(const char *s1, const char *s2);
     Description
 

-
-
+
 
2   The strcspn function computes the length of the maximum initial segment of the string
     pointed to by s1 which consists entirely of characters not from the string pointed to by
     s2.
     Returns
 

-
-
+
 
3   The strcspn function returns the length of the segment.
 

-
-
+
 

 
7.21.5.4 [The strpbrk function]

-

-
-
-
1          #include <string.h>
+
+
1 Synopsis
+          #include <string.h>
            char *strpbrk(const char *s1, const char *s2);
     Description
 

-
-
+
 
2   The strpbrk function locates the first occurrence in the string pointed to by s1 of any
     character from the string pointed to by s2.
     Returns
 

-
-
+
 
3   The strpbrk function returns a pointer to the character, or a null pointer if no character
     from s2 occurs in s1.
 

-
-
+
 

 
7.21.5.5 [The strrchr function]

-

-
-
-
1          #include <string.h>
+
+
1 Synopsis
+          #include <string.h>
            char *strrchr(const char *s, int c);
     Description
 

-
-
+
 
2   The strrchr function locates the last occurrence of c (converted to a char) in the
     string pointed to by s. The terminating null character is considered to be part of the
     string.
     Returns
 

-
-
+
 
3   The strrchr function returns a pointer to the character, or a null pointer if c does not
     occur in the string.
 
 

-
-
+
 

 
7.21.5.6 [The strspn function]

-

-
-
-
1          #include <string.h>
+
+
1 Synopsis
+          #include <string.h>
            size_t strspn(const char *s1, const char *s2);
     Description
 

-
-
+
 
2   The strspn function computes the length of the maximum initial segment of the string
     pointed to by s1 which consists entirely of characters from the string pointed to by s2.
     Returns
 

-
-
+
 
3   The strspn function returns the length of the segment.
 

-
-
+
 

 
7.21.5.7 [The strstr function]

-

-
-
-
1          #include <string.h>
+
+
1 Synopsis
+          #include <string.h>
            char *strstr(const char *s1, const char *s2);
     Description
 

-
-
+
 
2   The strstr function locates the first occurrence in the string pointed to by s1 of the
     sequence of characters (excluding the terminating null character) in the string pointed to
     by s2.
     Returns
 

-
-
+
 
3   The strstr function returns a pointer to the located string, or a null pointer if the string
     is not found. If s2 points to a string with zero length, the function returns s1.
 

-
-
+
 

 
7.21.5.8 [The strtok function]

-

-
-
-
1          #include <string.h>
+
+
1 Synopsis
+          #include <string.h>
            char *strtok(char * restrict s1,
                 const char * restrict s2);
     Description
 

-
-
+
 
2   A sequence of calls to the strtok function breaks the string pointed to by s1 into a
     sequence of tokens, each of which is delimited by a character from the string pointed to
     by s2. The first call in the sequence has a non-null first argument; subsequent calls in the
     sequence have a null first argument. The separator string pointed to by s2 may be
     different from call to call.
 

-
-
+
 
3   The first call in the sequence searches the string pointed to by s1 for the first character
     that is not contained in the current separator string pointed to by s2. If no such character
     is found, then there are no tokens in the string pointed to by s1 and the strtok function
     returns a null pointer. If such a character is found, it is the start of the first token.
 

-
-
+
 
4   The strtok function then searches from there for a character that is contained in the
     current separator string. If no such character is found, the current token extends to the
     end of the string pointed to by s1, and subsequent searches for a token will return a null
@@ -19071,23 +16460,19 @@ char int_p_sep_by_space
     terminates the current token. The strtok function saves a pointer to the following
     character, from which the next search for a token will start.
 

-
-
+
 
5   Each subsequent call, with a null pointer as the value of the first argument, starts
     searching from the saved pointer and behaves as described above.
 

-
-
+
 
6   The implementation shall behave as if no library function calls the strtok function.
     Returns
 

-
-
+
 
7   The strtok function returns a pointer to the first character of a token, or a null pointer
     if there is no token.
 

-
-
+
 
8   EXAMPLE
             #include <string.h>
             static char str[] = "?a???b,,,#c";
@@ -19098,105 +16483,84 @@ char int_p_sep_by_space
             t   =   strtok(NULL, "?");       //   t   is a null pointer
 
 

-
-
+
 

 
7.21.6 [Miscellaneous functions]

-
 Miscellaneous functions
-

-
-
+
 

 
7.21.6.1 [The memset function]

-

-
-
-
1           #include <string.h>
+
+
1 Synopsis
+           #include <string.h>
             void *memset(void *s, int c, size_t n);
     Description
 

-
-
+
 
2   The memset function copies the value of c (converted to an unsigned char) into
     each of the first n characters of the object pointed to by s.
     Returns
 

-
-
+
 
3   The memset function returns the value of s.
 
 

-
-
+
 

 
7.21.6.2 [The strerror function]

-

-
-
-
1          #include <string.h>
+
+
1 Synopsis
+          #include <string.h>
            char *strerror(int errnum);
     Description
 

-
-
+
 
2   The strerror function maps the number in errnum to a message string. Typically,
     the values for errnum come from errno, but strerror shall map any value of type
     int to a message.
 

-
-
+
 
3   The implementation shall behave as if no library function calls the strerror function.
     Returns
 

-
-
+
 
4   The strerror function returns a pointer to the string, the contents of which are locale-
     specific. The array pointed to shall not be modified by the program, but may be
     overwritten by a subsequent call to the strerror function.
 

-
-
+
 

 
7.21.6.3 [The strlen function]

-

-
-
-
1          #include <string.h>
+
+
1 Synopsis
+          #include <string.h>
            size_t strlen(const char *s);
     Description
 

-
-
+
 
2   The strlen function computes the length of the string pointed to by s.
     Returns
 

-
-
+
 
3   The strlen function returns the number of characters that precede the terminating null
     character.
 
 

-
-
+
 

-
7.22 [Type-generic math ]

-

-
-
+
7.22 [Type-generic math <tgmath.h>]

+
 
1   The header <tgmath.h> includes the headers <math.h> and <complex.h> and
     defines several type-generic macros.
 

-
-
+
 
2   Of the <math.h> and <complex.h> functions without an f (float) or l (long
     double) suffix, several have one or more parameters whose corresponding real type is
     double. For each such function, except modf, there is a corresponding type-generic
-    macro.272) The parameters whose corresponding real type is double in the function
+    macro.[272] The parameters whose corresponding real type is double in the function
     synopsis are generic parameters. Use of the macro invokes a function whose
     corresponding real type and type domain are determined by the arguments for the generic
-    parameters.273)
+    parameters.[273]
 

-
 
 
Footnote 272) Like other function-like macros in Standard libraries, each type-generic macro can be suppressed to
          make available the corresponding ordinary function.
@@ -19224,9 +16588,11 @@ char int_p_sep_by_space
               pow                cpow                 pow
               sqrt               csqrt                sqrt
               fabs               cabs                 fabs
+    If at least one argument for a generic parameter is complex, then use of the macro invokes
+    a complex function; otherwise, use of the macro invokes a real function.
 

 
-
+
 
3   Use of the macro invokes a function whose generic parameters have the corresponding
     real type determined as follows:
     -- First, if any argument for generic parameters has type long double, the type
@@ -19235,17 +16601,13 @@ char int_p_sep_by_space
        type, the type determined is double.
     -- Otherwise, the type determined is float.
 

-
-
+
 
4   For each unsuffixed function in <math.h> for which there is a function in
     <complex.h> with the same name except for a c prefix, the corresponding type-
     generic macro (for both functions) has the same name as the function in <math.h>. The
     corresponding type-generic macro for fabs and cabs is fabs.
-    If at least one argument for a generic parameter is complex, then use of the macro invokes
-    a complex function; otherwise, use of the macro invokes a real function.
 

-
-
+
 
5   For each unsuffixed function in <math.h> without a c-prefixed counterpart in
     <complex.h> (except modf), the corresponding type-generic macro has the same
     name as the function. These type-generic macros are:
@@ -19262,8 +16624,7 @@ char int_p_sep_by_space
     If all arguments for generic parameters are real, then use of the macro invokes a real
     function; otherwise, use of the macro results in undefined behavior.
 

-
-
+
 
6   For each unsuffixed function in <complex.h> that is not a c-prefixed counterpart to a
     function in <math.h>, the corresponding type-generic macro has the same name as the
     function. These type-generic macros are:
@@ -19271,8 +16632,7 @@ char int_p_sep_by_space
             cimag                   cproj
     Use of the macro with any real or complex argument invokes a complex function.
 

-
-
+
 
7   EXAMPLE       With the declarations
             #include <tgmath.h>
             int n;
@@ -19307,19 +16667,13 @@ char int_p_sep_by_space
                 cproj(ldc)                          cprojl(ldc)
 
 

-
-
+
 

-
7.23 [Date and time ]

-
 Date and time 
-

-
-
+
7.23 [Date and time <time.h>]

+
 

 
7.23.1 [Components of time]

-

-
-
+
 
1   The header <time.h> defines two macros, and declares several types and functions for
     manipulating time. Many functions deal with a calendar time that represents the current
     date (according to the Gregorian calendar) and time. Some functions deal with local
@@ -19327,16 +16681,14 @@ char int_p_sep_by_space
     Saving Time, which is a temporary change in the algorithm for determining local time.
     The local time zone and Daylight Saving Time are implementation-defined.
 

-
-
-
2   The macros defined are NULL (described in 7.17); and
+
+
2   The macros defined are NULL (described in 7.17); and
             CLOCKS_PER_SEC
     which expands to an expression with type clock_t (described below) that is the
     number per second of the value returned by the clock function.
 

-
-
-
3   The types declared are size_t (described in 7.17);
+
+
3   The types declared are size_t (described in 7.17);
             clock_t
     and
             time_t
@@ -19344,12 +16696,11 @@ char int_p_sep_by_space
             struct tm
     which holds the components of a calendar time, called the broken-down time.
 

-
-
+
 
4   The range and precision of times representable in clock_t and time_t are
     implementation-defined. The tm structure shall contain at least the following members,
     in any order. The semantics of the members and their normal ranges are expressed in the
-    comments.274)
+    comments.[274]
             int    tm_sec;           //   seconds after the minute -- [0, 60]
             int    tm_min;           //   minutes after the hour -- [0, 59]
             int    tm_hour;          //   hours since midnight -- [0, 23]
@@ -19359,95 +16710,80 @@ char int_p_sep_by_space
             int    tm_wday;          //   days since Sunday -- [0, 6]
             int    tm_yday;          //   days since January 1 -- [0, 365]
             int    tm_isdst;         //   Daylight Saving Time flag
-    The value of tm_isdst is positive if Daylight Saving Time is in effect, zero if Daylight
-    Saving Time is not in effect, and negative if the information is not available.
 

-
 
 
Footnote 274) The range [0, 60] for tm_sec allows for a positive leap second.
+    The value of tm_isdst is positive if Daylight Saving Time is in effect, zero if Daylight
+    Saving Time is not in effect, and negative if the information is not available.
 

 
-
+
 

 
7.23.2 [Time manipulation functions]

-
 Time manipulation functions
-

-
-
+
 

 
7.23.2.1 [The clock function]

-

-
-
-
1           #include <time.h>
+
+
1 Synopsis
+           #include <time.h>
             clock_t clock(void);
     Description
 

-
-
+
 
2   The clock function determines the processor time used.
     Returns
 

-
-
+
 
3   The clock function returns the implementation's best approximation to the processor
     time used by the program since the beginning of an implementation-defined era related
     only to the program invocation. To determine the time in seconds, the value returned by
     the clock function should be divided by the value of the macro CLOCKS_PER_SEC. If
     the processor time used is not available or its value cannot be represented, the function
-    returns the value (clock_t)(-1).275)
+    returns the value (clock_t)(-1).[275]
 

-
 
 
Footnote 275) In order to measure the time spent in a program, the clock function should be called at the start of
          the program and its return value subtracted from the value returned by subsequent calls.
 

 
-
+
 

 
7.23.2.2 [The difftime function]

-

-
-
-
1           #include <time.h>
+
+
1 Synopsis
+           #include <time.h>
             double difftime(time_t time1, time_t time0);
     Description
 

-
-
+
 
2   The difftime function computes the difference between two calendar times: time1 -
     time0.
     Returns
 

-
-
+
 
3   The difftime function returns the difference expressed in seconds as a double.
 

-
-
+
 

 
7.23.2.3 [The mktime function]

-

-
-
-
1           #include <time.h>
+
+
1 Synopsis
+           #include <time.h>
             time_t mktime(struct tm *timeptr);
     Description
 

-
-
+
 
2   The mktime function converts the broken-down time, expressed as local time, in the
     structure pointed to by timeptr into a calendar time value with the same encoding as
     that of the values returned by the time function. The original values of the tm_wday
     and tm_yday components of the structure are ignored, and the original values of the
-    other components are not restricted to the ranges indicated above.276) On successful
+    other components are not restricted to the ranges indicated above.[276] On successful
     completion, the values of the tm_wday and tm_yday components of the structure are
     set appropriately, and the other components are set to represent the specified calendar
     time, but with their values forced to the ranges indicated above; the final value of
     tm_mday is not set until tm_mon and tm_year are determined.
     Returns
 

-
 
 
Footnote 276) Thus, a positive or zero value for tm_isdst causes the mktime function to presume initially that
          Daylight Saving Time, respectively, is or is not in effect for the specified time. A negative value
@@ -19464,13 +16800,12 @@ char int_p_sep_by_space
            printf("%s\n", wday[time_str.tm_wday]);
 

 
-
+
 
3   The mktime function returns the specified calendar time encoded as a value of type
     time_t. If the calendar time cannot be represented, the function returns the value
     (time_t)(-1).
 

-
-
+
 
4   EXAMPLE       What day of the week is July 4, 2001?
             #include <stdio.h>
             #include <time.h>
@@ -19482,37 +16817,30 @@ char int_p_sep_by_space
             /* ... */
 
 

-
-
+
 

 
7.23.2.4 [The time function]

-

-
-
-
1          #include <time.h>
+
+
1 Synopsis
+          #include <time.h>
            time_t time(time_t *timer);
     Description
 

-
-
+
 
2   The time function determines the current calendar time. The encoding of the value is
     unspecified.
     Returns
 

-
-
+
 
3   The time function returns the implementation's best approximation to the current
     calendar time. The value (time_t)(-1) is returned if the calendar time is not
     available. If timer is not a null pointer, the return value is also assigned to the object it
     points to.
 

-
-
+
 

 
7.23.3 [Time conversion functions]

-

-
-
+
 
1   Except for the strftime function, these functions each return a pointer to one of two
     types of static objects: a broken-down time structure or an array of char. Execution of
     any of the functions that return a pointer to one of these object types may overwrite the
@@ -19520,19 +16848,16 @@ char int_p_sep_by_space
     previous call to any of them. The implementation shall behave as if no other library
     functions call these functions.
 

-
-
+
 

 
7.23.3.1 [The asctime function]

-

-
-
-
1          #include <time.h>
+
+
1 Synopsis
+          #include <time.h>
            char *asctime(const struct tm *timeptr);
     Description
 

-
-
+
 
2   The asctime function converts the broken-down time in the structure pointed to by
     timeptr into a string in the form
            Sun Sep 16 01:03:52 1973\n\0
@@ -19557,95 +16882,79 @@ char int_p_sep_by_space
     }
     Returns
 

-
-
+
 
3   The asctime function returns a pointer to the string.
 

-
-
+
 

 
7.23.3.2 [The ctime function]

-

-
-
-
1          #include <time.h>
+
+
1 Synopsis
+          #include <time.h>
            char *ctime(const time_t *timer);
     Description
 

-
-
+
 
2   The ctime function converts the calendar time pointed to by timer to local time in the
     form of a string. It is equivalent to
            asctime(localtime(timer))
     Returns
 

-
-
+
 
3   The ctime function returns the pointer returned by the asctime function with that
     broken-down time as argument.
-    Forward references: the localtime function (7.23.3.4).
+    Forward references: the localtime function (7.23.3.4).
 
 

-
-
+
 

 
7.23.3.3 [The gmtime function]

-

-
-
-
1          #include <time.h>
+
+
1 Synopsis
+          #include <time.h>
            struct tm *gmtime(const time_t *timer);
     Description
 

-
-
+
 
2   The gmtime function converts the calendar time pointed to by timer into a broken-
     down time, expressed as UTC.
     Returns
 

-
-
+
 
3   The gmtime function returns a pointer to the broken-down time, or a null pointer if the
     specified time cannot be converted to UTC.
 

-
-
+
 

 
7.23.3.4 [The localtime function]

-

-
-
-
1          #include <time.h>
+
+
1 Synopsis
+          #include <time.h>
            struct tm *localtime(const time_t *timer);
     Description
 

-
-
+
 
2   The localtime function converts the calendar time pointed to by timer into a
     broken-down time, expressed as local time.
     Returns
 

-
-
+
 
3   The localtime function returns a pointer to the broken-down time, or a null pointer if
     the specified time cannot be converted to local time.
 

-
-
+
 

 
7.23.3.5 [The strftime function]

-

-
-
-
1          #include <time.h>
+
+
1 Synopsis
+          #include <time.h>
            size_t strftime(char * restrict s,
                 size_t maxsize,
                 const char * restrict format,
                 const struct tm * restrict timeptr);
     Description
 

-
-
+
 
2   The strftime function places characters into the array pointed to by s as controlled by
     the string pointed to by format. The format shall be a multibyte character sequence,
     beginning and ending in its initial shift state. The format string consists of zero or
@@ -19656,8 +16965,7 @@ char int_p_sep_by_space
     unchanged into the array. If copying takes place between objects that overlap, the
     behavior is undefined. No more than maxsize characters are placed into the array.
 

-
-
+
 
3   Each conversion specifier is replaced by appropriate characters as described in the
     following list. The appropriate characters are determined using the LC_TIME category
     of the current locale and by the values of zero or more members of the broken-down time
@@ -19668,7 +16976,7 @@ char int_p_sep_by_space
     %b    is replaced by the locale's abbreviated month name. [tm_mon]
     %B    is replaced by the locale's full month name. [tm_mon]
     %c    is replaced by the locale's appropriate date and time representation. [all specified
-          in 7.23.1]
+          in 7.23.1]
     %C    is replaced by the year divided by 100 and truncated to an integer, as a decimal
           number (00-99). [tm_year]
     %d    is replaced by the day of the month as a decimal number (01-31). [tm_mday]
@@ -19698,16 +17006,16 @@ char int_p_sep_by_space
           tm_sec]
     %u    is replaced by the ISO 8601 weekday as a decimal number (1-7), where Monday
           is 1. [tm_wday]
-    %U    is replaced by the week number of the year (the first Sunday as the first day of week 1) 
+    %U    is replaced by the week number of the year (the first Sunday as the first day of week 1)
           as a decimal number (00-53). [tm_year, tm_wday, tm_yday]
     %V    is replaced by the ISO 8601 week number (see below) as a decimal number
           (01-53). [tm_year, tm_wday, tm_yday]
     %w    is replaced by the weekday as a decimal number (0-6), where Sunday is 0.
           [tm_wday]
-    %W    is replaced by the week number of the year (the first Monday as the first day of week 1) 
+    %W    is replaced by the week number of the year (the first Monday as the first day of week 1)
           as a decimal number (00-53). [tm_year, tm_wday, tm_yday]
-    %x    is replaced by the locale's appropriate date representation. [all specified in 7.23.1]
-    %X    is replaced by the locale's appropriate time representation. [all specified in 7.23.1]
+    %x    is replaced by the locale's appropriate date representation. [all specified in 7.23.1]
+    %X    is replaced by the locale's appropriate time representation. [all specified in 7.23.1]
     %y    is replaced by the last 2 digits of the year as a decimal number (00-99).
           [tm_year]
     %Y    is replaced by the year as a decimal number (e.g., 1997). [tm_year]
@@ -19718,8 +17026,7 @@ char int_p_sep_by_space
           time zone is determinable. [tm_isdst]
     %%    is replaced by %.
 

-
-
+
 
4   Some conversion specifiers can be modified by the inclusion of an E or O modifier
     character to indicate an alternative format or specification. If the alternative format or
     specification does not exist for the current locale, the modifier is ignored.
@@ -19755,8 +17062,7 @@ char int_p_sep_by_space
     %Oy is replaced by the last 2 digits of the year, using the locale's alternative numeric
         symbols.
 

-
-
+
 
5   %g, %G, and %V give values according to the ISO 8601 week-based year. In this system,
     weeks begin on a Monday and week 1 of the year is the week that includes January 4th,
     which is also the week that includes the first Thursday of the year, and is also the first
@@ -19767,12 +17073,10 @@ char int_p_sep_by_space
     the following year. Thus, for Tuesday 30th December 1997, %G is replaced by 1998 and
     %V is replaced by 01.
 

-
-
+
 
6   If a conversion specifier is not one of the above, the behavior is undefined.
 

-
-
+
 
7   In the "C" locale, the E and O modifiers are ignored and the replacement strings for the
     following specifiers are:
     %a    the first three characters of %A.
@@ -19787,37 +17091,29 @@ char int_p_sep_by_space
     %Z    implementation-defined.
     Returns
 

-
-
+
 
8   If the total number of resulting characters including the terminating null character is not
     more than maxsize, the strftime function returns the number of characters placed
     into the array pointed to by s not including the terminating null character. Otherwise,
     zero is returned and the contents of the array are indeterminate.
 
 

-
-
+
 

-
7.24 [Extended multibyte and wide character utilities ]

-
 Extended multibyte and wide character utilities 
-

-
-
+
7.24 [Extended multibyte and wide character utilities <wchar.h>]

+
 

 
7.24.1 [Introduction]

-

-
-
+
 
1   The header <wchar.h> declares four data types, one tag, four macros, and many
-    functions.277)
+    functions.[277]
 

-
 
-
Footnote 277) See ``future library directions'' (7.26.12).
+
Footnote 277) See ``future library directions'' (7.26.12).
 

 
-
-
2   The types declared are wchar_t and size_t (both described in 7.17);
+
+
2   The types declared are wchar_t and size_t (both described in 7.17);
              mbstate_t
     which is an object type other than an array type that can hold the conversion state
     information necessary to convert between sequences of multibyte characters and wide
@@ -19826,101 +17122,55 @@ char int_p_sep_by_space
     which is an integer type unchanged by default argument promotions that can hold any
     value corresponding to members of the extended character set, as well as at least one
     value that does not correspond to any member of the extended character set (see WEOF
-    below);278) and
+    below);[278] and
              struct tm
-    which is declared as an incomplete structure type (the contents are described in 7.23.1).
+    which is declared as an incomplete structure type (the contents are described in 7.23.1).
 

-
 
 
Footnote 278) wchar_t and wint_t can be the same integer type.
 

 
-
-
3   The macros defined are NULL (described in 7.17); WCHAR_MIN and WCHAR_MAX
-    (described in 7.18.3); and
+
+
3   The macros defined are NULL (described in 7.17); WCHAR_MIN and WCHAR_MAX
+    (described in 7.18.3); and
              WEOF
     which expands to a constant expression of type wint_t whose value does not
-    correspond to any member of the extended character set.279) It is accepted (and returned)
+    correspond to any member of the extended character set.[279] It is accepted (and returned)
     by several functions in this subclause to indicate end-of-file, that is, no more input from a
     stream. It is also used as a wide character value that does not correspond to any member
     of the extended character set.
 

-
 
 
Footnote 279) The value of the macro WEOF may differ from that of EOF and need not be negative.
+    -- Functions for wide string date and time conversion; and
+    -- Functions that provide extended capabilities for conversion between multibyte and
+       wide character sequences.
 

 
-
+
 
4   The functions declared are grouped as follows:
     -- Functions that perform input and output of wide characters, or multibyte characters,
        or both;
     -- Functions that provide wide string numeric conversion;
     -- Functions that perform general wide string manipulation;
-    -- Functions for wide string date and time conversion; and
-    -- Functions that provide extended capabilities for conversion between multibyte and
-       wide character sequences.
 

-
-
+
 
5   Unless explicitly stated otherwise, if the execution of a function described in this
     subclause causes copying to take place between objects that overlap, the behavior is
     undefined.
 

-
-
+
 

 
7.24.2 [Formatted wide character input/output functions]

-

-
-
+
 
1   The formatted wide character input/output functions shall behave as if there is a sequence
-    point after the actions associated with each specifier.280)
+    point after the actions associated with each specifier.[280]
 

-
 
 
Footnote 280) The fwprintf functions perform writes to memory for the %n specifier.
         left adjustment flag, described later, has been given) to the field width. The field
         width takes the form of an asterisk * (described later) or a nonnegative decimal
         integer.281)
-

-
-
-

-
7.24.2.1 [The fwprintf function]

-

-
-
-
1           #include <stdio.h>
-            #include <wchar.h>
-            int fwprintf(FILE * restrict stream,
-                 const wchar_t * restrict format, ...);
-    Description
-

-
-
-
2   The fwprintf function writes output to the stream pointed to by stream, under
-    control of the wide string pointed to by format that specifies how subsequent arguments
-    are converted for output. If there are insufficient arguments for the format, the behavior
-    is undefined. If the format is exhausted while arguments remain, the excess arguments
-    are evaluated (as always) but are otherwise ignored. The fwprintf function returns
-    when the end of the format string is encountered.
-

-
-
-
3   The format is composed of zero or more directives: ordinary wide characters (not %),
-    which are copied unchanged to the output stream; and conversion specifications, each of
-    which results in fetching zero or more subsequent arguments, converting them, if
-    applicable, according to the corresponding conversion specifier, and then writing the
-    result to the output stream.
-

-
-
-
4   Each conversion specification is introduced by the wide character %. After the %, the
-    following appear in sequence:
-    -- Zero or more flags (in any order) that modify the meaning of the conversion
-       specification.
-    -- An optional minimum field width. If the converted value has fewer wide characters
-       than the field width, it is padded with spaces (by default) on the left (or right, if the
     -- An optional precision that gives the minimum number of digits to appear for the d, i,
        o, u, x, and X conversions, the number of digits to appear after the decimal-point
        wide character for a, A, e, E, f, and F conversions, the maximum number of
@@ -19932,9 +17182,43 @@ char int_p_sep_by_space
     -- An optional length modifier that specifies the size of the argument.
     -- A conversion specifier wide character that specifies the type of conversion to be
        applied.
-

+

 
-
+
+

+
7.24.2.1 [The fwprintf function]

+
+
1 Synopsis
+           #include <stdio.h>
+            #include <wchar.h>
+            int fwprintf(FILE * restrict stream,
+                 const wchar_t * restrict format, ...);
+    Description
+

+
+
2   The fwprintf function writes output to the stream pointed to by stream, under
+    control of the wide string pointed to by format that specifies how subsequent arguments
+    are converted for output. If there are insufficient arguments for the format, the behavior
+    is undefined. If the format is exhausted while arguments remain, the excess arguments
+    are evaluated (as always) but are otherwise ignored. The fwprintf function returns
+    when the end of the format string is encountered.
+

+
+
3   The format is composed of zero or more directives: ordinary wide characters (not %),
+    which are copied unchanged to the output stream; and conversion specifications, each of
+    which results in fetching zero or more subsequent arguments, converting them, if
+    applicable, according to the corresponding conversion specifier, and then writing the
+    result to the output stream.
+

+
+
4   Each conversion specification is introduced by the wide character %. After the %, the
+    following appear in sequence:
+    -- Zero or more flags (in any order) that modify the meaning of the conversion
+       specification.
+    -- An optional minimum field width. If the converted value has fewer wide characters
+       than the field width, it is padded with spaces (by default) on the left (or right, if the
+

+
 
5   As noted above, a field width, or precision, or both, may be indicated by an asterisk. In
     this case, an int argument supplies the field width or precision. The arguments
     specifying field width, or precision, or both, shall appear (in that order) before the
@@ -19942,14 +17226,13 @@ char int_p_sep_by_space
     followed by a positive field width. A negative precision argument is taken as if the
     precision were omitted.
 

-
-
+
 
6   The flag wide characters and their meanings are:
     -        The result of the conversion is left-justified within the field. (It is right-justified if
              this flag is not specified.)
     +        The result of a signed conversion always begins with a plus or minus sign. (It
              begins with a sign only when a negative value is converted if this flag is not
-             specified.)282)
+             specified.)[282]
     space If the first wide character of a signed conversion is not a sign, or if a signed
           conversion results in no wide characters, a space is prefixed to the result. If the
           space and + flags both appear, the space flag is ignored.
@@ -19957,15 +17240,24 @@ char int_p_sep_by_space
              the precision, if and only if necessary, to force the first digit of the result to be a
              zero (if the value and precision are both 0, a single 0 is printed). For x (or X)
              conversion, a nonzero result has 0x (or 0X) prefixed to it. For a, A, e, E, f, F, g,
+

+
+
Footnote 282) The results of all floating conversions of a negative zero, and of negative values that round to zero,
+         include a minus sign.
+              and G conversions, the result of converting a floating-point number always
+              contains a decimal-point wide character, even if no digits follow it. (Normally, a
+              decimal-point wide character appears in the result of these conversions only if a
+              digit follows it.) For g and G conversions, trailing zeros are not removed from the
+              result. For other conversions, the behavior is undefined.
     0         For d, i, o, u, x, X, a, A, e, E, f, F, g, and G conversions, leading zeros
               (following any indication of sign or base) are used to pad to the field width rather
               than performing space padding, except when converting an infinity or NaN. If the
               0 and - flags both appear, the 0 flag is ignored. For d, i, o, u, x, and X
               conversions, if a precision is specified, the 0 flag is ignored. For other
               conversions, the behavior is undefined.
-

+

 
-
+
 
7   The length modifiers and their meanings are:
     hh             Specifies that a following d, i, o, u, x, or X conversion specifier applies to a
                    signed char or unsigned char argument (the argument will have
@@ -20006,8 +17298,7 @@ char int_p_sep_by_space
     If a length modifier appears with any conversion specifier other than as specified above,
     the behavior is undefined.
 

-
-
+
 
8   The conversion specifiers and their meanings are:
     d,i        The int argument is converted to signed decimal in the style [-]dddd. The
                precision specifies the minimum number of digits to appear; if the value
@@ -20034,9 +17325,9 @@ char int_p_sep_by_space
                [-]nan or [-]nan(n-wchar-sequence) -- which style, and the meaning of
                any n-wchar-sequence, is implementation-defined. The F conversion
                specifier produces INF, INFINITY, or NAN instead of inf, infinity, or
-               nan, respectively.283)
+               nan, respectively.[283]
     e,E          A double argument representing a floating-point number is converted in the
-                 style [-]d.ddd e±dd, where there is one digit (which is nonzero if the
+                 style [-]d.ddd e\xB1dd, where there is one digit (which is nonzero if the
                  argument is nonzero) before the decimal-point wide character and the number
                  of digits after it is equal to the precision; if the precision is missing, it is taken
                  as 6; if the precision is zero and the # flag is not specified, no decimal-point
@@ -20061,11 +17352,32 @@ char int_p_sep_by_space
                  A double argument representing an infinity or NaN is converted in the style
                  of an f or F conversion specifier.
     a,A          A double argument representing a floating-point number is converted in the
-                 style [-]0xh.hhhh p±d, where there is one hexadecimal digit (which is
+                 style [-]0xh.hhhh p\xB1d, where there is one hexadecimal digit (which is
                  nonzero if the argument is a normalized floating-point number and is
-                 otherwise unspecified) before the decimal-point wide character284) and the
+                 otherwise unspecified) before the decimal-point wide character[284] and the
                  number of hexadecimal digits after it is equal to the precision; if the precision
                  is missing and FLT_RADIX is a power of 2, then the precision is sufficient
+

+
+
Footnote 283) When applied to infinite and NaN values, the -, +, and space flag wide characters have their usual
+         meaning; the # and 0 flag wide characters have no effect.
+

+
+
+
Footnote 284) Binary implementations can choose the hexadecimal digit to the left of the decimal-point wide
+         character so that subsequent digits align to nibble (4-bit) boundaries.
+                 for an exact representation of the value; if the precision is missing and
+                 FLT_RADIX is not a power of 2, then the precision is sufficient to
+                 distinguish285) values of type double, except that trailing zeros may be
+                 omitted; if the precision is zero and the # flag is not specified, no decimal-
+                 point wide character appears. The letters abcdef are used for a conversion
+                 and the letters ABCDEF for A conversion. The A conversion specifier
+                 produces a number with X and P instead of x and p. The exponent always
+                 contains at least one digit, and only as many more digits as necessary to
+                 represent the decimal exponent of 2. If the value is zero, the exponent is
+                 zero.
+                 A double argument representing an infinity or NaN is converted in the style
+                 of an f or F conversion specifier.
     c            If no l length modifier is present, the int argument is converted to a wide
                  character as if by calling btowc and the resulting wide character is written.
                  If an l length modifier is present, the wint_t argument is converted to
@@ -20088,69 +17400,36 @@ char int_p_sep_by_space
                  shall contain a null wide character.
     p            The argument shall be a pointer to void. The value of the pointer is
                  converted to a sequence of printing wide characters, in an implementation-
-     n              The argument shall be a pointer to signed integer into which is written the
-                    number of wide characters written to the output stream so far by this call to
-                    fwprintf. No argument is converted, but one is consumed. If the
-                    conversion specification includes any flags, a field width, or a precision, the
-                    behavior is undefined.
-     %              A % wide character is written. No argument is converted. The complete
-                    conversion specification shall be %%.
-

-
-
-
Footnote 283) When applied to infinite and NaN values, the -, +, and space flag wide characters have their usual
-         meaning; the # and 0 flag wide characters have no effect.
 

 
-
-
Footnote 284) Binary implementations can choose the hexadecimal digit to the left of the decimal-point wide
-         character so that subsequent digits align to nibble (4-bit) boundaries.
-                 for an exact representation of the value; if the precision is missing and
-                 FLT_RADIX is not a power of 2, then the precision is sufficient to
-                 distinguish285) values of type double, except that trailing zeros may be
-                 omitted; if the precision is zero and the # flag is not specified, no decimal-
-                 point wide character appears. The letters abcdef are used for a conversion
-                 and the letters ABCDEF for A conversion. The A conversion specifier
-                 produces a number with X and P instead of x and p. The exponent always
-                 contains at least one digit, and only as many more digits as necessary to
-                 represent the decimal exponent of 2. If the value is zero, the exponent is
-                 zero.
-                 A double argument representing an infinity or NaN is converted in the style
-                 of an f or F conversion specifier.
-

-
-
-
9    If a conversion specification is invalid, the behavior is undefined.286) If any argument is
+
+
9    If a conversion specification is invalid, the behavior is undefined.[286] If any argument is
      not the correct type for the corresponding conversion specification, the behavior is
      undefined.
 

-
 
-
Footnote 286) See ``future library directions'' (7.26.12).
+
Footnote 286) See ``future library directions'' (7.26.12).
 

 
-
+
 
10   In no case does a nonexistent or small field width cause truncation of a field; if the result
      of a conversion is wider than the field width, the field is expanded to contain the
      conversion result.
 

-
-
+
 
11   For a and A conversions, if FLT_RADIX is a power of 2, the value is correctly rounded
      to a hexadecimal floating number with the given precision.
      Recommended practice
 

-
-
+
 
12   For a and A conversions, if FLT_RADIX is not a power of 2 and the result is not exactly
      representable in the given precision, the result should be one of the two adjacent numbers
      in hexadecimal floating style with the given precision, with the extra stipulation that the
      error should have a correct sign for the current rounding direction.
 

-
-
+
 
13   For e, E, f, F, g, and G conversions, if the number of significant decimal digits is at most
-     DECIMAL_DIG, then the result should be correctly rounded.287) If the number of
+     DECIMAL_DIG, then the result should be correctly rounded.[287] If the number of
      significant decimal digits is more than DECIMAL_DIG but the source value is exactly
      representable with DECIMAL_DIG digits, then the result should be an exact
      representation with trailing zeros. Otherwise, the source value is bounded by two
@@ -20159,25 +17438,22 @@ char int_p_sep_by_space
      the error should have a correct sign for the current rounding direction.
      Returns
 

-
 
 
Footnote 287) For binary-to-decimal conversion, the result format's values are the numbers representable with the
           given format specifier. The number of significant digits is determined by the format specifier, and in
           the case of fixed-point conversion by the source value as well.
+     Environmental limits
 

 
-
+
 
14   The fwprintf function returns the number of wide characters transmitted, or a negative
      value if an output or encoding error occurred.
-     Environmental limits
 

-
-
+
 
15   The number of wide characters that can be produced by any single conversion shall be at
      least 4095.
 

-
-
+
 
16   EXAMPLE       To print a date and time in the form ``Sunday, July 3, 10:02'' followed by  to five decimal
      places:
             #include <math.h>
@@ -20190,24 +17466,21 @@ char int_p_sep_by_space
                     weekday, month, day, hour, min);
             fwprintf(stdout, L"pi = %.5f\n", 4 * atan(1.0));
 
-     Forward references:          the btowc function (7.24.6.1.1), the mbrtowc function
-     (7.24.6.3.2).
+     Forward references:          the btowc function (7.24.6.1.1), the mbrtowc function
+     (7.24.6.3.2).
 

-
-
+
 

 
7.24.2.2 [The fwscanf function]

-

-
-
-
1           #include <stdio.h>
+
+
1 Synopsis
+           #include <stdio.h>
             #include <wchar.h>
             int fwscanf(FILE * restrict stream,
                  const wchar_t * restrict format, ...);
      Description
 

-
-
+
 
2    The fwscanf function reads input from the stream pointed to by stream, under
      control of the wide string pointed to by format that specifies the admissible input
      sequences and how they are to be converted for assignment, using subsequent arguments
@@ -20216,8 +17489,7 @@ char int_p_sep_by_space
      arguments remain, the excess arguments are evaluated (as always) but are otherwise
      ignored.
 

-
-
+
 
3    The format is composed of zero or more directives: one or more white-space wide
      characters, an ordinary wide character (neither % nor a white-space wide character), or a
      conversion specification. Each conversion specification is introduced by the wide
@@ -20229,70 +17501,62 @@ char int_p_sep_by_space
      -- A conversion specifier wide character that specifies the type of conversion to be
         applied.
 

-
-
+
 
4    The fwscanf function executes each directive of the format in turn. If a directive fails,
      as detailed below, the function returns. Failures are described as input failures (due to the
      occurrence of an encoding error or the unavailability of input characters), or matching
      failures (due to inappropriate input).
 

-
-
+
 
5    A directive composed of white-space wide character(s) is executed by reading input up to
      the first non-white-space wide character (which remains unread), or until no more wide
      characters can be read.
 

-
-
+
 
6    A directive that is an ordinary wide character is executed by reading the next wide
      character of the stream. If that wide character differs from the directive, the directive
      fails and the differing and subsequent wide characters remain unread. Similarly, if end-
      of-file, an encoding error, or a read error prevents a wide character from being read, the
      directive fails.
 

-
-
+
 
7    A directive that is a conversion specification defines a set of matching input sequences, as
      described below for each specifier. A conversion specification is executed in the
      following steps:
 

-
-
+
 
8    Input white-space wide characters (as specified by the iswspace function) are skipped,
-     unless the specification includes a [, c, or n specifier.288)
+     unless the specification includes a [, c, or n specifier.[288]
 

-
 
 
Footnote 288) These white-space wide characters are not counted against a specified field width.
 

 
-
+
 
9    An input item is read from the stream, unless the specification includes an n specifier. An
      input item is defined as the longest sequence of input wide characters which does not
      exceed any specified field width and which is, or is a prefix of, a matching input
-     sequence.289) The first wide character, if any, after the input item remains unread. If the
+     sequence.[289] The first wide character, if any, after the input item remains unread. If the
      length of the input item is zero, the execution of the directive fails; this condition is a
      matching failure unless end-of-file, an encoding error, or a read error prevented input
      from the stream, in which case it is an input failure.
 

-
 
 
Footnote 289) fwscanf pushes back at most one input wide character onto the input stream. Therefore, some
           sequences that are acceptable to wcstod, wcstol, etc., are unacceptable to fwscanf.
+     object does not have an appropriate type, or if the result of the conversion cannot be
+     represented in the object, the behavior is undefined.
 

 
-
+
 
10   Except in the case of a % specifier, the input item (or, in the case of a %n directive, the
      count of input wide characters) is converted to a type appropriate to the conversion
      specifier. If the input item is not a matching sequence, the execution of the directive fails:
      this condition is a matching failure. Unless assignment suppression was indicated by a *,
      the result of the conversion is placed in the object pointed to by the first argument
      following the format argument that has not already received a conversion result. If this
-     object does not have an appropriate type, or if the result of the conversion cannot be
-     represented in the object, the behavior is undefined.
 

-
-
+
 
11   The length modifiers and their meanings are:
      hh           Specifies that a following d, i, o, u, x, X, or n conversion specifier applies
                   to an argument with type pointer to signed char or unsigned char.
@@ -20320,8 +17584,7 @@ char int_p_sep_by_space
      If a length modifier appears with any conversion specifier other than as specified above,
      the behavior is undefined.
 

-
-
+
 
12   The conversion specifiers and their meanings are:
      d           Matches an optionally signed decimal integer, whose format is the same as
                  expected for the subject sequence of the wcstol function with the value 10
@@ -20412,35 +17675,33 @@ n        No input is consumed. The corresponding argument shall be a pointer to
      %              Matches a single % wide character; no conversion or assignment occurs. The
                     complete conversion specification shall be %%.
 

-
-
-
13   If a conversion specification is invalid, the behavior is undefined.290)
+
+
13   If a conversion specification is invalid, the behavior is undefined.[290]
 

-
 
-
Footnote 290) See ``future library directions'' (7.26.12).
+
Footnote 290) See ``future library directions'' (7.26.12).
+    Forward references: the wcstod, wcstof, and wcstold functions (7.24.4.1.1), the
+    wcstol, wcstoll, wcstoul, and wcstoull functions (7.24.4.1.2), the wcrtomb
+    function (7.24.6.3.3).
 

 
-
+
 
14   The conversion specifiers A, E, F, G, and X are also valid and behave the same as,
      respectively, a, e, f, g, and x.
 

-
-
+
 
15   Trailing white space (including new-line wide characters) is left unread unless matched
      by a directive. The success of literal matches and suppressed assignments is not directly
      determinable other than via the %n directive.
      Returns
 

-
-
+
 
16   The fwscanf function returns the value of the macro EOF if an input failure occurs
      before any conversion. Otherwise, the function returns the number of input items
      assigned, which can be fewer than provided for, or even zero, in the event of an early
      matching failure.
 

-
-
+
 
17   EXAMPLE 1        The call:
               #include <stdio.h>
               #include <wchar.h>
@@ -20453,8 +17714,7 @@ n        No input is consumed. The corresponding argument shall be a pointer to
      thompson\0.
 
 

-
-
+
 
18   EXAMPLE 2        The call:
               #include <stdio.h>
               #include <wchar.h>
@@ -20465,73 +17725,60 @@ n        No input is consumed. The corresponding argument shall be a pointer to
               56789 0123 56a72
      will assign to i the value 56 and to x the value 789.0, will skip past 0123, and will assign to y the value
      56.0. The next wide character read from the input stream will be a.
-    Forward references: the wcstod, wcstof, and wcstold functions (7.24.4.1.1), the
-    wcstol, wcstoll, wcstoul, and wcstoull functions (7.24.4.1.2), the wcrtomb
-    function (7.24.6.3.3).
 

-
-
+
 

 
7.24.2.3 [The swprintf function]

-

-
-
-
1          #include <wchar.h>
+
+
1 Synopsis
+          #include <wchar.h>
            int swprintf(wchar_t * restrict s,
                 size_t n,
                 const wchar_t * restrict format, ...);
     Description
 

-
-
+
 
2   The swprintf function is equivalent to fwprintf, except that the argument s
     specifies an array of wide characters into which the generated output is to be written,
     rather than written to a stream. No more than n wide characters are written, including a
     terminating null wide character, which is always added (unless n is zero).
     Returns
 

-
-
+
 
3   The swprintf function returns the number of wide characters written in the array, not
     counting the terminating null wide character, or a negative value if an encoding error
     occurred or if n or more wide characters were requested to be written.
 

-
-
+
 

 
7.24.2.4 [The swscanf function]

-

-
-
-
1          #include <wchar.h>
+
+
1 Synopsis
+          #include <wchar.h>
            int swscanf(const wchar_t * restrict s,
                 const wchar_t * restrict format, ...);
     Description
 

-
-
+
 
2   The swscanf function is equivalent to fwscanf, except that the argument s specifies a
     wide string from which the input is to be obtained, rather than from a stream. Reaching
     the end of the wide string is equivalent to encountering end-of-file for the fwscanf
     function.
     Returns
 

-
-
+
 
3   The swscanf function returns the value of the macro EOF if an input failure occurs
     before any conversion. Otherwise, the swscanf function returns the number of input
     items assigned, which can be fewer than provided for, or even zero, in the event of an
     early matching failure.
 
 

-
-
+
 

 
7.24.2.5 [The vfwprintf function]

-

-
-
-
1          #include <stdarg.h>
+
+
1 Synopsis
+          #include <stdarg.h>
            #include <stdio.h>
            #include <wchar.h>
            int vfwprintf(FILE * restrict stream,
@@ -20539,26 +17786,23 @@ n        No input is consumed. The corresponding argument shall be a pointer to
                 va_list arg);
     Description
 

-
-
+
 
2   The vfwprintf function is equivalent to fwprintf, with the variable argument list
     replaced by arg, which shall have been initialized by the va_start macro (and
     possibly subsequent va_arg calls). The vfwprintf function does not invoke the
-    va_end macro.291)
+    va_end macro.[291]
     Returns
 

-
 
 
Footnote 291) As the functions vfwprintf, vswprintf, vfwscanf, vwprintf, vwscanf, and vswscanf
          invoke the va_arg macro, the value of arg after the return is indeterminate.
 

 
-
+
 
3   The vfwprintf function returns the number of wide characters transmitted, or a
     negative value if an output or encoding error occurred.
 

-
-
+
 
4   EXAMPLE       The following shows the use of the vfwprintf function in a general error-reporting
     routine.
            #include <stdarg.h>
@@ -20575,14 +17819,12 @@ n        No input is consumed. The corresponding argument shall be a pointer to
                     va_end(args);
            }
 

-
-
+
 

 
7.24.2.6 [The vfwscanf function]

-

-
-
-
1          #include <stdarg.h>
+
+
1 Synopsis
+          #include <stdarg.h>
            #include <stdio.h>
            #include <wchar.h>
            int vfwscanf(FILE * restrict stream,
@@ -20590,34 +17832,30 @@ n        No input is consumed. The corresponding argument shall be a pointer to
                 va_list arg);
     Description
 

-
-
+
 
2   The vfwscanf function is equivalent to fwscanf, with the variable argument list
     replaced by arg, which shall have been initialized by the va_start macro (and
     possibly subsequent va_arg calls). The vfwscanf function does not invoke the
-    va_end macro.291)
+    va_end macro.[291]
     Returns
 

-
 
 
Footnote 291) As the functions vfwprintf, vswprintf, vfwscanf, vwprintf, vwscanf, and vswscanf
          invoke the va_arg macro, the value of arg after the return is indeterminate.
 

 
-
+
 
3   The vfwscanf function returns the value of the macro EOF if an input failure occurs
     before any conversion. Otherwise, the vfwscanf function returns the number of input
     items assigned, which can be fewer than provided for, or even zero, in the event of an
     early matching failure.
 

-
-
+
 

 
7.24.2.7 [The vswprintf function]

-

-
-
-
1          #include <stdarg.h>
+
+
1 Synopsis
+          #include <stdarg.h>
            #include <wchar.h>
            int vswprintf(wchar_t * restrict s,
                 size_t n,
@@ -20625,253 +17863,217 @@ n        No input is consumed. The corresponding argument shall be a pointer to
                 va_list arg);
     Description
 

-
-
+
 
2   The vswprintf function is equivalent to swprintf, with the variable argument list
     replaced by arg, which shall have been initialized by the va_start macro (and
     possibly subsequent va_arg calls). The vswprintf function does not invoke the
-    va_end macro.291)
+    va_end macro.[291]
     Returns
 

-
 
 
Footnote 291) As the functions vfwprintf, vswprintf, vfwscanf, vwprintf, vwscanf, and vswscanf
          invoke the va_arg macro, the value of arg after the return is indeterminate.
 

 
-
+
 
3   The vswprintf function returns the number of wide characters written in the array, not
     counting the terminating null wide character, or a negative value if an encoding error
     occurred or if n or more wide characters were requested to be generated.
 

-
-
+
 

 
7.24.2.8 [The vswscanf function]

-

-
-
-
1          #include <stdarg.h>
+
+
1 Synopsis
+          #include <stdarg.h>
            #include <wchar.h>
            int vswscanf(const wchar_t * restrict s,
                 const wchar_t * restrict format,
                 va_list arg);
     Description
 

-
-
+
 
2   The vswscanf function is equivalent to swscanf, with the variable argument list
     replaced by arg, which shall have been initialized by the va_start macro (and
     possibly subsequent va_arg calls). The vswscanf function does not invoke the
-    va_end macro.291)
+    va_end macro.[291]
     Returns
 

-
 
 
Footnote 291) As the functions vfwprintf, vswprintf, vfwscanf, vwprintf, vwscanf, and vswscanf
          invoke the va_arg macro, the value of arg after the return is indeterminate.
 

 
-
+
 
3   The vswscanf function returns the value of the macro EOF if an input failure occurs
     before any conversion. Otherwise, the vswscanf function returns the number of input
     items assigned, which can be fewer than provided for, or even zero, in the event of an
     early matching failure.
 

-
-
+
 

 
7.24.2.9 [The vwprintf function]

-

-
-
-
1          #include <stdarg.h>
+
+
1 Synopsis
+          #include <stdarg.h>
            #include <wchar.h>
            int vwprintf(const wchar_t * restrict format,
                 va_list arg);
     Description
 

-
-
+
 
2   The vwprintf function is equivalent to wprintf, with the variable argument list
     replaced by arg, which shall have been initialized by the va_start macro (and
     possibly subsequent va_arg calls). The vwprintf function does not invoke the
-    va_end macro.291)
+    va_end macro.[291]
     Returns
 

-
 
 
Footnote 291) As the functions vfwprintf, vswprintf, vfwscanf, vwprintf, vwscanf, and vswscanf
          invoke the va_arg macro, the value of arg after the return is indeterminate.
 

 
-
+
 
3   The vwprintf function returns the number of wide characters transmitted, or a negative
     value if an output or encoding error occurred.
 
 

-
-
+
 

 
7.24.2.10 [The vwscanf function]

-

-
-
-
1          #include <stdarg.h>
+
+
1 Synopsis
+          #include <stdarg.h>
            #include <wchar.h>
            int vwscanf(const wchar_t * restrict format,
                 va_list arg);
     Description
 

-
-
+
 
2   The vwscanf function is equivalent to wscanf, with the variable argument list
     replaced by arg, which shall have been initialized by the va_start macro (and
     possibly subsequent va_arg calls). The vwscanf function does not invoke the
-    va_end macro.291)
+    va_end macro.[291]
     Returns
 

-
 
 
Footnote 291) As the functions vfwprintf, vswprintf, vfwscanf, vwprintf, vwscanf, and vswscanf
          invoke the va_arg macro, the value of arg after the return is indeterminate.
 

 
-
+
 
3   The vwscanf function returns the value of the macro EOF if an input failure occurs
     before any conversion. Otherwise, the vwscanf function returns the number of input
     items assigned, which can be fewer than provided for, or even zero, in the event of an
     early matching failure.
 

-
-
+
 

 
7.24.2.11 [The wprintf function]

-

-
-
-
1          #include <wchar.h>
+
+
1 Synopsis
+          #include <wchar.h>
            int wprintf(const wchar_t * restrict format, ...);
     Description
 

-
-
+
 
2   The wprintf function is equivalent to fwprintf with the argument stdout
     interposed before the arguments to wprintf.
     Returns
 

-
-
+
 
3   The wprintf function returns the number of wide characters transmitted, or a negative
     value if an output or encoding error occurred.
 

-
-
+
 

 
7.24.2.12 [The wscanf function]

-

-
-
-
1          #include <wchar.h>
+
+
1 Synopsis
+          #include <wchar.h>
            int wscanf(const wchar_t * restrict format, ...);
     Description
 

-
-
+
 
2   The wscanf function is equivalent to fwscanf with the argument stdin interposed
     before the arguments to wscanf.
     Returns
 

-
-
+
 
3   The wscanf function returns the value of the macro EOF if an input failure occurs
     before any conversion. Otherwise, the wscanf function returns the number of input
     items assigned, which can be fewer than provided for, or even zero, in the event of an
     early matching failure.
 

-
-
+
 

 
7.24.3 [Wide character input/output functions]

-
 Wide character input/output functions
-

-
-
+
 

 
7.24.3.1 [The fgetwc function]

-

-
-
-
1           #include <stdio.h>
+
+
1 Synopsis
+           #include <stdio.h>
             #include <wchar.h>
             wint_t fgetwc(FILE *stream);
     Description
 

-
-
+
 
2   If the end-of-file indicator for the input stream pointed to by stream is not set and a
     next wide character is present, the fgetwc function obtains that wide character as a
     wchar_t converted to a wint_t and advances the associated file position indicator for
     the stream (if defined).
     Returns
 

-
-
+
 
3   If the end-of-file indicator for the stream is set, or if the stream is at end-of-file, the end-
     of-file indicator for the stream is set and the fgetwc function returns WEOF. Otherwise,
     the fgetwc function returns the next wide character from the input stream pointed to by
     stream. If a read error occurs, the error indicator for the stream is set and the fgetwc
     function returns WEOF. If an encoding error occurs (including too few bytes), the value of
-    the macro EILSEQ is stored in errno and the fgetwc function returns WEOF.292)
+    the macro EILSEQ is stored in errno and the fgetwc function returns WEOF.[292]
 

-
 
 
Footnote 292) An end-of-file and a read error can be distinguished by use of the feof and ferror functions.
          Also, errno will be set to EILSEQ by input/output functions only if an encoding error occurs.
+    additional wide characters are read after a new-line wide character (which is retained) or
+    after end-of-file. A null wide character is written immediately after the last wide
+    character read into the array.
+    Returns
 

 
-
+
 

 
7.24.3.2 [The fgetws function]

-

-
-
-
1           #include <stdio.h>
+
+
1 Synopsis
+           #include <stdio.h>
             #include <wchar.h>
             wchar_t *fgetws(wchar_t * restrict s,
                  int n, FILE * restrict stream);
     Description
 

-
-
+
 
2   The fgetws function reads at most one less than the number of wide characters
     specified by n from the stream pointed to by stream into the array pointed to by s. No
-    additional wide characters are read after a new-line wide character (which is retained) or
-    after end-of-file. A null wide character is written immediately after the last wide
-    character read into the array.
-    Returns
 

-
-
+
 
3   The fgetws function returns s if successful. If end-of-file is encountered and no
     characters have been read into the array, the contents of the array remain unchanged and a
     null pointer is returned. If a read or encoding error occurs during the operation, the array
     contents are indeterminate and a null pointer is returned.
 

-
-
+
 

 
7.24.3.3 [The fputwc function]

-

-
-
-
1          #include <stdio.h>
+
+
1 Synopsis
+          #include <stdio.h>
            #include <wchar.h>
            wint_t fputwc(wchar_t c, FILE *stream);
     Description
 

-
-
+
 
2   The fputwc function writes the wide character specified by c to the output stream
     pointed to by stream, at the position indicated by the associated file position indicator
     for the stream (if defined), and advances the indicator appropriately. If the file cannot
@@ -20879,168 +18081,140 @@ n        No input is consumed. The corresponding argument shall be a pointer to
     character is appended to the output stream.
     Returns
 

-
-
+
 
3   The fputwc function returns the wide character written. If a write error occurs, the
     error indicator for the stream is set and fputwc returns WEOF. If an encoding error
     occurs, the value of the macro EILSEQ is stored in errno and fputwc returns WEOF.
 

-
-
+
 

 
7.24.3.4 [The fputws function]

-

-
-
-
1          #include <stdio.h>
+
+
1 Synopsis
+          #include <stdio.h>
            #include <wchar.h>
            int fputws(const wchar_t * restrict s,
                 FILE * restrict stream);
     Description
 

-
-
+
 
2   The fputws function writes the wide string pointed to by s to the stream pointed to by
     stream. The terminating null wide character is not written.
     Returns
 

-
-
+
 
3   The fputws function returns EOF if a write or encoding error occurs; otherwise, it
     returns a nonnegative value.
 

-
-
+
 

 
7.24.3.5 [The fwide function]

-

-
-
-
1           #include <stdio.h>
+
+
1 Synopsis
+           #include <stdio.h>
             #include <wchar.h>
             int fwide(FILE *stream, int mode);
     Description
 

-
-
+
 
2   The fwide function determines the orientation of the stream pointed to by stream. If
     mode is greater than zero, the function first attempts to make the stream wide oriented. If
-    mode is less than zero, the function first attempts to make the stream byte oriented.293)
+    mode is less than zero, the function first attempts to make the stream byte oriented.[293]
     Otherwise, mode is zero and the function does not alter the orientation of the stream.
     Returns
 

-
 
 
Footnote 293) If the orientation of the stream has already been determined, fwide does not change it.
+    Description
 

 
-
+
 
3   The fwide function returns a value greater than zero if, after the call, the stream has
     wide orientation, a value less than zero if the stream has byte orientation, or zero if the
     stream has no orientation.
 

-
-
+
 

 
7.24.3.6 [The getwc function]

-

-
-
-
1           #include <stdio.h>
+
+
1 Synopsis
+           #include <stdio.h>
             #include <wchar.h>
             wint_t getwc(FILE *stream);
     Description
 

-
-
+
 
2   The getwc function is equivalent to fgetwc, except that if it is implemented as a
     macro, it may evaluate stream more than once, so the argument should never be an
     expression with side effects.
     Returns
 

-
-
+
 
3   The getwc function returns the next wide character from the input stream pointed to by
     stream, or WEOF.
 

-
-
+
 

 
7.24.3.7 [The getwchar function]

-

-
-
-
1           #include <wchar.h>
+
+
1 Synopsis
+           #include <wchar.h>
             wint_t getwchar(void);
-    Description
 

-
-
+
 
2   The getwchar function is equivalent to getwc with the argument stdin.
     Returns
 

-
-
+
 
3   The getwchar function returns the next wide character from the input stream pointed to
     by stdin, or WEOF.
 

-
-
+
 

 
7.24.3.8 [The putwc function]

-

-
-
-
1          #include <stdio.h>
+
+
1 Synopsis
+          #include <stdio.h>
            #include <wchar.h>
            wint_t putwc(wchar_t c, FILE *stream);
     Description
 

-
-
+
 
2   The putwc function is equivalent to fputwc, except that if it is implemented as a
     macro, it may evaluate stream more than once, so that argument should never be an
     expression with side effects.
     Returns
 

-
-
+
 
3   The putwc function returns the wide character written, or WEOF.
 

-
-
+
 

 
7.24.3.9 [The putwchar function]

-

-
-
-
1          #include <wchar.h>
+
+
1 Synopsis
+          #include <wchar.h>
            wint_t putwchar(wchar_t c);
     Description
 

-
-
+
 
2   The putwchar function is equivalent to putwc with the second argument stdout.
     Returns
 

-
-
+
 
3   The putwchar function returns the character written, or WEOF.
 

-
-
+
 

 
7.24.3.10 [The ungetwc function]

-

-
-
-
1          #include <stdio.h>
+
+
1 Synopsis
+          #include <stdio.h>
            #include <wchar.h>
            wint_t ungetwc(wint_t c, FILE *stream);
     Description
 

-
-
+
 
2   The ungetwc function pushes the wide character specified by c back onto the input
     stream pointed to by stream. Pushed-back wide characters will be returned by
     subsequent reads on that stream in the reverse order of their pushing. A successful
@@ -21048,21 +18222,18 @@ n        No input is consumed. The corresponding argument shall be a pointer to
     (fseek, fsetpos, or rewind) discards any pushed-back wide characters for the
     stream. The external storage corresponding to the stream is unchanged.
 

-
-
+
 
3   One wide character of pushback is guaranteed, even if the call to the ungetwc function
     follows just after a call to a formatted wide character input function fwscanf,
     vfwscanf, vwscanf, or wscanf. If the ungetwc function is called too many times
     on the same stream without an intervening read or file positioning operation on that
     stream, the operation may fail.
 

-
-
+
 
4   If the value of c equals that of the macro WEOF, the operation fails and the input stream is
     unchanged.
 

-
-
+
 
5   A successful call to the ungetwc function clears the end-of-file indicator for the stream.
     The value of the file position indicator for the stream after reading or discarding all
     pushed-back wide characters is the same as it was before the wide characters were pushed
@@ -21071,48 +18242,38 @@ n        No input is consumed. The corresponding argument shall be a pointer to
     read or discarded.
     Returns
 

-
-
+
 
6   The ungetwc function returns the wide character pushed back, or WEOF if the operation
     fails.
 

-
-
+
 

 
7.24.4 [General wide string utilities]

-

-
-
+
 
1   The header <wchar.h> declares a number of functions useful for wide string
     manipulation. Various methods are used for determining the lengths of the arrays, but in
     all cases a wchar_t * argument points to the initial (lowest addressed) element of the
     array. If an array is accessed beyond the end of an object, the behavior is undefined.
 

-
-
+
 
2   Where an argument declared as size_t n determines the length of the array for a
     function, n can have the value zero on a call to that function. Unless explicitly stated
     otherwise in the description of a particular function in this subclause, pointer arguments
-    on such a call shall still have valid values, as described in 7.1.4. On such a call, a
+    on such a call shall still have valid values, as described in 7.1.4. On such a call, a
     function that locates a wide character finds no occurrence, a function that compares two
     wide character sequences returns zero, and a function that copies wide characters copies
     zero wide characters.
 
 

-
-
+
 

 
7.24.4.1 [Wide string numeric conversion functions]

-
 Wide string numeric conversion functions
-

-
-
+
 

 
7.24.4.1.1 [The wcstod, wcstof, and wcstold functions]

-

-
-
-
1          #include <wchar.h>
+
+
1 Synopsis
+          #include <wchar.h>
            double wcstod(const wchar_t * restrict nptr,
                 wchar_t ** restrict endptr);
            float wcstof(const wchar_t * restrict nptr,
@@ -21121,8 +18282,7 @@ n        No input is consumed. The corresponding argument shall be a pointer to
                 wchar_t ** restrict endptr);
     Description
 

-
-
+
 
2   The wcstod, wcstof, and wcstold functions convert the initial portion of the wide
     string pointed to by nptr to double, float, and long double representation,
     respectively. First, they decompose the input string into three parts: an initial, possibly
@@ -21132,16 +18292,15 @@ n        No input is consumed. The corresponding argument shall be a pointer to
     including the terminating null wide character of the input wide string. Then, they attempt
     to convert the subject sequence to a floating-point number, and return the result.
 

-
-
+
 
3   The expected form of the subject sequence is an optional plus or minus sign, then one of
     the following:
     -- a nonempty sequence of decimal digits optionally containing a decimal-point wide
        character, then an optional exponent part as defined for the corresponding single-byte
-       characters in 6.4.4.2;
+       characters in 6.4.4.2;
     -- a 0x or 0X, then a nonempty sequence of hexadecimal digits optionally containing a
        decimal-point wide character, then an optional binary exponent part as defined in
-       6.4.4.2;
+       6.4.4.2;
     -- INF or INFINITY, or any other wide string equivalent except for case
     -- NAN or NAN(n-wchar-sequenceopt), or any other wide string equivalent except for
        case in the NAN part, where:
@@ -21155,29 +18314,27 @@ n        No input is consumed. The corresponding argument shall be a pointer to
     The subject sequence contains no wide characters if the input wide string is not of the
     expected form.
 

-
-
+
 
4   If the subject sequence has the expected form for a floating-point number, the sequence of
     wide characters starting with the first digit or the decimal-point wide character
     (whichever occurs first) is interpreted as a floating constant according to the rules of
-     6.4.4.2, except that the decimal-point wide character is used in place of a period, and that
+     6.4.4.2, except that the decimal-point wide character is used in place of a period, and that
     if neither an exponent part nor a decimal-point wide character appears in a decimal
     floating point number, or if a binary exponent part does not appear in a hexadecimal
     floating point number, an exponent part of the appropriate type with value zero is
     assumed to follow the last digit in the string. If the subject sequence begins with a minus
-    sign, the sequence is interpreted as negated.294) A wide character sequence INF or
+    sign, the sequence is interpreted as negated.[294] A wide character sequence INF or
     INFINITY is interpreted as an infinity, if representable in the return type, else like a
     floating constant that is too large for the range of the return type. A wide character
     sequence NAN or NAN(n-wchar-sequenceopt) is interpreted as a quiet NaN, if supported
     in the return type, else like a subject sequence part that does not have the expected form;
-    the meaning of the n-wchar sequences is implementation-defined.295) A pointer to the
+    the meaning of the n-wchar sequences is implementation-defined.[295] A pointer to the
     final wide string is stored in the object pointed to by endptr, provided that endptr is
     not a null pointer.
 

-
 
 
Footnote 294) It is unspecified whether a minus-signed sequence is converted to a negative number directly or by
-         negating the value resulting from converting the corresponding unsigned sequence (see F.5); the two
+         negating the value resulting from converting the corresponding unsigned sequence (see F.5); the two
          methods may yield different results if rounding is toward positive or negative infinity. In either case,
          the functions honor the sign of zero if floating-point arithmetic supports signed zeros.
 

@@ -21187,32 +18344,28 @@ n        No input is consumed. The corresponding argument shall be a pointer to
          the NaN's significand.
 

 
-
+
 
5   If the subject sequence has the hexadecimal form and FLT_RADIX is a power of 2, the
     value resulting from the conversion is correctly rounded.
 

-
-
+
 
6   In other than the "C" locale, additional locale-specific subject sequence forms may be
     accepted.
 

-
-
+
 
7   If the subject sequence is empty or does not have the expected form, no conversion is
     performed; the value of nptr is stored in the object pointed to by endptr, provided
     that endptr is not a null pointer.
     Recommended practice
 

-
-
+
 
8   If the subject sequence has the hexadecimal form, FLT_RADIX is not a power of 2, and
     the result is not exactly representable, the result should be one of the two numbers in the
     appropriate internal format that are adjacent to the hexadecimal floating source value,
     with the extra stipulation that the error should have a correct sign for the current rounding
     direction.
 

-
-
+
 
9    If the subject sequence has the decimal form and at most DECIMAL_DIG (defined in
      <float.h>) significant digits, the result should be correctly rounded. If the subject
      sequence D has the decimal form and more than DECIMAL_DIG significant digits,
@@ -21221,32 +18374,29 @@ n        No input is consumed. The corresponding argument shall be a pointer to
      The result should be one of the (equal or adjacent) values that would be obtained by
      correctly rounding L and U according to the current rounding direction, with the extra
      stipulation that the error with respect to D should have a correct sign for the current
-     rounding direction.296)
+     rounding direction.[296]
      Returns
 

-
 
 
Footnote 296) DECIMAL_DIG, defined in <float.h>, should be sufficiently large that L and U will usually round
           to the same internal floating value, but if not will round to adjacent values.
 

 
-
+
 
10   The functions return the converted value, if any. If no conversion could be performed,
      zero is returned. If the correct value is outside the range of representable values, plus or
      minus HUGE_VAL, HUGE_VALF, or HUGE_VALL is returned (according to the return
      type and sign of the value), and the value of the macro ERANGE is stored in errno. If
-     the result underflows (7.12.1), the functions return a value whose magnitude is no greater
+     the result underflows (7.12.1), the functions return a value whose magnitude is no greater
      than the smallest normalized positive number in the return type; whether errno acquires
      the value ERANGE is implementation-defined.
 

-
-
+
 

 
7.24.4.1.2 [The wcstol, wcstoll, wcstoul, and wcstoull functions]

-

-
-
-
1          #include <wchar.h>
+
+
1 Synopsis
+          #include <wchar.h>
            long int wcstol(
                 const wchar_t * restrict nptr,
                 wchar_t ** restrict endptr,
@@ -21265,8 +18415,7 @@ n        No input is consumed. The corresponding argument shall be a pointer to
                 int base);
     Description
 

-
-
+
 
2   The wcstol, wcstoll, wcstoul, and wcstoull functions convert the initial
     portion of the wide string pointed to by nptr to long int, long long int,
     unsigned long int, and unsigned long long int representation,
@@ -21277,10 +18426,9 @@ n        No input is consumed. The corresponding argument shall be a pointer to
     characters, including the terminating null wide character of the input wide string. Then,
     they attempt to convert the subject sequence to an integer, and return the result.
 

-
-
+
 
3   If the value of base is zero, the expected form of the subject sequence is that of an
-    integer constant as described for the corresponding single-byte characters in 6.4.4.1,
+    integer constant as described for the corresponding single-byte characters in 6.4.4.1,
     optionally preceded by a plus or minus sign, but not including an integer suffix. If the
     value of base is between 2 and 36 (inclusive), the expected form of the subject sequence
     is a sequence of letters and digits representing an integer with the radix specified by
@@ -21290,145 +18438,121 @@ n        No input is consumed. The corresponding argument shall be a pointer to
     value of base is 16, the wide characters 0x or 0X may optionally precede the sequence
     of letters and digits, following the sign if present.
 

-
-
+
 
4   The subject sequence is defined as the longest initial subsequence of the input wide
     string, starting with the first non-white-space wide character, that is of the expected form.
     The subject sequence contains no wide characters if the input wide string is empty or
     consists entirely of white space, or if the first non-white-space wide character is other
     than a sign or a permissible letter or digit.
 

-
-
+
 
5   If the subject sequence has the expected form and the value of base is zero, the sequence
     of wide characters starting with the first digit is interpreted as an integer constant
-    according to the rules of 6.4.4.1. If the subject sequence has the expected form and the
+    according to the rules of 6.4.4.1. If the subject sequence has the expected form and the
     value of base is between 2 and 36, it is used as the base for conversion, ascribing to each
     letter its value as given above. If the subject sequence begins with a minus sign, the value
     resulting from the conversion is negated (in the return type). A pointer to the final wide
     string is stored in the object pointed to by endptr, provided that endptr is not a null
     pointer.
 

-
-
+
 
6   In other than the "C" locale, additional locale-specific subject sequence forms may be
     accepted.
 

-
-
+
 
7   If the subject sequence is empty or does not have the expected form, no conversion is
     performed; the value of nptr is stored in the object pointed to by endptr, provided
     that endptr is not a null pointer.
     Returns
 

-
-
+
 
8   The wcstol, wcstoll, wcstoul, and wcstoull functions return the converted
     value, if any. If no conversion could be performed, zero is returned. If the correct value
     is outside the range of representable values, LONG_MIN, LONG_MAX, LLONG_MIN,
     LLONG_MAX, ULONG_MAX, or ULLONG_MAX is returned (according to the return type
     sign of the value, if any), and the value of the macro ERANGE is stored in errno.
 

-
-
+
 

 
7.24.4.2 [Wide string copying functions]

-
 Wide string copying functions
-

-
-
+
 

 
7.24.4.2.1 [The wcscpy function]

-

-
-
-
1          #include <wchar.h>
+
+
1 Synopsis
+          #include <wchar.h>
            wchar_t *wcscpy(wchar_t * restrict s1,
                 const wchar_t * restrict s2);
     Description
 

-
-
+
 
2   The wcscpy function copies the wide string pointed to by s2 (including the terminating
     null wide character) into the array pointed to by s1.
     Returns
 

-
-
+
 
3   The wcscpy function returns the value of s1.
 

-
-
+
 

 
7.24.4.2.2 [The wcsncpy function]

-

-
-
-
1            #include <wchar.h>
+
+
1 Synopsis
+            #include <wchar.h>
              wchar_t *wcsncpy(wchar_t * restrict s1,
                   const wchar_t * restrict s2,
                   size_t n);
     Description
 

-
-
+
 
2   The wcsncpy function copies not more than n wide characters (those that follow a null
     wide character are not copied) from the array pointed to by s2 to the array pointed to by
-    s1.297)
+    s1.[297]
 

-
 
 
Footnote 297) Thus, if there is no null wide character in the first n wide characters of the array pointed to by s2, the
          result will not be null-terminated.
 

 
-
+
 
3   If the array pointed to by s2 is a wide string that is shorter than n wide characters, null
     wide characters are appended to the copy in the array pointed to by s1, until n wide
     characters in all have been written.
     Returns
 

-
-
+
 
4   The wcsncpy function returns the value of s1.
 

-
-
+
 

 
7.24.4.2.3 [The wmemcpy function]

-

-
-
-
1            #include <wchar.h>
+
+
1 Synopsis
+            #include <wchar.h>
              wchar_t *wmemcpy(wchar_t * restrict s1,
                   const wchar_t * restrict s2,
                   size_t n);
     Description
 

-
-
+
 
2   The wmemcpy function copies n wide characters from the object pointed to by s2 to the
     object pointed to by s1.
     Returns
 

-
-
+
 
3   The wmemcpy function returns the value of s1.
 

-
-
+
 

 
7.24.4.2.4 [The wmemmove function]

-

-
-
-
1          #include <wchar.h>
+
+
1 Synopsis
+          #include <wchar.h>
            wchar_t *wmemmove(wchar_t *s1, const wchar_t *s2,
                 size_t n);
     Description
 

-
-
+
 
2   The wmemmove function copies n wide characters from the object pointed to by s2 to
     the object pointed to by s1. Copying takes place as if the n wide characters from the
     object pointed to by s2 are first copied into a temporary array of n wide characters that
@@ -21436,169 +18560,139 @@ n        No input is consumed. The corresponding argument shall be a pointer to
     the temporary array are copied into the object pointed to by s1.
     Returns
 

-
-
+
 
3   The wmemmove function returns the value of s1.
 

-
-
+
 

 
7.24.4.3 [Wide string concatenation functions]

-
 Wide string concatenation functions
-

-
-
+
 

 
7.24.4.3.1 [The wcscat function]

-

-
-
-
1          #include <wchar.h>
+
+
1 Synopsis
+          #include <wchar.h>
            wchar_t *wcscat(wchar_t * restrict s1,
                 const wchar_t * restrict s2);
     Description
 

-
-
+
 
2   The wcscat function appends a copy of the wide string pointed to by s2 (including the
     terminating null wide character) to the end of the wide string pointed to by s1. The initial
     wide character of s2 overwrites the null wide character at the end of s1.
     Returns
 

-
-
+
 
3   The wcscat function returns the value of s1.
 

-
-
+
 

 
7.24.4.3.2 [The wcsncat function]

-

-
-
-
1          #include <wchar.h>
+
+
1 Synopsis
+          #include <wchar.h>
            wchar_t *wcsncat(wchar_t * restrict s1,
                 const wchar_t * restrict s2,
                 size_t n);
     Description
 

-
-
+
 
2   The wcsncat function appends not more than n wide characters (a null wide character
     and those that follow it are not appended) from the array pointed to by s2 to the end of
     the wide string pointed to by s1. The initial wide character of s2 overwrites the null
     wide character at the end of s1. A terminating null wide character is always appended to
-    the result.298)
+    the result.[298]
     Returns
 

-
 
 
Footnote 298) Thus, the maximum number of wide characters that can end up in the array pointed to by s1 is
          wcslen(s1)+n+1.
+    wide string pointed to by s2 when both are interpreted as appropriate to the current
+    locale.
 

 
-
+
 
3   The wcsncat function returns the value of s1.
 

-
-
+
 

 
7.24.4.4 [Wide string comparison functions]

-

-
-
+
 
1   Unless explicitly stated otherwise, the functions described in this subclause order two
     wide characters the same way as two integers of the underlying integer type designated
     by wchar_t.
 

-
-
+
 

 
7.24.4.4.1 [The wcscmp function]

-

-
-
-
1           #include <wchar.h>
+
+
1 Synopsis
+           #include <wchar.h>
             int wcscmp(const wchar_t *s1, const wchar_t *s2);
     Description
 

-
-
+
 
2   The wcscmp function compares the wide string pointed to by s1 to the wide string
     pointed to by s2.
     Returns
 

-
-
+
 
3   The wcscmp function returns an integer greater than, equal to, or less than zero,
     accordingly as the wide string pointed to by s1 is greater than, equal to, or less than the
     wide string pointed to by s2.
 

-
-
+
 

 
7.24.4.4.2 [The wcscoll function]

-

-
-
-
1           #include <wchar.h>
+
+
1 Synopsis
+           #include <wchar.h>
             int wcscoll(const wchar_t *s1, const wchar_t *s2);
     Description
 

-
-
+
 
2   The wcscoll function compares the wide string pointed to by s1 to the wide string
     pointed to by s2, both interpreted as appropriate to the LC_COLLATE category of the
     current locale.
     Returns
 

-
-
+
 
3   The wcscoll function returns an integer greater than, equal to, or less than zero,
     accordingly as the wide string pointed to by s1 is greater than, equal to, or less than the
-    wide string pointed to by s2 when both are interpreted as appropriate to the current
-    locale.
 

-
-
+
 

 
7.24.4.4.3 [The wcsncmp function]

-

-
-
-
1          #include <wchar.h>
+
+
1 Synopsis
+          #include <wchar.h>
            int wcsncmp(const wchar_t *s1, const wchar_t *s2,
                 size_t n);
     Description
 

-
-
+
 
2   The wcsncmp function compares not more than n wide characters (those that follow a
     null wide character are not compared) from the array pointed to by s1 to the array
     pointed to by s2.
     Returns
 

-
-
+
 
3   The wcsncmp function returns an integer greater than, equal to, or less than zero,
     accordingly as the possibly null-terminated array pointed to by s1 is greater than, equal
     to, or less than the possibly null-terminated array pointed to by s2.
 

-
-
+
 

 
7.24.4.4.4 [The wcsxfrm function]

-

-
-
-
1          #include <wchar.h>
+
+
1 Synopsis
+          #include <wchar.h>
            size_t wcsxfrm(wchar_t * restrict s1,
                 const wchar_t * restrict s2,
                 size_t n);
     Description
 

-
-
+
 
2   The wcsxfrm function transforms the wide string pointed to by s2 and places the
     resulting wide string into the array pointed to by s1. The transformation is such that if
     the wcscmp function is applied to two transformed wide strings, it returns a value greater
@@ -21608,243 +18702,201 @@ n        No input is consumed. The corresponding argument shall be a pointer to
     n is zero, s1 is permitted to be a null pointer.
     Returns
 

-
-
+
 
3   The wcsxfrm function returns the length of the transformed wide string (not including
     the terminating null wide character). If the value returned is n or greater, the contents of
     the array pointed to by s1 are indeterminate.
 

-
-
+
 
4   EXAMPLE The value of the following expression is the length of the array needed to hold the
     transformation of the wide string pointed to by s:
            1 + wcsxfrm(NULL, s, 0)
 
 

-
-
+
 

 
7.24.4.4.5 [The wmemcmp function]

-

-
-
-
1          #include <wchar.h>
+
+
1 Synopsis
+          #include <wchar.h>
            int wmemcmp(const wchar_t *s1, const wchar_t *s2,
                 size_t n);
     Description
 

-
-
+
 
2   The wmemcmp function compares the first n wide characters of the object pointed to by
     s1 to the first n wide characters of the object pointed to by s2.
     Returns
 

-
-
+
 
3   The wmemcmp function returns an integer greater than, equal to, or less than zero,
     accordingly as the object pointed to by s1 is greater than, equal to, or less than the object
     pointed to by s2.
 

-
-
+
 

 
7.24.4.5 [Wide string search functions]

-
 Wide string search functions
-

-
-
+
 

 
7.24.4.5.1 [The wcschr function]

-

-
-
-
1          #include <wchar.h>
+
+
1 Synopsis
+          #include <wchar.h>
            wchar_t *wcschr(const wchar_t *s, wchar_t c);
     Description
 

-
-
+
 
2   The wcschr function locates the first occurrence of c in the wide string pointed to by s.
     The terminating null wide character is considered to be part of the wide string.
     Returns
 

-
-
+
 
3   The wcschr function returns a pointer to the located wide character, or a null pointer if
     the wide character does not occur in the wide string.
 

-
-
+
 

 
7.24.4.5.2 [The wcscspn function]

-

-
-
-
1          #include <wchar.h>
+
+
1 Synopsis
+          #include <wchar.h>
            size_t wcscspn(const wchar_t *s1, const wchar_t *s2);
     Description
 

-
-
+
 
2   The wcscspn function computes the length of the maximum initial segment of the wide
     string pointed to by s1 which consists entirely of wide characters not from the wide
     string pointed to by s2.
     Returns
 

-
-
+
 
3   The wcscspn function returns the length of the segment.
 

-
-
+
 

 
7.24.4.5.3 [The wcspbrk function]

-

-
-
-
1          #include <wchar.h>
+
+
1 Synopsis
+          #include <wchar.h>
            wchar_t *wcspbrk(const wchar_t *s1, const wchar_t *s2);
     Description
 

-
-
+
 
2   The wcspbrk function locates the first occurrence in the wide string pointed to by s1 of
     any wide character from the wide string pointed to by s2.
     Returns
 

-
-
+
 
3   The wcspbrk function returns a pointer to the wide character in s1, or a null pointer if
     no wide character from s2 occurs in s1.
 

-
-
+
 

 
7.24.4.5.4 [The wcsrchr function]

-

-
-
-
1          #include <wchar.h>
+
+
1 Synopsis
+          #include <wchar.h>
            wchar_t *wcsrchr(const wchar_t *s, wchar_t c);
     Description
 

-
-
+
 
2   The wcsrchr function locates the last occurrence of c in the wide string pointed to by
     s. The terminating null wide character is considered to be part of the wide string.
     Returns
 

-
-
+
 
3   The wcsrchr function returns a pointer to the wide character, or a null pointer if c does
     not occur in the wide string.
 

-
-
+
 

 
7.24.4.5.5 [The wcsspn function]

-

-
-
-
1          #include <wchar.h>
+
+
1 Synopsis
+          #include <wchar.h>
            size_t wcsspn(const wchar_t *s1, const wchar_t *s2);
     Description
 

-
-
+
 
2   The wcsspn function computes the length of the maximum initial segment of the wide
     string pointed to by s1 which consists entirely of wide characters from the wide string
     pointed to by s2.
     Returns
 

-
-
+
 
3   The wcsspn function returns the length of the segment.
 

-
-
+
 

 
7.24.4.5.6 [The wcsstr function]

-

-
-
-
1          #include <wchar.h>
+
+
1 Synopsis
+          #include <wchar.h>
            wchar_t *wcsstr(const wchar_t *s1, const wchar_t *s2);
     Description
 

-
-
+
 
2   The wcsstr function locates the first occurrence in the wide string pointed to by s1 of
     the sequence of wide characters (excluding the terminating null wide character) in the
     wide string pointed to by s2.
     Returns
 

-
-
+
 
3   The wcsstr function returns a pointer to the located wide string, or a null pointer if the
     wide string is not found. If s2 points to a wide string with zero length, the function
     returns s1.
 

-
-
+
 

 
7.24.4.5.7 [The wcstok function]

-

-
-
-
1          #include <wchar.h>
+
+
1 Synopsis
+          #include <wchar.h>
            wchar_t *wcstok(wchar_t * restrict s1,
                 const wchar_t * restrict s2,
                 wchar_t ** restrict ptr);
     Description
 

-
-
+
 
2   A sequence of calls to the wcstok function breaks the wide string pointed to by s1 into
     a sequence of tokens, each of which is delimited by a wide character from the wide string
     pointed to by s2. The third argument points to a caller-provided wchar_t pointer into
     which the wcstok function stores information necessary for it to continue scanning the
     same wide string.
 

-
-
+
 
3   The first call in a sequence has a non-null first argument and stores an initial value in the
     object pointed to by ptr. Subsequent calls in the sequence have a null first argument and
     the object pointed to by ptr is required to have the value stored by the previous call in
     the sequence, which is then updated. The separator wide string pointed to by s2 may be
     different from call to call.
 

-
-
+
 
4   The first call in the sequence searches the wide string pointed to by s1 for the first wide
     character that is not contained in the current separator wide string pointed to by s2. If no
     such wide character is found, then there are no tokens in the wide string pointed to by s1
     and the wcstok function returns a null pointer. If such a wide character is found, it is
     the start of the first token.
 

-
-
+
 
5   The wcstok function then searches from there for a wide character that is contained in
     the current separator wide string. If no such wide character is found, the current token
     extends to the end of the wide string pointed to by s1, and subsequent searches in the
     same wide string for a token return a null pointer. If such a wide character is found, it is
     overwritten by a null wide character, which terminates the current token.
 

-
-
+
 
6   In all cases, the wcstok function stores sufficient information in the pointer pointed to
     by ptr so that subsequent calls, with a null pointer for s1 and the unmodified pointer
     value for ptr, shall start searching just past the element overwritten by a null wide
     character (if any).
     Returns
 

-
-
+
 
7   The wcstok function returns a pointer to the first wide character of a token, or a null
     pointer if there is no token.
 

-
-
+
 
8   EXAMPLE
            #include <wchar.h>
            static wchar_t str1[] = L"?a???b,,,#c";
@@ -21857,92 +18909,72 @@ n        No input is consumed. The corresponding argument shall be a pointer to
            t   =   wcstok(NULL,   L"?", &ptr1);          //   t   is a null pointer
 
 

-
-
+
 

 
7.24.4.5.8 [The wmemchr function]

-

-
-
-
1          #include <wchar.h>
+
+
1 Synopsis
+          #include <wchar.h>
            wchar_t *wmemchr(const wchar_t *s, wchar_t c,
                 size_t n);
     Description
 

-
-
+
 
2   The wmemchr function locates the first occurrence of c in the initial n wide characters of
     the object pointed to by s.
     Returns
 

-
-
+
 
3   The wmemchr function returns a pointer to the located wide character, or a null pointer if
     the wide character does not occur in the object.
 
 

-
-
+
 

 
7.24.4.6 [Miscellaneous functions]

-
 Miscellaneous functions
-

-
-
+
 

 
7.24.4.6.1 [The wcslen function]

-

-
-
-
1          #include <wchar.h>
+
+
1 Synopsis
+          #include <wchar.h>
            size_t wcslen(const wchar_t *s);
     Description
 

-
-
+
 
2   The wcslen function computes the length of the wide string pointed to by s.
     Returns
 

-
-
+
 
3   The wcslen function returns the number of wide characters that precede the terminating
     null wide character.
 

-
-
+
 

 
7.24.4.6.2 [The wmemset function]

-

-
-
-
1          #include <wchar.h>
+
+
1 Synopsis
+          #include <wchar.h>
            wchar_t *wmemset(wchar_t *s, wchar_t c, size_t n);
     Description
 

-
-
+
 
2   The wmemset function copies the value of c into each of the first n wide characters of
     the object pointed to by s.
     Returns
 

-
-
+
 
3   The wmemset function returns the value of s.
 

-
-
+
 

 
7.24.5 [Wide character time conversion functions]

-
 Wide character time conversion functions
-

-
-
+
 

 
7.24.5.1 [The wcsftime function]

-

-
-
-
1          #include <time.h>
+
+
1 Synopsis
+          #include <time.h>
            #include <wchar.h>
            size_t wcsftime(wchar_t * restrict s,
                 size_t maxsize,
@@ -21950,8 +18982,7 @@ n        No input is consumed. The corresponding argument shall be a pointer to
                 const struct tm * restrict timeptr);
     Description
 

-
-
+
 
2   The wcsftime function is equivalent to the strftime function, except that:
     -- The argument s points to the initial element of an array of wide characters into which
        the generated output is to be placed.
@@ -21961,34 +18992,28 @@ n        No input is consumed. The corresponding argument shall be a pointer to
     -- The return value indicates the number of wide characters.
     Returns
 

-
-
+
 
3   If the total number of resulting wide characters including the terminating null wide
     character is not more than maxsize, the wcsftime function returns the number of
     wide characters placed into the array pointed to by s not including the terminating null
     wide character. Otherwise, zero is returned and the contents of the array are
     indeterminate.
 

-
-
+
 

 
7.24.6 [Extended multibyte/wide character conversion utilities]

-

-
-
+
 
1   The header <wchar.h> declares an extended set of functions useful for conversion
     between multibyte characters and wide characters.
 

-
-
-
2   Most of the following functions -- those that are listed as ``restartable'', 7.24.6.3 and 7.24.6.4
+
+
2   Most of the following functions -- those that are listed as ``restartable'', 7.24.6.3 and 7.24.6.4
     -- take as a last argument a pointer to an object of type mbstate_t that is used
     to describe the current conversion state from a particular multibyte character sequence to
     a wide character sequence (or the reverse) under the rules of a particular setting for the
     LC_CTYPE category of the current locale.
 

-
-
+
 
3   The initial conversion state corresponds, for a conversion in either direction, to the
     beginning of a new multibyte character in the initial shift state. A zero-valued
     mbstate_t object is (at least) one way to describe an initial conversion state. A zero-
@@ -21997,112 +19022,90 @@ n        No input is consumed. The corresponding argument shall be a pointer to
     been altered by any of the functions described in this subclause, and is then used with a
     different multibyte character sequence, or in the other conversion direction, or with a
     different LC_CTYPE category setting than on earlier function calls, the behavior is
-    undefined.299)
+    undefined.[299]
 

-
 
 
Footnote 299) Thus, a particular mbstate_t object can be used, for example, with both the mbrtowc and
          mbsrtowcs functions as long as they are used to step sequentially through the same multibyte
          character string.
 

 
-
+
 
4   On entry, each function takes the described conversion state (either internal or pointed to
     by an argument) as current. The conversion state described by the pointed-to object is
     altered as needed to track the shift state, and the position within a multibyte character, for
     the associated multibyte character sequence.
 

-
-
+
 

 
7.24.6.1 [Single-byte/wide character conversion functions]

-
 Single-byte/wide character conversion functions
-

-
-
+
 

 
7.24.6.1.1 [The btowc function]

-

-
-
-
1          #include <stdio.h>
+
+
1 Synopsis
+          #include <stdio.h>
            #include <wchar.h>
            wint_t btowc(int c);
     Description
 

-
-
+
 
2   The btowc function determines whether c constitutes a valid single-byte character in the
     initial shift state.
     Returns
 

-
-
+
 
3   The btowc function returns WEOF if c has the value EOF or if (unsigned char)c
     does not constitute a valid single-byte character in the initial shift state. Otherwise, it
     returns the wide character representation of that character.
 

-
-
+
 

 
7.24.6.1.2 [The wctob function]

-

-
-
-
1          #include <stdio.h>
+
+
1 Synopsis
+          #include <stdio.h>
            #include <wchar.h>
            int wctob(wint_t c);
     Description
 

-
-
+
 
2   The wctob function determines whether c corresponds to a member of the extended
     character set whose multibyte character representation is a single byte when in the initial
     shift state.
     Returns
 

-
-
+
 
3   The wctob function returns EOF if c does not correspond to a multibyte character with
     length one in the initial shift state. Otherwise, it returns the single-byte representation of
     that character as an unsigned char converted to an int.
 

-
-
+
 

 
7.24.6.2 [Conversion state functions]

-
 Conversion state functions
-

-
-
+
 

 
7.24.6.2.1 [The mbsinit function]

-

-
-
-
1          #include <wchar.h>
+
+
1 Synopsis
+          #include <wchar.h>
            int mbsinit(const mbstate_t *ps);
     Description
 

-
-
+
 
2   If ps is not a null pointer, the mbsinit function determines whether the pointed-to
     mbstate_t object describes an initial conversion state.
     Returns
 

-
-
+
 
3   The mbsinit function returns nonzero if ps is a null pointer or if the pointed-to object
     describes an initial conversion state; otherwise, it returns zero.
 

-
-
+
 

 
7.24.6.3 [Restartable multibyte/wide character conversion functions]

-

-
-
-
1   These functions differ from the corresponding multibyte character functions of 7.20.7
+
+
1   These functions differ from the corresponding multibyte character functions of 7.20.7
     (mblen, mbtowc, and wctomb) in that they have an extra parameter, ps, of type
     pointer to mbstate_t that points to an object that can completely describe the current
     conversion state of the associated multibyte character sequence. If ps is a null pointer,
@@ -22110,61 +19113,52 @@ n        No input is consumed. The corresponding argument shall be a pointer to
     program startup to the initial conversion state. The implementation behaves as if no
     library function calls these functions with a null pointer for ps.
 

-
-
+
 
2   Also unlike their corresponding functions, the return value does not represent whether the
     encoding is state-dependent.
 

-
-
+
 

 
7.24.6.3.1 [The mbrlen function]

-

-
-
-
1          #include <wchar.h>
+
+
1 Synopsis
+          #include <wchar.h>
            size_t mbrlen(const char * restrict s,
                 size_t n,
                 mbstate_t * restrict ps);
     Description
 

-
-
+
 
2   The mbrlen function is equivalent to the call:
            mbrtowc(NULL, s, n, ps != NULL ? ps : &internal)
     where internal is the mbstate_t object for the mbrlen function, except that the
     expression designated by ps is evaluated only once.
     Returns
 

-
-
+
 
3   The mbrlen function returns a value between zero and n, inclusive, (size_t)(-2),
     or (size_t)(-1).
-    Forward references: the mbrtowc function (7.24.6.3.2).
+    Forward references: the mbrtowc function (7.24.6.3.2).
 
 

-
-
+
 

 
7.24.6.3.2 [The mbrtowc function]

-

-
-
-
1           #include <wchar.h>
+
+
1 Synopsis
+           #include <wchar.h>
             size_t mbrtowc(wchar_t * restrict pwc,
                  const char * restrict s,
                  size_t n,
                  mbstate_t * restrict ps);
     Description
 

-
-
+
 
2   If s is a null pointer, the mbrtowc function is equivalent to the call:
                     mbrtowc(NULL, "", 1, ps)
     In this case, the values of the parameters pwc and n are ignored.
 

-
-
+
 
3   If s is not a null pointer, the mbrtowc function inspects at most n bytes beginning with
     the byte pointed to by s to determine the number of bytes needed to complete the next
     multibyte character (including any shift sequences). If the function determines that the
@@ -22174,8 +19168,7 @@ n        No input is consumed. The corresponding argument shall be a pointer to
     character, the resulting state described is the initial conversion state.
     Returns
 

-
-
+
 
4   The mbrtowc function returns the first of the following that applies (given the current
     conversion state):
     0                     if the next n or fewer bytes complete the multibyte character that
@@ -22185,38 +19178,34 @@ n        No input is consumed. The corresponding argument shall be a pointer to
                        of bytes that complete the multibyte character.
     (size_t)(-2) if the next n bytes contribute to an incomplete (but potentially valid)
                  multibyte character, and all n bytes have been processed (no value is
-                 stored).300)
+                 stored).[300]
     (size_t)(-1) if an encoding error occurs, in which case the next n or fewer bytes
                  do not contribute to a complete and valid multibyte character (no
                  value is stored); the value of the macro EILSEQ is stored in errno,
                  and the conversion state is unspecified.
 

-
 
 
Footnote 300) When n has at least the value of the MB_CUR_MAX macro, this case can only occur if s points at a
          sequence of redundant shift sequences (for implementations with state-dependent encodings).
 

 
-
+
 

 
7.24.6.3.3 [The wcrtomb function]

-

-
-
-
1           #include <wchar.h>
+
+
1 Synopsis
+           #include <wchar.h>
             size_t wcrtomb(char * restrict s,
                  wchar_t wc,
                  mbstate_t * restrict ps);
     Description
 

-
-
+
 
2   If s is a null pointer, the wcrtomb function is equivalent to the call
                     wcrtomb(buf, L'\0', ps)
     where buf is an internal buffer.
 

-
-
+
 
3   If s is not a null pointer, the wcrtomb function determines the number of bytes needed
     to represent the multibyte character that corresponds to the wide character given by wc
     (including any shift sequences), and stores the multibyte character representation in the
@@ -22225,21 +19214,17 @@ n        No input is consumed. The corresponding argument shall be a pointer to
     to restore the initial shift state; the resulting state described is the initial conversion state.
     Returns
 

-
-
+
 
4   The wcrtomb function returns the number of bytes stored in the array object (including
     any shift sequences). When wc is not a valid wide character, an encoding error occurs:
     the function stores the value of the macro EILSEQ in errno and returns
     (size_t)(-1); the conversion state is unspecified.
 

-
-
+
 

 
7.24.6.4 [Restartable multibyte/wide string conversion functions]

-

-
-
-
1   These functions differ from the corresponding multibyte string functions of 7.20.8
+
+
1   These functions differ from the corresponding multibyte string functions of 7.20.8
     (mbstowcs and wcstombs) in that they have an extra parameter, ps, of type pointer to
     mbstate_t that points to an object that can completely describe the current conversion
     state of the associated multibyte character sequence. If ps is a null pointer, each function
@@ -22247,30 +19232,26 @@ n        No input is consumed. The corresponding argument shall be a pointer to
     to the initial conversion state. The implementation behaves as if no library function calls
     these functions with a null pointer for ps.
 

-
-
+
 
2   Also unlike their corresponding functions, the conversion source parameter, src, has a
     pointer-to-pointer type. When the function is storing the results of conversions (that is,
     when dst is not a null pointer), the pointer object pointed to by this parameter is updated
     to reflect the amount of the source processed by that invocation.
 
 

-
-
+
 

 
7.24.6.4.1 [The mbsrtowcs function]

-

-
-
-
1            #include <wchar.h>
+
+
1 Synopsis
+            #include <wchar.h>
              size_t mbsrtowcs(wchar_t * restrict dst,
                   const char ** restrict src,
                   size_t len,
                   mbstate_t * restrict ps);
     Description
 

-
-
+
 
2   The mbsrtowcs function converts a sequence of multibyte characters that begins in the
     conversion state described by the object pointed to by ps, from the array indirectly
     pointed to by src into a sequence of corresponding wide characters. If dst is not a null
@@ -22278,15 +19259,14 @@ n        No input is consumed. The corresponding argument shall be a pointer to
     continues up to and including a terminating null character, which is also stored.
     Conversion stops earlier in two cases: when a sequence of bytes is encountered that does
     not form a valid multibyte character, or (if dst is not a null pointer) when len wide
-    characters have been stored into the array pointed to by dst.301) Each conversion takes
+    characters have been stored into the array pointed to by dst.[301] Each conversion takes
     place as if by a call to the mbrtowc function.
 

-
 
 
Footnote 301) Thus, the value of len is ignored if dst is a null pointer.
 

 
-
+
 
3   If dst is not a null pointer, the pointer object pointed to by src is assigned either a null
     pointer (if conversion stopped due to reaching a terminating null character) or the address
     just past the last multibyte character converted (if any). If conversion stopped due to
@@ -22294,30 +19274,26 @@ n        No input is consumed. The corresponding argument shall be a pointer to
     described is the initial conversion state.
     Returns
 

-
-
+
 
4   If the input conversion encounters a sequence of bytes that do not form a valid multibyte
     character, an encoding error occurs: the mbsrtowcs function stores the value of the
     macro EILSEQ in errno and returns (size_t)(-1); the conversion state is
     unspecified. Otherwise, it returns the number of multibyte characters successfully
     converted, not including the terminating null character (if any).
 

-
-
+
 

 
7.24.6.4.2 [The wcsrtombs function]

-

-
-
-
1           #include <wchar.h>
+
+
1 Synopsis
+           #include <wchar.h>
             size_t wcsrtombs(char * restrict dst,
                  const wchar_t ** restrict src,
                  size_t len,
                  mbstate_t * restrict ps);
     Description
 

-
-
+
 
2   The wcsrtombs function converts a sequence of wide characters from the array
     indirectly pointed to by src into a sequence of corresponding multibyte characters that
     begins in the conversion state described by the object pointed to by ps. If dst is not a
@@ -22327,15 +19303,14 @@ n        No input is consumed. The corresponding argument shall be a pointer to
     not correspond to a valid multibyte character, or (if dst is not a null pointer) when the
     next multibyte character would exceed the limit of len total bytes to be stored into the
     array pointed to by dst. Each conversion takes place as if by a call to the wcrtomb
-    function.302)
+    function.[302]
 

-
 
 
Footnote 302) If conversion stops because a terminating null wide character has been reached, the bytes stored
          include those necessary to reach the initial shift state immediately before the null byte.
 

 
-
+
 
3   If dst is not a null pointer, the pointer object pointed to by src is assigned either a null
     pointer (if conversion stopped due to reaching a terminating null wide character) or the
     address just past the last wide character converted (if any). If conversion stopped due to
@@ -22343,38 +19318,30 @@ n        No input is consumed. The corresponding argument shall be a pointer to
     conversion state.
     Returns
 

-
-
+
 
4   If conversion stops because a wide character is reached that does not correspond to a
     valid multibyte character, an encoding error occurs: the wcsrtombs function stores the
     value of the macro EILSEQ in errno and returns (size_t)(-1); the conversion
     state is unspecified. Otherwise, it returns the number of bytes in the resulting multibyte
     character sequence, not including the terminating null character (if any).
 

-
-
+
 

-
7.25 [Wide character classification and mapping utilities ]

-
 Wide character classification and mapping utilities 
-

-
-
+
7.25 [Wide character classification and mapping utilities <wctype.h>]

+
 

 
7.25.1 [Introduction]

-

-
-
-
1   The header <wctype.h> declares three data types, one macro, and many functions.303)
+
+
1   The header <wctype.h> declares three data types, one macro, and many functions.[303]
 

-
 
-
Footnote 303) See ``future library directions'' (7.26.13).
+
Footnote 303) See ``future library directions'' (7.26.13).
 

 
-
+
 
2   The types declared are
              wint_t
-    described in 7.24.1;
+    described in 7.24.1;
              wctrans_t
     which is a scalar type that can hold values which represent locale-specific character
     mappings; and
@@ -22382,320 +19349,260 @@ n        No input is consumed. The corresponding argument shall be a pointer to
     which is a scalar type that can hold values which represent locale-specific character
     classifications.
 

-
-
-
3   The macro defined is WEOF (described in 7.24.1).
+
+
3   The macro defined is WEOF (described in 7.24.1).
 

-
-
+
 
4   The functions declared are grouped as follows:
     -- Functions that provide wide character classification;
     -- Extensible functions that provide wide character classification;
     -- Functions that provide wide character case mapping;
     -- Extensible functions that provide wide character mapping.
 

-
-
+
 
5   For all functions described in this subclause that accept an argument of type wint_t, the
     value shall be representable as a wchar_t or shall equal the value of the macro WEOF. If
     this argument has any other value, the behavior is undefined.
 

-
-
+
 
6   The behavior of these functions is affected by the LC_CTYPE category of the current
     locale.
 

-
-
+
 

 
7.25.2 [Wide character classification utilities]

-

-
-
+
 
1   The header <wctype.h> declares several functions useful for classifying wide
     characters.
 

-
-
+
 
2   The term printing wide character refers to a member of a locale-specific set of wide
     characters, each of which occupies at least one printing position on a display device. The
     term control wide character refers to a member of a locale-specific set of wide characters
     that are not printing wide characters.
 

-
-
+
 

 
7.25.2.1 [Wide character classification functions]

-

-
-
+
 
1   The functions in this subclause return nonzero (true) if and only if the value of the
     argument wc conforms to that in the description of the function.
 

-
-
+
 
2   Each of the following functions returns true for each wide character that corresponds (as
     if by a call to the wctob function) to a single-byte character for which the corresponding
-    character classification function from 7.4.1 returns true, except that the iswgraph and
+    character classification function from 7.4.1 returns true, except that the iswgraph and
     iswpunct functions may differ with respect to wide characters other than L' ' that are
-    both printing and white-space wide characters.304)
-    Forward references: the wctob function (7.24.6.1.2).
+    both printing and white-space wide characters.[304]
+    Forward references: the wctob function (7.24.6.1.2).
 

-
 
 
Footnote 304) For example, if the expression isalpha(wctob(wc)) evaluates to true, then the call
          iswalpha(wc) also returns true. But, if the expression isgraph(wctob(wc)) evaluates to true
          (which cannot occur for wc == L' ' of course), then either iswgraph(wc) or iswprint(wc)
          && iswspace(wc) is true, but not both.
+    wide characters for which none of iswcntrl, iswdigit, iswpunct, or iswspace
+    is true.305)
 

 
-
+
 

 
7.25.2.1.1 [The iswalnum function]

-

-
-
-
1          #include <wctype.h>
+
+
1 Synopsis
+          #include <wctype.h>
            int iswalnum(wint_t wc);
     Description
 

-
-
+
 
2   The iswalnum function tests for any wide character for which iswalpha or
     iswdigit is true.
 

-
-
+
 

 
7.25.2.1.2 [The iswalpha function]

-

-
-
-
1          #include <wctype.h>
+
+
1 Synopsis
+          #include <wctype.h>
            int iswalpha(wint_t wc);
     Description
 

-
-
+
 
2   The iswalpha function tests for any wide character for which iswupper or
     iswlower is true, or any wide character that is one of a locale-specific set of alphabetic
-    wide characters for which none of iswcntrl, iswdigit, iswpunct, or iswspace
-    is true.305)
 

-
-
-
Footnote 305) The functions iswlower and iswupper test true or false separately for each of these additional
-         wide characters; all four combinations are possible.
-

-
-
+
 

 
7.25.2.1.3 [The iswblank function]

-

-
-
-
1           #include <wctype.h>
+
+
1 Synopsis
+           #include <wctype.h>
             int iswblank(wint_t wc);
     Description
 

-
-
+
 
2   The iswblank function tests for any wide character that is a standard blank wide
     character or is one of a locale-specific set of wide characters for which iswspace is true
     and that is used to separate words within a line of text. The standard blank wide
     characters are the following: space (L' '), and horizontal tab (L'\t'). In the "C"
     locale, iswblank returns true only for the standard blank characters.
 

-
-
+
 

 
7.25.2.1.4 [The iswcntrl function]

-

-
-
-
1           #include <wctype.h>
+
+
1 Synopsis
+           #include <wctype.h>
             int iswcntrl(wint_t wc);
     Description
 

-
-
+
 
2   The iswcntrl function tests for any control wide character.
 

-
-
+
 

 
7.25.2.1.5 [The iswdigit function]

-

-
-
-
1           #include <wctype.h>
+
+
1 Synopsis
+           #include <wctype.h>
             int iswdigit(wint_t wc);
     Description
 

-
-
+
 
2   The iswdigit function tests for any wide character that corresponds to a decimal-digit
-    character (as defined in 5.2.1).
+    character (as defined in 5.2.1).
 

-
-
+
 

 
7.25.2.1.6 [The iswgraph function]

-

-
-
-
1           #include <wctype.h>
+
+
1 Synopsis
+           #include <wctype.h>
             int iswgraph(wint_t wc);
-    Description
 

-
-
+
 
2   The iswgraph function tests for any wide character for which iswprint is true and
-    iswspace is false.306)
+    iswspace is false.[306]
 

-
 
 
Footnote 306) Note that the behavior of the iswgraph and iswpunct functions may differ from their
-         corresponding functions in 7.4.1 with respect to printing, white-space, single-byte execution
+         corresponding functions in 7.4.1 with respect to printing, white-space, single-byte execution
          characters other than ' '.
+    Description
 

 
-
+
 

 
7.25.2.1.7 [The iswlower function]

-

-
-
-
1           #include <wctype.h>
+
+
1 Synopsis
+           #include <wctype.h>
             int iswlower(wint_t wc);
     Description
 

-
-
+
 
2   The iswlower function tests for any wide character that corresponds to a lowercase
     letter or is one of a locale-specific set of wide characters for which none of iswcntrl,
     iswdigit, iswpunct, or iswspace is true.
 

-
-
+
 

 
7.25.2.1.8 [The iswprint function]

-

-
-
-
1           #include <wctype.h>
+
+
1 Synopsis
+           #include <wctype.h>
             int iswprint(wint_t wc);
     Description
 

-
-
+
 
2   The iswprint function tests for any printing wide character.
 

-
-
+
 

 
7.25.2.1.9 [The iswpunct function]

-

-
-
-
1           #include <wctype.h>
+
+
1 Synopsis
+           #include <wctype.h>
             int iswpunct(wint_t wc);
     Description
 

-
-
+
 
2   The iswpunct function tests for any printing wide character that is one of a locale-
     specific set of punctuation wide characters for which neither iswspace nor iswalnum
-    is true.306)
+    is true.[306]
 

-
 
 
Footnote 306) Note that the behavior of the iswgraph and iswpunct functions may differ from their
-         corresponding functions in 7.4.1 with respect to printing, white-space, single-byte execution
+         corresponding functions in 7.4.1 with respect to printing, white-space, single-byte execution
          characters other than ' '.
+    Description
 

 
-
+
 

 
7.25.2.1.10 [The iswspace function]

-

-
-
-
1           #include <wctype.h>
+
+
1 Synopsis
+           #include <wctype.h>
             int iswspace(wint_t wc);
-    Description
 

-
-
+
 
2   The iswspace function tests for any wide character that corresponds to a locale-specific
     set of white-space wide characters for which none of iswalnum, iswgraph, or
     iswpunct is true.
 

-
-
+
 

 
7.25.2.1.11 [The iswupper function]

-

-
-
-
1          #include <wctype.h>
+
+
1 Synopsis
+          #include <wctype.h>
            int iswupper(wint_t wc);
     Description
 

-
-
+
 
2   The iswupper function tests for any wide character that corresponds to an uppercase
     letter or is one of a locale-specific set of wide characters for which none of iswcntrl,
     iswdigit, iswpunct, or iswspace is true.
 

-
-
+
 

 
7.25.2.1.12 [The iswxdigit function]

-

-
-
-
1          #include <wctype.h>
+
+
1 Synopsis
+          #include <wctype.h>
            int iswxdigit(wint_t wc);
     Description
 

-
-
+
 
2   The iswxdigit function tests for any wide character that corresponds to a
-    hexadecimal-digit character (as defined in 6.4.4.1).
+    hexadecimal-digit character (as defined in 6.4.4.1).
 

-
-
+
 

 
7.25.2.2 [Extensible wide character classification functions]

-

-
-
+
 
1   The functions wctype and iswctype provide extensible wide character classification
     as well as testing equivalent to that performed by the functions described in the previous
-    subclause (7.25.2.1).
+    subclause (7.25.2.1).
 

-
-
+
 

 
7.25.2.2.1 [The iswctype function]

-

-
-
-
1          #include <wctype.h>
+
+
1 Synopsis
+          #include <wctype.h>
            int iswctype(wint_t wc, wctype_t desc);
     Description
 

-
-
+
 
2   The iswctype function determines whether the wide character wc has the property
     described by desc. The current setting of the LC_CTYPE category shall be the same as
     during the call to wctype that returned the value desc.
 

-
-
+
 
3   Each of the following expressions has a truth-value equivalent to the call to the wide
-    character classification function (7.25.2.1) in the comment that follows the expression:
+    character classification function (7.25.2.1) in the comment that follows the expression:
            iswctype(wc,       wctype("alnum"))            //   iswalnum(wc)
            iswctype(wc,       wctype("alpha"))            //   iswalpha(wc)
            iswctype(wc,       wctype("blank"))            //   iswblank(wc)
@@ -22710,192 +19617,153 @@ n        No input is consumed. The corresponding argument shall be a pointer to
            iswctype(wc,       wctype("xdigit"))           //   iswxdigit(wc)
     Returns
 

-
-
+
 
4   The iswctype function returns nonzero (true) if and only if the value of the wide
     character wc has the property described by desc.
-    Forward references: the wctype function (7.25.2.2.2).
+    Forward references: the wctype function (7.25.2.2.2).
 

-
-
+
 

 
7.25.2.2.2 [The wctype function]

-

-
-
-
1          #include <wctype.h>
+
+
1 Synopsis
+          #include <wctype.h>
            wctype_t wctype(const char *property);
     Description
 

-
-
+
 
2   The wctype function constructs a value with type wctype_t that describes a class of
     wide characters identified by the string argument property.
 

-
-
+
 
3   The strings listed in the description of the iswctype function shall be valid in all
     locales as property arguments to the wctype function.
     Returns
 

-
-
+
 
4   If property identifies a valid class of wide characters according to the LC_CTYPE
     category of the current locale, the wctype function returns a nonzero value that is valid
-    as the second argument to the iswctype function; otherwise, it returns zero.              
+    as the second argument to the iswctype function; otherwise, it returns zero.
 
 

-
-
+
 

 
7.25.3 [Wide character case mapping utilities]

-

-
-
+
 
1   The header <wctype.h> declares several functions useful for mapping wide characters.
 

-
-
+
 

 
7.25.3.1 [Wide character case mapping functions]

-
 Wide character case mapping functions
-

-
-
+
 

 
7.25.3.1.1 [The towlower function]

-

-
-
-
1          #include <wctype.h>
+
+
1 Synopsis
+          #include <wctype.h>
            wint_t towlower(wint_t wc);
     Description
 

-
-
+
 
2   The towlower function converts an uppercase letter to a corresponding lowercase letter.
     Returns
 

-
-
+
 
3   If the argument is a wide character for which iswupper is true and there are one or
     more corresponding wide characters, as specified by the current locale, for which
     iswlower is true, the towlower function returns one of the corresponding wide
     characters (always the same one for any given locale); otherwise, the argument is
     returned unchanged.
 

-
-
+
 

 
7.25.3.1.2 [The towupper function]

-

-
-
-
1          #include <wctype.h>
+
+
1 Synopsis
+          #include <wctype.h>
            wint_t towupper(wint_t wc);
     Description
 

-
-
+
 
2   The towupper function converts a lowercase letter to a corresponding uppercase letter.
     Returns
 

-
-
+
 
3   If the argument is a wide character for which iswlower is true and there are one or
     more corresponding wide characters, as specified by the current locale, for which
     iswupper is true, the towupper function returns one of the corresponding wide
     characters (always the same one for any given locale); otherwise, the argument is
     returned unchanged.
 

-
-
+
 

 
7.25.3.2 [Extensible wide character case mapping functions]

-

-
-
+
 
1   The functions wctrans and towctrans provide extensible wide character mapping as
     well as case mapping equivalent to that performed by the functions described in the
-    previous subclause (7.25.3.1).
+    previous subclause (7.25.3.1).
 
 

-
-
+
 

 
7.25.3.2.1 [The towctrans function]

-

-
-
-
1          #include <wctype.h>
+
+
1 Synopsis
+          #include <wctype.h>
            wint_t towctrans(wint_t wc, wctrans_t desc);
     Description
 

-
-
+
 
2   The towctrans function maps the wide character wc using the mapping described by
     desc. The current setting of the LC_CTYPE category shall be the same as during the call
     to wctrans that returned the value desc.
 

-
-
+
 
3   Each of the following expressions behaves the same as the call to the wide character case
-    mapping function (7.25.3.1) in the comment that follows the expression:
+    mapping function (7.25.3.1) in the comment that follows the expression:
            towctrans(wc, wctrans("tolower"))                      // towlower(wc)
            towctrans(wc, wctrans("toupper"))                      // towupper(wc)
     Returns
 

-
-
+
 
4   The towctrans function returns the mapped value of wc using the mapping described
     by desc.
 

-
-
+
 

 
7.25.3.2.2 [The wctrans function]

-

-
-
-
1          #include <wctype.h>
+
+
1 Synopsis
+          #include <wctype.h>
            wctrans_t wctrans(const char *property);
     Description
 

-
-
+
 
2   The wctrans function constructs a value with type wctrans_t that describes a
     mapping between wide characters identified by the string argument property.
 

-
-
+
 
3   The strings listed in the description of the towctrans function shall be valid in all
     locales as property arguments to the wctrans function.
     Returns
 

-
-
+
 
4   If property identifies a valid mapping of wide characters according to the LC_CTYPE
     category of the current locale, the wctrans function returns a nonzero value that is valid
     as the second argument to the towctrans function; otherwise, it returns zero.
 
 

-
-
+
 

 
7.26 [Future library directions]

-

-
-
+
 
1   The following names are grouped under individual headers for convenience. All external
     names described below are reserved no matter what headers are included by the program.
 

-
-
+
 

-
7.26.1 [Complex arithmetic ]

-

-
-
+
7.26.1 [Complex arithmetic <complex.h>]

+
 
1   The function names
          cerf                cexpm1              clog2
          cerfc               clog10              clgamma
@@ -22903,173 +19771,127 @@ n        No input is consumed. The corresponding argument shall be a pointer to
     and the same names suffixed with f or l may be added to the declarations in the
     <complex.h> header.
 

-
-
+
 

-
7.26.2 [Character handling ]

-

-
-
+
7.26.2 [Character handling <ctype.h>]

+
 
1   Function names that begin with either is or to, and a lowercase letter may be added to
     the declarations in the <ctype.h> header.
 

-
-
+
 

-
7.26.3 [Errors ]

-

-
-
+
7.26.3 [Errors <errno.h>]

+
 
1   Macros that begin with E and a digit or E and an uppercase letter may be added to the
     declarations in the <errno.h> header.
 

-
-
+
 

-
7.26.4 [Format conversion of integer types ]

-

-
-
+
7.26.4 [Format conversion of integer types <inttypes.h>]

+
 
1   Macro names beginning with PRI or SCN followed by any lowercase letter or X may be
     added to the macros defined in the <inttypes.h> header.
 

-
-
+
 

-
7.26.5 [Localization ]

-

-
-
+
7.26.5 [Localization <locale.h>]

+
 
1   Macros that begin with LC_ and an uppercase letter may be added to the definitions in
     the <locale.h> header.
 

-
-
+
 

-
7.26.6 [Signal handling ]

-

-
-
+
7.26.6 [Signal handling <signal.h>]

+
 
1   Macros that begin with either SIG and an uppercase letter or SIG_ and an uppercase
     letter may be added to the definitions in the <signal.h> header.
 

-
-
+
 

-
7.26.7 [Boolean type and values ]

-

-
-
+
7.26.7 [Boolean type and values <stdbool.h>]

+
 
1   The ability to undefine and perhaps then redefine the macros bool, true, and false is
     an obsolescent feature.
 

-
-
+
 

-
7.26.8 [Integer types ]

-

-
-
+
7.26.8 [Integer types <stdint.h>]

+
 
1   Typedef names beginning with int or uint and ending with _t may be added to the
     types defined in the <stdint.h> header. Macro names beginning with INT or UINT
     and ending with _MAX, _MIN, or _C may be added to the macros defined in the
     <stdint.h> header.
 

-
-
+
 

-
7.26.9 [Input/output ]

-

-
-
+
7.26.9 [Input/output <stdio.h>]

+
 
1   Lowercase letters may be added to the conversion specifiers and length modifiers in
     fprintf and fscanf. Other characters may be used in extensions.
 

-
-
+
 
2   The gets function is obsolescent, and is deprecated.
 

-
-
+
 
3   The use of ungetc on a binary stream where the file position indicator is zero prior to
     the call is an obsolescent feature.
 

-
-
+
 

-
7.26.10 [General utilities ]

-

-
-
+
7.26.10 [General utilities <stdlib.h>]

+
 
1   Function names that begin with str and a lowercase letter may be added to the
     declarations in the <stdlib.h> header.
 

-
-
+
 

-
7.26.11 [String handling ]

-

-
-
+
7.26.11 [String handling <string.h>]

+
 
1   Function names that begin with str, mem, or wcs and a lowercase letter may be added
     to the declarations in the <string.h> header.
 

-
-
+
 

-
7.26.12 [Extended multibyte and wide character utilities ]

-

-
-
+
7.26.12 [Extended multibyte and wide character utilities <wchar.h>]

+
 
1   Function names that begin with wcs and a lowercase letter may be added to the
     declarations in the <wchar.h> header.
 

-
-
+
 
2   Lowercase letters may be added to the conversion specifiers and length modifiers in
     fwprintf and fwscanf. Other characters may be used in extensions.
 

-
-
+
 

 
7.26.13 [Wide character classification and mapping utilities]

-

-
-
-
1   Function names that begin with is or to and a lowercase letter may be added to the
+
+
1 <wctype.h>
+   Function names that begin with is or to and a lowercase letter may be added to the
     declarations in the <wctype.h> header.
 
                                                    Annex A
                                                  (informative)
 

-
-
+
 

 
A. [Language syntax summary]

-

-
-
-
1   NOTE     The notation is described in 6.1.
+
+
1   NOTE     The notation is described in 6.1.
 
 

-
-
+
 

 
A.1 [Lexical grammar]

-
 Lexical grammar
-

-
-
+
 

 
A.1.1 [Lexical elements]

-
 Lexical elements
-    (6.4) token:
+
(6.4) token:
                      keyword
                      identifier
                      constant
                      string-literal
                      punctuator
-    (6.4) preprocessing-token:
+    (6.4) preprocessing-token:
                   header-name
                   identifier
                   pp-number
@@ -23078,12 +19900,10 @@ n        No input is consumed. The corresponding argument shall be a pointer to
                   punctuator
                   each non-white-space character that cannot be one of the above
 

-
-
+
 

 
A.1.2 [Keywords]

-
 Keywords
-    (6.4.1) keyword: one of
+
(6.4.1) keyword: one of
                   auto                      enum             restrict     unsigned
                   break                     extern           return       void
                   case                      float            short        volatile
@@ -23095,204 +19915,190 @@ n        No input is consumed. The corresponding argument shall be a pointer to
                   double                    long             typedef
                   else                      register         union
 

-
-
+
 

 
A.1.3 [Identifiers]

-
 Identifiers
-(6.4.2.1) identifier:
+
(6.4.2.1) identifier:
                identifier-nondigit
                identifier identifier-nondigit
                identifier digit
-(6.4.2.1) identifier-nondigit:
+(6.4.2.1) identifier-nondigit:
                nondigit
                universal-character-name
                other implementation-defined characters
-(6.4.2.1) nondigit: one of
+(6.4.2.1) nondigit: one of
               _ a b          c    d   e    f    g   h    i   j   k   l   m
                    n o       p    q   r    s    t   u    v   w   x   y   z
                    A B       C    D   E    F    G   H    I   J   K   L   M
                    N O       P    Q   R    S    T   U    V   W   X   Y   Z
-(6.4.2.1) digit: one of
+(6.4.2.1) digit: one of
                0 1 2         3    4   5    6    7   8    9
 

-
-
+
 

 
A.1.4 [Universal character names]

-
 Universal character names
-(6.4.3) universal-character-name:
+
(6.4.3) universal-character-name:
               \u hex-quad
               \U hex-quad hex-quad
-(6.4.3) hex-quad:
+(6.4.3) hex-quad:
               hexadecimal-digit hexadecimal-digit
                            hexadecimal-digit hexadecimal-digit
 

-
-
+
 

 
A.1.5 [Constants]

-
 Constants
-(6.4.4) constant:
+
(6.4.4) constant:
               integer-constant
               floating-constant
               enumeration-constant
               character-constant
-(6.4.4.1) integer-constant:
+(6.4.4.1) integer-constant:
                decimal-constant integer-suffixopt
                octal-constant integer-suffixopt
                hexadecimal-constant integer-suffixopt
-(6.4.4.1) decimal-constant:
+(6.4.4.1) decimal-constant:
               nonzero-digit
               decimal-constant digit
-(6.4.4.1) octal-constant:
+(6.4.4.1) octal-constant:
                0
                octal-constant octal-digit
-(6.4.4.1) hexadecimal-constant:
+(6.4.4.1) hexadecimal-constant:
               hexadecimal-prefix hexadecimal-digit
               hexadecimal-constant hexadecimal-digit
-(6.4.4.1) hexadecimal-prefix: one of
+(6.4.4.1) hexadecimal-prefix: one of
               0x 0X
-(6.4.4.1) nonzero-digit: one of
+(6.4.4.1) nonzero-digit: one of
               1 2 3 4 5              6      7   8    9
-(6.4.4.1) octal-digit: one of
+(6.4.4.1) octal-digit: one of
                0 1 2 3           4   5      6   7
-(6.4.4.1) hexadecimal-digit: one of
+(6.4.4.1) hexadecimal-digit: one of
               0 1 2 3 4 5                   6   7    8   9
               a b c d e f
               A B C D E F
-(6.4.4.1) integer-suffix:
+(6.4.4.1) integer-suffix:
                unsigned-suffix long-suffixopt
                unsigned-suffix long-long-suffix
                long-suffix unsigned-suffixopt
                long-long-suffix unsigned-suffixopt
-(6.4.4.1) unsigned-suffix: one of
+(6.4.4.1) unsigned-suffix: one of
                u U
-(6.4.4.1) long-suffix: one of
+(6.4.4.1) long-suffix: one of
                l L
-(6.4.4.1) long-long-suffix: one of
+(6.4.4.1) long-long-suffix: one of
                ll LL
-(6.4.4.2) floating-constant:
+(6.4.4.2) floating-constant:
                 decimal-floating-constant
                 hexadecimal-floating-constant
-(6.4.4.2) decimal-floating-constant:
+(6.4.4.2) decimal-floating-constant:
               fractional-constant exponent-partopt floating-suffixopt
               digit-sequence exponent-part floating-suffixopt
 
-(6.4.4.2) hexadecimal-floating-constant:
+(6.4.4.2) hexadecimal-floating-constant:
               hexadecimal-prefix hexadecimal-fractional-constant
                              binary-exponent-part floating-suffixopt
               hexadecimal-prefix hexadecimal-digit-sequence
                              binary-exponent-part floating-suffixopt
-(6.4.4.2) fractional-constant:
+(6.4.4.2) fractional-constant:
                digit-sequenceopt . digit-sequence
                digit-sequence .
-(6.4.4.2) exponent-part:
+(6.4.4.2) exponent-part:
               e signopt digit-sequence
               E signopt digit-sequence
-(6.4.4.2) sign: one of
+(6.4.4.2) sign: one of
                + -
-(6.4.4.2) digit-sequence:
+(6.4.4.2) digit-sequence:
                digit
                digit-sequence digit
-(6.4.4.2) hexadecimal-fractional-constant:
+(6.4.4.2) hexadecimal-fractional-constant:
               hexadecimal-digit-sequenceopt .
                              hexadecimal-digit-sequence
               hexadecimal-digit-sequence .
-(6.4.4.2) binary-exponent-part:
+(6.4.4.2) binary-exponent-part:
                p signopt digit-sequence
                P signopt digit-sequence
-(6.4.4.2) hexadecimal-digit-sequence:
+(6.4.4.2) hexadecimal-digit-sequence:
               hexadecimal-digit
               hexadecimal-digit-sequence hexadecimal-digit
-(6.4.4.2) floating-suffix: one of
+(6.4.4.2) floating-suffix: one of
                 f l F L
-(6.4.4.3) enumeration-constant:
+(6.4.4.3) enumeration-constant:
               identifier
-(6.4.4.4) character-constant:
-              ' c-char-sequence '
-              L' c-char-sequence '
+(6.4.4.4) character-constant:
+              ' c-char-sequence '
+              L' c-char-sequence '
 
-(6.4.4.4) c-char-sequence:
+(6.4.4.4) c-char-sequence:
                c-char
                c-char-sequence c-char
-(6.4.4.4) c-char:
+(6.4.4.4) c-char:
                any member of the source character set except
-                            the single-quote ', backslash \, or new-line character
+                            the single-quote ', backslash \, or new-line character
                escape-sequence
-(6.4.4.4) escape-sequence:
+(6.4.4.4) escape-sequence:
               simple-escape-sequence
               octal-escape-sequence
               hexadecimal-escape-sequence
               universal-character-name
-(6.4.4.4) simple-escape-sequence: one of
-              \' \" \? \\
+(6.4.4.4) simple-escape-sequence: one of
+              \' \" \? \\
               \a \b \f \n \r \t                   \v
-(6.4.4.4) octal-escape-sequence:
+(6.4.4.4) octal-escape-sequence:
                \ octal-digit
                \ octal-digit octal-digit
                \ octal-digit octal-digit octal-digit
-(6.4.4.4) hexadecimal-escape-sequence:
+(6.4.4.4) hexadecimal-escape-sequence:
               \x hexadecimal-digit
               hexadecimal-escape-sequence hexadecimal-digit
 

-
-
+
 

 
A.1.6 [String literals]

-
 String literals
-(6.4.5) string-literal:
-               " s-char-sequenceopt "
-               L" s-char-sequenceopt "
-(6.4.5) s-char-sequence:
+
(6.4.5) string-literal:
+               " s-char-sequenceopt "
+               L" s-char-sequenceopt "
+(6.4.5) s-char-sequence:
                s-char
                s-char-sequence s-char
-(6.4.5) s-char:
+(6.4.5) s-char:
                any member of the source character set except
-                            the double-quote ", backslash \, or new-line character
+                            the double-quote ", backslash \, or new-line character
                escape-sequence
 

-
-
+
 

 
A.1.7 [Punctuators]

-
 Punctuators
-(6.4.6) punctuator: one of
-              [ ] ( ) { } . ->
-              ++ -- & * + - ~ !
-              / % << >> < > <= >=                     ==      !=    ^    |    &&   ||
+
(6.4.6) punctuator: one of
+              [ ] ( ) { } . ->
+              ++ -- & * + - ~ !
+              / % << >> < > <= >=                     ==      !=    ^    |    &&   ||
               ? : ; ...
-              = *= /= %= += -= <<=                    >>=      &=       ^=   |=
+              = *= /= %= += -= <<=                    >>=      &=       ^=   |=
               , # ##
-              <: :> <% %> %: %:%:
+              <: :> <% %> %: %:%:
 

-
-
+
 

 
A.1.8 [Header names]

-
 Header names
-(6.4.7) header-name:
-              < h-char-sequence >
-              " q-char-sequence "
-(6.4.7) h-char-sequence:
+
(6.4.7) header-name:
+              < h-char-sequence >
+              " q-char-sequence "
+(6.4.7) h-char-sequence:
               h-char
               h-char-sequence h-char
-(6.4.7) h-char:
+(6.4.7) h-char:
               any member of the source character set except
-                           the new-line character and >
-(6.4.7) q-char-sequence:
+                           the new-line character and >
+(6.4.7) q-char-sequence:
               q-char
               q-char-sequence q-char
-(6.4.7) q-char:
+(6.4.7) q-char:
               any member of the source character set except
-                           the new-line character and "
+                           the new-line character and "
 

-
-
+
 

 
A.1.9 [Preprocessing numbers]

-
 Preprocessing numbers
-(6.4.8) pp-number:
+
(6.4.8) pp-number:
               digit
               . digit
               pp-number   digit
@@ -23303,125 +20109,118 @@ n        No input is consumed. The corresponding argument shall be a pointer to
               pp-number   P sign
               pp-number   .
 

-
-
+
 

 
A.2 [Phrase structure grammar]

-
 Phrase structure grammar
-

-
-
+
 

 
A.2.1 [Expressions]

-
 Expressions
-(6.5.1) primary-expression:
+
(6.5.1) primary-expression:
               identifier
               constant
               string-literal
               ( expression )
-(6.5.2) postfix-expression:
+(6.5.2) postfix-expression:
                primary-expression
                postfix-expression [ expression ]
                postfix-expression ( argument-expression-listopt )
                postfix-expression . identifier
-               postfix-expression -> identifier
+               postfix-expression -> identifier
                postfix-expression ++
                postfix-expression --
                ( type-name ) { initializer-list }
                ( type-name ) { initializer-list , }
-(6.5.2) argument-expression-list:
+(6.5.2) argument-expression-list:
              assignment-expression
              argument-expression-list , assignment-expression
-(6.5.3) unary-expression:
+(6.5.3) unary-expression:
               postfix-expression
               ++ unary-expression
               -- unary-expression
               unary-operator cast-expression
               sizeof unary-expression
               sizeof ( type-name )
-(6.5.3) unary-operator: one of
-              & * + - ~             !
-(6.5.4) cast-expression:
+(6.5.3) unary-operator: one of
+              & * + - ~             !
+(6.5.4) cast-expression:
                unary-expression
                ( type-name ) cast-expression
-(6.5.5) multiplicative-expression:
+(6.5.5) multiplicative-expression:
                cast-expression
                multiplicative-expression * cast-expression
                multiplicative-expression / cast-expression
                multiplicative-expression % cast-expression
-(6.5.6) additive-expression:
+(6.5.6) additive-expression:
                multiplicative-expression
                additive-expression + multiplicative-expression
                additive-expression - multiplicative-expression
-(6.5.7) shift-expression:
+(6.5.7) shift-expression:
                 additive-expression
-                shift-expression << additive-expression
-                shift-expression >> additive-expression
-(6.5.8) relational-expression:
+                shift-expression << additive-expression
+                shift-expression >> additive-expression
+(6.5.8) relational-expression:
                shift-expression
-               relational-expression   <    shift-expression
-               relational-expression   >    shift-expression
-               relational-expression   <=   shift-expression
-               relational-expression   >=   shift-expression
-(6.5.9) equality-expression:
+               relational-expression   <    shift-expression
+               relational-expression   >    shift-expression
+               relational-expression   <=   shift-expression
+               relational-expression   >=   shift-expression
+(6.5.9) equality-expression:
                relational-expression
                equality-expression == relational-expression
                equality-expression != relational-expression
-(6.5.10) AND-expression:
+(6.5.10) AND-expression:
              equality-expression
-             AND-expression & equality-expression
-(6.5.11) exclusive-OR-expression:
+             AND-expression & equality-expression
+(6.5.11) exclusive-OR-expression:
               AND-expression
               exclusive-OR-expression ^ AND-expression
-(6.5.12) inclusive-OR-expression:
+(6.5.12) inclusive-OR-expression:
                exclusive-OR-expression
                inclusive-OR-expression | exclusive-OR-expression
-(6.5.13) logical-AND-expression:
+(6.5.13) logical-AND-expression:
               inclusive-OR-expression
-              logical-AND-expression && inclusive-OR-expression
-(6.5.14) logical-OR-expression:
+              logical-AND-expression && inclusive-OR-expression
+(6.5.14) logical-OR-expression:
               logical-AND-expression
               logical-OR-expression || logical-AND-expression
-(6.5.15) conditional-expression:
+(6.5.15) conditional-expression:
               logical-OR-expression
               logical-OR-expression ? expression : conditional-expression
-(6.5.16) assignment-expression:
+(6.5.16) assignment-expression:
               conditional-expression
               unary-expression assignment-operator assignment-expression
-(6.5.16) assignment-operator: one of
-              = *= /= %= +=                -=    <<=     >>=       &=   ^=   |=
-(6.5.17) expression:
+(6.5.16) assignment-operator: one of
+              = *= /= %= +=                -=    <<=     >>=       &=   ^=   |=
+(6.5.17) expression:
               assignment-expression
               expression , assignment-expression
-(6.6) constant-expression:
+(6.6) constant-expression:
               conditional-expression
 

-
-
+
 

 
A.2.2 [Declarations]

-
 Declarations
-(6.7) declaration:
+
(6.7) declaration:
                declaration-specifiers init-declarator-listopt ;
-(6.7) declaration-specifiers:
+(6.7) declaration-specifiers:
                storage-class-specifier declaration-specifiersopt
                type-specifier declaration-specifiersopt
                type-qualifier declaration-specifiersopt
                function-specifier declaration-specifiersopt
-(6.7) init-declarator-list:
+(6.7) init-declarator-list:
                init-declarator
                init-declarator-list , init-declarator
-(6.7) init-declarator:
+(6.7) init-declarator:
                declarator
                declarator = initializer
-(6.7.1) storage-class-specifier:
+(6.7.1) storage-class-specifier:
               typedef
               extern
               static
               auto
               register
 
-(6.7.2) type-specifier:
+(6.7.2) type-specifier:
                void
                char
                short
@@ -23433,49 +20232,49 @@ n        No input is consumed. The corresponding argument shall be a pointer to
                unsigned
                _Bool
                _Complex
-               struct-or-union-specifier                                                 
+               struct-or-union-specifier
                enum-specifier
                typedef-name
-(6.7.2.1) struct-or-union-specifier:
+(6.7.2.1) struct-or-union-specifier:
                struct-or-union identifieropt { struct-declaration-list }
                struct-or-union identifier
-(6.7.2.1) struct-or-union:
+(6.7.2.1) struct-or-union:
                struct
                union
-(6.7.2.1) struct-declaration-list:
+(6.7.2.1) struct-declaration-list:
                struct-declaration
                struct-declaration-list struct-declaration
-(6.7.2.1) struct-declaration:
+(6.7.2.1) struct-declaration:
                specifier-qualifier-list struct-declarator-list ;
-(6.7.2.1) specifier-qualifier-list:
+(6.7.2.1) specifier-qualifier-list:
                type-specifier specifier-qualifier-listopt
                type-qualifier specifier-qualifier-listopt
-(6.7.2.1) struct-declarator-list:
+(6.7.2.1) struct-declarator-list:
                struct-declarator
                struct-declarator-list , struct-declarator
-(6.7.2.1) struct-declarator:
+(6.7.2.1) struct-declarator:
                declarator
                declaratoropt : constant-expression
 
-(6.7.2.2) enum-specifier:
+(6.7.2.2) enum-specifier:
               enum identifieropt { enumerator-list }
               enum identifieropt { enumerator-list , }
               enum identifier
-(6.7.2.2) enumerator-list:
+(6.7.2.2) enumerator-list:
               enumerator
               enumerator-list , enumerator
-(6.7.2.2) enumerator:
+(6.7.2.2) enumerator:
               enumeration-constant
               enumeration-constant = constant-expression
-(6.7.3) type-qualifier:
+(6.7.3) type-qualifier:
               const
               restrict
               volatile
-(6.7.4) function-specifier:
+(6.7.4) function-specifier:
                inline
-(6.7.5) declarator:
+(6.7.5) declarator:
               pointeropt direct-declarator
-(6.7.5) direct-declarator:
+(6.7.5) direct-declarator:
                identifier
                ( declarator )
                direct-declarator [ type-qualifier-listopt assignment-expressionopt ]
@@ -23484,30 +20283,30 @@ n        No input is consumed. The corresponding argument shall be a pointer to
                direct-declarator [ type-qualifier-listopt * ]
                direct-declarator ( parameter-type-list )
                direct-declarator ( identifier-listopt )
-(6.7.5) pointer:
+(6.7.5) pointer:
                * type-qualifier-listopt
                * type-qualifier-listopt pointer
-(6.7.5) type-qualifier-list:
+(6.7.5) type-qualifier-list:
               type-qualifier
               type-qualifier-list type-qualifier
-(6.7.5) parameter-type-list:
+(6.7.5) parameter-type-list:
              parameter-list
              parameter-list , ...
-(6.7.5) parameter-list:
+(6.7.5) parameter-list:
              parameter-declaration
              parameter-list , parameter-declaration
-(6.7.5) parameter-declaration:
+(6.7.5) parameter-declaration:
              declaration-specifiers declarator
              declaration-specifiers abstract-declaratoropt
-(6.7.5) identifier-list:
+(6.7.5) identifier-list:
                 identifier
                 identifier-list , identifier
-(6.7.6) type-name:
+(6.7.6) type-name:
               specifier-qualifier-list abstract-declaratoropt
-(6.7.6) abstract-declarator:
+(6.7.6) abstract-declarator:
               pointer
               pointeropt direct-abstract-declarator
-(6.7.6) direct-abstract-declarator:
+(6.7.6) direct-abstract-declarator:
                ( abstract-declarator )
                direct-abstract-declaratoropt [ type-qualifier-listopt
                               assignment-expressionopt ]
@@ -23517,114 +20316,108 @@ n        No input is consumed. The corresponding argument shall be a pointer to
                               assignment-expression ]
                direct-abstract-declaratoropt [ * ]
                direct-abstract-declaratoropt ( parameter-type-listopt )
-(6.7.7) typedef-name:
+(6.7.7) typedef-name:
               identifier
-(6.7.8) initializer:
+(6.7.8) initializer:
                 assignment-expression
                 { initializer-list }
                 { initializer-list , }
-(6.7.8) initializer-list:
+(6.7.8) initializer-list:
                 designationopt initializer
                 initializer-list , designationopt initializer
-(6.7.8) designation:
+(6.7.8) designation:
               designator-list =
-(6.7.8) designator-list:
+(6.7.8) designator-list:
               designator
               designator-list designator
-(6.7.8) designator:
+(6.7.8) designator:
               [ constant-expression ]
               . identifier
 

-
-
+
 

 
A.2.3 [Statements]

-
 Statements
-(6.8) statement:
+
(6.8) statement:
               labeled-statement
               compound-statement
               expression-statement
               selection-statement
               iteration-statement
               jump-statement
-(6.8.1) labeled-statement:
+(6.8.1) labeled-statement:
                identifier : statement
                case constant-expression : statement
                default : statement
-(6.8.2) compound-statement:
+(6.8.2) compound-statement:
              { block-item-listopt }
-(6.8.2) block-item-list:
+(6.8.2) block-item-list:
                block-item
                block-item-list block-item
-(6.8.2) block-item:
+(6.8.2) block-item:
                declaration
                statement
-(6.8.3) expression-statement:
+(6.8.3) expression-statement:
               expressionopt ;
-(6.8.4) selection-statement:
+(6.8.4) selection-statement:
                if ( expression ) statement
                if ( expression ) statement else statement
                switch ( expression ) statement
 
-(6.8.5) iteration-statement:
+(6.8.5) iteration-statement:
                 while ( expression ) statement
                 do statement while ( expression ) ;
                 for ( expressionopt ; expressionopt ; expressionopt ) statement
                 for ( declaration expressionopt ; expressionopt ) statement
-(6.8.6) jump-statement:
+(6.8.6) jump-statement:
               goto identifier ;
               continue ;
               break ;
               return expressionopt ;
 

-
-
+
 

 
A.2.4 [External definitions]

-
 External definitions
-(6.9) translation-unit:
+
(6.9) translation-unit:
                external-declaration
                translation-unit external-declaration
-(6.9) external-declaration:
+(6.9) external-declaration:
                function-definition
                declaration
-(6.9.1) function-definition:
+(6.9.1) function-definition:
                declaration-specifiers declarator declaration-listopt compound-statement
-(6.9.1) declaration-list:
+(6.9.1) declaration-list:
               declaration
               declaration-list declaration
 

-
-
+
 

 
A.3 [Preprocessing directives]

-
 Preprocessing directives
-(6.10) preprocessing-file:
+
(6.10) preprocessing-file:
               groupopt
-(6.10) group:
+(6.10) group:
                 group-part
                 group group-part
-(6.10) group-part:
+(6.10) group-part:
               if-section
               control-line
               text-line
               # non-directive
-(6.10) if-section:
+(6.10) if-section:
                 if-group elif-groupsopt else-groupopt endif-line
-(6.10) if-group:
+(6.10) if-group:
                # if     constant-expression new-line groupopt
                # ifdef identifier new-line groupopt
                # ifndef identifier new-line groupopt
-(6.10) elif-groups:
+(6.10) elif-groups:
                elif-group
                elif-groups elif-group
-(6.10) elif-group:
+(6.10) elif-group:
                # elif        constant-expression new-line groupopt
-(6.10) else-group:
+(6.10) else-group:
                # else        new-line groupopt
-(6.10) endif-line:
+(6.10) endif-line:
                # endif       new-line
-(6.10) control-line:
+(6.10) control-line:
               # include pp-tokens new-line
               # define identifier replacement-list new-line
               # define identifier lparen identifier-listopt )
@@ -23637,44 +20430,37 @@ n        No input is consumed. The corresponding argument shall be a pointer to
               # error   pp-tokensopt new-line
               # pragma pp-tokensopt new-line
               #         new-line
-(6.10) text-line:
+(6.10) text-line:
                pp-tokensopt new-line
-(6.10) non-directive:
+(6.10) non-directive:
               pp-tokens new-line
-(6.10) lparen:
+(6.10) lparen:
                  a ( character not immediately preceded by white-space
-(6.10) replacement-list:
+(6.10) replacement-list:
               pp-tokensopt
 
-(6.10) pp-tokens:
+(6.10) pp-tokens:
               preprocessing-token
               pp-tokens preprocessing-token
-(6.10) new-line:
+(6.10) new-line:
               the new-line character
 
                                 Annex B
                               (informative)
 

-
-
+
 

 
B. [Library summary]

-
 Library summary
-

-
-
+
 

-
B.1 [Diagnostics ]

-
 Diagnostics 
-       NDEBUG
+
B.1 [Diagnostics <assert.h>]

+
NDEBUG
        void assert(scalar expression);
 

-
-
+
 

-
B.2 [Complex ]

-
 Complex 
-       complex               imaginary                I
+
B.2 [Complex <complex.h>]

+
complex               imaginary                I
        _Complex_I            _Imaginary_I
        #pragma STDC CX_LIMITED_RANGE on-off-switch
        double complex cacos(double complex z);
@@ -23745,12 +20531,10 @@ n        No input is consumed. The corresponding argument shall be a pointer to
       float crealf(float complex z);
       long double creall(long double complex z);
 

-
-
+
 

-
B.3 [Character handling ]

-
 Character handling 
-       int    isalnum(int c);
+
B.3 [Character handling <ctype.h>]

+
int    isalnum(int c);
        int    isalpha(int c);
        int    isblank(int c);
        int    iscntrl(int c);
@@ -23765,19 +20549,15 @@ n        No input is consumed. The corresponding argument shall be a pointer to
        int    tolower(int c);
        int    toupper(int c);
 

-
-
+
 

-
B.4 [Errors ]

-
 Errors 
-       EDOM             EILSEQ            ERANGE             errno
+
B.4 [Errors <errno.h>]

+
EDOM             EILSEQ            ERANGE             errno
 

-
-
+
 

-
B.5 [Floating-point environment ]

-
 Floating-point environment 
-       fenv_t                 FE_OVERFLOW              FE_TOWARDZERO
+
B.5 [Floating-point environment <fenv.h>]

+
fenv_t                 FE_OVERFLOW              FE_TOWARDZERO
        fexcept_t              FE_UNDERFLOW             FE_UPWARD
        FE_DIVBYZERO           FE_ALL_EXCEPT            FE_DFL_ENV
        FE_INEXACT             FE_DOWNWARD
@@ -23796,12 +20576,10 @@ n        No input is consumed. The corresponding argument shall be a pointer to
        int fesetenv(const fenv_t *envp);
        int feupdateenv(const fenv_t *envp);
 

-
-
+
 

-
B.6 [Characteristics of floating types ]

-
 Characteristics of floating types 
-      FLT_ROUNDS              DBL_MIN_EXP              FLT_MAX
+
B.6 [Characteristics of floating types <float.h>]

+
FLT_ROUNDS              DBL_MIN_EXP              FLT_MAX
       FLT_EVAL_METHOD         LDBL_MIN_EXP             DBL_MAX
       FLT_RADIX               FLT_MIN_10_EXP           LDBL_MAX
       FLT_MANT_DIG            DBL_MIN_10_EXP           FLT_EPSILON
@@ -23813,12 +20591,10 @@ n        No input is consumed. The corresponding argument shall be a pointer to
       LDBL_DIG                DBL_MAX_10_EXP
       FLT_MIN_EXP             LDBL_MAX_10_EXP
 

-
-
+
 

-
B.7 [Format conversion of integer types ]

-
 Format conversion of integer types 
-      imaxdiv_t
+
B.7 [Format conversion of integer types <inttypes.h>]

+
imaxdiv_t
       PRIdN        PRIdLEASTN        PRIdFASTN         PRIdMAX     PRIdPTR
       PRIiN        PRIiLEASTN        PRIiFASTN         PRIiMAX     PRIiPTR
       PRIoN        PRIoLEASTN        PRIoFASTN         PRIoMAX     PRIoPTR
@@ -23841,42 +20617,34 @@ n        No input is consumed. The corresponding argument shall be a pointer to
       uintmax_t wcstoumax(const wchar_t * restrict nptr,
               wchar_t ** restrict endptr, int base);
 

-
-
+
 

-
B.8 [Alternative spellings ]

-
 Alternative spellings 
-     and              bitor             not_eq             xor
+
B.8 [Alternative spellings <iso646.h>]

+
and              bitor             not_eq             xor
      and_eq           compl             or                 xor_eq
      bitand           not               or_eq
 

-
-
+
 

-
B.9 [Sizes of integer types ]

-
 Sizes of integer types 
-     CHAR_BIT         CHAR_MAX          INT_MIN            ULONG_MAX
+
B.9 [Sizes of integer types <limits.h>]

+
CHAR_BIT         CHAR_MAX          INT_MIN            ULONG_MAX
      SCHAR_MIN        MB_LEN_MAX        INT_MAX            LLONG_MIN
      SCHAR_MAX        SHRT_MIN          UINT_MAX           LLONG_MAX
      UCHAR_MAX        SHRT_MAX          LONG_MIN           ULLONG_MAX
      CHAR_MIN         USHRT_MAX         LONG_MAX
 

-
-
+
 

-
B.10 [Localization ]

-
 Localization 
-     struct lconv     LC_ALL            LC_CTYPE           LC_NUMERIC
+
B.10 [Localization <locale.h>]

+
struct lconv     LC_ALL            LC_CTYPE           LC_NUMERIC
      NULL             LC_COLLATE        LC_MONETARY        LC_TIME
      char *setlocale(int category, const char *locale);
      struct lconv *localeconv(void);
 

-
-
+
 

-
B.11 [Mathematics ]

-
 Mathematics 
-     float_t                FP_INFINITE              FP_FAST_FMAL
+
B.11 [Mathematics <math.h>]

+
float_t                FP_INFINITE              FP_FAST_FMAL
      double_t               FP_NAN                   FP_ILOGB0
      HUGE_VAL               FP_NORMAL                FP_ILOGBNAN
      HUGE_VALF              FP_SUBNORMAL             MATH_ERRNO
@@ -24070,61 +20838,49 @@ n        No input is consumed. The corresponding argument shall be a pointer to
       int islessgreater(real-floating x, real-floating y);
       int isunordered(real-floating x, real-floating y);
 

-
-
+
 

-
B.12 [Nonlocal jumps ]

-
 Nonlocal jumps 
-      jmp_buf
+
B.12 [Nonlocal jumps <setjmp.h>]

+
jmp_buf
       int setjmp(jmp_buf env);
       void longjmp(jmp_buf env, int val);
 

-
-
+
 

-
B.13 [Signal handling ]

-
 Signal handling 
-      sig_atomic_t    SIG_IGN           SIGILL             SIGTERM
+
B.13 [Signal handling <signal.h>]

+
sig_atomic_t    SIG_IGN           SIGILL             SIGTERM
       SIG_DFL         SIGABRT           SIGINT
       SIG_ERR         SIGFPE            SIGSEGV
       void (*signal(int sig, void (*func)(int)))(int);
       int raise(int sig);
 

-
-
+
 

-
B.14 [Variable arguments ]

-
 Variable arguments 
-      va_list
+
B.14 [Variable arguments <stdarg.h>]

+
va_list
       type va_arg(va_list ap, type);
       void va_copy(va_list dest, va_list src);
       void va_end(va_list ap);
       void va_start(va_list ap, parmN);
 

-
-
+
 

-
B.15 [Boolean type and values ]

-
 Boolean type and values 
-      bool
+
B.15 [Boolean type and values <stdbool.h>]

+
bool
       true
       false
       _ _bool_true_false_are_defined
 

-
-
+
 

-
B.16 [Common definitions ]

-
 Common definitions 
-        ptrdiff_t       size_t            wchar_t            NULL
+
B.16 [Common definitions <stddef.h>]

+
ptrdiff_t       size_t            wchar_t            NULL
         offsetof(type, member-designator)
 

-
-
+
 

-
B.17 [Integer types ]

-
 Integer types 
-        intN_t                INT_LEASTN_MIN           PTRDIFF_MAX
+
B.17 [Integer types <stdint.h>]

+
intN_t                INT_LEASTN_MIN           PTRDIFF_MAX
         uintN_t               INT_LEASTN_MAX           SIG_ATOMIC_MIN
         int_leastN_t          UINT_LEASTN_MAX          SIG_ATOMIC_MAX
         uint_leastN_t         INT_FASTN_MIN            SIZE_MAX
@@ -24138,12 +20894,10 @@ n        No input is consumed. The corresponding argument shall be a pointer to
         INTN_MAX              UINTMAX_MAX              UINTMAX_C(value)
         UINTN_MAX             PTRDIFF_MIN
 

-
-
+
 

-
B.18 [Input/output ]

-
 Input/output 
-        size_t          _IOLBF            FILENAME_MAX       TMP_MAX
+
B.18 [Input/output <stdio.h>]

+
size_t          _IOLBF            FILENAME_MAX       TMP_MAX
         FILE            _IONBF            L_tmpnam           stderr
         fpos_t          BUFSIZ            SEEK_CUR           stdin
         NULL            EOF               SEEK_END           stdout
@@ -24218,12 +20972,10 @@ n        No input is consumed. The corresponding argument shall be a pointer to
         int ferror(FILE *stream);
         void perror(const char *s);
 

-
-
+
 

-
B.19 [General utilities ]

-
 General utilities 
-        size_t        ldiv_t            EXIT_FAILURE       MB_CUR_MAX
+
B.19 [General utilities <stdlib.h>]

+
size_t        ldiv_t            EXIT_FAILURE       MB_CUR_MAX
         wchar_t       lldiv_t           EXIT_SUCCESS
         div_t         NULL              RAND_MAX
         double atof(const char *nptr);
@@ -24280,12 +21032,10 @@ n        No input is consumed. The corresponding argument shall be a pointer to
       size_t wcstombs(char * restrict s,
            const wchar_t * restrict pwcs, size_t n);
 

-
-
+
 

-
B.20 [String handling ]

-
 String handling 
-        size_t
+
B.20 [String handling <string.h>]

+
size_t
         NULL
         void *memcpy(void * restrict s1,
              const void * restrict s2, size_t n);
@@ -24317,12 +21067,10 @@ n        No input is consumed. The corresponding argument shall be a pointer to
         char *strerror(int errnum);
         size_t strlen(const char *s);
 

-
-
+
 

-
B.21 [Type-generic math ]

-
 Type-generic math 
-      acos            sqrt              fmod               nextafter
+
B.21 [Type-generic math <tgmath.h>]

+
acos            sqrt              fmod               nextafter
       asin            fabs              frexp              nexttoward
       atan            atan2             hypot              remainder
       acosh           cbrt              ilogb              remquo
@@ -24338,12 +21086,10 @@ n        No input is consumed. The corresponding argument shall be a pointer to
       log             fmax              lround             cproj
       pow             fmin              nearbyint          creal
 

-
-
+
 

-
B.22 [Date and time ]

-
 Date and time 
-      NULL                  size_t                   time_t
+
B.22 [Date and time <time.h>]

+
NULL                  size_t                   time_t
       CLOCKS_PER_SEC        clock_t                  struct tm
       clock_t clock(void);
       double difftime(time_t time1, time_t time0);
@@ -24358,12 +21104,10 @@ n        No input is consumed. The corresponding argument shall be a pointer to
            const char * restrict format,
            const struct tm * restrict timeptr);
 

-
-
+
 

-
B.23 [Extended multibyte/wide character utilities ]

-
 Extended multibyte/wide character utilities 
-        wchar_t        wint_t            WCHAR_MAX
+
B.23 [Extended multibyte/wide character utilities <wchar.h>]

+
wchar_t        wint_t            WCHAR_MAX
         size_t         struct tm         WCHAR_MIN
         mbstate_t      NULL              WEOF
         int fwprintf(FILE * restrict stream,
@@ -24437,7 +21181,7 @@ n        No input is consumed. The corresponding argument shall be a pointer to
            size_t n);
       wchar_t *wcschr(const wchar_t *s, wchar_t c);
       size_t wcscspn(const wchar_t *s1, const wchar_t *s2);
-      wchar_t *wcspbrk(const wchar_t *s1, const wchar_t *s2); 
+      wchar_t *wcspbrk(const wchar_t *s1, const wchar_t *s2);
       wchar_t *wcsrchr(const wchar_t *s, wchar_t c);
       size_t wcsspn(const wchar_t *s1, const wchar_t *s2);
       wchar_t *wcsstr(const wchar_t *s1, const wchar_t *s2);
@@ -24467,12 +21211,10 @@ n        No input is consumed. The corresponding argument shall be a pointer to
              const wchar_t ** restrict src, size_t len,
              mbstate_t * restrict ps);
 

-
-
+
 

-
B.24 [Wide character classification and mapping utilities ]

-
 Wide character classification and mapping utilities 
-        wint_t          wctrans_t         wctype_t           WEOF
+
B.24 [Wide character classification and mapping utilities <wctype.h>]

+
wint_t          wctrans_t         wctype_t           WEOF
         int   iswalnum(wint_t wc);
         int   iswalpha(wint_t wc);
         int   iswblank(wint_t wc);
@@ -24495,45 +21237,38 @@ n        No input is consumed. The corresponding argument shall be a pointer to
                                            Annex C
                                          (informative)
 

-
-
+
 

 
C. [Sequence points]

-

-
-
-
1   The following are the sequence points described in 5.1.2.3:
-    -- The call to a function, after the arguments have been evaluated (6.5.2.2).
-    -- The end of the first operand of the following operators: logical AND && (6.5.13);
-       logical OR || (6.5.14); conditional ? (6.5.15); comma , (6.5.17).
-    -- The end of a full declarator: declarators (6.7.5);
-    -- The end of a full expression: an initializer (6.7.8); the expression in an expression
-       statement (6.8.3); the controlling expression of a selection statement (if or switch)
-       (6.8.4); the controlling expression of a while or do statement (6.8.5); each of the
-       expressions of a for statement (6.8.5.3); the expression in a return statement
-       (6.8.6.4).
-    -- Immediately before a library function returns (7.1.4).
+
+
1   The following are the sequence points described in 5.1.2.3:
+    -- The call to a function, after the arguments have been evaluated (6.5.2.2).
+    -- The end of the first operand of the following operators: logical AND && (6.5.13);
+       logical OR || (6.5.14); conditional ? (6.5.15); comma , (6.5.17).
+    -- The end of a full declarator: declarators (6.7.5);
+    -- The end of a full expression: an initializer (6.7.8); the expression in an expression
+       statement (6.8.3); the controlling expression of a selection statement (if or switch)
+       (6.8.4); the controlling expression of a while or do statement (6.8.5); each of the
+       expressions of a for statement (6.8.5.3); the expression in a return statement
+       (6.8.6.4).
+    -- Immediately before a library function returns (7.1.4).
     -- After the actions associated with each formatted input/output function conversion
-       specifier (7.19.6, 7.24.2).
+       specifier (7.19.6, 7.24.2).
     -- Immediately before and immediately after each call to a comparison function, and
        also between any call to a comparison function and any movement of the objects
-       passed as arguments to that call (7.20.5).
+       passed as arguments to that call (7.20.5).
 
                                          Annex D
                                         (normative)
 

-
-
+
 

 
D. [Universal character names for identifiers]

-

-
-
+
 
1   This clause lists the hexadecimal code values that are valid in universal character names
     in identifiers.
 

-
-
+
 
2   This table is reproduced unchanged from ISO/IEC TR 10176:1998, produced by ISO/IEC
     JTC 1/SC 22/WG 20, except for the omission of ranges that are part of the basic character
     sets.
@@ -24599,17 +21334,14 @@ Special characters: 00B5, 00B7, 02B0-02B8, 02BB, 02BD-02C1, 02D0-02D1,
                                          Annex E
                                        (informative)
 

-
-
+
 

 
E. [Implementation limits]

-

-
-
+
 
1   The contents of the header <limits.h> are given below, in alphabetical order. The
     minimum magnitudes shown shall be replaced by implementation-defined magnitudes
     with the same sign. The values shall all be constant expressions suitable for use in #if
-    preprocessing directives. The components are described further in 5.2.4.2.1.
+    preprocessing directives. The components are described further in 5.2.4.2.1.
            #define     CHAR_BIT                               8
            #define     CHAR_MAX          UCHAR_MAX or SCHAR_MAX
            #define     CHAR_MIN                  0 or SCHAR_MIN
@@ -24630,22 +21362,19 @@ Special characters: 00B5, 00B7, 02B0-02B8, 02BB, 02BD-02C1, 02D0-02D1,
            #define     ULONG_MAX                     4294967295
            #define     ULLONG_MAX          18446744073709551615
 

-
-
+
 
2   The contents of the header <float.h> are given below. All integer values, except
     FLT_ROUNDS, shall be constant expressions suitable for use in #if preprocessing
     directives; all floating values shall be constant expressions. The components are
-    described further in 5.2.4.2.2.
+    described further in 5.2.4.2.2.
 

-
-
+
 
3   The values given in the following list shall be replaced by implementation-defined
     expressions:
            #define FLT_EVAL_METHOD
            #define FLT_ROUNDS
 

-
-
+
 
4   The values given in the following list shall be replaced by implementation-defined
     constant expressions that are greater or equal in magnitude (absolute value) to those
     shown, with the same sign:
@@ -24670,16 +21399,14 @@ Special characters: 00B5, 00B7, 02B0-02B8, 02BB, 02BD-02C1, 02D0-02D1,
            #define    LDBL_MIN_10_EXP                              -37
            #define    LDBL_MIN_EXP
 

-
-
+
 
5   The values given in the following list shall be replaced by implementation-defined
     constant expressions with values that are greater than or equal to those shown:
            #define DBL_MAX                                      1E+37
            #define FLT_MAX                                      1E+37
            #define LDBL_MAX                                     1E+37
 

-
-
+
 
6   The values given in the following list shall be replaced by implementation-defined
     constant expressions with (positive) values that are less than or equal to those shown:
            #define    DBL_EPSILON                                1E-9
@@ -24692,19 +21419,13 @@ Special characters: 00B5, 00B7, 02B0-02B8, 02BB, 02BD-02C1, 02D0-02D1,
                                                Annex F
                                               (normative)
 

-
-
+
 

 
F. [IEC 60559 floating-point arithmetic]

-
 IEC 60559 floating-point arithmetic
-

-
-
+
 

 
F.1 [Introduction]

-

-
-
+
 
1   This annex specifies C language support for the IEC 60559 floating-point standard. The
     IEC 60559 floating-point standard is specifically Binary floating-point arithmetic for
     microprocessor systems, second edition (IEC 60559:1989), previously designated
@@ -24717,82 +21438,43 @@ Special characters: 00B5, 00B7, 02B0-02B8, 02BB, 02BD-02C1, 02D0-02D1,
     a binding between the C language and IEC 60559 is indicated, the IEC 60559-specified
     behavior is adopted by reference, unless stated otherwise.
 

-
-
+
 

 
F.2 [Types]

-

-
-
+
 
1   The C floating types match the IEC 60559 formats as follows:
     -- The float type matches the IEC 60559 single format.
     -- The double type matches the IEC 60559 double format.
-    -- The long double type matches an IEC 60559 extended format,307) else a
+    -- The long double type matches an IEC 60559 extended format,[307] else a
        non-IEC 60559 extended format, else the IEC 60559 double format.
     Any non-IEC 60559 extended format used for the long double type shall have more
-    precision than IEC 60559 double and at least the range of IEC 60559 double.308)
+    precision than IEC 60559 double and at least the range of IEC 60559 double.[308]
     Recommended practice
 

+
+
Footnote 307) ``Extended'' is IEC 60559's double-extended data format. Extended refers to both the common 80-bit
+         and quadruple 128-bit IEC 60559 formats.
+

 
 
 
Footnote 308) A non-IEC 60559 long double type is required to provide infinity and NaNs, as its values include
          all double values.
 

 
-
+
 
2   The long double type should match an IEC 60559 extended format.
 

-
-
+
 

 
F.2.1 [Infinities, signed zeros, and NaNs]

-

-
-
-
1   This specification does not define the behavior of signaling NaNs.309) It generally uses
+
+
1   This specification does not define the behavior of signaling NaNs.[309] It generally uses
     the term NaN to denote quiet NaNs. The NAN and INFINITY macros and the nan
     functions in <math.h> provide designations for IEC 60559 NaNs and infinities.
 

-
 
 
Footnote 309) Since NaNs created by IEC 60559 operations are always quiet, quiet NaNs (along with infinities) are
          sufficient for closure of the arithmetic.
-

-
-
-

-
F.3 [Operators and functions]

-

-
-
-
1   C operators and functions provide IEC 60559 required and recommended facilities as
-    listed below.
-    -- The +, -, *, and / operators provide the IEC 60559 add, subtract, multiply, and
-       divide operations.
-    -- The sqrt functions in <math.h> provide the IEC 60559 square root operation.
-    -- The remainder functions in <math.h> provide the IEC 60559 remainder
-       operation. The remquo functions in <math.h> provide the same operation but
-       with additional information.
-    -- The rint functions in <math.h> provide the IEC 60559 operation that rounds a
-       floating-point number to an integer value (in the same precision). The nearbyint
-       functions in <math.h> provide the nearbyinteger function recommended in the
-       Appendix to ANSI/IEEE 854.
-    -- The conversions for floating types provide the IEC 60559 conversions between
-       floating-point precisions.
-    -- The conversions from integer to floating types provide the IEC 60559 conversions
-       from integer to floating point.
-    -- The conversions from floating to integer types provide IEC 60559-like conversions
-       but always round toward zero.
-    -- The lrint and llrint functions in <math.h> provide the IEC 60559
-       conversions, which honor the directed rounding mode, from floating point to the
-       long int and long long int integer formats. The lrint and llrint
-       functions can be used to implement IEC 60559 conversions from floating to other
-       integer formats.
-    -- The translation time conversion of floating constants and the strtod, strtof,
-       strtold, fprintf, fscanf, and related library functions in <stdlib.h>,
-       <stdio.h>, and <wchar.h> provide IEC 60559 binary-decimal conversions. The
-       strtold function in <stdlib.h> provides the conv function recommended in the
-       Appendix to ANSI/IEEE 854.
     -- The relational and equality operators provide IEC 60559 comparisons. IEC 60559
        identifies a need for additional comparison predicates to facilitate writing code that
        accounts for NaNs. The comparison macros (isgreater, isgreaterequal,
@@ -24834,22 +21516,52 @@ Special characters: 00B5, 00B7, 02B0-02B8, 02BB, 02BD-02C1, 02D0-02D1,
        conjunction with the number classification macros (FP_NAN, FP_INFINITE,
        FP_NORMAL, FP_SUBNORMAL, FP_ZERO), provide the facility of the class
        function recommended in the Appendix to IEC 60559 (except that the classification
-       macros defined in 7.12.3 do not distinguish signaling from quiet NaNs).
-

+       macros defined in 7.12.3 do not distinguish signaling from quiet NaNs).
+

 
-
+
+

+
F.3 [Operators and functions]

+
+
1   C operators and functions provide IEC 60559 required and recommended facilities as
+    listed below.
+    -- The +, -, *, and / operators provide the IEC 60559 add, subtract, multiply, and
+       divide operations.
+    -- The sqrt functions in <math.h> provide the IEC 60559 square root operation.
+    -- The remainder functions in <math.h> provide the IEC 60559 remainder
+       operation. The remquo functions in <math.h> provide the same operation but
+       with additional information.
+    -- The rint functions in <math.h> provide the IEC 60559 operation that rounds a
+       floating-point number to an integer value (in the same precision). The nearbyint
+       functions in <math.h> provide the nearbyinteger function recommended in the
+       Appendix to ANSI/IEEE 854.
+    -- The conversions for floating types provide the IEC 60559 conversions between
+       floating-point precisions.
+    -- The conversions from integer to floating types provide the IEC 60559 conversions
+       from integer to floating point.
+    -- The conversions from floating to integer types provide IEC 60559-like conversions
+       but always round toward zero.
+    -- The lrint and llrint functions in <math.h> provide the IEC 60559
+       conversions, which honor the directed rounding mode, from floating point to the
+       long int and long long int integer formats. The lrint and llrint
+       functions can be used to implement IEC 60559 conversions from floating to other
+       integer formats.
+    -- The translation time conversion of floating constants and the strtod, strtof,
+       strtold, fprintf, fscanf, and related library functions in <stdlib.h>,
+       <stdio.h>, and <wchar.h> provide IEC 60559 binary-decimal conversions. The
+       strtold function in <stdlib.h> provides the conv function recommended in the
+       Appendix to ANSI/IEEE 854.
+

+
 

 
F.4 [Floating to integer conversion]

-

-
-
+
 
1   If the floating value is infinite or NaN or if the integral part of the floating value exceeds
     the range of the integer type, then the ``invalid'' floating-point exception is raised and the
     resulting value is unspecified. Whether conversion of non-integer floating values whose
     integral part is within the range of the integer type raises the ``inexact'' floating-point
-    exception is unspecified.310)
+    exception is unspecified.[310]
 

-
 
 
Footnote 310) ANSI/IEEE 854, but not IEC 60559 (ANSI/IEEE 754), directly specifies that floating-to-integer
          conversions raise the ``inexact'' floating-point exception for non-integer in-range values. In those
@@ -24858,16 +21570,13 @@ Special characters: 00B5, 00B7, 02B0-02B8, 02BB, 02BD-02C1, 02D0-02D1,
          <math.h>.
 

 
-
+
 

 
F.5 [Binary-decimal conversion]

-

-
-
+
 
1   Conversion from the widest supported IEC 60559 format to decimal with
-    DECIMAL_DIG digits and back is the identity function.311)
+    DECIMAL_DIG digits and back is the identity function.[311]
 

-
 
 
Footnote 311) If the minimum-width IEC 60559 extended format (64 bits of precision) is supported,
          DECIMAL_DIG shall be at least 21. If IEC 60559 double (53 bits of precision) is the widest
@@ -24875,106 +21584,81 @@ Special characters: 00B5, 00B7, 02B0-02B8, 02BB, 02BD-02C1, 02D0-02D1,
          DBL_DIG are 18 and 15, respectively, for these formats.)
 

 
-
+
 
2   Conversions involving IEC 60559 formats follow all pertinent recommended practice. In
     particular, conversion between any supported IEC 60559 format and decimal with
     DECIMAL_DIG or fewer significant digits is correctly rounded (honoring the current
     rounding mode), which assures that conversion from the widest supported IEC 60559
     format to decimal with DECIMAL_DIG digits and back is the identity function.
 

-
-
+
 
3   Functions such as strtod that convert character sequences to floating types honor the
     rounding direction. Hence, if the rounding direction might be upward or downward, the
     implementation cannot convert a minus-signed sequence by negating the converted
     unsigned sequence.
 

-
-
+
 

 
F.6 [Contracted expressions]

-

-
-
+
 
1   A contracted expression treats infinities, NaNs, signed zeros, subnormals, and the
     rounding directions in a manner consistent with the basic arithmetic operations covered
     by IEC 60559.
     Recommended practice
 

-
-
+
 
2   A contracted expression should raise floating-point exceptions in a manner generally
     consistent with the basic arithmetic operations. A contracted expression should deliver
     the same value as its uncontracted counterpart, else should be correctly rounded (once).
 

-
-
+
 

 
F.7 [Floating-point environment]

-

-
-
+
 
1   The floating-point environment defined in <fenv.h> includes the IEC 60559 floating-
     point exception status flags and directed-rounding control modes. It includes also
     IEC 60559 dynamic rounding precision and trap enablement modes, if the
-    implementation supports them.312)
+    implementation supports them.[312]
 

-
 
 
Footnote 312) This specification does not require dynamic rounding precision nor trap enablement modes.
 

 
-
+
 

 
F.7.1 [Environment management]

-

-
-
+
 
1   IEC 60559 requires that floating-point operations implicitly raise floating-point exception
     status flags, and that rounding control modes can be set explicitly to affect result values of
     floating-point operations. When the state for the FENV_ACCESS pragma (defined in
     <fenv.h>) is ``on'', these changes to the floating-point state are treated as side effects
-    which respect sequence points.313)
+    which respect sequence points.[313]
 

-
 
 
Footnote 313) If the state for the FENV_ACCESS pragma is ``off'', the implementation is free to assume the floating-
          point control modes will be the default ones and the floating-point status flags will not be tested,
-         which allows certain optimizations (see F.8).
+         which allows certain optimizations (see F.8).
+    floating-point exception, other than ``inexact'';314) the implementation should then
+    proceed with the translation of the program.
 

 
-
+
 

 
F.7.2 [Translation]

-

-
-
+
 
1   During translation the IEC 60559 default modes are in effect:
     -- The rounding direction mode is rounding to nearest.
     -- The rounding precision mode (if supported) is set so that results are not shortened.
     -- Trapping or stopping (if supported) is disabled on all floating-point exceptions.
     Recommended practice
 

-
-
+
 
2   The implementation should produce a diagnostic message for each translation-time
-    floating-point exception, other than ``inexact'';314) the implementation should then
-    proceed with the translation of the program.
 

-
-
-
Footnote 314) As floating constants are converted to appropriate internal representations at translation time, their
-         conversion is subject to default rounding modes and raises no execution-time floating-point exceptions
-         (even where the state of the FENV_ACCESS pragma is ``on''). Library functions, for example
-         strtod, provide execution-time conversion of numeric strings.
-

-
-
+
 

 
F.7.3 [Execution]

-

-
-
+
 
1   At program startup the floating-point environment is initialized as prescribed by
     IEC 60559:
     -- All floating-point exception status flags are cleared.
@@ -24983,29 +21667,26 @@ Special characters: 00B5, 00B7, 02B0-02B8, 02BB, 02BD-02C1, 02D0-02D1,
        shortened.
     -- Trapping or stopping (if supported) is disabled on all floating-point exceptions.
 

-
-
+
 

 
F.7.4 [Constant expressions]

-

-
-
+
 
1   An arithmetic constant expression of floating type, other than one in an initializer for an
     object that has static storage duration, is evaluated (as if) during execution; thus, it is
     affected by any operative floating-point control modes and raises floating-point
     exceptions as required by IEC 60559 (provided the state for the FENV_ACCESS pragma
-    is ``on'').315)
+    is ``on'').[315]
 

-
 
 
Footnote 315) Where the state for the FENV_ACCESS pragma is ``on'', results of inexact expressions like 1.0/3.0
          are affected by rounding modes set at execution time, and expressions such as 0.0/0.0 and
          1.0/0.0 generate execution-time floating-point exceptions. The programmer can achieve the
          efficiency of translation-time evaluation through static initialization, such as
                   const static double one_third = 1.0/3.0;
+    execution time.
 

 
-
+
 
2   EXAMPLE
              #include <fenv.h>
              #pragma STDC FENV_ACCESS ON
@@ -25018,104 +21699,86 @@ Special characters: 00B5, 00B7, 02B0-02B8, 02BB, 02BD-02C1, 02D0-02D1,
                    /* ... */
              }
 

-
-
+
 
3   For the static initialization, the division is done at translation time, raising no (execution-time) floating-
     point exceptions. On the other hand, for the three automatic initializations the invalid division occurs at
-    execution time.
 
 

-
-
+
 

 
F.7.5 [Initialization]

-

-
-
+
 
1   All computation for automatic initialization is done (as if) at execution time; thus, it is
     affected by any operative modes and raises floating-point exceptions as required by
     IEC 60559 (provided the state for the FENV_ACCESS pragma is ``on''). All computation
     for initialization of objects that have static storage duration is done (as if) at translation
     time.
 

-
-
+
 
2   EXAMPLE
              #include <fenv.h>
              #pragma STDC FENV_ACCESS ON
              void f(void)
              {
-                   float u[] = { 1.1e75 };                  //   raises exceptions
-                   static float v = 1.1e75;                 //   does not raise exceptions
-                   float w = 1.1e75;                        //   raises exceptions
-                   double x = 1.1e75;                       //   may raise exceptions
-                   float y = 1.1e75f;                       //   may raise exceptions
-                   long double z = 1.1e75;                  //   does not raise exceptions
+                   float u[] = { 1.1e75 };                  //   raises exceptions
+                   static float v = 1.1e75;                 //   does not raise exceptions
+                   float w = 1.1e75;                        //   raises exceptions
+                   double x = 1.1e75;                       //   may raise exceptions
+                   float y = 1.1e75f;                       //   may raise exceptions
+                   long double z = 1.1e75;                  //   does not raise exceptions
                    /* ... */
              }
 

-
-
+
 
3   The static initialization of v raises no (execution-time) floating-point exceptions because its computation is
     done at translation time. The automatic initialization of u and w require an execution-time conversion to
-    float of the wider value 1.1e75, which raises floating-point exceptions. The automatic initializations
+    float of the wider value 1.1e75, which raises floating-point exceptions. The automatic initializations
     of x and y entail execution-time conversion; however, in some expression evaluation methods, the
-    conversions is not to a narrower format, in which case no floating-point exception is raised.316) The
+    conversions is not to a narrower format, in which case no floating-point exception is raised.[316] The
     automatic initialization of z entails execution-time conversion, but not to a narrower format, so no floating-
-    point exception is raised. Note that the conversions of the floating constants 1.1e75 and 1.1e75f to
+    point exception is raised. Note that the conversions of the floating constants 1.1e75 and 1.1e75f to
     their internal representations occur at translation time in all cases.
 

-
 
 
Footnote 316) Use of float_t and double_t variables increases the likelihood of translation-time computation.
          For example, the automatic initialization
-                   double_t x = 1.1e75;
+                   double_t x = 1.1e75;
           could be done at translation time, regardless of the expression evaluation method.
 

 
-
+
 

 
F.7.6 [Changing the environment]

-

-
-
-
1   Operations defined in 6.5 and functions and macros defined for the standard libraries
+
+
1   Operations defined in 6.5 and functions and macros defined for the standard libraries
     change floating-point status flags and control modes just as indicated by their
     specifications (including conformance to IEC 60559). They do not change flags or modes
     (so as to be detectable by the user) in any other cases.
 

-
-
+
 
2   If the argument to the feraiseexcept function in <fenv.h> represents IEC 60559
     valid coincident floating-point exceptions for atomic operations (namely ``overflow'' and
     ``inexact'', or ``underflow'' and ``inexact''), then ``overflow'' or ``underflow'' is raised
     before ``inexact''.
 

-
-
+
 

 
F.8 [Optimization]

-

-
-
+
 
1   This section identifies code transformations that might subvert IEC 60559-specified
     behavior, and others that do not.
 

-
-
+
 

 
F.8.1 [Global transformations]

-

-
-
+
 
1   Floating-point arithmetic operations and external function calls may entail side effects
     which optimization shall honor, at least where the state of the FENV_ACCESS pragma is
     ``on''. The flags and modes in the floating-point environment may be regarded as global
     variables; floating-point operations (+, *, etc.) implicitly read the modes and write the
     flags.
 

-
-
+
 
2   Concern about side effects may inhibit code motion and removal of seemingly useless
     code. For example, in
              #include <fenv.h>
@@ -25131,8 +21794,7 @@ Special characters: 00B5, 00B7, 02B0-02B8, 02BB, 02BD-02C1, 02D0-02D1,
     course these optimizations are valid if the implementation can rule out the nettlesome
     cases.)
 

-
-
+
 
3   This specification does not require support for trap handlers that maintain information
     about the order or count of floating-point exceptions. Therefore, between function calls,
     floating-point exceptions need not be precise: the actual order and number of occurrences
@@ -25140,27 +21802,24 @@ Special characters: 00B5, 00B7, 02B0-02B8, 02BB, 02BD-02C1, 02D0-02D1,
     the preceding loop could be treated as
             if (0 < n) x + 1;
 

-
-
+
 

 
F.8.2 [Expression transformations]

-

-
-
+
 
1   x / 2  x * 0.5                          Although similar transformations involving inexact
                                             constants generally do not yield numerically equivalent
                                             expressions, if the constants are exact then such
                                             transformations can be made on IEC 60559 machines
                                             and others that round perfectly.
     1 * x and x / 1  x                      The expressions 1 * x, x / 1, and x are equivalent
-                                            (on IEC 60559 machines, among others).317)
+                                            (on IEC 60559 machines, among others).[317]
     x / x  1.0                              The expressions x / x and 1.0 are not equivalent if x
                                             can be zero, infinite, or NaN.
     x - y  x + (-y)                         The expressions x - y, x + (-y), and (-y) + x
                                             are equivalent (on IEC 60559 machines, among others).
     x - y  -(y - x)                         The expressions x - y and -(y - x) are not
                                             equivalent because 1 - 1 is +0 but -(1 - 1) is -0 (in the
-                                            default rounding direction).318)
+                                            default rounding direction).[318]
     x - x  0.0                              The expressions x - x and 0.0 are not equivalent if
                                             x is a NaN or infinite.
     0 * x  0.0                              The expressions 0 * x and 0.0 are not equivalent if
@@ -25173,11 +21832,7 @@ Special characters: 00B5, 00B7, 02B0-02B8, 02BB, 02BD-02C1, 02D0-02D1,
                                             yields -0; so, if the state of the FENV_ACCESS pragma
                                             is ``off'', promising default rounding, then the
                                             implementation can replace x - 0 by x, even if x
-    -x  0 - x                                The expressions -x and 0 - x are not equivalent if x
-                                             is +0, because -(+0) yields -0, but 0 - (+0) yields +0
-                                             (unless rounding is downward).
 

-
 
 
Footnote 317) Strict support for signaling NaNs -- not required by this specification -- would invalidate these and
          other transformations that remove arithmetic operators.
@@ -25186,19 +21841,20 @@ Special characters: 00B5, 00B7, 02B0-02B8, 02BB, 02BD-02C1, 02D0-02D1,
 
 
Footnote 318) IEC 60559 prescribes a signed zero to preserve mathematical identities across certain discontinuities.
          Examples include:
-            1/(1/ ± ) is ± 
+            1/(1/ \xB1 ) is \xB1
          and
             conj(csqrt( z )) is csqrt(conj( z )),
          for complex z .
                                              might be zero.
+    -x  0 - x                                The expressions -x and 0 - x are not equivalent if x
+                                             is +0, because -(+0) yields -0, but 0 - (+0) yields +0
+                                             (unless rounding is downward).
 

 
-
+
 

 
F.8.3 [Relational operators]

-

-
-
+
 
1   x != x  false                            The statement x != x is true if x is a NaN.
     x == x  true                             The statement x == x is false if x is a NaN.
     x < y  isless(x,y)                       (and similarly for <=, >, >=) Though numerically
@@ -25212,8 +21868,7 @@ Special characters: 00B5, 00B7, 02B0-02B8, 02BB, 02BD-02C1, 02D0-02D1,
     The sense of relational operators shall be maintained. This includes handling unordered
     cases as expressed by the source code.
 

-
-
+
 
2   EXAMPLE
              // calls g and raises ``invalid'' if a and b are unordered
              if (a < b)
@@ -25246,437 +21901,332 @@ Special characters: 00B5, 00B7, 02B0-02B8, 02BB, 02BD-02C1, 02D0-02D1,
                    f();
 
 

-
-
+
 

 
F.8.4 [Constant arithmetic]

-

-
-
+
 
1   The implementation shall honor floating-point exceptions raised by execution-time
-    constant arithmetic wherever the state of the FENV_ACCESS pragma is ``on''. (See F.7.4
-    and F.7.5.) An operation on constants that raises no floating-point exception can be
+    constant arithmetic wherever the state of the FENV_ACCESS pragma is ``on''. (See F.7.4
+    and F.7.5.) An operation on constants that raises no floating-point exception can be
     folded during translation, except, if the state of the FENV_ACCESS pragma is ``on'', a
     further check is required to assure that changing the rounding direction to downward does
-    not alter the sign of the result,319) and implementations that support dynamic rounding
+    not alter the sign of the result,[319] and implementations that support dynamic rounding
     precision modes shall assure further that the result of the operation raises no floating-
     point exception when converted to the semantic type of the operation.
 

-
 
 
Footnote 319) 0 - 0 yields -0 instead of +0 just when the rounding direction is downward.
+     whose magnitude is too large.
 

 
-
+
 

-
F.9 [Mathematics ]

-

-
-
+
F.9 [Mathematics <math.h>]

+
 
1   This subclause contains specifications of <math.h> facilities that are particularly suited
     for IEC 60559 implementations.
 

-
-
+
 
2   The Standard C macro HUGE_VAL and its float and long double analogs,
     HUGE_VALF and HUGE_VALL, expand to expressions whose values are positive
     infinities.
 

-
-
+
 
3   Special cases for functions in <math.h> are covered directly or indirectly by
-    IEC 60559. The functions that IEC 60559 specifies directly are identified in F.3. The
+    IEC 60559. The functions that IEC 60559 specifies directly are identified in F.3. The
     other functions in <math.h> treat infinities, NaNs, signed zeros, subnormals, and
     (provided the state of the FENV_ACCESS pragma is ``on'') the floating-point status flags
     in a manner consistent with the basic arithmetic operations covered by IEC 60559.
 

-
-
+
 
4   The expression math_errhandling & MATH_ERREXCEPT shall evaluate to a
     nonzero value.
 

-
-
+
 
5   The ``invalid'' and ``divide-by-zero'' floating-point exceptions are raised as specified in
     subsequent subclauses of this annex.
 

-
-
+
 
6   The ``overflow'' floating-point exception is raised whenever an infinity -- or, because of
     rounding direction, a maximal-magnitude finite number -- is returned in lieu of a value
-     whose magnitude is too large.
 

-
-
+
 
7    The ``underflow'' floating-point exception is raised whenever a result is tiny (essentially
-     subnormal or zero) and suffers loss of accuracy.320)
+     subnormal or zero) and suffers loss of accuracy.[320]
 

-
 
 
Footnote 320) IEC 60559 allows different definitions of underflow. They all result in the same values, but differ on
           when the floating-point exception is raised.
 

 
-
+
 
8    Whether or when library functions raise the ``inexact'' floating-point exception is
      unspecified, unless explicitly specified otherwise.
 

-
-
+
 
9    Whether or when library functions raise an undeserved ``underflow'' floating-point
-     exception is unspecified.321) Otherwise, as implied by F.7.6, the <math.h> functions do
+     exception is unspecified.[321] Otherwise, as implied by F.7.6, the <math.h> functions do
      not raise spurious floating-point exceptions (detectable by the user), other than the
      ``inexact'' floating-point exception.
 

-
 
 
Footnote 321) It is intended that undeserved ``underflow'' and ``inexact'' floating-point exceptions are raised only if
           avoiding them would be too costly.
 

 
-
+
 
10   Whether the functions honor the rounding direction mode is implementation-defined,
      unless explicitly specified otherwise.
 

-
-
+
 
11   Functions with a NaN argument return a NaN result and raise no floating-point exception,
      except where stated otherwise.
 

-
-
+
 
12   The specifications in the following subclauses append to the definitions in <math.h>.
      For families of functions, the specifications apply to all of the functions even though only
-     the principal function is shown. Unless otherwise specified, where the symbol ``±''
+     the principal function is shown. Unless otherwise specified, where the symbol ``\xB1''
      occurs in both an argument and the result, the result has the same sign as the argument.
      Recommended practice
 

-
-
+
 
13   If a function with one or more NaN arguments returns a NaN result, the result should be
      the same as one of the NaN arguments (after possible type conversion), except perhaps
      for the sign.
 

-
-
+
 

 
F.9.1 [Trigonometric functions]

-
 Trigonometric functions
-

-
-
+
 

 
F.9.1.1 [The acos functions]

-

-
-
+
 
1    -- acos(1) returns +0.
      -- acos( x ) returns a NaN and raises the ``invalid'' floating-point exception for
         | x | > 1.
 

-
-
+
 

 
F.9.1.2 [The asin functions]

-

-
-
-
1   -- asin(±0) returns ±0.
+
+
1   -- asin(\xB10) returns \xB10.
     -- asin( x ) returns a NaN and raises the ``invalid'' floating-point exception for
        | x | > 1.
 

-
-
+
 

 
F.9.1.3 [The atan functions]

-

-
-
-
1   -- atan(±0) returns ±0.
-    -- atan(±) returns ± /2.
+
+
1   -- atan(\xB10) returns \xB10.
+    -- atan(\xB1) returns \xB1 /2.
 

-
-
+
 

 
F.9.1.4 [The atan2 functions]

-

-
-
-
1   -- atan2(±0, -0) returns ± .322)
-    -- atan2(±0, +0) returns ±0.
-    -- atan2(±0, x ) returns ± for x < 0.
-    -- atan2(±0, x ) returns ±0 for x > 0.
-    -- atan2( y , ±0) returns - /2 for y < 0.
-    -- atan2( y , ±0) returns  /2 for y > 0.
-    -- atan2(± y , -) returns ± for finite y > 0.
-    -- atan2(± y , +) returns ±0 for finite y > 0.
-    -- atan2(±, x ) returns ± /2 for finite x .
-    -- atan2(±, -) returns ±3 /4.
-    -- atan2(±, +) returns ± /4.
+
+
1   -- atan2(\xB10, -0) returns \xB1 .[322]
+    -- atan2(\xB10, +0) returns \xB10.
+    -- atan2(\xB10, x ) returns \xB1 for x < 0.
+    -- atan2(\xB10, x ) returns \xB10 for x > 0.
+    -- atan2( y , \xB10) returns - /2 for y < 0.
+    -- atan2( y , \xB10) returns  /2 for y > 0.
+    -- atan2(\xB1 y , -) returns \xB1 for finite y > 0.
+    -- atan2(\xB1 y , +) returns \xB10 for finite y > 0.
+    -- atan2(\xB1, x ) returns \xB1 /2 for finite x .
+    -- atan2(\xB1, -) returns \xB13 /4.
+    -- atan2(\xB1, +) returns \xB1 /4.
 

-
 
 
Footnote 322) atan2(0, 0) does not raise the ``invalid'' floating-point exception, nor does atan2( y ,    0) raise
          the ``divide-by-zero'' floating-point exception.
 

 
-
+
 

 
F.9.1.5 [The cos functions]

-

-
-
-
1   -- cos(±0) returns 1.
-    -- cos(±) returns a NaN and raises the ``invalid'' floating-point exception.
+
+
1   -- cos(\xB10) returns 1.
+    -- cos(\xB1) returns a NaN and raises the ``invalid'' floating-point exception.
 

-
-
+
 

 
F.9.1.6 [The sin functions]

-

-
-
-
1   -- sin(±0) returns ±0.
-    -- sin(±) returns a NaN and raises the ``invalid'' floating-point exception.
+
+
1   -- sin(\xB10) returns \xB10.
+    -- sin(\xB1) returns a NaN and raises the ``invalid'' floating-point exception.
 

-
-
+
 

 
F.9.1.7 [The tan functions]

-

-
-
-
1   -- tan(±0) returns ±0.
-    -- tan(±) returns a NaN and raises the ``invalid'' floating-point exception.
+
+
1   -- tan(\xB10) returns \xB10.
+    -- tan(\xB1) returns a NaN and raises the ``invalid'' floating-point exception.
 

-
-
+
 

 
F.9.2 [Hyperbolic functions]

-
 Hyperbolic functions
-

-
-
+
 

 
F.9.2.1 [The acosh functions]

-

-
-
+
 
1   -- acosh(1) returns +0.
     -- acosh( x ) returns a NaN and raises the ``invalid'' floating-point exception for x < 1.
     -- acosh(+) returns +.
 

-
-
+
 

 
F.9.2.2 [The asinh functions]

-

-
-
-
1   -- asinh(±0) returns ±0.
-    -- asinh(±) returns ±.
+
+
1   -- asinh(\xB10) returns \xB10.
+    -- asinh(\xB1) returns \xB1.
 

-
-
+
 

 
F.9.2.3 [The atanh functions]

-

-
-
-
1   -- atanh(±0) returns ±0.
-    -- atanh(±1) returns ± and raises the ``divide-by-zero'' floating-point exception.
+
+
1   -- atanh(\xB10) returns \xB10.
+    -- atanh(\xB11) returns \xB1 and raises the ``divide-by-zero'' floating-point exception.
     -- atanh( x ) returns a NaN and raises the ``invalid'' floating-point exception for
        | x | > 1.
 

-
-
+
 

 
F.9.2.4 [The cosh functions]

-

-
-
-
1   -- cosh(±0) returns 1.
-    -- cosh(±) returns +.
+
+
1   -- cosh(\xB10) returns 1.
+    -- cosh(\xB1) returns +.
 

-
-
+
 

 
F.9.2.5 [The sinh functions]

-

-
-
-
1   -- sinh(±0) returns ±0.
-    -- sinh(±) returns ±.
+
+
1   -- sinh(\xB10) returns \xB10.
+    -- sinh(\xB1) returns \xB1.
 

-
-
+
 

 
F.9.2.6 [The tanh functions]

-

-
-
-
1   -- tanh(±0) returns ±0.
-    -- tanh(±) returns ±1.
+
+
1   -- tanh(\xB10) returns \xB10.
+    -- tanh(\xB1) returns \xB11.
 
 

-
-
+
 

 
F.9.3 [Exponential and logarithmic functions]

-
 Exponential and logarithmic functions
-

-
-
+
 

 
F.9.3.1 [The exp functions]

-

-
-
-
1   -- exp(±0) returns 1.
+
+
1   -- exp(\xB10) returns 1.
     -- exp(-) returns +0.
     -- exp(+) returns +.
 

-
-
+
 

 
F.9.3.2 [The exp2 functions]

-

-
-
-
1   -- exp2(±0) returns 1.
+
+
1   -- exp2(\xB10) returns 1.
     -- exp2(-) returns +0.
     -- exp2(+) returns +.
 

-
-
+
 

 
F.9.3.3 [The expm1 functions]

-

-
-
-
1   -- expm1(±0) returns ±0.
+
+
1   -- expm1(\xB10) returns \xB10.
     -- expm1(-) returns -1.
     -- expm1(+) returns +.
 

-
-
+
 

 
F.9.3.4 [The frexp functions]

-

-
-
-
1   -- frexp(±0, exp) returns ±0, and stores 0 in the object pointed to by exp.
-    -- frexp(±, exp) returns ±, and stores an unspecified value in the object
+
+
1   -- frexp(\xB10, exp) returns \xB10, and stores 0 in the object pointed to by exp.
+    -- frexp(\xB1, exp) returns \xB1, and stores an unspecified value in the object
        pointed to by exp.
     -- frexp(NaN, exp) stores an unspecified value in the object pointed to by exp
        (and returns a NaN).
 

-
-
+
 
2   frexp raises no floating-point exceptions.
 

-
-
+
 
3   On a binary system, the body of the frexp function might be
            {
                   *exp = (value == 0) ? 0 : (int)(1 + logb(value));
                   return scalbn(value, -(*exp));
            }
 

-
-
+
 

 
F.9.3.5 [The ilogb functions]

-

-
-
+
 
1   If the correct result is outside the range of the return type, the numeric result is
     unspecified and the ``invalid'' floating-point exception is raised.
 
 

-
-
+
 

 
F.9.3.6 [The ldexp functions]

-

-
-
+
 
1   On a binary system, ldexp(x, exp) is equivalent to scalbn(x, exp).
 

-
-
+
 

 
F.9.3.7 [The log functions]

-

-
-
-
1   -- log(±0) returns - and raises the ``divide-by-zero'' floating-point exception.
+
+
1   -- log(\xB10) returns - and raises the ``divide-by-zero'' floating-point exception.
     -- log(1) returns +0.
     -- log( x ) returns a NaN and raises the ``invalid'' floating-point exception for x < 0.
     -- log(+) returns +.
 

-
-
+
 

 
F.9.3.8 [The log10 functions]

-

-
-
-
1   -- log10(±0) returns - and raises the ``divide-by-zero'' floating-point exception.
+
+
1   -- log10(\xB10) returns - and raises the ``divide-by-zero'' floating-point exception.
     -- log10(1) returns +0.
     -- log10( x ) returns a NaN and raises the ``invalid'' floating-point exception for x < 0.
     -- log10(+) returns +.
 

-
-
+
 

 
F.9.3.9 [The log1p functions]

-

-
-
-
1   -- log1p(±0) returns ±0.
+
+
1   -- log1p(\xB10) returns \xB10.
     -- log1p(-1) returns - and raises the ``divide-by-zero'' floating-point exception.
     -- log1p( x ) returns a NaN and raises the ``invalid'' floating-point exception for
        x < -1.
     -- log1p(+) returns +.
 

-
-
+
 

 
F.9.3.10 [The log2 functions]

-

-
-
-
1   -- log2(±0) returns - and raises the ``divide-by-zero'' floating-point exception.
+
+
1   -- log2(\xB10) returns - and raises the ``divide-by-zero'' floating-point exception.
     -- log2(1) returns +0.
     -- log2( x ) returns a NaN and raises the ``invalid'' floating-point exception for x < 0.
     -- log2(+) returns +.
 

-
-
+
 

 
F.9.3.11 [The logb functions]

-

-
-
-
1   -- logb(±0) returns - and raises the ``divide-by-zero'' floating-point exception.
-    -- logb(±) returns +.
+
+
1   -- logb(\xB10) returns - and raises the ``divide-by-zero'' floating-point exception.
+    -- logb(\xB1) returns +.
 
 

-
-
+
 

 
F.9.3.12 [The modf functions]

-

-
-
-
1   -- modf(± x , iptr) returns a result with the same sign as x .
-    -- modf(±, iptr) returns ±0 and stores ± in the object pointed to by iptr.
+
+
1   -- modf(\xB1 x , iptr) returns a result with the same sign as x .
+    -- modf(\xB1, iptr) returns \xB10 and stores \xB1 in the object pointed to by iptr.
     -- modf(NaN, iptr) stores a NaN in the object pointed to by iptr (and returns a
        NaN).
 

-
-
+
 
2   modf behaves as though implemented by
            #include <math.h>
            #include <fenv.h>
@@ -25692,71 +22242,53 @@ Special characters: 00B5, 00B7, 02B0-02B8, 02BB, 02BD-02C1, 02D0-02D1,
                           value - (*iptr), value);
            }
 

-
-
+
 

 
F.9.3.13 [The scalbn and scalbln functions]

-

-
-
-
1   -- scalbn(±0, n) returns ±0.
+
+
1   -- scalbn(\xB10, n) returns \xB10.
     -- scalbn( x , 0) returns x .
-    -- scalbn(±, n) returns ±.
+    -- scalbn(\xB1, n) returns \xB1.
 

-
-
+
 

 
F.9.4 [Power and absolute value functions]

-
 Power and absolute value functions
-

-
-
+
 

 
F.9.4.1 [The cbrt functions]

-

-
-
-
1   -- cbrt(±0) returns ±0.
-    -- cbrt(±) returns ±.
+
+
1   -- cbrt(\xB10) returns \xB10.
+    -- cbrt(\xB1) returns \xB1.
 

-
-
+
 

 
F.9.4.2 [The fabs functions]

-

-
-
-
1   -- fabs(±0) returns +0.
-    -- fabs(±) returns +.
+
+
1   -- fabs(\xB10) returns +0.
+    -- fabs(\xB1) returns +.
 
 

-
-
+
 

 
F.9.4.3 [The hypot functions]

-

-
-
+
 
1   -- hypot( x , y ), hypot( y , x ), and hypot( x , - y ) are equivalent.
-    -- hypot( x , ±0) is equivalent to fabs( x ).
-    -- hypot(±, y ) returns +, even if y is a NaN.
+    -- hypot( x , \xB10) is equivalent to fabs( x ).
+    -- hypot(\xB1, y ) returns +, even if y is a NaN.
 

-
-
+
 

 
F.9.4.4 [The pow functions]

-

-
-
-
1   -- pow(±0, y ) returns ± and raises the ``divide-by-zero'' floating-point exception
+
+
1   -- pow(\xB10, y ) returns \xB1 and raises the ``divide-by-zero'' floating-point exception
        for y an odd integer < 0.
-    -- pow(±0, y ) returns + and raises the ``divide-by-zero'' floating-point exception
+    -- pow(\xB10, y ) returns + and raises the ``divide-by-zero'' floating-point exception
        for y < 0 and not an odd integer.
-    -- pow(±0, y ) returns ±0 for y an odd integer > 0.
-    -- pow(±0, y ) returns +0 for y > 0 and not an odd integer.
-    -- pow(-1, ±) returns 1.
+    -- pow(\xB10, y ) returns \xB10 for y an odd integer > 0.
+    -- pow(\xB10, y ) returns +0 for y > 0 and not an odd integer.
+    -- pow(-1, \xB1) returns 1.
     -- pow(+1, y ) returns 1 for any y , even a NaN.
-    -- pow( x , ±0) returns 1 for any x , even a NaN.
+    -- pow( x , \xB10) returns 1 for any x , even a NaN.
     -- pow( x , y ) returns a NaN and raises the ``invalid'' floating-point exception for
        finite x < 0 and finite non-integer y .
     -- pow( x , -) returns + for | x | < 1.
@@ -25771,48 +22303,33 @@ Special characters: 00B5, 00B7, 02B0-02B8, 02BB, 02BD-02C1, 02D0-02D1,
     -- pow(+, y ) returns + for y > 0.
 
 

-
-
+
 

 
F.9.4.5 [The sqrt functions]

-

-
-
+
 
1   sqrt is fully specified as a basic arithmetic operation in IEC 60559.
 

-
-
+
 

 
F.9.5 [Error and gamma functions]

-
 Error and gamma functions
-

-
-
+
 

 
F.9.5.1 [The erf functions]

-

-
-
-
1   -- erf(±0) returns ±0.
-    -- erf(±) returns ±1.
+
+
1   -- erf(\xB10) returns \xB10.
+    -- erf(\xB1) returns \xB11.
 

-
-
+
 

 
F.9.5.2 [The erfc functions]

-

-
-
+
 
1   -- erfc(-) returns 2.
     -- erfc(+) returns +0.
 

-
-
+
 

 
F.9.5.3 [The lgamma functions]

-

-
-
+
 
1   -- lgamma(1) returns +0.
     -- lgamma(2) returns +0.
     -- lgamma( x ) returns + and raises the ``divide-by-zero'' floating-point exception for
@@ -25820,37 +22337,27 @@ Special characters: 00B5, 00B7, 02B0-02B8, 02BB, 02BD-02C1, 02D0-02D1,
     -- lgamma(-) returns +.
     -- lgamma(+) returns +.
 

-
-
+
 

 
F.9.5.4 [The tgamma functions]

-

-
-
-
1   -- tgamma(±0) returns ± and raises the ``divide-by-zero'' floating-point exception.
+
+
1   -- tgamma(\xB10) returns \xB1 and raises the ``divide-by-zero'' floating-point exception.
     -- tgamma( x ) returns a NaN and raises the ``invalid'' floating-point exception for x a
        negative integer.
     -- tgamma(-) returns a NaN and raises the ``invalid'' floating-point exception.
     -- tgamma(+) returns +.
 

-
-
+
 

 
F.9.6 [Nearest integer functions]

-
 Nearest integer functions
-

-
-
+
 

 
F.9.6.1 [The ceil functions]

-

-
-
-
1   -- ceil(±0) returns ±0.
-    -- ceil(±) returns ±.
+
+
1   -- ceil(\xB10) returns \xB10.
+    -- ceil(\xB1) returns \xB1.
 

-
-
+
 
2   The double version of ceil behaves as though implemented by
 
            #include <math.h>
@@ -25866,50 +22373,37 @@ Special characters: 00B5, 00B7, 02B0-02B8, 02BB, 02BD-02C1, 02D0-02D1,
                 return result;
            }
 

-
-
+
 

 
F.9.6.2 [The floor functions]

-

-
-
-
1   -- floor(±0) returns ±0.
-    -- floor(±) returns ±.
+
+
1   -- floor(\xB10) returns \xB10.
+    -- floor(\xB1) returns \xB1.
 

-
-
-
2   See the sample implementation for ceil in F.9.6.1.
+
+
2   See the sample implementation for ceil in F.9.6.1.
 

-
-
+
 

 
F.9.6.3 [The nearbyint functions]

-

-
-
+
 
1   The nearbyint functions use IEC 60559 rounding according to the current rounding
     direction. They do not raise the ``inexact'' floating-point exception if the result differs in
     value from the argument.
-    -- nearbyint(±0) returns ±0 (for all rounding directions).
-    -- nearbyint(±) returns ± (for all rounding directions).
+    -- nearbyint(\xB10) returns \xB10 (for all rounding directions).
+    -- nearbyint(\xB1) returns \xB1 (for all rounding directions).
 

-
-
+
 

 
F.9.6.4 [The rint functions]

-

-
-
+
 
1   The rint functions differ from the nearbyint functions only in that they do raise the
     ``inexact'' floating-point exception if the result differs in value from the argument.
 

-
-
+
 

 
F.9.6.5 [The lrint and llrint functions]

-

-
-
+
 
1   The lrint and llrint functions provide floating-to-integer conversion as prescribed
     by IEC 60559. They round according to the current rounding direction. If the rounded
     value is outside the range of the return type, the numeric result is unspecified and the
@@ -25918,18 +22412,14 @@ Special characters: 00B5, 00B7, 02B0-02B8, 02BB, 02BD-02C1, 02D0-02D1,
     exception.
 
 

-
-
+
 

 
F.9.6.6 [The round functions]

-

-
-
-
1   -- round(±0) returns ±0.
-    -- round(±) returns ±.
+
+
1   -- round(\xB10) returns \xB10.
+    -- round(\xB1) returns \xB1.
 

-
-
+
 
2   The double version of round behaves as though implemented by
            #include <math.h>
            #include <fenv.h>
@@ -25950,51 +22440,38 @@ Special characters: 00B5, 00B7, 02B0-02B8, 02BB, 02BD-02C1, 02D0-02D1,
     The round functions may, but are not required to, raise the ``inexact'' floating-point
     exception for non-integer numeric arguments, as this implementation does.
 

-
-
+
 

 
F.9.6.7 [The lround and llround functions]

-

-
-
+
 
1   The lround and llround functions differ from the lrint and llrint functions
     with the default rounding direction just in that the lround and llround functions
     round halfway cases away from zero and need not raise the ``inexact'' floating-point
     exception for non-integer arguments that round to within the range of the return type.
 

-
-
+
 

 
F.9.6.8 [The trunc functions]

-

-
-
+
 
1   The trunc functions use IEC 60559 rounding toward zero (regardless of the current
     rounding direction).
-    -- trunc(±0) returns ±0.
-    -- trunc(±) returns ±.
+    -- trunc(\xB10) returns \xB10.
+    -- trunc(\xB1) returns \xB1.
 
 

-
-
+
 

 
F.9.7 [Remainder functions]

-
 Remainder functions
-

-
-
+
 

 
F.9.7.1 [The fmod functions]

-

-
-
-
1   -- fmod(±0, y ) returns ±0 for y not zero.
+
+
1   -- fmod(\xB10, y ) returns \xB10 for y not zero.
     -- fmod( x , y ) returns a NaN and raises the ``invalid'' floating-point exception for x
        infinite or y zero.
-    -- fmod( x , ±) returns x for x not infinite.
+    -- fmod( x , \xB1) returns x for x not infinite.
 

-
-
+
 
2   The double version of fmod behaves as though implemented by
            #include <math.h>
            #include <fenv.h>
@@ -26007,104 +22484,72 @@ Special characters: 00B5, 00B7, 02B0-02B8, 02BB, 02BD-02C1, 02D0-02D1,
                 return copysign(result, x);
            }
 

-
-
+
 

 
F.9.7.2 [The remainder functions]

-

-
-
+
 
1   The remainder functions are fully specified as a basic arithmetic operation in
     IEC 60559.
 

-
-
+
 

 
F.9.7.3 [The remquo functions]

-

-
-
+
 
1   The remquo functions follow the specifications for the remainder functions. They
     have no further specifications special to IEC 60559 implementations.
 

-
-
+
 

 
F.9.8 [Manipulation functions]

-
 Manipulation functions
-

-
-
+
 

 
F.9.8.1 [The copysign functions]

-

-
-
+
 
1   copysign is specified in the Appendix to IEC 60559.
 

-
-
+
 

 
F.9.8.2 [The nan functions]

-

-
-
+
 
1   All IEC 60559 implementations support quiet NaNs, in all floating formats.
 
 

-
-
+
 

 
F.9.8.3 [The nextafter functions]

-

-
-
+
 
1   -- nextafter( x , y ) raises the ``overflow'' and ``inexact'' floating-point exceptions
        for x finite and the function value infinite.
     -- nextafter( x , y ) raises the ``underflow'' and ``inexact'' floating-point
        exceptions for the function value subnormal or zero and x  y .
 

-
-
+
 

 
F.9.8.4 [The nexttoward functions]

-

-
-
+
 
1   No additional requirements beyond those on nextafter.
 

-
-
+
 

 
F.9.9 [Maximum, minimum, and positive difference functions]

-
 Maximum, minimum, and positive difference functions
-

-
-
+
 

 
F.9.9.1 [The fdim functions]

-

-
-
+
 
1   No additional requirements.
 

-
-
+
 

 
F.9.9.2 [The fmax functions]

-

-
-
+
 
1   If just one argument is a NaN, the fmax functions return the other argument (if both
     arguments are NaNs, the functions return a NaN).
 

-
-
-
2   The body of the fmax function might be323)
+
+
2   The body of the fmax function might be[323]
             { return (isgreaterequal(x, y) ||
                  isnan(y)) ? x : y; }
 

-
 
 
Footnote 323) Ideally, fmax would be sensitive to the sign of zero, for example fmax(-0. 0,   +0. 0) would
          return +0; however, implementation in software might be impractical.
@@ -26112,27 +22557,19 @@ Special characters: 00B5, 00B7, 02B0-02B8, 02BB, 02BD-02C1, 02D0-02D1,
                                         (informative)
 

 
-
+
 

 
F.9.9.3 [The fmin functions]

-

-
-
-
1   The fmin functions are analogous to the fmax functions (see F.9.9.2).
+
+
1   The fmin functions are analogous to the fmax functions (see F.9.9.2).
 

-
-
+
 

 
F.9.10 [Floating multiply-add]

-
 Floating multiply-add
-

-
-
+
 

 
F.9.10.1 [The fma functions]

-

-
-
+
 
1   -- fma( x , y , z ) computes xy + z , correctly rounded once.
     -- fma( x , y , z ) returns a NaN and optionally raises the ``invalid'' floating-point
        exception if one of x and y is infinite, the other is zero, and z is a NaN.
@@ -26141,19 +22578,13 @@ Special characters: 00B5, 00B7, 02B0-02B8, 02BB, 02BD-02C1, 02D0-02D1,
     -- fma( x , y , z ) returns a NaN and raises the ``invalid'' floating-point exception if x
        times y is an exact infinity and z is also an infinity but with the opposite sign.
 

-
-
+
 

 
G. [IEC 60559-compatible complex arithmetic]

-
 IEC 60559-compatible complex arithmetic
-

-
-
+
 

 
G.1 [Introduction]

-

-
-
+
 
1   This annex supplements annex F to specify complex arithmetic for compatibility with
     IEC 60559 real floating-point arithmetic. Although these specifications have been
     carefully designed, there is little existing practice to validate the design decisions.
@@ -26161,135 +22592,104 @@ Special characters: 00B5, 00B7, 02B0-02B8, 02BB, 02BD-02C1, 02D0-02D1,
     recommended          practice.       An         implementation        that     defines
     _ _STDC_IEC_559_COMPLEX_ _ should conform to the specifications in this annex.
 

-
-
+
 

 
G.2 [Types]

-

-
-
+
 
1   There is a new keyword _Imaginary, which is used to specify imaginary types. It is
     used as a type specifier within declaration specifiers in the same way as _Complex is
     (thus, _Imaginary float is a valid type name).
 

-
-
+
 
2   There are three imaginary types, designated as float _Imaginary, double
     _Imaginary, and long double _Imaginary. The imaginary types (along with
     the real floating and complex types) are floating types.
 

-
-
+
 
3   For imaginary types, the corresponding real type is given by deleting the keyword
     _Imaginary from the type name.
 

-
-
+
 
4   Each imaginary type has the same representation and alignment requirements as the
     corresponding real type. The value of an object of imaginary type is the value of the real
     representation times the imaginary unit.
 

-
-
+
 
5   The imaginary type domain comprises the imaginary types.
 

-
-
+
 

 
G.3 [Conventions]

-

-
-
+
 
1   A complex or imaginary value with at least one infinite part is regarded as an infinity
     (even if its other part is a NaN). A complex or imaginary value is a finite number if each
     of its parts is a finite number (neither infinite nor NaN). A complex or imaginary value is
     a zero if each of its parts is a zero.
 
 

-
-
+
 

 
G.4 [Conversions]

-
 Conversions
-

-
-
+
 

 
G.4.1 [Imaginary types]

-

-
-
+
 
1   Conversions among imaginary types follow rules analogous to those for real floating
     types.
 

-
-
+
 

 
G.4.2 [Real and imaginary]

-

-
-
-
1   When a value of imaginary type is converted to a real type other than _Bool,324) the
+
+
1   When a value of imaginary type is converted to a real type other than _Bool,[324] the
     result is a positive zero.
 

-
 
-
Footnote 324) See 6.3.1.2.
+
Footnote 324) See 6.3.1.2.
 

 
-
+
 
2   When a value of real type is converted to an imaginary type, the result is a positive
     imaginary zero.
 

-
-
+
 

 
G.4.3 [Imaginary and complex]

-

-
-
+
 
1   When a value of imaginary type is converted to a complex type, the real part of the
     complex result value is a positive zero and the imaginary part of the complex result value
     is determined by the conversion rules for the corresponding real types.
 

-
-
+
 
2   When a value of complex type is converted to an imaginary type, the real part of the
     complex value is discarded and the value of the imaginary part is converted according to
     the conversion rules for the corresponding real types.
 

-
-
+
 

 
G.5 [Binary operators]

-

-
-
-
1   The following subclauses supplement 6.5 in order to specify the type of the result for an
+
+
1   The following subclauses supplement 6.5 in order to specify the type of the result for an
     operation with an imaginary operand.
 

-
-
+
 
2   For most operand types, the value of the result of a binary operator with an imaginary or
     complex operand is completely determined, with reference to real arithmetic, by the usual
     mathematical formula. For some operand types, the usual mathematical formula is
     problematic because of its treatment of infinities and because of undue overflow or
-    underflow; in these cases the result satisfies certain properties (specified in G.5.1), but is
+    underflow; in these cases the result satisfies certain properties (specified in G.5.1), but is
     not completely determined.
 

-
-
+
 

 
G.5.1 [Multiplicative operators]

-

-
-
-
1   If one operand has real type and the other operand has imaginary type, then the result has
+
+
1 Semantics
+   If one operand has real type and the other operand has imaginary type, then the result has
     imaginary type. If both operands have imaginary type, then the result has real type. (If
     either operand has complex type, then the result has complex type.)
 

-
-
+
 
2   If the operands are not both complex, then the result and floating-point exception
     behavior of the * operator is defined by the usual mathematical formula:
            *                    u                       iv                       u + iv
@@ -26300,8 +22700,7 @@ Special characters: 00B5, 00B7, 02B0-02B8, 02BB, 02BD-02C1, 02D0-02D1,
 
            x + iy       ( xu) + i ( yu)         (- yv ) + i ( xv )
 

-
-
+
 
3   If the second operand is not complex, then the result and floating-point exception
     behavior of the / operator is defined by the usual mathematical formula:
            /                     u                           iv
@@ -26312,34 +22711,31 @@ Special characters: 00B5, 00B7, 02B0-02B8, 02BB, 02BD-02C1, 02D0-02D1,
 
            x + iy       ( x /u ) + i ( y /u )     ( y / v ) + i (- x / v )
 

-
-
+
 
4   The * and / operators satisfy the following infinity properties for all real, imaginary, and
-    complex operands:325)
+    complex operands:[325]
     -- if one operand is an infinity and the other operand is a nonzero finite number or an
        infinity, then the result of the * operator is an infinity;
     -- if the first operand is an infinity and the second operand is a finite number, then the
        result of the / operator is an infinity;
     -- if the first operand is a finite number and the second operand is an infinity, then the
        result of the / operator is a zero;
-    -- if the first operand is a nonzero finite number or an infinity and the second operand is
-       a zero, then the result of the / operator is an infinity.
 

-
 
 
Footnote 325) These properties are already implied for those cases covered in the tables, but are required for all cases
          (at least where the state for CX_LIMITED_RANGE is ``off'').
+    -- if the first operand is a nonzero finite number or an infinity and the second operand is
+       a zero, then the result of the / operator is an infinity.
 

 
-
+
 
5   If both operands of the * operator are complex or if the second operand of the / operator
     is complex, the operator raises floating-point exceptions if appropriate for the calculation
     of the parts of the result, and may raise spurious floating-point exceptions.
 

-
-
+
 
6   EXAMPLE 1 Multiplication of double _Complex operands could be implemented as follows. Note
-    that the imaginary unit I has imaginary type (see G.6).
+    that the imaginary unit I has imaginary type (see G.6).
            #include <math.h>
            #include <complex.h>
            /* Multiply z * w ... */
@@ -26388,14 +22784,12 @@ Special characters: 00B5, 00B7, 02B0-02B8, 02BB, 02BD-02C1, 02D0-02D1,
                      return x + I * y;
              }
 

-
-
+
 
7   This implementation achieves the required treatment of infinities at the cost of only one isnan test in
     ordinary (finite) cases. It is less than ideal in that undue overflow and underflow may occur.
 
 

-
-
+
 
8   EXAMPLE 2      Division of two double _Complex operands could be implemented as follows.
              #include <math.h>
              #include <complex.h>
@@ -26441,44 +22835,37 @@ Special characters: 00B5, 00B7, 02B0-02B8, 02BB, 02BD-02C1, 02D0-02D1,
                      return x + I * y;
             }
 

-
-
+
 
9   Scaling the denominator alleviates the main overflow and underflow problem, which is more serious than
     for multiplication. In the spirit of the multiplication example above, this code does not defend against
     overflow and underflow in the calculation of the numerator. Scaling with the scalbn function, instead of
     with division, provides better roundoff characteristics.
 
 

-
-
+
 

 
G.5.2 [Additive operators]

-

-
-
-
1   If both operands have imaginary type, then the result has imaginary type. (If one operand
+
+
1 Semantics
+   If both operands have imaginary type, then the result has imaginary type. (If one operand
     has real type and the other operand has imaginary type, or if either operand has complex
     type, then the result has complex type.)
 

-
-
+
 
2   In all cases the result and floating-point exception behavior of a + or - operator is defined
     by the usual mathematical formula:
            + or -              u                       iv                    u + iv
 
-           x                 x±u                     x ± iv              ( x ± u) ± iv
+           x                 x\xB1u                     x \xB1 iv              ( x \xB1 u) \xB1 iv
 
-           iy               ±u + iy                 i( y ± v)            ±u + i ( y ± v )
+           iy               \xB1u + iy                 i( y \xB1 v)            \xB1u + i ( y \xB1 v )
 
-           x + iy         ( x ± u) + iy           x + i( y ± v)       ( x ± u) + i ( y ± v)
+           x + iy         ( x \xB1 u) + iy           x + i( y \xB1 v)       ( x \xB1 u) + i ( y \xB1 v)
 

-
-
+
 

-
G.6 [Complex arithmetic ]

-

-
-
+
G.6 [Complex arithmetic <complex.h>]

+
 
1   The macros
             imaginary
     and
@@ -26486,50 +22873,44 @@ Special characters: 00B5, 00B7, 02B0-02B8, 02BB, 02BD-02C1, 02D0-02D1,
     are defined, respectively, as _Imaginary and a constant expression of type const
     float _Imaginary with the value of the imaginary unit. The macro
             I
-    is defined to be _Imaginary_I (not _Complex_I as stated in 7.3). Notwithstanding
-    the provisions of 7.1.3, a program may undefine and then perhaps redefine the macro
+    is defined to be _Imaginary_I (not _Complex_I as stated in 7.3). Notwithstanding
+    the provisions of 7.1.3, a program may undefine and then perhaps redefine the macro
     imaginary.
 

-
-
+
 
2   This subclause contains specifications for the <complex.h> functions that are
     particularly suited to IEC 60559 implementations. For families of functions, the
     specifications apply to all of the functions even though only the principal function is
-    shown. Unless otherwise specified, where the symbol ``±'' occurs in both an argument
+    shown. Unless otherwise specified, where the symbol ``\xB1'' occurs in both an argument
     and the result, the result has the same sign as the argument.
 

-
-
+
 
3   The functions are continuous onto both sides of their branch cuts, taking into account the
-    sign of zero. For example, csqrt(-2 ± i 0) = ±i     2.
+    sign of zero. For example, csqrt(-2 \xB1 i 0) = \xB1i     2.
 

-
-
+
 
4   Since complex and imaginary values are composed of real values, each function may be
     regarded as computing real values from real values. Except as noted, the functions treat
     real infinities, NaNs, signed zeros, subnormals, and the floating-point exception flags in a
-    manner consistent with the specifications for real functions in F.9.326)
+    manner consistent with the specifications for real functions in F.9.[326]
 

-
 
-
Footnote 326) As noted in G.3, a complex value with at least one infinite part is regarded as an infinity even if its
+
Footnote 326) As noted in G.3, a complex value with at least one infinite part is regarded as an infinity even if its
          other part is a NaN.
 

 
-
+
 
5   The functions cimag, conj, cproj, and creal are fully specified for all
-    implementations, including IEC 60559 ones, in 7.3.9. These functions raise no floating-
+    implementations, including IEC 60559 ones, in 7.3.9. These functions raise no floating-
     point exceptions.
 

-
-
+
 
6   Each of the functions cabs and carg is specified by a formula in terms of a real
     function (whose special cases are covered in annex F):
             cabs( x + iy ) = hypot( x , y )
             carg( x + iy ) = atan2( y , x )
 

-
-
+
 
7   Each of the functions casin, catan, ccos, csin, and ctan is specified implicitly by
     a formula in terms of other complex functions (whose special cases are specified below):
             casin( z )      =   -i casinh(iz )
@@ -26538,8 +22919,7 @@ Special characters: 00B5, 00B7, 02B0-02B8, 02BB, 02BD-02C1, 02D0-02D1,
             csin( z )       =   -i csinh(iz )
             ctan( z )       =   -i ctanh(iz )
 

-
-
+
 
8   For the other functions, the following subclauses specify behavior for special cases,
     including treatment of the ``invalid'' and ``divide-by-zero'' floating-point exceptions. For
     families of functions, the specifications apply to all of the functions even though only the
@@ -26548,26 +22928,19 @@ Special characters: 00B5, 00B7, 02B0-02B8, 02BB, 02BD-02C1, 02D0-02D1,
     the function f is also either even, f (- z ) = f ( z ), or odd, f (- z ) = - f ( z ), then the
     specifications for the first quadrant imply the specifications for the other three quadrants.
 

-
-
+
 
9   In the following subclauses, cis( y ) is defined as cos( y ) + i sin( y ).
 

-
-
+
 

 
G.6.1 [Trigonometric functions]

-
 Trigonometric functions
-

-
-
+
 

 
G.6.1.1 [The cacos functions]

-

-
-
+
 
1   -- cacos(conj( z )) = conj(cacos( z )).
-    -- cacos(±0 + i 0) returns  /2 - i 0.
-    -- cacos(±0 + i NaN) returns  /2 + i NaN.
+    -- cacos(\xB10 + i 0) returns  /2 - i 0.
+    -- cacos(\xB10 + i NaN) returns  /2 + i NaN.
     -- cacos( x + i ) returns  /2 - i , for finite x .
     -- cacos( x + i NaN) returns NaN + i NaN and optionally raises the ``invalid'' floating-
        point exception, for nonzero finite x .
@@ -26575,28 +22948,22 @@ Special characters: 00B5, 00B7, 02B0-02B8, 02BB, 02BD-02C1, 02D0-02D1,
     -- cacos(+ + iy ) returns +0 - i , for positive-signed finite y .
     -- cacos(- + i ) returns 3 /4 - i .
     -- cacos(+ + i ) returns  /4 - i .
-    -- cacos(± + i NaN) returns NaN ± i  (where the sign of the imaginary part of the
+    -- cacos(\xB1 + i NaN) returns NaN \xB1 i  (where the sign of the imaginary part of the
        result is unspecified).
     -- cacos(NaN + iy ) returns NaN + i NaN and optionally raises the ``invalid'' floating-
        point exception, for finite y .
     -- cacos(NaN + i ) returns NaN - i .
     -- cacos(NaN + i NaN) returns NaN + i NaN.
 

-
-
+
 

 
G.6.2 [Hyperbolic functions]

-
 Hyperbolic functions
-

-
-
+
 

 
G.6.2.1 [The cacosh functions]

-

-
-
+
 
1   -- cacosh(conj( z )) = conj(cacosh( z )).
-    -- cacosh(±0 + i 0) returns +0 + i /2.
+    -- cacosh(\xB10 + i 0) returns +0 + i /2.
     -- cacosh( x + i ) returns + + i /2, for finite x .
     -- cacosh( x + i NaN) returns NaN + i NaN and optionally raises the ``invalid''
        floating-point exception, for finite x .
@@ -26604,19 +22971,16 @@ Special characters: 00B5, 00B7, 02B0-02B8, 02BB, 02BD-02C1, 02D0-02D1,
     -- cacosh(+ + iy ) returns + + i 0, for positive-signed finite y .
     -- cacosh(- + i ) returns + + i 3 /4.
     -- cacosh(+ + i ) returns + + i /4.
-    -- cacosh(± + i NaN) returns + + i NaN.
+    -- cacosh(\xB1 + i NaN) returns + + i NaN.
     -- cacosh(NaN + iy ) returns NaN + i NaN and optionally raises the ``invalid''
        floating-point exception, for finite y .
     -- cacosh(NaN + i ) returns + + i NaN.
     -- cacosh(NaN + i NaN) returns NaN + i NaN.
 

-
-
+
 

 
G.6.2.2 [The casinh functions]

-

-
-
+
 
1   -- casinh(conj( z )) = conj(casinh( z )) and casinh is odd.
     -- casinh(+0 + i 0) returns 0 + i 0.
     -- casinh( x + i ) returns + + i /2 for positive-signed finite x .
@@ -26628,17 +22992,14 @@ Special characters: 00B5, 00B7, 02B0-02B8, 02BB, 02BD-02C1, 02D0-02D1,
     -- casinh(NaN + i 0) returns NaN + i 0.
     -- casinh(NaN + iy ) returns NaN + i NaN and optionally raises the ``invalid''
        floating-point exception, for finite nonzero y .
-    -- casinh(NaN + i ) returns ± + i NaN (where the sign of the real part of the result
+    -- casinh(NaN + i ) returns \xB1 + i NaN (where the sign of the real part of the result
        is unspecified).
     -- casinh(NaN + i NaN) returns NaN + i NaN.
 

-
-
+
 

 
G.6.2.3 [The catanh functions]

-

-
-
+
 
1   -- catanh(conj( z )) = conj(catanh( z )) and catanh is odd.
     -- catanh(+0 + i 0) returns +0 + i 0.
     -- catanh(+0 + i NaN) returns +0 + i NaN.
@@ -26652,22 +23013,19 @@ Special characters: 00B5, 00B7, 02B0-02B8, 02BB, 02BD-02C1, 02D0-02D1,
     -- catanh(+ + i NaN) returns +0 + i NaN.
     -- catanh(NaN + iy ) returns NaN + i NaN and optionally raises the ``invalid''
        floating-point exception, for finite y .
-    -- catanh(NaN + i ) returns ±0 + i /2 (where the sign of the real part of the result is
+    -- catanh(NaN + i ) returns \xB10 + i /2 (where the sign of the real part of the result is
        unspecified).
     -- catanh(NaN + i NaN) returns NaN + i NaN.
 

-
-
+
 

 
G.6.2.4 [The ccosh functions]

-

-
-
+
 
1   -- ccosh(conj( z )) = conj(ccosh( z )) and ccosh is even.
     -- ccosh(+0 + i 0) returns 1 + i 0.
-    -- ccosh(+0 + i ) returns NaN ± i 0 (where the sign of the imaginary part of the
+    -- ccosh(+0 + i ) returns NaN \xB1 i 0 (where the sign of the imaginary part of the
        result is unspecified) and raises the ``invalid'' floating-point exception.
-    -- ccosh(+0 + i NaN) returns NaN ± i 0 (where the sign of the imaginary part of the
+    -- ccosh(+0 + i NaN) returns NaN \xB1 i 0 (where the sign of the imaginary part of the
        result is unspecified).
     -- ccosh( x + i ) returns NaN + i NaN and raises the ``invalid'' floating-point
        exception, for finite nonzero x .
@@ -26675,27 +23033,24 @@ Special characters: 00B5, 00B7, 02B0-02B8, 02BB, 02BD-02C1, 02D0-02D1,
        point exception, for finite nonzero x .
     -- ccosh(+ + i 0) returns + + i 0.
     -- ccosh(+ + iy ) returns + cis( y ), for finite nonzero y .
-    -- ccosh(+ + i ) returns ± + i NaN (where the sign of the real part of the result is
+    -- ccosh(+ + i ) returns \xB1 + i NaN (where the sign of the real part of the result is
        unspecified) and raises the ``invalid'' floating-point exception.
     -- ccosh(+ + i NaN) returns + + i NaN.
-    -- ccosh(NaN + i 0) returns NaN ± i 0 (where the sign of the imaginary part of the
+    -- ccosh(NaN + i 0) returns NaN \xB1 i 0 (where the sign of the imaginary part of the
        result is unspecified).
     -- ccosh(NaN + iy ) returns NaN + i NaN and optionally raises the ``invalid'' floating-
        point exception, for all nonzero numbers y .
     -- ccosh(NaN + i NaN) returns NaN + i NaN.
 

-
-
+
 

 
G.6.2.5 [The csinh functions]

-

-
-
+
 
1   -- csinh(conj( z )) = conj(csinh( z )) and csinh is odd.
     -- csinh(+0 + i 0) returns +0 + i 0.
-    -- csinh(+0 + i ) returns ±0 + i NaN (where the sign of the real part of the result is
+    -- csinh(+0 + i ) returns \xB10 + i NaN (where the sign of the real part of the result is
        unspecified) and raises the ``invalid'' floating-point exception.
-    -- csinh(+0 + i NaN) returns ±0 + i NaN (where the sign of the real part of the result is
+    -- csinh(+0 + i NaN) returns \xB10 + i NaN (where the sign of the real part of the result is
        unspecified).
     -- csinh( x + i ) returns NaN + i NaN and raises the ``invalid'' floating-point
        exception, for positive finite x .
@@ -26703,22 +23058,19 @@ Special characters: 00B5, 00B7, 02B0-02B8, 02BB, 02BD-02C1, 02D0-02D1,
        point exception, for finite nonzero x .
     -- csinh(+ + i 0) returns + + i 0.
     -- csinh(+ + iy ) returns + cis( y ), for positive finite y .
-    -- csinh(+ + i ) returns ± + i NaN (where the sign of the real part of the result is
+    -- csinh(+ + i ) returns \xB1 + i NaN (where the sign of the real part of the result is
        unspecified) and raises the ``invalid'' floating-point exception.
-    -- csinh(+ + i NaN) returns ± + i NaN (where the sign of the real part of the result
+    -- csinh(+ + i NaN) returns \xB1 + i NaN (where the sign of the real part of the result
        is unspecified).
     -- csinh(NaN + i 0) returns NaN + i 0.
     -- csinh(NaN + iy ) returns NaN + i NaN and optionally raises the ``invalid'' floating-
        point exception, for all nonzero numbers y .
     -- csinh(NaN + i NaN) returns NaN + i NaN.
 

-
-
+
 

 
G.6.2.6 [The ctanh functions]

-

-
-
+
 
1   -- ctanh(conj( z )) = conj(ctanh( z ))and ctanh is odd.
     -- ctanh(+0 + i 0) returns +0 + i 0.
     -- ctanh( x + i ) returns NaN + i NaN and raises the ``invalid'' floating-point
@@ -26726,9 +23078,9 @@ Special characters: 00B5, 00B7, 02B0-02B8, 02BB, 02BD-02C1, 02D0-02D1,
     -- ctanh( x + i NaN) returns NaN + i NaN and optionally raises the ``invalid'' floating-
        point exception, for finite x .
     -- ctanh(+ + iy ) returns 1 + i 0 sin(2 y ), for positive-signed finite y .
-    -- ctanh(+ + i ) returns 1 ± i 0 (where the sign of the imaginary part of the result
+    -- ctanh(+ + i ) returns 1 \xB1 i 0 (where the sign of the imaginary part of the result
        is unspecified).
-    -- ctanh(+ + i NaN) returns 1 ± i 0 (where the sign of the imaginary part of the
+    -- ctanh(+ + i NaN) returns 1 \xB1 i 0 (where the sign of the imaginary part of the
        result is unspecified).
     -- ctanh(NaN + i 0) returns NaN + i 0.
     -- ctanh(NaN + iy ) returns NaN + i NaN and optionally raises the ``invalid'' floating-
@@ -26736,21 +23088,15 @@ Special characters: 00B5, 00B7, 02B0-02B8, 02BB, 02BD-02C1, 02D0-02D1,
     -- ctanh(NaN + i NaN) returns NaN + i NaN.
 
 

-
-
+
 

 
G.6.3 [Exponential and logarithmic functions]

-
 Exponential and logarithmic functions
-

-
-
+
 

 
G.6.3.1 [The cexp functions]

-

-
-
+
 
1   -- cexp(conj( z )) = conj(cexp( z )).
-    -- cexp(±0 + i 0) returns 1 + i 0.
+    -- cexp(\xB10 + i 0) returns 1 + i 0.
     -- cexp( x + i ) returns NaN + i NaN and raises the ``invalid'' floating-point
        exception, for finite x .
     -- cexp( x + i NaN) returns NaN + i NaN and optionally raises the ``invalid'' floating-
@@ -26758,26 +23104,23 @@ Special characters: 00B5, 00B7, 02B0-02B8, 02BB, 02BD-02C1, 02D0-02D1,
     -- cexp(+ + i 0) returns + + i 0.
     -- cexp(- + iy ) returns +0 cis( y ), for finite y .
     -- cexp(+ + iy ) returns + cis( y ), for finite nonzero y .
-    -- cexp(- + i ) returns ±0 ± i 0 (where the signs of the real and imaginary parts of
+    -- cexp(- + i ) returns \xB10 \xB1 i 0 (where the signs of the real and imaginary parts of
        the result are unspecified).
-    -- cexp(+ + i ) returns ± + i NaN and raises the ``invalid'' floating-point
+    -- cexp(+ + i ) returns \xB1 + i NaN and raises the ``invalid'' floating-point
        exception (where the sign of the real part of the result is unspecified).
-    -- cexp(- + i NaN) returns ±0 ± i 0 (where the signs of the real and imaginary parts
+    -- cexp(- + i NaN) returns \xB10 \xB1 i 0 (where the signs of the real and imaginary parts
        of the result are unspecified).
-    -- cexp(+ + i NaN) returns ± + i NaN (where the sign of the real part of the result
+    -- cexp(+ + i NaN) returns \xB1 + i NaN (where the sign of the real part of the result
        is unspecified).
     -- cexp(NaN + i 0) returns NaN + i 0.
     -- cexp(NaN + iy ) returns NaN + i NaN and optionally raises the ``invalid'' floating-
        point exception, for all nonzero numbers y .
     -- cexp(NaN + i NaN) returns NaN + i NaN.
 

-
-
+
 

 
G.6.3.2 [The clog functions]

-

-
-
+
 
1   -- clog(conj( z )) = conj(clog( z )).
     -- clog(-0 + i 0) returns - + i and raises the ``divide-by-zero'' floating-point
        exception.
@@ -26790,68 +23133,49 @@ Special characters: 00B5, 00B7, 02B0-02B8, 02BB, 02BD-02C1, 02D0-02D1,
     -- clog(+ + iy ) returns + + i 0, for finite positive-signed y .
     -- clog(- + i ) returns + + i 3 /4.
     -- clog(+ + i ) returns + + i /4.
-    -- clog(± + i NaN) returns + + i NaN.
+    -- clog(\xB1 + i NaN) returns + + i NaN.
     -- clog(NaN + iy ) returns NaN + i NaN and optionally raises the ``invalid'' floating-
        point exception, for finite y .
     -- clog(NaN + i ) returns + + i NaN.
     -- clog(NaN + i NaN) returns NaN + i NaN.
 

-
-
+
 

 
G.6.4 [Power and absolute-value functions]

-
 Power and absolute-value functions
-

-
-
+
 

 
G.6.4.1 [The cpow functions]

-

-
-
+
 
1   The cpow functions raise floating-point exceptions if appropriate for the calculation of
-    the parts of the result, and may raise spurious exceptions.327)
+    the parts of the result, and may raise spurious exceptions.[327]
 

-
 
 
Footnote 327) This allows cpow( z , c ) to be implemented as cexp(c      clog( z )) without precluding
          implementations that treat special cases more carefully.
 

 
-
+
 

 
G.6.4.2 [The csqrt functions]

-

-
-
+
 
1   -- csqrt(conj( z )) = conj(csqrt( z )).
-    -- csqrt(±0 + i 0) returns +0 + i 0.
+    -- csqrt(\xB10 + i 0) returns +0 + i 0.
     -- csqrt( x + i ) returns + + i , for all x (including NaN).
     -- csqrt( x + i NaN) returns NaN + i NaN and optionally raises the ``invalid'' floating-
        point exception, for finite x .
     -- csqrt(- + iy ) returns +0 + i , for finite positive-signed y .
     -- csqrt(+ + iy ) returns + + i 0, for finite positive-signed y .
-    -- csqrt(- + i NaN) returns NaN ± i  (where the sign of the imaginary part of the
+    -- csqrt(- + i NaN) returns NaN \xB1 i  (where the sign of the imaginary part of the
        result is unspecified).
     -- csqrt(+ + i NaN) returns + + i NaN.
     -- csqrt(NaN + iy ) returns NaN + i NaN and optionally raises the ``invalid'' floating-
        point exception, for finite y .
     -- csqrt(NaN + i NaN) returns NaN + i NaN.
-    327) This allows cpow( z , c ) to be implemented as cexp(c      clog( z )) without precluding
-         implementations that treat special cases more carefully.
 

-
-
-
Footnote 327) This allows cpow( z , c ) to be implemented as cexp(c      clog( z )) without precluding
-         implementations that treat special cases more carefully.
-

-
-
+
 

-
G.7 [Type-generic math ]

-

-
-
+
G.7 [Type-generic math <tgmath.h>]

+
 
1   Type-generic macros that accept complex arguments also accept imaginary arguments. If
     an argument is imaginary, the macro expands to an expression whose type is real,
     imaginary, or complex, as appropriate for the particular function: if the argument is
@@ -26859,8 +23183,7 @@ Special characters: 00B5, 00B7, 02B0-02B8, 02BB, 02BD-02C1, 02D0-02D1,
     types of sin, tan, sinh, tanh, asin, atan, asinh, and atanh are imaginary; and
     the types of the others are complex.
 

-
-
+
 
2   Given an imaginary argument, each of the type-generic macros cos, sin, tan, cosh,
     sinh, tanh, asin, atan, asinh, atanh is specified by a formula in terms of real
     functions:
@@ -26878,51 +23201,36 @@ Special characters: 00B5, 00B7, 02B0-02B8, 02BB, 02BD-02C1, 02D0-02D1,
                                           Annex H
                                         (informative)
 

-
-
+
 

 
H. [Language independent arithmetic]

-
 Language independent arithmetic
-

-
-
+
 

 
H.1 [Introduction]

-

-
-
+
 
1   This annex documents the extent to which the C language supports the ISO/IEC 10967-1
     standard for language-independent arithmetic (LIA-1). LIA-1 is more general than
     IEC 60559 (annex F) in that it covers integer and diverse floating-point arithmetics.
 

-
-
+
 

 
H.2 [Types]

-

-
-
+
 
1   The relevant C arithmetic types meet the requirements of LIA-1 types if an
     implementation adds notification of exceptional arithmetic operations and meets the 1
     unit in the last place (ULP) accuracy requirement (LIA-1 subclause 5.2.8).
 

-
-
+
 

 
H.2.1 [Boolean type]

-

-
-
+
 
1   The LIA-1 data type Boolean is implemented by the C data type bool with values of
     true and false, all from <stdbool.h>.
 

-
-
+
 

 
H.2.2 [Integer types]

-

-
-
+
 
1   The signed C integer types int, long int, long long int, and the corresponding
     unsigned types are compatible with LIA-1. If an implementation adds support for the
     LIA-1 exceptional values ``integer_overflow'' and ``undefined'', then those types are
@@ -26931,26 +23239,21 @@ Special characters: 00B5, 00B7, 02B0-02B8, 02BB, 02BD-02C1, 02D0-02D1,
     signed integer types as also being modulo need not detect integer overflow, in which case,
     only integer divide-by-zero need be detected.
 

-
-
+
 
2   The parameters for the integer data types can be accessed by the following:
     maxint         INT_MAX, LONG_MAX, LLONG_MAX, UINT_MAX, ULONG_MAX,
                    ULLONG_MAX
     minint         INT_MIN, LONG_MIN, LLONG_MIN
 

-
-
+
 
3   The parameter ``bounded'' is always true, and is not provided. The parameter ``minint''
     is always 0 for the unsigned types, and is not provided for those types.
 
 

-
-
+
 

 
H.2.2.1 [Integer operations]

-

-
-
+
 
1   The integer operations on integer types are the following:
     addI           x + y
     subI           x - y
@@ -26967,13 +23270,10 @@ Special characters: 00B5, 00B7, 02B0-02B8, 02BB, 02BD-02C1, 02D0-02D1,
     geqI           x >= y
     where x and y are expressions of the same integer type.
 

-
-
+
 

 
H.2.3 [Floating-point types]

-

-
-
+
 
1   The C floating-point types float, double, and long double are compatible with
     LIA-1. If an implementation adds support for the LIA-1 exceptional values
     ``underflow'', ``floating_overflow'', and ``"undefined'', then those types are conformant
@@ -26981,34 +23281,27 @@ Special characters: 00B5, 00B7, 02B0-02B8, 02BB, 02BD-02C1, 02D0-02D1,
     operations (see annex F) along with IEC 60559 status flags and traps has LIA-1
     conformant types.
 

-
-
+
 

 
H.2.3.1 [Floating-point parameters]

-

-
-
+
 
1   The parameters for a floating point data type can be accessed by the following:
     r              FLT_RADIX
     p              FLT_MANT_DIG, DBL_MANT_DIG, LDBL_MANT_DIG
     emax           FLT_MAX_EXP, DBL_MAX_EXP, LDBL_MAX_EXP
     emin           FLT_MIN_EXP, DBL_MIN_EXP, LDBL_MIN_EXP
 

-
-
+
 
2   The derived constants for the floating point types are accessed by the following:
     fmax           FLT_MAX, DBL_MAX, LDBL_MAX
     fminN          FLT_MIN, DBL_MIN, LDBL_MIN
     epsilon        FLT_EPSILON, DBL_EPSILON, LDBL_EPSILON
     rnd_style      FLT_ROUNDS
 

-
-
+
 

 
H.2.3.2 [Floating-point operations]

-

-
-
+
 
1   The floating-point operations on floating-point types are the following:
     addF           x + y
     subF           x - y
@@ -27016,7 +23309,7 @@ Special characters: 00B5, 00B7, 02B0-02B8, 02BB, 02BD-02C1, 02D0-02D1,
     divF           x / y
     negF           -x
     absF           fabsf(x), fabs(x), fabsl(x)
-    exponentF      1.f+logbf(x), 1.0+logb(x), 1.L+logbl(x)
+    exponentF      1.f+logbf(x), 1.0+logb(x), 1.L+logbl(x)
     scaleF         scalbnf(x, n), scalbn(x, n), scalbnl(x, n),
                    scalblnf(x, li), scalbln(x, li), scalblnl(x, li)
     intpartF       modff(x, &y), modf(x, &y), modfl(x, &y)
@@ -27030,18 +23323,14 @@ Special characters: 00B5, 00B7, 02B0-02B8, 02BB, 02BD-02C1, 02D0-02D1,
     where x and y are expressions of the same floating point type, n is of type int, and li
     is of type long int.
 

-
-
+
 

 
H.2.3.3 [Rounding styles]

-

-
-
+
 
1   The C Standard requires all floating types to use the same radix and rounding style, so
     that only one identifier for each is provided to map to LIA-1.
 

-
-
+
 
2   The FLT_ROUNDS parameter can be used to indicate the LIA-1 rounding styles:
     truncate       FLT_ROUNDS == 0
     nearest        FLT_ROUNDS == 1
@@ -27049,13 +23338,10 @@ Special characters: 00B5, 00B7, 02B0-02B8, 02BB, 02BD-02C1, 02D0-02D1,
     provided that an implementation extends FLT_ROUNDS to cover the rounding style used
     in all relevant LIA-1 operations, not just addition as in C.
 

-
-
+
 

 
H.2.4 [Type conversions]

-

-
-
+
 
1   The LIA-1 type conversions are the following type casts:
     cvtI'  I       (int)i, (long int)i, (long long int)i,
                    (unsigned int)i, (unsigned long int)i,
@@ -27066,8 +23352,7 @@ Special characters: 00B5, 00B7, 02B0-02B8, 02BB, 02BD-02C1, 02D0-02D1,
     cvtI  F        (float)i, (double)i, (long double)i
     cvtF'  F       (float)x, (double)x, (long double)x
 

-
-
+
 
2   In the above conversions from floating to integer, the use of (cast)x can be replaced with
     (cast)round(x), (cast)rint(x), (cast)nearbyint(x), (cast)trunc(x),
     (cast)ceil(x), or (cast)floor(x). In addition, C's floating-point to integer
@@ -27075,8 +23360,7 @@ Special characters: 00B5, 00B7, 02B0-02B8, 02BB, 02BD-02C1, 02D0-02D1,
     used. They all meet LIA-1's requirements on floating to integer rounding for in-range
     values. For out-of-range values, the conversions shall silently wrap for the modulo types.
 

-
-
+
 
3   The fmod() function is useful for doing silent wrapping to unsigned integer types, e.g.,
     fmod( fabs(rint(x)), 65536.0 ) or (0.0 <= (y = fmod( rint(x),
      65536.0 )) ? y : 65536.0 + y) will compute an integer value in the range 0.0
@@ -27086,78 +23370,62 @@ Special characters: 00B5, 00B7, 02B0-02B8, 02BB, 02BD-02C1, 02D0-02D1,
     range -32767.0 to +32768.0 which is not, in general, in the range of signed short
     int.
 

-
-
+
 
4   C's conversions (casts) from floating-point to floating-point can meet LIA-1
     requirements if an implementation uses round-to-nearest (IEC 60559 default).
 

-
-
+
 
5   C's conversions (casts) from integer to floating-point can meet LIA-1 requirements if an
     implementation uses round-to-nearest.
 
 

-
-
+
 

 
H.3 [Notification]

-

-
-
+
 
1   Notification is the process by which a user or program is informed that an exceptional
     arithmetic operation has occurred. C's operations are compatible with LIA-1 in that C
     allows an implementation to cause a notification to occur when any arithmetic operation
     returns an exceptional value as defined in LIA-1 clause 5.
 

-
-
+
 

 
H.3.1 [Notification alternatives]

-

-
-
+
 
1   LIA-1 requires at least the following two alternatives for handling of notifications:
     setting indicators or trap-and-terminate. LIA-1 allows a third alternative: trap-and-
     resume.
 

-
-
+
 
2   An implementation need only support a given notification alternative for the entire
     program. An implementation may support the ability to switch between notification
     alternatives during execution, but is not required to do so. An implementation can
     provide separate selection for each kind of notification, but this is not required.
 

-
-
+
 
3   C allows an implementation to provide notification. C's SIGFPE (for traps) and
     FE_INVALID, FE_DIVBYZERO, FE_OVERFLOW, FE_UNDERFLOW (for indicators)
     can provide LIA-1 notification.
 

-
-
+
 
4   C's signal handlers are compatible with LIA-1. Default handling of SIGFPE can
     provide trap-and-terminate behavior, except for those LIA-1 operations implemented by
     math library function calls. User-provided signal handlers for SIGFPE allow for trap-
     and-resume behavior with the same constraint.
 

-
-
+
 

 
H.3.1.1 [Indicators]

-

-
-
+
 
1   C's <fenv.h> status flags are compatible with the LIA-1 indicators.
 

-
-
+
 
2   The following mapping is for floating-point types:
     undefined                FE_INVALID, FE_DIVBYZERO
     floating_overflow        FE_OVERFLOW
     underflow                FE_UNDERFLOW
 

-
-
+
 
3   The floating-point indicator interrogation and manipulation operations are:
     set_indicators           feraiseexcept(i)
     clear_indicators         feclearexcept(i)
@@ -27165,41 +23433,33 @@ Special characters: 00B5, 00B7, 02B0-02B8, 02BB, 02BD-02C1, 02D0-02D1,
     current_indicators       fetestexcept(FE_ALL_EXCEPT)
     where i is an expression of type int representing a subset of the LIA-1 indicators.
 

-
-
+
 
4   C allows an implementation to provide the following LIA-1 required behavior: at
     program termination if any indicator is set the implementation shall send an unambiguous
     and ``hard to ignore'' message (see LIA-1 subclause 6.1.2)
 

-
-
+
 
5   LIA-1 does not make the distinction between floating-point and integer for ``undefined''.
     This documentation makes that distinction because <fenv.h> covers only the floating-
     point indicators.
 

-
-
+
 

 
H.3.1.2 [Traps]

-

-
-
+
 
1   C is compatible with LIA-1's trap requirements for arithmetic operations, but not for
     math library functions (which are not permitted to generate any externally visible
     exceptional conditions). An implementation can provide an alternative of notification
     through termination with a ``hard-to-ignore'' message (see LIA-1 subclause 6.1.3).
 

-
-
+
 
2   LIA-1 does not require that traps be precise.
 

-
-
+
 
3   C does require that SIGFPE be the signal corresponding to arithmetic exceptions, if there
     is any signal raised for them.
 

-
-
+
 
4   C supports signal handlers for SIGFPE and allows trapping of arithmetic exceptions.
     When arithmetic exceptions do trap, C's signal-handler mechanism allows trap-and-
     terminate (either default implementation behavior or user replacement for it) or trap-and-
@@ -27208,1246 +23468,1070 @@ Special characters: 00B5, 00B7, 02B0-02B8, 02BB, 02BD-02C1, 02D0-02D1,
                                            Annex I
                                         (informative)
 

-
-
+
 

 
I. [Common warnings]

-

-
-
+
 
1   An implementation may generate warnings in many situations, none of which are
     specified as part of this International Standard. The following are a few of the more
     common situations.
 

-
-
-
2   -- A new struct or union type appears in a function prototype (6.2.1, 6.7.2.3).
+
+
2   -- A new struct or union type appears in a function prototype (6.2.1, 6.7.2.3).
     -- A block with initialization of an object that has automatic storage duration is jumped
-       into (6.2.4).
+       into (6.2.4).
     -- An implicit narrowing conversion is encountered, such as the assignment of a long
        int or a double to an int, or a pointer to void to a pointer to any type other than
-       a character type (6.3).
+       a character type (6.3).
     -- A hexadecimal floating constant cannot be represented exactly in its evaluation format
-       (6.4.4.2).
+       (6.4.4.2).
     -- An integer character constant includes more than one character or a wide character
-       constant includes more than one multibyte character (6.4.4.4).
-    -- The characters /* are found in a comment (6.4.7).
+       constant includes more than one multibyte character (6.4.4.4).
+    -- The characters /* are found in a comment (6.4.7).
     -- An ``unordered'' binary operator (not comma, &&, or ||) contains a side effect to an
        lvalue in one operand, and a side effect to, or an access to the value of, the identical
-       lvalue in the other operand (6.5).
-    -- A function is called but no prototype has been supplied (6.5.2.2).
+       lvalue in the other operand (6.5).
+    -- A function is called but no prototype has been supplied (6.5.2.2).
     -- The arguments in a function call do not agree in number and type with those of the
-       parameters in a function definition that is not a prototype (6.5.2.2).
-    -- An object is defined but not used (6.7).
+       parameters in a function definition that is not a prototype (6.5.2.2).
+    -- An object is defined but not used (6.7).
     -- A value is given to an object of an enumerated type other than by assignment of an
        enumeration constant that is a member of that type, or an enumeration object that has
        the same type, or the value of a function that returns the same enumerated type
-       (6.7.2.2).
-    -- An aggregate has a partly bracketed initialization (6.7.7).
-    -- A statement cannot be reached (6.8).
-    -- A statement with no apparent effect is encountered (6.8).
+       (6.7.2.2).
+    -- An aggregate has a partly bracketed initialization (6.7.7).
+    -- A statement cannot be reached (6.8).
+    -- A statement with no apparent effect is encountered (6.8).
     -- A constant expression is used as the controlling expression of a selection statement
-       (6.8.4).
+       (6.8.4).
 -- An incorrectly formed preprocessing group is encountered while skipping a
-   preprocessing group (6.10.1).
--- An unrecognized #pragma directive is encountered (6.10.6).
+   preprocessing group (6.10.1).
+-- An unrecognized #pragma directive is encountered (6.10.6).
 
                                              Annex J
                                           (informative)
 

-
-
+
+

+
INTRODUCTION. [Introduction]

+
 

 
J. [Portability issues]

-

-
-
+
 
1   This annex collects some information about portability that appears in this International
     Standard.
 

-
-
+
 

 
J.1 [Unspecified behavior]

-

-
-
+
 
1   The following are unspecified:
-    -- The manner and timing of static initialization (5.1.2).
+    -- The manner and timing of static initialization (5.1.2).
     -- The termination status returned to the hosted environment if the return type of main
-       is not compatible with int (5.1.2.2.3).
+       is not compatible with int (5.1.2.2.3).
     -- The behavior of the display device if a printing character is written when the active
-       position is at the final position of a line (5.2.2).
+       position is at the final position of a line (5.2.2).
     -- The behavior of the display device if a backspace character is written when the active
-       position is at the initial position of a line (5.2.2).
+       position is at the initial position of a line (5.2.2).
     -- The behavior of the display device if a horizontal tab character is written when the
-       active position is at or past the last defined horizontal tabulation position (5.2.2).
+       active position is at or past the last defined horizontal tabulation position (5.2.2).
     -- The behavior of the display device if a vertical tab character is written when the active
-       position is at or past the last defined vertical tabulation position (5.2.2).
+       position is at or past the last defined vertical tabulation position (5.2.2).
     -- How an extended source character that does not correspond to a universal character
-       name counts toward the significant initial characters in an external identifier (5.2.4.1).
-    -- Many aspects of the representations of types (6.2.6).
-    -- The value of padding bytes when storing values in structures or unions (6.2.6.1).
-    -- The value of a union member other than the last one stored into (6.2.6.1).
+       name counts toward the significant initial characters in an external identifier (5.2.4.1).
+    -- Many aspects of the representations of types (6.2.6).
+    -- The value of padding bytes when storing values in structures or unions (6.2.6.1).
+    -- The value of a union member other than the last one stored into (6.2.6.1).
     -- The representation used when storing a value in an object that has more than one
-       object representation for that value (6.2.6.1).
-    -- The values of any padding bits in integer representations (6.2.6.2).
+       object representation for that value (6.2.6.1).
+    -- The values of any padding bits in integer representations (6.2.6.2).
     -- Whether certain operators can generate negative zeros and whether a negative zero
-       becomes a normal zero when stored in an object (6.2.6.2).
-    -- Whether two string literals result in distinct arrays (6.4.5).
+       becomes a normal zero when stored in an object (6.2.6.2).
+    -- Whether two string literals result in distinct arrays (6.4.5).
     -- The order in which subexpressions are evaluated and the order in which side effects
        take place, except as specified for the function-call (), &&, ||, ?:, and comma
-       operators (6.5).
+       operators (6.5).
 -- The order in which the function designator, arguments, and subexpressions within the
-   arguments are evaluated in a function call (6.5.2.2).
+   arguments are evaluated in a function call (6.5.2.2).
 -- The order of side effects among compound literal initialization list expressions
-   (6.5.2.5).
--- The order in which the operands of an assignment operator are evaluated (6.5.16).
--- The alignment of the addressable storage unit allocated to hold a bit-field (6.7.2.1).
+   (6.5.2.5).
+-- The order in which the operands of an assignment operator are evaluated (6.5.16).
+-- The alignment of the addressable storage unit allocated to hold a bit-field (6.7.2.1).
 -- Whether a call to an inline function uses the inline definition or the external definition
-   of the function (6.7.4).
+   of the function (6.7.4).
 -- Whether or not a size expression is evaluated when it is part of the operand of a
    sizeof operator and changing the value of the size expression would not affect the
-   result of the operator (6.7.5.2).
+   result of the operator (6.7.5.2).
 -- The order in which any side effects occur among the initialization list expressions in
-   an initializer (6.7.8).
--- The layout of storage for function parameters (6.9.1).
+   an initializer (6.7.8).
+-- The layout of storage for function parameters (6.9.1).
 -- When a fully expanded macro replacement list contains a function-like macro name
    as its last preprocessing token and the next preprocessing token from the source file is
    a (, and the fully expanded replacement of that macro ends with the name of the first
    macro and the next preprocessing token from the source file is again a (, whether that
-   is considered a nested replacement (6.10.3).
+   is considered a nested replacement (6.10.3).
 -- The order in which # and ## operations are evaluated during macro substitution
-   (6.10.3.2, 6.10.3.3).
--- Whether errno is a macro or an identifier with external linkage (7.5).
+   (6.10.3.2, 6.10.3.3).
+-- Whether errno is a macro or an identifier with external linkage (7.5).
 -- The state of the floating-point status flags when execution passes from a part of the
    program translated with FENV_ACCESS ``off'' to a part translated with
-   FENV_ACCESS ``on'' (7.6.1).
+   FENV_ACCESS ``on'' (7.6.1).
 -- The order in which feraiseexcept raises floating-point exceptions, except as
-   stated in F.7.6 (7.6.2.3).
+   stated in F.7.6 (7.6.2.3).
 -- Whether math_errhandling is a macro or an identifier with external linkage
-   (7.12).
+   (7.12).
 -- The results of the frexp functions when the specified value is not a floating-point
-   number (7.12.6.4).
+   number (7.12.6.4).
 -- The numeric result of the ilogb functions when the correct value is outside the
-   range of the return type (7.12.6.5, F.9.3.5).
--- The result of rounding when the value is out of range (7.12.9.5, 7.12.9.7, F.9.6.5).
+   range of the return type (7.12.6.5, F.9.3.5).
+-- The result of rounding when the value is out of range (7.12.9.5, 7.12.9.7, F.9.6.5).
 -- The value stored by the remquo functions in the object pointed to by quo when y is
-   zero (7.12.10.3).
--- Whether setjmp is a macro or an identifier with external linkage (7.13).
+   zero (7.12.10.3).
+-- Whether setjmp is a macro or an identifier with external linkage (7.13).
 -- Whether va_copy and va_end are macros or identifiers with external linkage
-   (7.15.1).
+   (7.15.1).
 -- The hexadecimal digit before the decimal point when a non-normalized floating-point
-   number is printed with an a or A conversion specifier (7.19.6.1, 7.24.2.1).
+   number is printed with an a or A conversion specifier (7.19.6.1, 7.24.2.1).
 -- The value of the file position indicator after a successful call to the ungetc function
    for a text stream, or the ungetwc function for any stream, until all pushed-back
-   characters are read or discarded (7.19.7.11, 7.24.3.10).
--- The details of the value stored by the fgetpos function (7.19.9.1).
--- The details of the value returned by the ftell function for a text stream (7.19.9.4).
+   characters are read or discarded (7.19.7.11, 7.24.3.10).
+-- The details of the value stored by the fgetpos function (7.19.9.1).
+-- The details of the value returned by the ftell function for a text stream (7.19.9.4).
 -- Whether the strtod, strtof, strtold, wcstod, wcstof, and wcstold
    functions convert a minus-signed sequence to a negative number directly or by
    negating the value resulting from converting the corresponding unsigned sequence
-   (7.20.1.3, 7.24.4.1.1).
+   (7.20.1.3, 7.24.4.1.1).
 -- The order and contiguity of storage allocated by successive calls to the calloc,
-   malloc, and realloc functions (7.20.3).
+   malloc, and realloc functions (7.20.3).
 -- The amount of storage allocated by a successful call to the calloc, malloc, or
-   realloc function when 0 bytes was requested (7.20.3).
+   realloc function when 0 bytes was requested (7.20.3).
 -- Which of two elements that compare as equal is matched by the bsearch function
-   (7.20.5.1).
+   (7.20.5.1).
 -- The order of two elements that compare as equal in an array sorted by the qsort
-   function (7.20.5.2).
--- The encoding of the calendar time returned by the time function (7.23.2.4).
+   function (7.20.5.2).
+-- The encoding of the calendar time returned by the time function (7.23.2.4).
 -- The characters stored by the strftime or wcsftime function if any of the time
-   values being converted is outside the normal range (7.23.3.5, 7.24.5.1).
--- The conversion state after an encoding error occurs (7.24.6.3.2, 7.24.6.3.3, 7.24.6.4.1,
-     7.24.6.4.2,
+   values being converted is outside the normal range (7.23.3.5, 7.24.5.1).
+-- The conversion state after an encoding error occurs (7.24.6.3.2, 7.24.6.3.3, 7.24.6.4.1,
+     7.24.6.4.2,
 -- The resulting value when the ``invalid'' floating-point exception is raised during
-   IEC 60559 floating to integer conversion (F.4).
+   IEC 60559 floating to integer conversion (F.4).
 -- Whether conversion of non-integer IEC 60559 floating values to integer raises the
-   ``inexact'' floating-point exception (F.4).
+   ``inexact'' floating-point exception (F.4).
     -- Whether or when library functions in <math.h> raise the ``inexact'' floating-point
-       exception in an IEC 60559 conformant implementation (F.9).
+       exception in an IEC 60559 conformant implementation (F.9).
     -- Whether or when library functions in <math.h> raise an undeserved ``underflow''
-       floating-point exception in an IEC 60559 conformant implementation (F.9).
-    -- The exponent value stored by frexp for a NaN or infinity (F.9.3.4).
+       floating-point exception in an IEC 60559 conformant implementation (F.9).
+    -- The exponent value stored by frexp for a NaN or infinity (F.9.3.4).
     -- The numeric result returned by the lrint, llrint, lround, and llround
-       functions if the rounded value is outside the range of the return type (F.9.6.5, F.9.6.7).
+       functions if the rounded value is outside the range of the return type (F.9.6.5, F.9.6.7).
     -- The sign of one part of the complex result of several math functions for certain
-       exceptional values in IEC 60559 compatible implementations (G.6.1.1, G.6.2.2,
-       G.6.2.3, G.6.2.4, G.6.2.5, G.6.2.6, G.6.3.1, G.6.4.2).
+       exceptional values in IEC 60559 compatible implementations (G.6.1.1, G.6.2.2,
+       G.6.2.3, G.6.2.4, G.6.2.5, G.6.2.6, G.6.3.1, G.6.4.2).
 

-
-
+
 

 
J.2 [Undefined behavior]

-

-
-
+
 
1   The behavior is undefined in the following circumstances:
     -- A ``shall'' or ``shall not'' requirement that appears outside of a constraint is violated
        (clause 4).
     -- A nonempty source file does not end in a new-line character which is not immediately
        preceded by a backslash character or ends in a partial preprocessing token or
-       comment (5.1.1.2).
+       comment (5.1.1.2).
     -- Token concatenation produces a character sequence matching the syntax of a
-       universal character name (5.1.1.2).
+       universal character name (5.1.1.2).
     -- A program in a hosted environment does not define a function named main using one
-       of the specified forms (5.1.2.2.1).
+       of the specified forms (5.1.2.2.1).
     -- A character not in the basic source character set is encountered in a source file, except
        in an identifier, a character constant, a string literal, a header name, a comment, or a
-       preprocessing token that is never converted to a token (5.2.1).
+       preprocessing token that is never converted to a token (5.2.1).
     -- An identifier, comment, string literal, character constant, or header name contains an
-       invalid multibyte character or does not begin and end in the initial shift state (5.2.1.2).
+       invalid multibyte character or does not begin and end in the initial shift state (5.2.1.2).
     -- The same identifier has both internal and external linkage in the same translation unit
-       (6.2.2).
-    -- An object is referred to outside of its lifetime (6.2.4).
-    -- The value of a pointer to an object whose lifetime has ended is used (6.2.4).
+       (6.2.2).
+    -- An object is referred to outside of its lifetime (6.2.4).
+    -- The value of a pointer to an object whose lifetime has ended is used (6.2.4).
     -- The value of an object with automatic storage duration is used while it is
-       indeterminate (6.2.4, 6.7.8, 6.8).
+       indeterminate (6.2.4, 6.7.8, 6.8).
     -- A trap representation is read by an lvalue expression that does not have character type
-       (6.2.6.1).
+       (6.2.6.1).
     -- A trap representation is produced by a side effect that modifies any part of the object
-       using an lvalue expression that does not have character type (6.2.6.1).
+       using an lvalue expression that does not have character type (6.2.6.1).
     -- The arguments to certain operators are such that could produce a negative zero result,
-       but the implementation does not support negative zeros (6.2.6.2).
+       but the implementation does not support negative zeros (6.2.6.2).
     -- Two declarations of the same object or function specify types that are not compatible
-       (6.2.7).
+       (6.2.7).
     -- Conversion to or from an integer type produces a value outside the range that can be
-       represented (6.3.1.4).
+       represented (6.3.1.4).
     -- Demotion of one real floating type to another produces a value outside the range that
-       can be represented (6.3.1.5).
-    -- An lvalue does not designate an object when evaluated (6.3.2.1).
+       can be represented (6.3.1.5).
+    -- An lvalue does not designate an object when evaluated (6.3.2.1).
     -- A non-array lvalue with an incomplete type is used in a context that requires the value
-       of the designated object (6.3.2.1).
+       of the designated object (6.3.2.1).
     -- An lvalue having array type is converted to a pointer to the initial element of the
-       array, and the array object has register storage class (6.3.2.1).
+       array, and the array object has register storage class (6.3.2.1).
     -- An attempt is made to use the value of a void expression, or an implicit or explicit
-       conversion (except to void) is applied to a void expression (6.3.2.2).
+       conversion (except to void) is applied to a void expression (6.3.2.2).
     -- Conversion of a pointer to an integer type produces a value outside the range that can
-       be represented (6.3.2.3).
+       be represented (6.3.2.3).
     -- Conversion between two pointer types produces a result that is incorrectly aligned
-       (6.3.2.3).
+       (6.3.2.3).
     -- A pointer is used to call a function whose type is not compatible with the pointed-to
-       type (6.3.2.3).
+       type (6.3.2.3).
     -- An unmatched ' or " character is encountered on a logical source line during
-       tokenization (6.4).
+       tokenization (6.4).
     -- A reserved keyword token is used in translation phase 7 or 8 for some purpose other
-       than as a keyword (6.4.1).
+       than as a keyword (6.4.1).
     -- A universal character name in an identifier does not designate a character whose
-       encoding falls into one of the specified ranges (6.4.2.1).
+       encoding falls into one of the specified ranges (6.4.2.1).
     -- The initial character of an identifier is a universal character name designating a digit
-       (6.4.2.1).
-    -- Two identifiers differ only in nonsignificant characters (6.4.2.1).
-    -- The identifier _ _func_ _ is explicitly declared (6.4.2.2).
-    -- The program attempts to modify a string literal (6.4.5).
+       (6.4.2.1).
+    -- Two identifiers differ only in nonsignificant characters (6.4.2.1).
+    -- The identifier _ _func_ _ is explicitly declared (6.4.2.2).
+    -- The program attempts to modify a string literal (6.4.5).
     -- The characters ', \, ", //, or /* occur in the sequence between the < and >
        delimiters, or the characters ', \, //, or /* occur in the sequence between the "
-       delimiters, in a header name preprocessing token (6.4.7).
+       delimiters, in a header name preprocessing token (6.4.7).
     -- Between two sequence points, an object is modified more than once, or is modified
-       and the prior value is read other than to determine the value to be stored (6.5).
-    -- An exceptional condition occurs during the evaluation of an expression (6.5).
+       and the prior value is read other than to determine the value to be stored (6.5).
+    -- An exceptional condition occurs during the evaluation of an expression (6.5).
     -- An object has its stored value accessed other than by an lvalue of an allowable type
-       (6.5).
+       (6.5).
     -- An attempt is made to modify the result of a function call, a conditional operator, an
        assignment operator, or a comma operator, or to access it after the next sequence
-       point (6.5.2.2, 6.5.15, 6.5.16, 6.5.17).
+       point (6.5.2.2, 6.5.15, 6.5.16, 6.5.17).
     -- For a call to a function without a function prototype in scope, the number of
-       arguments does not equal the number of parameters (6.5.2.2).
+       arguments does not equal the number of parameters (6.5.2.2).
     -- For call to a function without a function prototype in scope where the function is
        defined with a function prototype, either the prototype ends with an ellipsis or the
        types of the arguments after promotion are not compatible with the types of the
-       parameters (6.5.2.2).
+       parameters (6.5.2.2).
     -- For a call to a function without a function prototype in scope where the function is not
        defined with a function prototype, the types of the arguments after promotion are not
        compatible with those of the parameters after promotion (with certain exceptions)
-       (6.5.2.2).
+       (6.5.2.2).
     -- A function is defined with a type that is not compatible with the type (of the
-       expression) pointed to by the expression that denotes the called function (6.5.2.2).
-    -- The operand of the unary * operator has an invalid value (6.5.3.2).
-    -- A pointer is converted to other than an integer or pointer type (6.5.4).
-    -- The value of the second operand of the / or % operator is zero (6.5.5).
+       expression) pointed to by the expression that denotes the called function (6.5.2.2).
+    -- The operand of the unary * operator has an invalid value (6.5.3.2).
+    -- A pointer is converted to other than an integer or pointer type (6.5.4).
+    -- The value of the second operand of the / or % operator is zero (6.5.5).
     -- Addition or subtraction of a pointer into, or just beyond, an array object and an
        integer type produces a result that does not point into, or just beyond, the same array
-       object (6.5.6).
+       object (6.5.6).
     -- Addition or subtraction of a pointer into, or just beyond, an array object and an
        integer type produces a result that points just beyond the array object and is used as
-       the operand of a unary * operator that is evaluated (6.5.6).
+       the operand of a unary * operator that is evaluated (6.5.6).
     -- Pointers that do not point into, or just beyond, the same array object are subtracted
-       (6.5.6).
+       (6.5.6).
     -- An array subscript is out of range, even if an object is apparently accessible with the
        given subscript (as in the lvalue expression a[1][7] given the declaration int
-       a[4][5]) (6.5.6).
+       a[4][5]) (6.5.6).
     -- The result of subtracting two pointers is not representable in an object of type
-       ptrdiff_t (6.5.6).
+       ptrdiff_t (6.5.6).
     -- An expression is shifted by a negative number or by an amount greater than or equal
-       to the width of the promoted expression (6.5.7).
+       to the width of the promoted expression (6.5.7).
     -- An expression having signed promoted type is left-shifted and either the value of the
        expression is negative or the result of shifting would be not be representable in the
-       promoted type (6.5.7).
+       promoted type (6.5.7).
     -- Pointers that do not point to the same aggregate or union (nor just beyond the same
-       array object) are compared using relational operators (6.5.8).
+       array object) are compared using relational operators (6.5.8).
     -- An object is assigned to an inexactly overlapping object or to an exactly overlapping
-       object with incompatible type (6.5.16.1).
+       object with incompatible type (6.5.16.1).
     -- An expression that is required to be an integer constant expression does not have an
        integer type; has operands that are not integer constants, enumeration constants,
        character constants, sizeof expressions whose results are integer constants, or
        immediately-cast floating constants; or contains casts (outside operands to sizeof
-       operators) other than conversions of arithmetic types to integer types (6.6).
+       operators) other than conversions of arithmetic types to integer types (6.6).
     -- A constant expression in an initializer is not, or does not evaluate to, one of the
        following: an arithmetic constant expression, a null pointer constant, an address
        constant, or an address constant for an object type plus or minus an integer constant
-       expression (6.6).
+       expression (6.6).
     -- An arithmetic constant expression does not have arithmetic type; has operands that
        are not integer constants, floating constants, enumeration constants, character
        constants, or sizeof expressions; or contains casts (outside operands to sizeof
-       operators) other than conversions of arithmetic types to arithmetic types (6.6).
+       operators) other than conversions of arithmetic types to arithmetic types (6.6).
     -- The value of an object is accessed by an array-subscript [], member-access . or ->,
        address &, or indirection * operator or a pointer cast in creating an address constant
-       (6.6).
+       (6.6).
     -- An identifier for an object is declared with no linkage and the type of the object is
-       incomplete after its declarator, or after its init-declarator if it has an initializer (6.7).
+       incomplete after its declarator, or after its init-declarator if it has an initializer (6.7).
     -- A function is declared at block scope with an explicit storage-class specifier other
-       than extern (6.7.1).
-    -- A structure or union is defined as containing no named members (6.7.2.1).
+       than extern (6.7.1).
+    -- A structure or union is defined as containing no named members (6.7.2.1).
     -- An attempt is made to access, or generate a pointer to just past, a flexible array
        member of a structure when the referenced object provides no elements for that array
-       (6.7.2.1).
+       (6.7.2.1).
     -- When the complete type is needed, an incomplete structure or union type is not
        completed in the same scope by another declaration of the tag that defines the content
-       (6.7.2.3).
+       (6.7.2.3).
     -- An attempt is made to modify an object defined with a const-qualified type through
-       use of an lvalue with non-const-qualified type (6.7.3).
+       use of an lvalue with non-const-qualified type (6.7.3).
     -- An attempt is made to refer to an object defined with a volatile-qualified type through
-       use of an lvalue with non-volatile-qualified type (6.7.3).
-    -- The specification of a function type includes any type qualifiers (6.7.3).
+       use of an lvalue with non-volatile-qualified type (6.7.3).
+    -- The specification of a function type includes any type qualifiers (6.7.3).
     -- Two qualified types that are required to be compatible do not have the identically
-       qualified version of a compatible type (6.7.3).
+       qualified version of a compatible type (6.7.3).
     -- An object which has been modified is accessed through a restrict-qualified pointer to
        a const-qualified type, or through a restrict-qualified pointer and another pointer that
-       are not both based on the same object (6.7.3.1).
+       are not both based on the same object (6.7.3.1).
     -- A restrict-qualified pointer is assigned a value based on another restricted pointer
        whose associated block neither began execution before the block associated with this
-       pointer, nor ended before the assignment (6.7.3.1).
+       pointer, nor ended before the assignment (6.7.3.1).
     -- A function with external linkage is declared with an inline function specifier, but is
-       not also defined in the same translation unit (6.7.4).
+       not also defined in the same translation unit (6.7.4).
     -- Two pointer types that are required to be compatible are not identically qualified, or
-       are not pointers to compatible types (6.7.5.1).
+       are not pointers to compatible types (6.7.5.1).
     -- The size expression in an array declaration is not a constant expression and evaluates
-       at program execution time to a nonpositive value (6.7.5.2).
+       at program execution time to a nonpositive value (6.7.5.2).
     -- In a context requiring two array types to be compatible, they do not have compatible
-       element types, or their size specifiers evaluate to unequal values (6.7.5.2).
+       element types, or their size specifiers evaluate to unequal values (6.7.5.2).
     -- A declaration of an array parameter includes the keyword static within the [ and
        ] and the corresponding argument does not provide access to the first element of an
-       array with at least the specified number of elements (6.7.5.3).
+       array with at least the specified number of elements (6.7.5.3).
     -- A storage-class specifier or type qualifier modifies the keyword void as a function
-       parameter type list (6.7.5.3).
+       parameter type list (6.7.5.3).
     -- In a context requiring two function types to be compatible, they do not have
        compatible return types, or their parameters disagree in use of the ellipsis terminator
        or the number and type of parameters (after default argument promotion, when there
         is no parameter type list or when one type is specified by a function definition with an
-       identifier list) (6.7.5.3).
-    -- The value of an unnamed member of a structure or union is used (6.7.8).
+       identifier list) (6.7.5.3).
+    -- The value of an unnamed member of a structure or union is used (6.7.8).
     -- The initializer for a scalar is neither a single expression nor a single expression
-       enclosed in braces (6.7.8).
+       enclosed in braces (6.7.8).
     -- The initializer for a structure or union object that has automatic storage duration is
        neither an initializer list nor a single expression that has compatible structure or union
-       type (6.7.8).
+       type (6.7.8).
     -- The initializer for an aggregate or union, other than an array initialized by a string
-       literal, is not a brace-enclosed list of initializers for its elements or members (6.7.8).
+       literal, is not a brace-enclosed list of initializers for its elements or members (6.7.8).
     -- An identifier with external linkage is used, but in the program there does not exist
        exactly one external definition for the identifier, or the identifier is not used and there
-       exist multiple external definitions for the identifier (6.9).
+       exist multiple external definitions for the identifier (6.9).
     -- A function definition includes an identifier list, but the types of the parameters are not
-       declared in a following declaration list (6.9.1).
-    -- An adjusted parameter type in a function definition is not an object type (6.9.1).
+       declared in a following declaration list (6.9.1).
+    -- An adjusted parameter type in a function definition is not an object type (6.9.1).
     -- A function that accepts a variable number of arguments is defined without a
-       parameter type list that ends with the ellipsis notation (6.9.1).
+       parameter type list that ends with the ellipsis notation (6.9.1).
     -- The } that terminates a function is reached, and the value of the function call is used
-       by the caller (6.9.1).
+       by the caller (6.9.1).
     -- An identifier for an object with internal linkage and an incomplete type is declared
-       with a tentative definition (6.9.2).
+       with a tentative definition (6.9.2).
     -- The token defined is generated during the expansion of a #if or #elif
        preprocessing directive, or the use of the defined unary operator does not match
-       one of the two specified forms prior to macro replacement (6.10.1).
+       one of the two specified forms prior to macro replacement (6.10.1).
     -- The #include preprocessing directive that results after expansion does not match
-       one of the two header name forms (6.10.2).
+       one of the two header name forms (6.10.2).
     -- The character sequence in an #include preprocessing directive does not start with a
-       letter (6.10.2).
+       letter (6.10.2).
     -- There are sequences of preprocessing tokens within the list of macro arguments that
-       would otherwise act as preprocessing directives (6.10.3).
+       would otherwise act as preprocessing directives (6.10.3).
     -- The result of the preprocessing operator # is not a valid character string literal
-       (6.10.3.2).
+       (6.10.3.2).
     -- The result of the preprocessing operator ## is not a valid preprocessing token
-       (6.10.3.3).
+       (6.10.3.3).
     -- The #line preprocessing directive that results after expansion does not match one of
        the two well-defined forms, or its digit sequence specifies zero or a number greater
-       than 2147483647 (6.10.4).
+       than 2147483647 (6.10.4).
     -- A non-STDC #pragma preprocessing directive that is documented as causing
-       translation failure or some other form of undefined behavior is encountered (6.10.6).
+       translation failure or some other form of undefined behavior is encountered (6.10.6).
     -- A #pragma STDC preprocessing directive does not match one of the well-defined
-       forms (6.10.6).
+       forms (6.10.6).
     -- The name of a predefined macro, or the identifier defined, is the subject of a
-       #define or #undef preprocessing directive (6.10.8).
+       #define or #undef preprocessing directive (6.10.8).
     -- An attempt is made to copy an object to an overlapping object by use of a library
        function, other than as explicitly allowed (e.g., memmove) (clause 7).
     -- A file with the same name as one of the standard headers, not provided as part of the
        implementation, is placed in any of the standard places that are searched for included
-       source files (7.1.2).
-    -- A header is included within an external declaration or definition (7.1.2).
+       source files (7.1.2).
+    -- A header is included within an external declaration or definition (7.1.2).
     -- A function, object, type, or macro that is specified as being declared or defined by
        some standard header is used before any header that declares or defines it is included
-       (7.1.2).
+       (7.1.2).
     -- A standard header is included while a macro is defined with the same name as a
-       keyword (7.1.2).
+       keyword (7.1.2).
     -- The program attempts to declare a library function itself, rather than via a standard
-       header, but the declaration does not have external linkage (7.1.2).
-    -- The program declares or defines a reserved identifier, other than as allowed by 7.1.4
-       (7.1.3).
+       header, but the declaration does not have external linkage (7.1.2).
+    -- The program declares or defines a reserved identifier, other than as allowed by 7.1.4
+       (7.1.3).
     -- The program removes the definition of a macro whose name begins with an
-       underscore and either an uppercase letter or another underscore (7.1.3).
+       underscore and either an uppercase letter or another underscore (7.1.3).
     -- An argument to a library function has an invalid value or a type not expected by a
-       function with variable number of arguments (7.1.4).
+       function with variable number of arguments (7.1.4).
     -- The pointer passed to a library function array parameter does not have a value such
-       that all address computations and object accesses are valid (7.1.4).
+       that all address computations and object accesses are valid (7.1.4).
     -- The macro definition of assert is suppressed in order to access an actual function
-       (7.2).
-    -- The argument to the assert macro does not have a scalar type (7.2).
+       (7.2).
+    -- The argument to the assert macro does not have a scalar type (7.2).
     -- The CX_LIMITED_RANGE, FENV_ACCESS, or FP_CONTRACT pragma is used in
        any context other than outside all external declarations or preceding all explicit
-       declarations and statements inside a compound statement (7.3.4, 7.6.1, 7.12.2).
+       declarations and statements inside a compound statement (7.3.4, 7.6.1, 7.12.2).
     -- The value of an argument to a character handling function is neither equal to the value
-       of EOF nor representable as an unsigned char (7.4).
+       of EOF nor representable as an unsigned char (7.4).
     -- A macro definition of errno is suppressed in order to access an actual object, or the
-       program defines an identifier with the name errno (7.5).
+       program defines an identifier with the name errno (7.5).
     -- Part of the program tests floating-point status flags, sets floating-point control modes,
        or runs under non-default mode settings, but was translated with the state for the
-       FENV_ACCESS pragma ``off'' (7.6.1).
+       FENV_ACCESS pragma ``off'' (7.6.1).
     -- The exception-mask argument for one of the functions that provide access to the
        floating-point status flags has a nonzero value not obtained by bitwise OR of the
-       floating-point exception macros (7.6.2).
+       floating-point exception macros (7.6.2).
     -- The fesetexceptflag function is used to set floating-point status flags that were
        not specified in the call to the fegetexceptflag function that provided the value
-       of the corresponding fexcept_t object (7.6.2.4).
+       of the corresponding fexcept_t object (7.6.2.4).
     -- The argument to fesetenv or feupdateenv is neither an object set by a call to
-       fegetenv or feholdexcept, nor is it an environment macro (7.6.4.3, 7.6.4.4).
+       fegetenv or feholdexcept, nor is it an environment macro (7.6.4.3, 7.6.4.4).
     -- The value of the result of an integer arithmetic or conversion function cannot be
-       represented (7.8.2.1, 7.8.2.2, 7.8.2.3, 7.8.2.4, 7.20.6.1, 7.20.6.2, 7.20.1).
+       represented (7.8.2.1, 7.8.2.2, 7.8.2.3, 7.8.2.4, 7.20.6.1, 7.20.6.2, 7.20.1).
     -- The program modifies the string pointed to by the value returned by the setlocale
-       function (7.11.1.1).
+       function (7.11.1.1).
     -- The program modifies the structure pointed to by the value returned by the
-       localeconv function (7.11.2.1).
+       localeconv function (7.11.2.1).
     -- A macro definition of math_errhandling is suppressed or the program defines
-       an identifier with the name math_errhandling (7.12).
+       an identifier with the name math_errhandling (7.12).
     -- An argument to a floating-point classification or comparison macro is not of real
-       floating type (7.12.3, 7.12.14).
+       floating type (7.12.3, 7.12.14).
     -- A macro definition of setjmp is suppressed in order to access an actual function, or
-       the program defines an external identifier with the name setjmp (7.13).
+       the program defines an external identifier with the name setjmp (7.13).
     -- An invocation of the setjmp macro occurs other than in an allowed context
-       (7.13.2.1).
-    -- The longjmp function is invoked to restore a nonexistent environment (7.13.2.1).
+       (7.13.2.1).
+    -- The longjmp function is invoked to restore a nonexistent environment (7.13.2.1).
     -- After a longjmp, there is an attempt to access the value of an object of automatic
        storage class with non-volatile-qualified type, local to the function containing the
        invocation of the corresponding setjmp macro, that was changed between the
-       setjmp invocation and longjmp call (7.13.2.1).
-    -- The program specifies an invalid pointer to a signal handler function (7.14.1.1).
+       setjmp invocation and longjmp call (7.13.2.1).
+    -- The program specifies an invalid pointer to a signal handler function (7.14.1.1).
     -- A signal handler returns when the signal corresponded to a computational exception
-       (7.14.1.1).
+       (7.14.1.1).
     -- A signal occurs as the result of calling the abort or raise function, and the signal
-       handler calls the raise function (7.14.1.1).
+       handler calls the raise function (7.14.1.1).
     -- A signal occurs other than as the result of calling the abort or raise function, and
        the signal handler refers to an object with static storage duration other than by
        assigning a value to an object declared as volatile sig_atomic_t, or calls any
        function in the standard library other than the abort function, the _Exit function,
-       or the signal function (for the same signal number) (7.14.1.1).
+       or the signal function (for the same signal number) (7.14.1.1).
     -- The value of errno is referred to after a signal occurred other than as the result of
        calling the abort or raise function and the corresponding signal handler obtained
-       a SIG_ERR return from a call to the signal function (7.14.1.1).
-    -- A signal is generated by an asynchronous signal handler (7.14.1.1).
+       a SIG_ERR return from a call to the signal function (7.14.1.1).
+    -- A signal is generated by an asynchronous signal handler (7.14.1.1).
     -- A function with a variable number of arguments attempts to access its varying
        arguments other than through a properly declared and initialized va_list object, or
-       before the va_start macro is invoked (7.15, 7.15.1.1, 7.15.1.4).
+       before the va_start macro is invoked (7.15, 7.15.1.1, 7.15.1.4).
     -- The macro va_arg is invoked using the parameter ap that was passed to a function
-       that invoked the macro va_arg with the same parameter (7.15).
+       that invoked the macro va_arg with the same parameter (7.15).
     -- A macro definition of va_start, va_arg, va_copy, or va_end is suppressed in
        order to access an actual function, or the program defines an external identifier with
-       the name va_copy or va_end (7.15.1).
+       the name va_copy or va_end (7.15.1).
     -- The va_start or va_copy macro is invoked without a corresponding invocation
-       of the va_end macro in the same function, or vice versa (7.15.1, 7.15.1.2, 7.15.1.3,
-         7.15.1.4).
+       of the va_end macro in the same function, or vice versa (7.15.1, 7.15.1.2, 7.15.1.3,
+         7.15.1.4).
     -- The type parameter to the va_arg macro is not such that a pointer to an object of
-       that type can be obtained simply by postfixing a * (7.15.1.1).
+       that type can be obtained simply by postfixing a * (7.15.1.1).
     -- The va_arg macro is invoked when there is no actual next argument, or with a
        specified type that is not compatible with the promoted type of the actual next
-       argument, with certain exceptions (7.15.1.1).
+       argument, with certain exceptions (7.15.1.1).
     -- The va_copy or va_start macro is called to initialize a va_list that was
        previously initialized by either macro without an intervening invocation of the
-       va_end macro for the same va_list (7.15.1.2, 7.15.1.4).
+       va_end macro for the same va_list (7.15.1.2, 7.15.1.4).
     -- The parameter parmN of a va_start macro is declared with the register
        storage class, with a function or array type, or with a type that is not compatible with
-       the type that results after application of the default argument promotions (7.15.1.4).
+       the type that results after application of the default argument promotions (7.15.1.4).
     -- The member designator parameter of an offsetof macro is an invalid right
-       operand of the . operator for the type parameter, or designates a bit-field (7.17).
+       operand of the . operator for the type parameter, or designates a bit-field (7.17).
     -- The argument in an instance of one of the integer-constant macros is not a decimal,
        octal, or hexadecimal constant, or it has a value that exceeds the limits for the
-       corresponding type (7.18.4).
+       corresponding type (7.18.4).
     -- A byte input/output function is applied to a wide-oriented stream, or a wide character
-       input/output function is applied to a byte-oriented stream (7.19.2).
+       input/output function is applied to a byte-oriented stream (7.19.2).
     -- Use is made of any portion of a file beyond the most recent wide character written to
-       a wide-oriented stream (7.19.2).
+       a wide-oriented stream (7.19.2).
     -- The value of a pointer to a FILE object is used after the associated file is closed
-       (7.19.3).
+       (7.19.3).
     -- The stream for the fflush function points to an input stream or to an update stream
-       in which the most recent operation was input (7.19.5.2).
+       in which the most recent operation was input (7.19.5.2).
     -- The string pointed to by the mode argument in a call to the fopen function does not
-       exactly match one of the specified character sequences (7.19.5.3).
+       exactly match one of the specified character sequences (7.19.5.3).
     -- An output operation on an update stream is followed by an input operation without an
        intervening call to the fflush function or a file positioning function, or an input
        operation on an update stream is followed by an output operation with an intervening
-       call to a file positioning function (7.19.5.3).
+       call to a file positioning function (7.19.5.3).
     -- An attempt is made to use the contents of the array that was supplied in a call to the
-       setvbuf function (7.19.5.6).
+       setvbuf function (7.19.5.6).
     -- There are insufficient arguments for the format in a call to one of the formatted
-       input/output functions, or an argument does not have an appropriate type (7.19.6.1,
-         7.19.6.2, 7.24.2.1, 7.24.2.2).
+       input/output functions, or an argument does not have an appropriate type (7.19.6.1,
+         7.19.6.2, 7.24.2.1, 7.24.2.2).
     -- The format in a call to one of the formatted input/output functions or to the
        strftime or wcsftime function is not a valid multibyte character sequence that
-       begins and ends in its initial shift state (7.19.6.1, 7.19.6.2, 7.23.3.5, 7.24.2.1, 7.24.2.2,
-         7.24.5.1).
+       begins and ends in its initial shift state (7.19.6.1, 7.19.6.2, 7.23.3.5, 7.24.2.1, 7.24.2.2,
+         7.24.5.1).
     -- In a call to one of the formatted output functions, a precision appears with a
-       conversion specifier other than those described (7.19.6.1, 7.24.2.1).
+       conversion specifier other than those described (7.19.6.1, 7.24.2.1).
     -- A conversion specification for a formatted output function uses an asterisk to denote
        an argument-supplied field width or precision, but the corresponding argument is not
-       provided (7.19.6.1, 7.24.2.1).
+       provided (7.19.6.1, 7.24.2.1).
     -- A conversion specification for a formatted output function uses a # or 0 flag with a
-       conversion specifier other than those described (7.19.6.1, 7.24.2.1).
+       conversion specifier other than those described (7.19.6.1, 7.24.2.1).
     -- A conversion specification for one of the formatted input/output functions uses a
-       length modifier with a conversion specifier other than those described (7.19.6.1,
-         7.19.6.2, 7.24.2.1, 7.24.2.2).
+       length modifier with a conversion specifier other than those described (7.19.6.1,
+         7.19.6.2, 7.24.2.1, 7.24.2.2).
     -- An s conversion specifier is encountered by one of the formatted output functions,
        and the argument is missing the null terminator (unless a precision is specified that
-       does not require null termination) (7.19.6.1, 7.24.2.1).
+       does not require null termination) (7.19.6.1, 7.24.2.1).
     -- An n conversion specification for one of the formatted input/output functions includes
-       any flags, an assignment-suppressing character, a field width, or a precision (7.19.6.1,
-         7.19.6.2, 7.24.2.1, 7.24.2.2).
+       any flags, an assignment-suppressing character, a field width, or a precision (7.19.6.1,
+         7.19.6.2, 7.24.2.1, 7.24.2.2).
     -- A % conversion specifier is encountered by one of the formatted input/output
-       functions, but the complete conversion specification is not exactly %% (7.19.6.1,
-         7.19.6.2, 7.24.2.1, 7.24.2.2).
+       functions, but the complete conversion specification is not exactly %% (7.19.6.1,
+         7.19.6.2, 7.24.2.1, 7.24.2.2).
     -- An invalid conversion specification is found in the format for one of the formatted
-       input/output functions, or the strftime or wcsftime function (7.19.6.1, 7.19.6.2,
-         7.23.3.5, 7.24.2.1, 7.24.2.2, 7.24.5.1).
+       input/output functions, or the strftime or wcsftime function (7.19.6.1, 7.19.6.2,
+         7.23.3.5, 7.24.2.1, 7.24.2.2, 7.24.5.1).
     -- The number of characters transmitted by a formatted output function is greater than
-       INT_MAX (7.19.6.1, 7.19.6.3, 7.19.6.8, 7.19.6.10).
+       INT_MAX (7.19.6.1, 7.19.6.3, 7.19.6.8, 7.19.6.10).
     -- The result of a conversion by one of the formatted input functions cannot be
        represented in the corresponding object, or the receiving object does not have an
-       appropriate type (7.19.6.2, 7.24.2.2).
+       appropriate type (7.19.6.2, 7.24.2.2).
     -- A c, s, or [ conversion specifier is encountered by one of the formatted input
        functions, and the array pointed to by the corresponding argument is not large enough
        to accept the input sequence (and a null terminator if the conversion specifier is s or
-       [) (7.19.6.2, 7.24.2.2).
+       [) (7.19.6.2, 7.24.2.2).
     -- A c, s, or [ conversion specifier with an l qualifier is encountered by one of the
        formatted input functions, but the input is not a valid multibyte character sequence
-       that begins in the initial shift state (7.19.6.2, 7.24.2.2).
+       that begins in the initial shift state (7.19.6.2, 7.24.2.2).
     -- The input item for a %p conversion by one of the formatted input functions is not a
-       value converted earlier during the same program execution (7.19.6.2, 7.24.2.2).
+       value converted earlier during the same program execution (7.19.6.2, 7.24.2.2).
     -- The vfprintf, vfscanf, vprintf, vscanf, vsnprintf, vsprintf,
        vsscanf, vfwprintf, vfwscanf, vswprintf, vswscanf, vwprintf, or
        vwscanf function is called with an improperly initialized va_list argument, or
        the argument is used (other than in an invocation of va_end) after the function
-       returns (7.19.6.8, 7.19.6.9, 7.19.6.10, 7.19.6.11, 7.19.6.12, 7.19.6.13, 7.19.6.14,
-         7.24.2.5, 7.24.2.6, 7.24.2.7, 7.24.2.8, 7.24.2.9, 7.24.2.10).
+       returns (7.19.6.8, 7.19.6.9, 7.19.6.10, 7.19.6.11, 7.19.6.12, 7.19.6.13, 7.19.6.14,
+         7.24.2.5, 7.24.2.6, 7.24.2.7, 7.24.2.8, 7.24.2.9, 7.24.2.10).
     -- The contents of the array supplied in a call to the fgets, gets, or fgetws function
-       are used after a read error occurred (7.19.7.2, 7.19.7.7, 7.24.3.2).
+       are used after a read error occurred (7.19.7.2, 7.19.7.7, 7.24.3.2).
     -- The file position indicator for a binary stream is used after a call to the ungetc
-       function where its value was zero before the call (7.19.7.11).
+       function where its value was zero before the call (7.19.7.11).
     -- The file position indicator for a stream is used after an error occurred during a call to
-       the fread or fwrite function (7.19.8.1, 7.19.8.2).
-    -- A partial element read by a call to the fread function is used (7.19.8.1).
+       the fread or fwrite function (7.19.8.1, 7.19.8.2).
+    -- A partial element read by a call to the fread function is used (7.19.8.1).
     -- The fseek function is called for a text stream with a nonzero offset and either the
        offset was not returned by a previous successful call to the ftell function on a
-       stream associated with the same file or whence is not SEEK_SET (7.19.9.2).
+       stream associated with the same file or whence is not SEEK_SET (7.19.9.2).
     -- The fsetpos function is called to set a position that was not returned by a previous
        successful call to the fgetpos function on a stream associated with the same file
-       (7.19.9.3).
+       (7.19.9.3).
     -- A non-null pointer returned by a call to the calloc, malloc, or realloc function
-       with a zero requested size is used to access an object (7.20.3).
+       with a zero requested size is used to access an object (7.20.3).
     -- The value of a pointer that refers to space deallocated by a call to the free or
-       realloc function is used (7.20.3).
+       realloc function is used (7.20.3).
     -- The pointer argument to the free or realloc function does not match a pointer
        earlier returned by calloc, malloc, or realloc, or the space has been
-       deallocated by a call to free or realloc (7.20.3.2, 7.20.3.4).
-    -- The value of the object allocated by the malloc function is used (7.20.3.3).
+       deallocated by a call to free or realloc (7.20.3.2, 7.20.3.4).
+    -- The value of the object allocated by the malloc function is used (7.20.3.3).
     -- The value of any bytes in a new object allocated by the realloc function beyond
-       the size of the old object are used (7.20.3.4).
-    -- The program executes more than one call to the exit function (7.20.4.3).
+       the size of the old object are used (7.20.3.4).
+    -- The program executes more than one call to the exit function (7.20.4.3).
     -- During the call to a function registered with the atexit function, a call is made to
        the longjmp function that would terminate the call to the registered function
-       (7.20.4.3).
+       (7.20.4.3).
     -- The string set up by the getenv or strerror function is modified by the program
-       (7.20.4.5, 7.21.6.2).
+       (7.20.4.5, 7.21.6.2).
     -- A command is executed through the system function in a way that is documented as
-       causing termination or some other form of undefined behavior (7.20.4.6).
+       causing termination or some other form of undefined behavior (7.20.4.6).
     -- A searching or sorting utility function is called with an invalid pointer argument, even
-       if the number of elements is zero (7.20.5).
+       if the number of elements is zero (7.20.5).
     -- The comparison function called by a searching or sorting utility function alters the
        contents of the array being searched or sorted, or returns ordering values
-       inconsistently (7.20.5).
+       inconsistently (7.20.5).
     -- The array being searched by the bsearch function does not have its elements in
-       proper order (7.20.5.1).
+       proper order (7.20.5.1).
     -- The current conversion state is used by a multibyte/wide character conversion
-       function after changing the LC_CTYPE category (7.20.7).
+       function after changing the LC_CTYPE category (7.20.7).
     -- A string or wide string utility function is instructed to access an array beyond the end
-       of an object (7.21.1, 7.24.4).
+       of an object (7.21.1, 7.24.4).
     -- A string or wide string utility function is called with an invalid pointer argument, even
-       if the length is zero (7.21.1, 7.24.4).
+       if the length is zero (7.21.1, 7.24.4).
     -- The contents of the destination array are used after a call to the strxfrm,
        strftime, wcsxfrm, or wcsftime function in which the specified length was
-       too small to hold the entire null-terminated result (7.21.4.5, 7.23.3.5, 7.24.4.4.4,
-         7.24.5.1).
+       too small to hold the entire null-terminated result (7.21.4.5, 7.23.3.5, 7.24.4.4.4,
+         7.24.5.1).
     -- The first argument in the very first call to the strtok or wcstok is a null pointer
-       (7.21.5.8, 7.24.4.5.7).
+       (7.21.5.8, 7.24.4.5.7).
     -- The type of an argument to a type-generic macro is not compatible with the type of
-       the corresponding parameter of the selected function (7.22).
+       the corresponding parameter of the selected function (7.22).
     -- A complex argument is supplied for a generic parameter of a type-generic macro that
-       has no corresponding complex function (7.22).
+       has no corresponding complex function (7.22).
     -- The argument corresponding to an s specifier without an l qualifier in a call to the
        fwprintf function does not point to a valid multibyte character sequence that
-       begins in the initial shift state (7.24.2.11).
+       begins in the initial shift state (7.24.2.11).
     -- In a call to the wcstok function, the object pointed to by ptr does not have the
-       value stored by the previous call for the same wide string (7.24.4.5.7).
-    -- An mbstate_t object is used inappropriately (7.24.6).
+       value stored by the previous call for the same wide string (7.24.4.5.7).
+    -- An mbstate_t object is used inappropriately (7.24.6).
     -- The value of an argument of type wint_t to a wide character classification or case
        mapping function is neither equal to the value of WEOF nor representable as a
-       wchar_t (7.25.1).
+       wchar_t (7.25.1).
     -- The iswctype function is called using a different LC_CTYPE category from the
        one in effect for the call to the wctype function that returned the description
-       (7.25.2.2.1).
+       (7.25.2.2.1).
     -- The towctrans function is called using a different LC_CTYPE category from the
        one in effect for the call to the wctrans function that returned the description
-       (7.25.3.2.1).
+       (7.25.3.2.1).
 
 

-
-
+
 

 
J.3 [Implementation-defined behavior]

-

-
-
+
 
1   A conforming implementation is required to document its choice of behavior in each of
     the areas listed in this subclause. The following are implementation-defined:
 

-
-
+
 

 
J.3.1 [Translation]

-

-
-
-
1   -- How a diagnostic is identified (3.10, 5.1.1.3).
+
+
1   -- How a diagnostic is identified (3.10, 5.1.1.3).
     -- Whether each nonempty sequence of white-space characters other than new-line is
-       retained or replaced by one space character in translation phase 3 (5.1.1.2).
+       retained or replaced by one space character in translation phase 3 (5.1.1.2).
 

-
-
+
 

 
J.3.2 [Environment]

-

-
-
+
 
1   -- The mapping between physical source file multibyte characters and the source
-       character set in translation phase 1 (5.1.1.2).
+       character set in translation phase 1 (5.1.1.2).
     -- The name and type of the function called at program startup in a freestanding
-       environment (5.1.2.1).
-    -- The effect of program termination in a freestanding environment (5.1.2.1).
-    -- An alternative manner in which the main function may be defined (5.1.2.2.1).
-    -- The values given to the strings pointed to by the argv argument to main (5.1.2.2.1).
-    -- What constitutes an interactive device (5.1.2.3).
-    -- The set of signals, their semantics, and their default handling (7.14).
+       environment (5.1.2.1).
+    -- The effect of program termination in a freestanding environment (5.1.2.1).
+    -- An alternative manner in which the main function may be defined (5.1.2.2.1).
+    -- The values given to the strings pointed to by the argv argument to main (5.1.2.2.1).
+    -- What constitutes an interactive device (5.1.2.3).
+    -- The set of signals, their semantics, and their default handling (7.14).
     -- Signal values other than SIGFPE, SIGILL, and SIGSEGV that correspond to a
-       computational exception (7.14.1.1).
+       computational exception (7.14.1.1).
     -- Signals for which the equivalent of signal(sig, SIG_IGN); is executed at
-       program startup (7.14.1.1).
+       program startup (7.14.1.1).
     -- The set of environment names and the method for altering the environment list used
-       by the getenv function (7.20.4.5).
-    -- The manner of execution of the string by the system function (7.20.4.6).
+       by the getenv function (7.20.4.5).
+    -- The manner of execution of the string by the system function (7.20.4.6).
 

-
-
+
 

 
J.3.3 [Identifiers]

-

-
-
+
 
1   -- Which additional multibyte characters may appear in identifiers and their
-       correspondence to universal character names (6.4.2).
-    -- The number of significant initial characters in an identifier (5.2.4.1, 6.4.2).
+       correspondence to universal character names (6.4.2).
+    -- The number of significant initial characters in an identifier (5.2.4.1, 6.4.2).
 
 

-
-
+
 

 
J.3.4 [Characters]

-

-
-
-
1   -- The number of bits in a byte (3.6).
-    -- The values of the members of the execution character set (5.2.1).
+
+
1   -- The number of bits in a byte (3.6).
+    -- The values of the members of the execution character set (5.2.1).
     -- The unique value of the member of the execution character set produced for each of
-       the standard alphabetic escape sequences (5.2.2).
+       the standard alphabetic escape sequences (5.2.2).
     -- The value of a char object into which has been stored any character other than a
-       member of the basic execution character set (6.2.5).
+       member of the basic execution character set (6.2.5).
     -- Which of signed char or unsigned char has the same range, representation,
-       and behavior as ``plain'' char (6.2.5, 6.3.1.1).
+       and behavior as ``plain'' char (6.2.5, 6.3.1.1).
     -- The mapping of members of the source character set (in character constants and string
-       literals) to members of the execution character set (6.4.4.4, 5.1.1.2).
+       literals) to members of the execution character set (6.4.4.4, 5.1.1.2).
     -- The value of an integer character constant containing more than one character or
        containing a character or escape sequence that does not map to a single-byte
-       execution character (6.4.4.4).
+       execution character (6.4.4.4).
     -- The value of a wide character constant containing more than one multibyte character,
        or containing a multibyte character or escape sequence not represented in the
-       extended execution character set (6.4.4.4).
+       extended execution character set (6.4.4.4).
     -- The current locale used to convert a wide character constant consisting of a single
        multibyte character that maps to a member of the extended execution character set
-       into a corresponding wide character code (6.4.4.4).
+       into a corresponding wide character code (6.4.4.4).
     -- The current locale used to convert a wide string literal into corresponding wide
-       character codes (6.4.5).
+       character codes (6.4.5).
     -- The value of a string literal containing a multibyte character or escape sequence not
-       represented in the execution character set (6.4.5).
+       represented in the execution character set (6.4.5).
 

-
-
+
 

 
J.3.5 [Integers]

-

-
-
-
1   -- Any extended integer types that exist in the implementation (6.2.5).
+
+
1   -- Any extended integer types that exist in the implementation (6.2.5).
     -- Whether signed integer types are represented using sign and magnitude, two's
        complement, or ones' complement, and whether the extraordinary value is a trap
-       representation or an ordinary value (6.2.6.2).
+       representation or an ordinary value (6.2.6.2).
     -- The rank of any extended integer type relative to another extended integer type with
-       the same precision (6.3.1.1).
+       the same precision (6.3.1.1).
     -- The result of, or the signal raised by, converting an integer to a signed integer type
-       when the value cannot be represented in an object of that type (6.3.1.3).
-    -- The results of some bitwise operations on signed integers (6.5).
+       when the value cannot be represented in an object of that type (6.3.1.3).
+    -- The results of some bitwise operations on signed integers (6.5).
 

-
-
+
 

 
J.3.6 [Floating point]

-

-
-
+
 
1   -- The accuracy of the floating-point operations and of the library functions in
-       <math.h> and <complex.h> that return floating-point results (5.2.4.2.2).
+       <math.h> and <complex.h> that return floating-point results (5.2.4.2.2).
     -- The accuracy of the conversions between floating-point internal representations and
        string representations performed by the library functions in <stdio.h>,
-       <stdlib.h>, and <wchar.h> (5.2.4.2.2).
+       <stdlib.h>, and <wchar.h> (5.2.4.2.2).
     -- The rounding behaviors characterized by non-standard values of FLT_ROUNDS
-       (5.2.4.2.2).
+       (5.2.4.2.2).
     -- The evaluation methods characterized by non-standard negative values of
-       FLT_EVAL_METHOD (5.2.4.2.2).
+       FLT_EVAL_METHOD (5.2.4.2.2).
     -- The direction of rounding when an integer is converted to a floating-point number that
-       cannot exactly represent the original value (6.3.1.4).
+       cannot exactly represent the original value (6.3.1.4).
     -- The direction of rounding when a floating-point number is converted to a narrower
-       floating-point number (6.3.1.5).
+       floating-point number (6.3.1.5).
     -- How the nearest representable value or the larger or smaller representable value
        immediately adjacent to the nearest representable value is chosen for certain floating
-       constants (6.4.4.2).
+       constants (6.4.4.2).
     -- Whether and how floating expressions are contracted when not disallowed by the
-       FP_CONTRACT pragma (6.5).
-    -- The default state for the FENV_ACCESS pragma (7.6.1).
+       FP_CONTRACT pragma (6.5).
+    -- The default state for the FENV_ACCESS pragma (7.6.1).
     -- Additional floating-point exceptions, rounding            modes,    environments,   and
-       classifications, and their macro names (7.6, 7.12).
-    -- The default state for the FP_CONTRACT pragma (7.12.2).                                    
+       classifications, and their macro names (7.6, 7.12).
+    -- The default state for the FP_CONTRACT pragma (7.12.2).
 

-
-
+
 

 
J.3.7 [Arrays and pointers]

-

-
-
-
1   -- The result of converting a pointer to an integer or vice versa (6.3.2.3).
+
+
1   -- The result of converting a pointer to an integer or vice versa (6.3.2.3).
     -- The size of the result of subtracting two pointers to elements of the same array
-       (6.5.6).
+       (6.5.6).
 
 

-
-
+
 

 
J.3.8 [Hints]

-

-
-
+
 
1   -- The extent to which suggestions made by using the register storage-class
-       specifier are effective (6.7.1).
+       specifier are effective (6.7.1).
     -- The extent to which suggestions made by using the inline function specifier are
-       effective (6.7.4).
+       effective (6.7.4).
 

-
-
+
 

 
J.3.9 [Structures, unions, enumerations, and bit-fields]

-

-
-
+
 
1   -- Whether a ``plain'' int bit-field is treated as a signed int bit-field or as an
-       unsigned int bit-field (6.7.2, 6.7.2.1).
+       unsigned int bit-field (6.7.2, 6.7.2.1).
     -- Allowable bit-field types other than _Bool, signed int, and unsigned int
-       (6.7.2.1).
-    -- Whether a bit-field can straddle a storage-unit boundary (6.7.2.1).
-    -- The order of allocation of bit-fields within a unit (6.7.2.1).
-    -- The alignment of non-bit-field members of structures (6.7.2.1). This should present
+       (6.7.2.1).
+    -- Whether a bit-field can straddle a storage-unit boundary (6.7.2.1).
+    -- The order of allocation of bit-fields within a unit (6.7.2.1).
+    -- The alignment of non-bit-field members of structures (6.7.2.1). This should present
        no problem unless binary data written by one implementation is read by another.
-    -- The integer type compatible with each enumerated type (6.7.2.2).
+    -- The integer type compatible with each enumerated type (6.7.2.2).
 

-
-
+
 

 
J.3.10 [Qualifiers]

-

-
-
-
1   -- What constitutes an access to an object that has volatile-qualified type (6.7.3).
+
+
1   -- What constitutes an access to an object that has volatile-qualified type (6.7.3).
 

-
-
+
 

 
J.3.11 [Preprocessing directives]

-

-
-
+
 
1   -- The locations within #pragma directives where header name preprocessing tokens
-       are recognized (6.4, 6.4.7).
+       are recognized (6.4, 6.4.7).
     -- How sequences in both forms of header names are mapped to headers or external
-       source file names (6.4.7).
+       source file names (6.4.7).
     -- Whether the value of a character constant in a constant expression that controls
        conditional inclusion matches the value of the same character constant in the
-       execution character set (6.10.1).
+       execution character set (6.10.1).
     -- Whether the value of a single-character character constant in a constant expression
-       that controls conditional inclusion may have a negative value (6.10.1).
+       that controls conditional inclusion may have a negative value (6.10.1).
     -- The places that are searched for an included < > delimited header, and how the places
-       are specified or the header is identified (6.10.2).
+       are specified or the header is identified (6.10.2).
     -- How the named source file is searched for in an included " " delimited header
-       (6.10.2).
+       (6.10.2).
     -- The method by which preprocessing tokens (possibly resulting from macro
-       expansion) in a #include directive are combined into a header name (6.10.2).
-    -- The nesting limit for #include processing (6.10.2).
+       expansion) in a #include directive are combined into a header name (6.10.2).
+    -- The nesting limit for #include processing (6.10.2).
     -- Whether the # operator inserts a \ character before the \ character that begins a
-       universal character name in a character constant or string literal (6.10.3.2).
-    -- The behavior on each recognized non-STDC #pragma directive (6.10.6).
+       universal character name in a character constant or string literal (6.10.3.2).
+    -- The behavior on each recognized non-STDC #pragma directive (6.10.6).
     -- The definitions for _ _DATE_ _ and _ _TIME_ _ when respectively, the date and
-       time of translation are not available (6.10.8).
+       time of translation are not available (6.10.8).
 

-
-
+
 

 
J.3.12 [Library functions]

-

-
-
+
 
1   -- Any library facilities available to a freestanding program, other than the minimal set
-       required by clause 4 (5.1.2.1).
-    -- The format of the diagnostic printed by the assert macro (7.2.1.1).
+       required by clause 4 (5.1.2.1).
+    -- The format of the diagnostic printed by the assert macro (7.2.1.1).
     -- The representation of the floating-point              status   flags     stored   by   the
-       fegetexceptflag function (7.6.2.2).
+       fegetexceptflag function (7.6.2.2).
     -- Whether the feraiseexcept function raises the ``inexact'' floating-point
        exception in addition to the ``overflow'' or ``underflow'' floating-point exception
-       (7.6.2.3).
+       (7.6.2.3).
     -- Strings other than "C" and "" that may be passed as the second argument to the
-       setlocale function (7.11.1.1).
+       setlocale function (7.11.1.1).
     -- The types defined for float_t and double_t when the value of the
-       FLT_EVAL_METHOD macro is less than 0 (7.12).
+       FLT_EVAL_METHOD macro is less than 0 (7.12).
     -- Domain errors for the mathematics functions, other than those required by this
-       International Standard (7.12.1).
-    -- The values returned by the mathematics functions on domain errors (7.12.1).
+       International Standard (7.12.1).
+    -- The values returned by the mathematics functions on domain errors (7.12.1).
     -- The values returned by the mathematics functions on underflow range errors, whether
        errno is set to the value of the macro ERANGE when the integer expression
        math_errhandling & MATH_ERRNO is nonzero, and whether the ``underflow''
        floating-point exception is raised when the integer expression math_errhandling
-       & MATH_ERREXCEPT is nonzero. (7.12.1).
+       & MATH_ERREXCEPT is nonzero. (7.12.1).
     -- Whether a domain error occurs or zero is returned when an fmod function has a
-       second argument of zero (7.12.10.1).
+       second argument of zero (7.12.10.1).
     -- Whether a domain error occurs or zero is returned when a remainder function has
-       a second argument of zero (7.12.10.2).
+       a second argument of zero (7.12.10.2).
     -- The base-2 logarithm of the modulus used by the remquo functions in reducing the
-       quotient (7.12.10.3).
+       quotient (7.12.10.3).
     -- Whether a domain error occurs or zero is returned when a remquo function has a
-       second argument of zero (7.12.10.3).
+       second argument of zero (7.12.10.3).
     -- Whether the equivalent of signal(sig, SIG_DFL); is executed prior to the call
-       of a signal handler, and, if not, the blocking of signals that is performed (7.14.1.1).
-    -- The null pointer constant to which the macro NULL expands (7.17).
+       of a signal handler, and, if not, the blocking of signals that is performed (7.14.1.1).
+    -- The null pointer constant to which the macro NULL expands (7.17).
     -- Whether the last line of a text stream requires a terminating new-line character
-       (7.19.2).
+       (7.19.2).
     -- Whether space characters that are written out to a text stream immediately before a
-       new-line character appear when read in (7.19.2).
+       new-line character appear when read in (7.19.2).
     -- The number of null characters that may be appended to data written to a binary
-       stream (7.19.2).
+       stream (7.19.2).
     -- Whether the file position indicator of an append-mode stream is initially positioned at
-       the beginning or end of the file (7.19.3).
+       the beginning or end of the file (7.19.3).
     -- Whether a write on a text stream causes the associated file to be truncated beyond that
-       point (7.19.3).
-    -- The characteristics of file buffering (7.19.3).
-    -- Whether a zero-length file actually exists (7.19.3).
-    -- The rules for composing valid file names (7.19.3).
-    -- Whether the same file can be simultaneously open multiple times (7.19.3).
-    -- The nature and choice of encodings used for multibyte characters in files (7.19.3).
-    -- The effect of the remove function on an open file (7.19.4.1).
+       point (7.19.3).
+    -- The characteristics of file buffering (7.19.3).
+    -- Whether a zero-length file actually exists (7.19.3).
+    -- The rules for composing valid file names (7.19.3).
+    -- Whether the same file can be simultaneously open multiple times (7.19.3).
+    -- The nature and choice of encodings used for multibyte characters in files (7.19.3).
+    -- The effect of the remove function on an open file (7.19.4.1).
     -- The effect if a file with the new name exists prior to a call to the rename function
-       (7.19.4.2).
+       (7.19.4.2).
     -- Whether an open temporary file is removed upon abnormal program termination
-       (7.19.4.3).
+       (7.19.4.3).
     -- Which changes of mode are permitted (if any), and under what circumstances
-       (7.19.5.4).
+       (7.19.5.4).
     -- The style used to print an infinity or NaN, and the meaning of any n-char or n-wchar
-       sequence printed for a NaN (7.19.6.1, 7.24.2.1).
-    -- The output for %p conversion in the fprintf or fwprintf function (7.19.6.1,
-       7.24.2.1).
+       sequence printed for a NaN (7.19.6.1, 7.24.2.1).
+    -- The output for %p conversion in the fprintf or fwprintf function (7.19.6.1,
+       7.24.2.1).
     -- The interpretation of a - character that is neither the first nor the last character, nor
         the second where a ^ character is the first, in the scanlist for %[ conversion in the
-        fscanf or fwscanf function (7.19.6.2, 7.24.2.1).
+        fscanf or fwscanf function (7.19.6.2, 7.24.2.1).
     -- The set of sequences matched by a %p conversion and the interpretation of the
-       corresponding input item in the fscanf or fwscanf function (7.19.6.2, 7.24.2.2).
+       corresponding input item in the fscanf or fwscanf function (7.19.6.2, 7.24.2.2).
     -- The value to which the macro errno is set by the fgetpos, fsetpos, or ftell
-       functions on failure (7.19.9.1, 7.19.9.3, 7.19.9.4).
+       functions on failure (7.19.9.1, 7.19.9.3, 7.19.9.4).
     -- The meaning of any n-char or n-wchar sequence in a string representing a NaN that is
        converted by the strtod, strtof, strtold, wcstod, wcstof, or wcstold
-       function (7.20.1.3, 7.24.4.1.1).
+       function (7.20.1.3, 7.24.4.1.1).
     -- Whether or not the strtod, strtof, strtold, wcstod, wcstof, or wcstold
-       function sets errno to ERANGE when underflow occurs (7.20.1.3, 7.24.4.1.1).
+       function sets errno to ERANGE when underflow occurs (7.20.1.3, 7.24.4.1.1).
     -- Whether the calloc, malloc, and realloc functions return a null pointer or a
-       pointer to an allocated object when the size requested is zero (7.20.3).
+       pointer to an allocated object when the size requested is zero (7.20.3).
     -- Whether open streams with unwritten buffered data are flushed, open streams are
        closed, or temporary files are removed when the abort or _Exit function is called
-       (7.20.4.1, 7.20.4.4).
+       (7.20.4.1, 7.20.4.4).
     -- The termination status returned to the host environment by the abort, exit, or
-       _Exit function (7.20.4.1, 7.20.4.3, 7.20.4.4).
+       _Exit function (7.20.4.1, 7.20.4.3, 7.20.4.4).
     -- The value returned by the system function when its argument is not a null pointer
-       (7.20.4.6).
-    -- The local time zone and Daylight Saving Time (7.23.1).
-    -- The range and precision of times representable in clock_t and time_t (7.23).
-    -- The era for the clock function (7.23.2.1).
+       (7.20.4.6).
+    -- The local time zone and Daylight Saving Time (7.23.1).
+    -- The range and precision of times representable in clock_t and time_t (7.23).
+    -- The era for the clock function (7.23.2.1).
     -- The replacement string for the %Z specifier to the strftime, and wcsftime
-       functions in the "C" locale (7.23.3.5, 7.24.5.1).
+       functions in the "C" locale (7.23.3.5, 7.24.5.1).
     -- Whether the functions in <math.h> honor the rounding direction mode in an
-       IEC 60559 conformant implementation, unless explicitly specified otherwise (F.9).
+       IEC 60559 conformant implementation, unless explicitly specified otherwise (F.9).
 

-
-
+
 

 
J.3.13 [Architecture]

-

-
-
+
 
1   -- The values or expressions assigned to the macros specified in the headers
-       <float.h>, <limits.h>, and <stdint.h> (5.2.4.2, 7.18.2, 7.18.3).
+       <float.h>, <limits.h>, and <stdint.h> (5.2.4.2, 7.18.2, 7.18.3).
     -- The number, order, and encoding of bytes in any object (when not explicitly specified
-       in this International Standard) (6.2.6.1).
-    -- The value of the result of the sizeof operator (6.5.3.4).
+       in this International Standard) (6.2.6.1).
+    -- The value of the result of the sizeof operator (6.5.3.4).
 
 

-
-
+
 

 
J.4 [Locale-specific behavior]

-

-
-
+
 
1   The following characteristics of a hosted environment are locale-specific and are required
     to be documented by the implementation:
     -- Additional members of the source and execution character sets beyond the basic
-       character set (5.2.1).
+       character set (5.2.1).
     -- The presence, meaning, and representation of additional multibyte characters in the
-       execution character set beyond the basic character set (5.2.1.2).
-    -- The shift states used for the encoding of multibyte characters (5.2.1.2).
-    -- The direction of writing of successive printing characters (5.2.2).
-    -- The decimal-point character (7.1.1).
-    -- The set of printing characters (7.4, 7.25.2).
-    -- The set of control characters (7.4, 7.25.2).
+       execution character set beyond the basic character set (5.2.1.2).
+    -- The shift states used for the encoding of multibyte characters (5.2.1.2).
+    -- The direction of writing of successive printing characters (5.2.2).
+    -- The decimal-point character (7.1.1).
+    -- The set of printing characters (7.4, 7.25.2).
+    -- The set of control characters (7.4, 7.25.2).
     -- The sets of characters tested for by the isalpha, isblank, islower, ispunct,
        isspace, isupper, iswalpha, iswblank, iswlower, iswpunct,
-       iswspace, or iswupper functions (7.4.1.2, 7.4.1.3, 7.4.1.7, 7.4.1.9, 7.4.1.10,
-       7.4.1.11, 7.25.2.1.2, 7.25.2.1.3, 7.25.2.1.7, 7.25.2.1.9, 7.25.2.1.10, 7.25.2.1.11).
-    -- The native environment (7.11.1.1).
-    -- Additional subject sequences accepted by the numeric conversion functions (7.20.1,
-       7.24.4.1).
-    -- The collation sequence of the execution character set (7.21.4.3, 7.24.4.4.2).
+       iswspace, or iswupper functions (7.4.1.2, 7.4.1.3, 7.4.1.7, 7.4.1.9, 7.4.1.10,
+       7.4.1.11, 7.25.2.1.2, 7.25.2.1.3, 7.25.2.1.7, 7.25.2.1.9, 7.25.2.1.10, 7.25.2.1.11).
+    -- The native environment (7.11.1.1).
+    -- Additional subject sequences accepted by the numeric conversion functions (7.20.1,
+       7.24.4.1).
+    -- The collation sequence of the execution character set (7.21.4.3, 7.24.4.4.2).
     -- The contents of the error message strings set up by the strerror function
-       (7.21.6.2).
-    -- The formats for time and date (7.23.3.5, 7.24.5.1).
-    -- Character mappings that are supported by the towctrans function (7.25.1).
-    -- Character classifications that are supported by the iswctype function (7.25.1).
+       (7.21.6.2).
+    -- The formats for time and date (7.23.3.5, 7.24.5.1).
+    -- Character mappings that are supported by the towctrans function (7.25.1).
+    -- Character classifications that are supported by the iswctype function (7.25.1).
 
 

-
-
+
 

 
J.5 [Common extensions]

-

-
-
+
 
1   The following extensions are widely used in many systems, but are not portable to all
     implementations. The inclusion of any extension that may cause a strictly conforming
     program to become invalid renders an implementation nonconforming. Examples of such
     extensions are new keywords, extra library functions declared in standard headers, or
     predefined macros with names that do not begin with an underscore.
 

-
-
+
 

 
J.5.1 [Environment arguments]

-

-
-
+
 
1   In a hosted environment, the main function receives a third argument, char *envp[],
     that points to a null-terminated array of pointers to char, each of which points to a string
     that provides information about the environment for this execution of the program
-    (5.1.2.2.1).
+    (5.1.2.2.1).
 

-
-
+
 

 
J.5.2 [Specialized identifiers]

-

-
-
+
 
1   Characters other than the underscore _, letters, and digits, that are not part of the basic
     source character set (such as the dollar sign $, or characters in national character sets)
-    may appear in an identifier (6.4.2).
+    may appear in an identifier (6.4.2).
 

-
-
+
 

 
J.5.3 [Lengths and cases of identifiers]

-

-
-
-
1   All characters in identifiers (with or without external linkage) are significant (6.4.2).
+
+
1   All characters in identifiers (with or without external linkage) are significant (6.4.2).
 

-
-
+
 

 
J.5.4 [Scopes of identifiers]

-

-
-
+
 
1   A function identifier, or the identifier of an object the declaration of which contains the
-    keyword extern, has file scope (6.2.1).
+    keyword extern, has file scope (6.2.1).
 

-
-
+
 

 
J.5.5 [Writable string literals]

-

-
-
+
 
1   String literals are modifiable (in which case, identical string literals should denote distinct
-    objects) (6.4.5).
+    objects) (6.4.5).
 

-
-
+
 

 
J.5.6 [Other arithmetic types]

-

-
-
+
 
1   Additional arithmetic types, such as _ _int128 or double double, and their
-    appropriate conversions are defined (6.2.5, 6.3.1). Additional floating types may have
+    appropriate conversions are defined (6.2.5, 6.3.1). Additional floating types may have
     more range or precision than long double, may be used for evaluating expressions of
     other floating types, and may be used to define float_t or double_t.
 
 

-
-
+
 

 
J.5.7 [Function pointer casts]

-

-
-
+
 
1   A pointer to an object or to void may be cast to a pointer to a function, allowing data to
-    be invoked as a function (6.5.4).
+    be invoked as a function (6.5.4).
 

-
-
+
 
2   A pointer to a function may be cast to a pointer to an object or to void, allowing a
-    function to be inspected or modified (for example, by a debugger) (6.5.4).
+    function to be inspected or modified (for example, by a debugger) (6.5.4).
 

-
-
+
 

 
J.5.8 [Extended bit-field types]

-

-
-
+
 
1   A bit-field may be declared with a type other than _Bool, unsigned int, or
-    signed int, with an appropriate maximum width (6.7.2.1).
+    signed int, with an appropriate maximum width (6.7.2.1).
 

-
-
+
 

 
J.5.9 [The fortran keyword]

-

-
-
+
 
1   The fortran function specifier may be used in a function declaration to indicate that
     calls suitable for FORTRAN should be generated, or that a different representation for the
-    external name is to be generated (6.7.4).
+    external name is to be generated (6.7.4).
 

-
-
+
 

 
J.5.10 [The asm keyword]

-

-
-
+
 
1   The asm keyword may be used to insert assembly language directly into the translator
-    output (6.8). The most common implementation is via a statement of the form:
+    output (6.8). The most common implementation is via a statement of the form:
            asm ( character-string-literal );
 

-
-
+
 

 
J.5.11 [Multiple external definitions]

-

-
-
+
 
1   There may be more than one external definition for the identifier of an object, with or
     without the explicit use of the keyword extern; if the definitions disagree, or more than
-    one is initialized, the behavior is undefined (6.9.2).
+    one is initialized, the behavior is undefined (6.9.2).
 

-
-
+
 

 
J.5.12 [Predefined macro names]

-

-
-
+
 
1   Macro names that do not begin with an underscore, describing the translation and
     execution environments, are defined by the implementation before translation begins
-    (6.10.8).
+    (6.10.8).
 

-
-
+
 

 
J.5.13 [Floating-point status flags]

-

-
-
+
 
1   If any floating-point status flags are set on normal termination after all calls to functions
-    registered by the atexit function have been made (see 7.20.4.3), the implementation
+    registered by the atexit function have been made (see 7.20.4.3), the implementation
     writes some diagnostics indicating the fact to the stderr stream, if it is still open,
 
 

-
-
+
 

 
J.5.14 [Extra arguments for signal handlers]

-

-
-
+
 
1   Handlers for specific signals are called with extra arguments in addition to the signal
-    number (7.14.1.1).
+    number (7.14.1.1).
 

-
-
+
 

 
J.5.15 [Additional stream types and file-opening modes]

-

-
-
-
1   Additional mappings from files to streams are supported (7.19.2).
+
+
1   Additional mappings from files to streams are supported (7.19.2).
 

-
-
+
 
2   Additional file-opening modes may be specified by characters appended to the mode
-    argument of the fopen function (7.19.5.3).
+    argument of the fopen function (7.19.5.3).
 

-
-
+
 

 
J.5.16 [Defined file position indicator]

-

-
-
+
 
1   The file position indicator is decremented by each successful call to the ungetc or
-    ungetwc function for a text stream, except if its value was zero before a call (7.19.7.11, 7.24.3.10).
+    ungetwc function for a text stream, except if its value was zero before a call (7.19.7.11, 7.24.3.10).
 

-
-
+
 

 
J.5.17 [Math error reporting]

-

-
-
+
 
1   Functions declared in <complex.h> and <math.h> raise SIGFPE to report errors
-    instead of, or in addition to, setting errno or raising floating-point exceptions (7.3, 7.12).
+    instead of, or in addition to, setting errno or raising floating-point exceptions (7.3, 7.12).
 

-
-
-

-
BIBLIOGRAPHY. [Bibliography]

-
                                        Bibliography
-          1.   ``The C Reference Manual'' by Dennis M. Ritchie, a version of which was
-               published in The C Programming Language by Brian W. Kernighan and Dennis
-               M. Ritchie, Prentice-Hall, Inc., (1978). Copyright owned by AT&T.
-          2.   1984 /usr/group Standard by the /usr/group Standards Committee, Santa Clara,
-               California, USA, November 1984.
-          3.   ANSI X3/TR-1-82 (1982), American National Dictionary for Information
-               Processing Systems, Information Processing Systems Technical Report.
-          4.   ANSI/IEEE 754-1985, American National Standard for Binary Floating-Point
-               Arithmetic .
-          5.   ANSI/IEEE 854-1988, American National Standard for Radix-Independent
-               Floating-Point Arithmetic .
-          6.   IEC 60559:1989, Binary floating-point arithmetic for microprocessor systems,
-               second edition (previously designated IEC 559:1989).
-          7.   ISO 31-11:1992, Quantities and units -- Part 11: Mathematical signs and
-               symbols for use in the physical sciences and technology .
-          8.   ISO/IEC 646:1991, Information technology -- ISO 7-bit coded character set for
-               information interchange.
-          9.   ISO/IEC 2382-1:1993, Information technology -- Vocabulary -- Part 1:
-               Fundamental terms.
-         10.   ISO 4217:1995, Codes for the representation of currencies and funds.
-         11.   ISO 8601:1988, Data elements and interchange formats -- Information
-               interchange -- Representation of dates and times.
-         12.   ISO/IEC 9899:1990, Programming languages -- C .
-         13.   ISO/IEC 9899/COR1:1994, Technical Corrigendum 1.
-         14.   ISO/IEC 9899/COR2:1996, Technical Corrigendum 2.
-         15.   ISO/IEC 9899/AMD1:1995, Amendment 1 to ISO/IEC 9899:1990 C Integrity .
-         16.   ISO/IEC 9945-2:1993, Information technology -- Portable Operating System
-               Interface (POSIX) -- Part 2: Shell and Utilities.
-         17.   ISO/IEC TR 10176:1998, Information technology -- Guidelines for the
-               preparation of programming language standards.
-         18.   ISO/IEC 10646-1:1993, Information technology -- Universal Multiple-Octet
-               Coded Character Set (UCS) -- Part 1: Architecture and Basic Multilingual Plane.
-         19.   ISO/IEC 10646-1/COR1:1996,      Technical       Corrigendum      1      to
-               ISO/IEC 10646-1:1993.
-         20.   ISO/IEC 10646-1/COR2:1998,      Technical       Corrigendum      2      to
-               ISO/IEC 10646-1:1993.
-         21.   ISO/IEC 10646-1/AMD1:1996, Amendment 1 to ISO/IEC 10646-1:1993
-               Transformation Format for 16 planes of group 00 (UTF-16).
-         22.   ISO/IEC 10646-1/AMD2:1996, Amendment 2 to ISO/IEC 10646-1:1993 UCS
-               Transformation Format 8 (UTF-8).
-         23.   ISO/IEC 10646-1/AMD3:1996, Amendment 3 to ISO/IEC 10646-1:1993.
-         24.   ISO/IEC 10646-1/AMD4:1996, Amendment 4 to ISO/IEC 10646-1:1993.
-         25.   ISO/IEC 10646-1/AMD5:1998, Amendment 5 to ISO/IEC 10646-1:1993 Hangul
-               syllables.
-         26.   ISO/IEC 10646-1/AMD6:1997, Amendment 6 to ISO/IEC 10646-1:1993 Tibetan.
-         27.   ISO/IEC 10646-1/AMD7:1997, Amendment 7 to ISO/IEC 10646-1:1993 33
-               additional characters.
-         28.   ISO/IEC 10646-1/AMD8:1997, Amendment 8 to ISO/IEC 10646-1:1993.
-         29.   ISO/IEC 10646-1/AMD9:1997,    Amendment     9   to    ISO/IEC 10646-1:1993
-               Identifiers for characters.
-         30.   ISO/IEC 10646-1/AMD10:1998, Amendment 10 to ISO/IEC 10646-1:1993
-               Ethiopic .
-         31.   ISO/IEC 10646-1/AMD11:1998, Amendment 11 to ISO/IEC 10646-1:1993
-               Unified Canadian Aboriginal Syllabics.
-         32.   ISO/IEC 10646-1/AMD12:1998, Amendment 12 to ISO/IEC 10646-1:1993
-               Cherokee.
-         33.   ISO/IEC 10967-1:1994, Information technology -- Language independent
-               arithmetic -- Part 1: Integer and floating point arithmetic .
-

-
 
 
 
diff --git a/applets/n1570.html b/applets/n1570.html
index ad088283..54c88bff 100644
--- a/applets/n1570.html
+++ b/applets/n1570.html
@@ -1,12 +1,10 @@
 
 
-  
ISO/IEC 9899:201x Committee Draft April 12, 2011 N1570

-
+
ISO/IEC 9899:201x Committee Draft April 12, 2011 N1570

+
 

 
FOREWORD. [Foreword]

-

-
-
+
 
1   ISO (the International Organization for Standardization) and IEC (the International
     Electrotechnical Commission) form the specialized system for worldwide
     standardization. National bodies that are member of ISO or IEC participate in the
@@ -16,27 +14,23 @@
     organizations, governmental and non-governmental, in liaison with ISO and IEC, also
     take part in the work.
 

-
-
+
 
2   International Standards are drafted in accordance with the rules given in the ISO/IEC
     Directives, Part 2. This International Standard was drafted in accordance with the fifth
     edition (2004).
 

-
-
+
 
3   In the field of information technology, ISO and IEC have established a joint technical
     committee, ISO/IEC JTC 1. Draft International Standards adopted by the joint technical
     committee are circulated to national bodies for voting. Publication as an International
     Standard requires approval by at least 75% of the national bodies casting a vote.
 

-
-
+
 
4   Attention is drawn to the possibility that some of the elements of this document may be
     the subject of patent rights. ISO and IEC shall not be held responsible for identifying any
     or all such patent rights.
 

-
-
+
 
5   This International Standard was prepared by Joint Technical Committee ISO/IEC JTC 1,
     Information technology , Subcommittee SC 22, Programming languages, their
     environments and system software interfaces. The Working Group responsible for this
@@ -45,8 +39,7 @@
     standard such as a Rationale for many of the decisions made during its preparation and a
     log of Defect Reports and Responses.
 

-
-
+
 
6   This third edition cancels and replaces the second edition, ISO/IEC 9899:1999, as
     corrected by ISO/IEC 9899:1999/Cor 1:2001, ISO/IEC 9899:1999/Cor 2:2004, and
     ISO/IEC 9899:1999/Cor 3:2007. Major changes from the previous edition include:
@@ -71,8 +64,7 @@
        ISO/IEC TR 24731-1:2007)
     -- (conditional) support for analyzability
 

-
-
+
 
7   Major changes in the second edition included:
     -- restricted character set support via digraphs and <iso646.h> (originally specified
        in AMD1)
@@ -133,42 +125,35 @@
     -- return without expression not permitted in function that returns a value (and vice
        versa)
 

-
-
+
 
8   Annexes D, F, G, K, and L form a normative part of this standard; annexes A, B, C, E, H,
     I, J, the bibliography, and the index are for information only. In accordance with Part 2 of
     the ISO/IEC Directives, this foreword, the introduction, notes, footnotes, and examples
     are also for information only.
 

-
-
+
 

 
INTRODUCTION. [Introduction]

-

-
-
+
 
1   With the introduction of new devices and extended character sets, new features may be
     added to this International Standard. Subclauses in the language and library clauses warn
     implementors and programmers of usages which, though valid in themselves, may
     conflict with future additions.
 

-
-
+
 
2   Certain features are obsolescent , which means that they may be considered for
     withdrawal in future revisions of this International Standard. They are retained because
     of their widespread use, but their use in new implementations (for implementation
-    features) or new programs (for language [6.11] or library features [7.31]) is discouraged.
+    features) or new programs (for language [6.11] or library features [7.31]) is discouraged.
 

-
-
+
 
3   This International Standard is divided into four major subdivisions:
     -- preliminary elements (clauses 1-4);
     -- the characteristics of environments that translate and execute C programs (clause 5);
     -- the language syntax, constraints, and semantics (clause 6);
     -- the library facilities (clause 7).
 

-
-
+
 
4   Examples are provided to illustrate possible forms of the constructions described.
     Footnotes are provided to emphasize consequences of the rules described in that
     subclause or elsewhere in this International Standard. References are used to refer to
@@ -177,27 +162,22 @@
     contained in this International Standard. A bibliography lists documents that were
     referred to during the preparation of the standard.
 

-
-
+
 
5   The language clause (clause 6) is derived from ``The C Reference Manual''.
 

-
-
+
 
6   The library clause (clause 7) is based on the 1984 /usr/group Standard .
 xviii                         Introduction
-    INTERNATIONAL STANDARD                                ©ISO/IEC                 ISO/IEC 9899:201x
+    INTERNATIONAL STANDARD                                \xA9ISO/IEC                 ISO/IEC 9899:201x
     Programming languages -- C
 
 

-
-
+
 

 
1. [Scope]

-

-
-
+
 
1   This International Standard specifies the form and establishes the interpretation of
-    programs written in the C programming language.1) It specifies
+    programs written in the C programming language.[1] It specifies
     -- the representation of C programs;
     -- the syntax and constraints of the C language;
     -- the semantic rules for interpreting C programs;
@@ -205,13 +185,12 @@ xviii                         Introduction
     -- the representation of output data produced by C programs;
     -- the restrictions and limits imposed by a conforming implementation of C.
 

-
 
 
Footnote 1) This International Standard is designed to promote the portability of C programs among a variety of
          data-processing systems. It is intended for use by implementors and programmers.
 

 
-
+
 
2   This International Standard does not specify
     -- the mechanism by which C programs are transformed for use by a data-processing
        system;
@@ -225,59 +204,46 @@ xviii                         Introduction
     -- all minimal requirements of a data-processing system that is capable of supporting a
        conforming implementation.
 

-
-
+
 

 
2. [Normative references]

-

-
-
+
 
1   The following referenced documents are indispensable for the application of this
     document. For dated references, only the edition cited applies. For undated references,
     the latest edition of the referenced document (including any amendments) applies.
 

-
-
+
 
2   ISO 31-11:1992, Quantities and units -- Part 11: Mathematical signs and symbols for
     use in the physical sciences and technology .
 

-
-
+
 
3   ISO/IEC 646, Information technology -- ISO 7-bit coded character set for information
     interchange.
 

-
-
+
 
4   ISO/IEC 2382-1:1993, Information technology -- Vocabulary -- Part 1: Fundamental
     terms.
 

-
-
+
 
5   ISO 4217, Codes for the representation of currencies and funds.
 

-
-
+
 
6   ISO 8601, Data elements and interchange formats -- Information interchange --
     Representation of dates and times.
 

-
-
+
 
7   ISO/IEC 10646 (all parts), Information technology -- Universal Multiple-Octet Coded
     Character Set (UCS).
 

-
-
+
 
8   IEC 60559:1989, Binary floating-point arithmetic for microprocessor systems (previously
     designated IEC 559:1989).
 
 

-
-
+
 

 
3. [Terms, definitions, and symbols]

-

-
-
+
 
1   For the purposes of this International Standard, the following definitions apply. Other
     terms are defined where they appear in italic type or on the left side of a syntax rule.
     Terms explicitly defined in this International Standard are not to be presumed to refer
@@ -285,49 +251,37 @@ xviii                         Introduction
     Standard are to be interpreted according to ISO/IEC 2382-1. Mathematical symbols not
     defined in this International Standard are to be interpreted according to ISO 31-11.
 

-
-
+
 

 
3.1 [Terms, definitions, and symbols]

-

-
-
+
 
1   access
     execution-time action to read or modify the value of an object
 

-
-
+
 
2   NOTE 1   Where only one of these two actions is meant, ``read'' or ``modify'' is used.
 
 

-
-
+
 
3   NOTE 2   ``Modify'' includes the case where the new value being stored is the same as the previous value.
 
 

-
-
+
 
4   NOTE 3   Expressions that are not evaluated do not access objects.
 
 

-
-
+
 

 
3.2 [Terms, definitions, and symbols]

-

-
-
+
 
1   alignment
     requirement that objects of a particular type be located on storage boundaries with
     addresses that are particular multiples of a byte address
 

-
-
+
 

 
3.3 [Terms, definitions, and symbols]

-

-
-
+
 
1   argument
     actual argument
     actual parameter (deprecated)
@@ -335,265 +289,200 @@ xviii                         Introduction
     expression, or a sequence of preprocessing tokens in the comma-separated list bounded
     by the parentheses in a function-like macro invocation
 

-
-
+
 

 
3.4 [Terms, definitions, and symbols]

-

-
-
+
 
1   behavior
     external appearance or action
 

-
-
+
 

 
3.4.1 [Terms, definitions, and symbols]

-

-
-
+
 
1   implementation-defined behavior
     unspecified behavior where each implementation documents how the choice is made
 

-
-
+
 
2   EXAMPLE An example of implementation-defined behavior is the propagation of the high-order bit
     when a signed integer is shifted right.
 
 

-
-
+
 

 
3.4.2 [Terms, definitions, and symbols]

-

-
-
+
 
1   locale-specific behavior
     behavior that depends on local conventions of nationality, culture, and language that each
     implementation documents
 

-
-
+
 
2   EXAMPLE An example of locale-specific behavior is whether the islower function returns true for
     characters other than the 26 lowercase Latin letters.
 
 

-
-
+
 

 
3.4.3 [Terms, definitions, and symbols]

-

-
-
+
 
1   undefined behavior
     behavior, upon use of a nonportable or erroneous program construct or of erroneous data,
     for which this International Standard imposes no requirements
 

-
-
+
 
2   NOTE Possible undefined behavior ranges from ignoring the situation completely with unpredictable
     results, to behaving during translation or program execution in a documented manner characteristic of the
     environment (with or without the issuance of a diagnostic message), to terminating a translation or
     execution (with the issuance of a diagnostic message).
 
 

-
-
+
 
3   EXAMPLE        An example of undefined behavior is the behavior on integer overflow.
 
 

-
-
+
 

 
3.4.4 [Terms, definitions, and symbols]

-

-
-
+
 
1   unspecified behavior
     use of an unspecified value, or other behavior where this International Standard provides
     two or more possibilities and imposes no further requirements on which is chosen in any
     instance
 

-
-
+
 
2   EXAMPLE        An example of unspecified behavior is the order in which the arguments to a function are
     evaluated.
 
 

-
-
+
 

 
3.5 [Terms, definitions, and symbols]

-

-
-
+
 
1   bit
     unit of data storage in the execution environment large enough to hold an object that may
     have one of two values
 

-
-
+
 
2   NOTE      It need not be possible to express the address of each individual bit of an object.
 
 

-
-
+
 

 
3.6 [Terms, definitions, and symbols]

-

-
-
+
 
1   byte
     addressable unit of data storage large enough to hold any member of the basic character
     set of the execution environment
 

-
-
+
 
2   NOTE 1     It is possible to express the address of each individual byte of an object uniquely.
 
 

-
-
+
 
3   NOTE 2 A byte is composed of a contiguous sequence of bits, the number of which is implementation-
     defined. The least significant bit is called the low-order bit ; the most significant bit is called the high-order
     bit .
 
 

-
-
+
 

 
3.7 [Terms, definitions, and symbols]

-

-
-
+
 
1   character
     abstract member of a set of elements used for the organization, control, or
     representation of data
 

-
-
+
 

 
3.7.1 [Terms, definitions, and symbols]

-

-
-
+
 
1   character
     single-byte character
     C bit representation that fits in a byte
 

-
-
+
 

 
3.7.2 [Terms, definitions, and symbols]

-

-
-
+
 
1   multibyte character
     sequence of one or more bytes representing a member of the extended character set of
     either the source or the execution environment
 

-
-
+
 
2   NOTE    The extended character set is a superset of the basic character set.
 
 

-
-
+
 

 
3.7.3 [Terms, definitions, and symbols]

-

-
-
+
 
1   wide character
     value representable by an object of type wchar_t, capable of representing any character
     in the current locale
 

-
-
+
 

 
3.8 [Terms, definitions, and symbols]

-

-
-
+
 
1   constraint
     restriction, either syntactic or semantic, by which the exposition of language elements is
     to be interpreted
 

-
-
+
 

 
3.9 [Terms, definitions, and symbols]

-

-
-
+
 
1   correctly rounded result
     representation in the result format that is nearest in value, subject to the current rounding
     mode, to what the result would be given unlimited range and precision
 

-
-
+
 

 
3.10 [Terms, definitions, and symbols]

-

-
-
+
 
1   diagnostic message
     message belonging to an implementation-defined subset of the implementation's message
     output
 

-
-
+
 

 
3.11 [Terms, definitions, and symbols]

-

-
-
+
 
1   forward reference
     reference to a later subclause of this International Standard that contains additional
     information relevant to this subclause
 

-
-
+
 

 
3.12 [Terms, definitions, and symbols]

-

-
-
+
 
1   implementation
     particular set of software, running in a particular translation environment under particular
     control options, that performs translation of programs for, and supports execution of
     functions in, a particular execution environment
 

-
-
+
 

 
3.13 [Terms, definitions, and symbols]

-

-
-
+
 
1   implementation limit
     restriction imposed upon programs by the implementation
 

-
-
+
 

 
3.14 [Terms, definitions, and symbols]

-

-
-
+
 
1   memory location
     either an object of scalar type, or a maximal sequence of adjacent bit-fields all having
     nonzero width
 
 

-
-
+
 
2   NOTE 1 Two threads of execution can update and access separate memory locations without interfering
     with each other.
 
 

-
-
+
 
3   NOTE 2 A bit-field and an adjacent non-bit-field member are in separate memory locations. The same
     applies to two bit-fields, if one is declared inside a nested structure declaration and the other is not, or if the
     two are separated by a zero-length bit-field declaration, or if they are separated by a non-bit-field member
@@ -602,8 +491,7 @@ xviii                         Introduction
     intervening bit-fields happen to be.
 
 

-
-
+
 
4   EXAMPLE        A structure declared as
              struct {
                    char a;
@@ -616,29 +504,22 @@ xviii                         Introduction
     modified, but b and a, for example, can be.
 
 

-
-
+
 

 
3.15 [Terms, definitions, and symbols]

-

-
-
+
 
1   object
     region of data storage in the execution environment, the contents of which can represent
     values
 

-
-
-
2   NOTE      When referenced, an object may be interpreted as having a particular type; see 6.3.2.1.
+
+
2   NOTE      When referenced, an object may be interpreted as having a particular type; see 6.3.2.1.
 
 

-
-
+
 

 
3.16 [Terms, definitions, and symbols]

-

-
-
+
 
1   parameter
     formal parameter
     formal argument (deprecated)
@@ -646,185 +527,141 @@ xviii                         Introduction
     entry to the function, or an identifier from the comma-separated list bounded by the
     parentheses immediately following the macro name in a function-like macro definition
 

-
-
+
 

 
3.17 [Terms, definitions, and symbols]

-

-
-
+
 
1   recommended practice
     specification that is strongly recommended as being in keeping with the intent of the
     standard, but that may be impractical for some implementations
 

-
-
+
 

 
3.18 [Terms, definitions, and symbols]

-

-
-
+
 
1   runtime-constraint
     requirement on a program when calling a library function
 

-
-
-
2   NOTE 1 Despite the similar terms, a runtime-constraint is not a kind of constraint as defined by 3.8, and
+
+
2   NOTE 1 Despite the similar terms, a runtime-constraint is not a kind of constraint as defined by 3.8, and
     need not be diagnosed at translation time.
 
 

-
-
+
 
3   NOTE 2 Implementations that support the extensions in annex K are required to verify that the runtime-
-    constraints for a library function are not violated by the program; see K.3.1.4.
+    constraints for a library function are not violated by the program; see K.3.1.4.
 
 

-
-
+
 

 
3.19 [Terms, definitions, and symbols]

-

-
-
+
 
1   value
     precise meaning of the contents of an object when interpreted as having a specific type
 

-
-
+
 

 
3.19.1 [Terms, definitions, and symbols]

-

-
-
+
 
1   implementation-defined value
     unspecified value where each implementation documents how the choice is made
 

-
-
+
 

 
3.19.2 [Terms, definitions, and symbols]

-

-
-
+
 
1   indeterminate value
     either an unspecified value or a trap representation
 

-
-
+
 

 
3.19.3 [Terms, definitions, and symbols]

-

-
-
+
 
1   unspecified value
     valid value of the relevant type where this International Standard imposes no
     requirements on which value is chosen in any instance
 

-
-
+
 
2   NOTE     An unspecified value cannot be a trap representation.
 
 

-
-
+
 

 
3.19.4 [Terms, definitions, and symbols]

-

-
-
+
 
1   trap representation
     an object representation that need not represent a value of the object type
 

-
-
+
 

 
3.19.5 [Terms, definitions, and symbols]

-

-
-
+
 
1   perform a trap
     interrupt execution of the program such that no further operations are performed
 

-
-
+
 
2   NOTE In this International Standard, when the word ``trap'' is not immediately followed by
-    ``representation'', this is the intended usage.2)
+    ``representation'', this is the intended usage.[2]
 
 

-
 
-
Footnote 2) For example, ``Trapping or stopping (if supported) is disabled...'' (F.8.2). Note that fetching a trap
-         representation might perform a trap but is not required to (see 6.2.6.1).
+
Footnote 2) For example, ``Trapping or stopping (if supported) is disabled...'' (F.8.2). Note that fetching a trap
+         representation might perform a trap but is not required to (see 6.2.6.1).
 

 
-
+
 

 
3.20 [Terms, definitions, and symbols]

-

-
-
+
 
1    x
     ceiling of x : the least integer greater than or equal to x
 

-
-
+
 
2   EXAMPLE       2. 4 is 3, -2. 4 is -2.
 
 

-
-
+
 

 
3.21 [Terms, definitions, and symbols]

-

-
-
+
 
1    x
     floor of x : the greatest integer less than or equal to x
 

-
-
+
 
2   EXAMPLE       2. 4 is 2, -2. 4 is -3.
 

-
-
+
 

 
4. [Conformance]

-

-
-
+
 
1   In this International Standard, ``shall'' is to be interpreted as a requirement on an
     implementation or on a program; conversely, ``shall not'' is to be interpreted as a
     prohibition.
 

-
-
+
 
2   If a ``shall'' or ``shall not'' requirement that appears outside of a constraint or runtime-
     constraint is violated, the behavior is undefined. Undefined behavior is otherwise
     indicated in this International Standard by the words ``undefined behavior'' or by the
     omission of any explicit definition of behavior. There is no difference in emphasis among
     these three; they all describe ``behavior that is undefined''.
 

-
-
+
 
3   A program that is correct in all other aspects, operating on correct data, containing
-    unspecified behavior shall be a correct program and act in accordance with 5.1.2.3.
+    unspecified behavior shall be a correct program and act in accordance with 5.1.2.3.
 

-
-
+
 
4   The implementation shall not successfully translate a preprocessing translation unit
     containing a #error preprocessing directive unless it is part of a group skipped by
     conditional inclusion.
 

-
-
+
 
5   A strictly conforming program shall use only those features of the language and library
-    specified in this International Standard.3) It shall not produce output dependent on any
+    specified in this International Standard.[3] It shall not produce output dependent on any
     unspecified, undefined, or implementation-defined behavior, and shall not exceed any
     minimum implementation limit.
 

-
 
-
Footnote 3) A strictly conforming program can use conditional features (see 6.10.8.3) provided the use is guarded
+
Footnote 3) A strictly conforming program can use conditional features (see 6.10.8.3) provided the use is guarded
          by an appropriate conditional inclusion preprocessing directive using the related macro. For example:
                  #ifdef _ _STDC_IEC_559_ _ /* FE_UPWARD defined */
                     /* ... */
@@ -833,51 +670,46 @@ xviii                         Introduction
                  #endif
 

 
-
+
 
6   The two forms of conforming implementation are hosted and freestanding. A conforming
     hosted implementation shall accept any strictly conforming program. A conforming
-    freestanding implementation shall accept any strictly conforming program in which the 
+    freestanding implementation shall accept any strictly conforming program in which the
     use of the features specified in the library clause (clause 7) is confined to the contents of
     the standard headers <float.h>, <iso646.h>, <limits.h>, <stdalign.h>,
     <stdarg.h>,           <stdbool.h>,            <stddef.h>,           <stdint.h>,          and
     <stdnoreturn.h>. A conforming implementation may have extensions (including
     additional library functions), provided they do not alter the behavior of any strictly
-    conforming program.4)
+    conforming program.[4]
 
 

-
 
 
Footnote 4) This implies that a conforming implementation reserves no identifiers other than those explicitly
          reserved in this International Standard.
 

 
-
-
7   A conforming program is one that is acceptable to a conforming implementation.5)
+
+
7   A conforming program is one that is acceptable to a conforming implementation.[5]
 

-
 
 
Footnote 5) Strictly conforming programs are intended to be maximally portable among conforming
          implementations. Conforming programs may depend upon nonportable features of a conforming
          implementation.
 

 
-
+
 
8   An implementation shall be accompanied by a document that defines all implementation-
     defined and locale-specific characteristics and all extensions.
-    Forward references: conditional inclusion (6.10.1), error directive (6.10.5),
-    characteristics of floating types <float.h> (7.7), alternative spellings <iso646.h>
-    (7.9), sizes of integer types <limits.h> (7.10), alignment <stdalign.h> (7.15),
-    variable arguments <stdarg.h> (7.16), boolean type and values <stdbool.h>
-    (7.18), common definitions <stddef.h> (7.19), integer types <stdint.h> (7.20),
-    <stdnoreturn.h> (7.23).
+    Forward references: conditional inclusion (6.10.1), error directive (6.10.5),
+    characteristics of floating types <float.h> (7.7), alternative spellings <iso646.h>
+    (7.9), sizes of integer types <limits.h> (7.10), alignment <stdalign.h> (7.15),
+    variable arguments <stdarg.h> (7.16), boolean type and values <stdbool.h>
+    (7.18), common definitions <stddef.h> (7.19), integer types <stdint.h> (7.20),
+    <stdnoreturn.h> (7.23).
 

-
-
+
 

 
5. [Environment]

-

-
-
+
 
1   An implementation translates C source files and executes C programs in two data-
     processing-system environments, which will be called the translation environment and
     the execution environment in this International Standard. Their characteristics define and
@@ -886,25 +718,16 @@ xviii                         Introduction
     Forward references: In this clause, only a few of many possible forward references
     have been noted.
 

-
-
+
 

 
5.1 [Conceptual models]

-
 Conceptual models
-

-
-
+
 

 
5.1.1 [Translation environment]

-
 Translation environment
-

-
-
+
 

 
5.1.1.1 [Program structure]

-

-
-
+
 
1   A C program need not all be translated at the same time. The text of the program is kept
     in units called source files, (or preprocessing files) in this International Standard. A
     source file together with all the headers and source files included via the preprocessing
@@ -915,96 +738,78 @@ xviii                         Introduction
     linkage, manipulation of objects whose identifiers have external linkage, or manipulation
     of data files. Translation units may be separately translated and then later linked to
     produce an executable program.
-    Forward references: linkages of identifiers (6.2.2), external definitions (6.9),
-    preprocessing directives (6.10).
+    Forward references: linkages of identifiers (6.2.2), external definitions (6.9),
+    preprocessing directives (6.10).
 

-
-
+
 

 
5.1.1.2 [Translation phases]

-

-
-
+
 
1   The precedence among the syntax rules of translation is specified by the following
-    phases.6)
+    phases.[6]
          1.   Physical source file multibyte characters are mapped, in an implementation-
               defined manner, to the source character set (introducing new-line characters for
               end-of-line indicators) if necessary. Trigraph sequences are replaced by
               corresponding single-character internal representations.
 
-     2.   Each instance of a backslash character (\) immediately followed by a new-line
-          character is deleted, splicing physical source lines to form logical source lines.
-          Only the last backslash on any physical source line shall be eligible for being part
-          of such a splice. A source file that is not empty shall end in a new-line character,
-          which shall not be immediately preceded by a backslash character before any such
-          splicing takes place.
-     3.   The source file is decomposed into preprocessing tokens7) and sequences of
-          white-space characters (including comments). A source file shall not end in a
-          partial preprocessing token or in a partial comment. Each comment is replaced by
-          one space character. New-line characters are retained. Whether each nonempty
-          sequence of white-space characters other than new-line is retained or replaced by
-          one space character is implementation-defined.
-     4. Preprocessing directives are executed, macro invocations are expanded, and
-        _Pragma unary operator expressions are executed. If a character sequence that
-        matches the syntax of a universal character name is produced by token
-        concatenation (6.10.3.3), the behavior is undefined. A #include preprocessing
-        directive causes the named header or source file to be processed from phase 1
-        through phase 4, recursively. All preprocessing directives are then deleted.
-     5. Each source character set member and escape sequence in character constants and
-        string literals is converted to the corresponding member of the execution character
-        set; if there is no corresponding member, it is converted to an implementation-
-        defined member other than the null (wide) character.8)
-     6.   Adjacent string literal tokens are concatenated.
-     7. White-space characters separating tokens are no longer significant. Each
-        preprocessing token is converted into a token. The resulting tokens are
-        syntactically and semantically analyzed and translated as a translation unit.
-     8.   All external object and function references are resolved. Library components are
-          linked to satisfy external references to functions and objects not defined in the
-          current translation. All such translator output is collected into a program image
-          which contains information needed for execution in its execution environment.
-    Forward references: universal character names (6.4.3), lexical elements (6.4),
-    preprocessing directives (6.10), trigraph sequences (5.2.1.1), external definitions (6.9).
-
 

-
 
 
Footnote 6) Implementations shall behave as if these separate phases occur, even though many are typically folded
           together in practice. Source files, translation units, and translated translation units need not
           necessarily be stored as files, nor need there be any one-to-one correspondence between these entities
           and any external representation. The description is conceptual only, and does not specify any
           particular implementation.
+         2.   Each instance of a backslash character (\) immediately followed by a new-line
+              character is deleted, splicing physical source lines to form logical source lines.
+              Only the last backslash on any physical source line shall be eligible for being part
+              of such a splice. A source file that is not empty shall end in a new-line character,
+              which shall not be immediately preceded by a backslash character before any such
+              splicing takes place.
+         3.   The source file is decomposed into preprocessing tokens7) and sequences of
+              white-space characters (including comments). A source file shall not end in a
+              partial preprocessing token or in a partial comment. Each comment is replaced by
+              one space character. New-line characters are retained. Whether each nonempty
+              sequence of white-space characters other than new-line is retained or replaced by
+              one space character is implementation-defined.
+         4. Preprocessing directives are executed, macro invocations are expanded, and
+            _Pragma unary operator expressions are executed. If a character sequence that
+            matches the syntax of a universal character name is produced by token
+            concatenation (6.10.3.3), the behavior is undefined. A #include preprocessing
+            directive causes the named header or source file to be processed from phase 1
+            through phase 4, recursively. All preprocessing directives are then deleted.
+         5. Each source character set member and escape sequence in character constants and
+            string literals is converted to the corresponding member of the execution character
+            set; if there is no corresponding member, it is converted to an implementation-
+            defined member other than the null (wide) character.8)
+         6.   Adjacent string literal tokens are concatenated.
+         7. White-space characters separating tokens are no longer significant. Each
+            preprocessing token is converted into a token. The resulting tokens are
+            syntactically and semantically analyzed and translated as a translation unit.
+         8.   All external object and function references are resolved. Library components are
+              linked to satisfy external references to functions and objects not defined in the
+              current translation. All such translator output is collected into a program image
+              which contains information needed for execution in its execution environment.
+    Forward references: universal character names (6.4.3), lexical elements (6.4),
+    preprocessing directives (6.10), trigraph sequences (5.2.1.1), external definitions (6.9).
 

 
-
-
Footnote 7) As described in 6.4, the process of dividing a source file's characters into preprocessing tokens is
-          context-dependent. For example, see the handling of < within a #include preprocessing directive.
-

-
-
-
Footnote 8) An implementation need not convert all non-corresponding source characters to the same execution
-          character.
-

-
-
+
 

 
5.1.1.3 [Diagnostics]

-

-
-
+
 
1   A conforming implementation shall produce at least one diagnostic message (identified in
     an implementation-defined manner) if a preprocessing translation unit or translation unit
     contains a violation of any syntax rule or constraint, even if the behavior is also explicitly
     specified as undefined or implementation-defined. Diagnostic messages need not be
-    produced in other circumstances.9)
+    produced in other circumstances.[9]
 

-
 
 
Footnote 9) The intent is that an implementation should identify the nature of, and where possible localize, each
          violation. Of course, an implementation is free to produce any number of diagnostics as long as a
          valid program is still correctly translated. It may also successfully translate an invalid program.
 

 
-
+
 
2   EXAMPLE        An implementation shall issue a diagnostic for the translation unit:
              char i;
              int i;
@@ -1012,56 +817,43 @@ xviii                         Introduction
     as being both a constraint error and resulting in undefined behavior, the constraint error shall be diagnosed.
 
 

-
-
+
 

 
5.1.2 [Execution environments]

-

-
-
+
 
1   Two execution environments are defined: freestanding and hosted . In both cases,
     program startup occurs when a designated C function is called by the execution
     environment. All objects with static storage duration shall be initialized (set to their
     initial values) before program startup. The manner and timing of such initialization are
     otherwise unspecified. Program termination returns control to the execution
     environment.
-    Forward references: storage durations of objects (6.2.4), initialization (6.7.9).
+    Forward references: storage durations of objects (6.2.4), initialization (6.7.9).
 

-
-
+
 

 
5.1.2.1 [Freestanding environment]

-

-
-
+
 
1   In a freestanding environment (in which C program execution may take place without any
     benefit of an operating system), the name and type of the function called at program
     startup are implementation-defined. Any library facilities available to a freestanding
     program, other than the minimal set required by clause 4, are implementation-defined.
 

-
-
+
 
2   The effect of program termination in a freestanding environment is implementation-
     defined.
 

-
-
+
 

 
5.1.2.2 [Hosted environment]

-

-
-
+
 
1   A hosted environment need not be provided, but shall conform to the following
     specifications if present.
 
 

-
-
+
 

 
5.1.2.2.1 [Program startup]

-

-
-
+
 
1   The function called at program startup is named main. The implementation declares no
     prototype for this function. It shall be defined with a return type of int and with no
     parameters:
@@ -1069,15 +861,14 @@ xviii                         Introduction
     or with two parameters (referred to here as argc and argv, though any names may be
     used, as they are local to the function in which they are declared):
             int main(int argc, char *argv[]) { /* ... */ }
-    or equivalent;10) or in some other implementation-defined manner.
+    or equivalent;[10] or in some other implementation-defined manner.
 

-
 
 
Footnote 10) Thus, int can be replaced by a typedef name defined as int, or the type of argv can be written as
         char ** argv, and so on.
 

 
-
+
 
2   If they are declared, the parameters to the main function shall obey the following
     constraints:
     -- The value of argc shall be nonnegative.
@@ -1098,55 +889,44 @@ xviii                         Introduction
        be modifiable by the program, and retain their last-stored values between program
        startup and program termination.
 

-
-
+
 

 
5.1.2.2.2 [Program execution]

-

-
-
+
 
1   In a hosted environment, a program may use all the functions, macros, type definitions,
     and objects described in the library clause (clause 7).
 
 

-
-
+
 

 
5.1.2.2.3 [Program termination]

-

-
-
+
 
1   If the return type of the main function is a type compatible with int, a return from the
     initial call to the main function is equivalent to calling the exit function with the value
-    returned by the main function as its argument;11) reaching the } that terminates the
+    returned by the main function as its argument;[11] reaching the } that terminates the
     main function returns a value of 0. If the return type is not compatible with int, the
     termination status returned to the host environment is unspecified.
-    Forward references: definition of terms (7.1.1), the exit function (7.22.4.4).
+    Forward references: definition of terms (7.1.1), the exit function (7.22.4.4).
 

-
 
-
Footnote 11) In accordance with 6.2.4, the lifetimes of objects with automatic storage duration declared in main
+
Footnote 11) In accordance with 6.2.4, the lifetimes of objects with automatic storage duration declared in main
         will have ended in the former case, even where they would not have in the latter.
 

 
-
+
 

 
5.1.2.3 [Program execution]

-

-
-
+
 
1   The semantic descriptions in this International Standard describe the behavior of an
     abstract machine in which issues of optimization are irrelevant.
 

-
-
+
 
2   Accessing a volatile object, modifying an object, modifying a file, or calling a function
-    that does any of those operations are all side effects,12) which are changes in the state of
+    that does any of those operations are all side effects,[12] which are changes in the state of
     the execution environment. Evaluation of an expression in general includes both value
     computations and initiation of side effects. Value computation for an lvalue expression
     includes determining the identity of the designated object.
 

-
 
 
Footnote 12) The IEC 60559 standard for binary floating-point arithmetic requires certain user-accessible status
         flags and control modes. Floating-point operations implicitly set the status flags; modes affect result
@@ -1156,33 +936,30 @@ xviii                         Introduction
         effects matter, freeing the implementations in other cases.
 

 
-
+
 
3   Sequenced before is an asymmetric, transitive, pair-wise relation between evaluations
     executed by a single thread, which induces a partial order among those evaluations.
     Given any two evaluations A and B, if A is sequenced before B, then the execution of A
     shall precede the execution of B. (Conversely, if A is sequenced before B, then B is
     sequenced after A.) If A is not sequenced before or after B, then A and B are
     unsequenced . Evaluations A and B are indeterminately sequenced when A is sequenced
-    either before or after B, but it is unspecified which.13) The presence of a sequence point
+    either before or after B, but it is unspecified which.[13] The presence of a sequence point
     between the evaluation of expressions A and B implies that every value computation and
     side effect associated with A is sequenced before every value computation and side effect
     associated with B. (A summary of the sequence points is given in annex C.)
 

-
 
 
Footnote 13) The executions of unsequenced evaluations can interleave. Indeterminately sequenced evaluations
         cannot interleave, but can be executed in any order.
+     calling a function or accessing a volatile object).
 

 
-
+
 
4   In the abstract machine, all expressions are evaluated as specified by the semantics. An
     actual implementation need not evaluate part of an expression if it can deduce that its
     value is not used and that no needed side effects are produced (including any caused by
-
-     calling a function or accessing a volatile object).
 

-
-
+
 
5    When the processing of the abstract machine is interrupted by receipt of a signal, the
      values of objects that are neither lock-free atomic objects nor of type volatile
      sig_atomic_t are unspecified, as is the state of the floating-point environment. The
@@ -1191,36 +968,31 @@ xviii                         Introduction
      does the state of the floating-point environment if it is modified by the handler and not
      restored to its original state.
 

-
-
+
 
6    The least requirements on a conforming implementation are:
      -- Accesses to volatile objects are evaluated strictly according to the rules of the abstract
         machine.
      -- At program termination, all data written into files shall be identical to the result that
         execution of the program according to the abstract semantics would have produced.
      -- The input and output dynamics of interactive devices shall take place as specified in
-        7.21.3. The intent of these requirements is that unbuffered or line-buffered output
+        7.21.3. The intent of these requirements is that unbuffered or line-buffered output
         appear as soon as possible, to ensure that prompting messages actually appear prior to
         a program waiting for input.
      This is the observable behavior of the program.
 

-
-
+
 
7    What constitutes an interactive device is implementation-defined.
 

-
-
+
 
8    More stringent correspondences between abstract and actual semantics may be defined by
      each implementation.
 

-
-
+
 
9    EXAMPLE 1 An implementation might define a one-to-one correspondence between abstract and actual
      semantics: at every sequence point, the values of the actual objects would agree with those specified by the
      abstract semantics. The keyword volatile would then be redundant.
 

-
-
+
 
10   Alternatively, an implementation might perform various optimizations within each translation unit, such
      that the actual semantics would agree with the abstract semantics only when making function calls across
      translation unit boundaries. In such an implementation, at the time of each function entry and function
@@ -1233,8 +1005,7 @@ xviii                         Introduction
      restrictions.
 
 

-
-
+
 
11   EXAMPLE 2       In executing the fragment
               char c1, c2;
               /* ... */
@@ -1245,8 +1016,7 @@ xviii                         Introduction
      produce the same result, possibly omitting the promotions.
 
 

-
-
+
 
12   EXAMPLE 3       Similarly, in the fragment
               float f1, f2;
               double d;
@@ -1257,8 +1027,7 @@ xviii                         Introduction
      were replaced by the constant 2.0, which has type double).
 
 

-
-
+
 
13   EXAMPLE 4 Implementations employing wide registers have to take care to honor appropriate
      semantics. Values are independent of whether they are represented in a register or in memory. For
      example, an implicit spilling of a register is not permitted to alter the value. Also, an explicit store and load
@@ -1271,14 +1040,13 @@ xviii                         Introduction
      the values assigned to d1 and d2 are required to have been converted to float.
 
 

-
-
+
 
14   EXAMPLE 5 Rearrangement for floating-point expressions is often restricted because of limitations in
      precision as well as range. The implementation cannot generally apply the mathematical associative rules
      for addition or multiplication, nor the distributive rule, because of roundoff error, even in the absence of
      overflow and underflow. Likewise, implementations cannot generally replace decimal constants in order to
      rearrange expressions. In the following fragment, rearrangements suggested by mathematical rules for real
-     numbers are often not valid (see F.9).
+     numbers are often not valid (see F.9).
               double x, y, z;
               /* ... */
               x = (x * y) * z;            //   not equivalent to x   *= y * z;
@@ -1287,8 +1055,7 @@ xviii                         Introduction
               y = x / 5.0;                //   not equivalent to y   = x * 0.2;
 
 

-
-
+
 
15   EXAMPLE 6       To illustrate the grouping behavior of expressions, in the following fragment
               int a, b;
               /* ... */
@@ -1312,8 +1079,7 @@ xviii                         Introduction
      same result will occur.
 
 

-
-
+
 
16   EXAMPLE 7 The grouping of an expression does not completely determine its evaluation. In the
      following fragment
               #include <stdio.h>
@@ -1327,51 +1093,44 @@ xviii                         Introduction
      sequence point (the ;), and the call to getchar can occur at any point prior to the need of its returned
      value.
 
-     Forward references: expressions (6.5), type qualifiers (6.7.3), statements (6.8), floating-
-     point environment <fenv.h> (7.6), the signal function (7.14), files (7.21.3).
+     Forward references: expressions (6.5), type qualifiers (6.7.3), statements (6.8), floating-
+     point environment <fenv.h> (7.6), the signal function (7.14), files (7.21.3).
 

-
-
+
 

 
5.1.2.4 [Multi-threaded executions and data races]

-

-
-
+
 
1    Under a hosted implementation, a program can have more than one thread of execution
      (or thread ) running concurrently. The execution of each thread proceeds as defined by
      the remainder of this standard. The execution of the entire program consists of an
-     execution of all of its threads.14) Under a freestanding implementation, it is
+     execution of all of its threads.[14] Under a freestanding implementation, it is
      implementation-defined whether a program can have more than one thread of execution.
 

-
 
 
Footnote 14) The execution can usually be viewed as an interleaving of all of the threads. However, some kinds of
          atomic operations, for example, allow executions inconsistent with a simple interleaving as described
          below.
 

 
-
+
 
2    The value of an object visible to a thread T at a particular point is the initial value of the
      object, a value stored in the object by T , or a value stored in the object by another thread,
      according to the rules below.
 

-
-
+
 
3    NOTE 1 In some cases, there may instead be undefined behavior. Much of this section is motivated by
      the desire to support atomic operations with explicit and detailed visibility constraints. However, it also
      implicitly supports a simpler view for more restricted programs.
 
 

-
-
+
 
4    Two expression evaluations conflict if one of them modifies a memory location and the
      other one reads or modifies the same memory location.
 
 

-
-
-
5    The library defines a number of atomic operations (7.17) and operations on mutexes
-     (7.26.4) that are specially identified as synchronization operations. These operations play
+
+
5    The library defines a number of atomic operations (7.17) and operations on mutexes
+     (7.26.4) that are specially identified as synchronization operations. These operations play
      a special role in making assignments in one thread visible to another. A synchronization
      operation on one or more memory locations is either an acquire operation, a release
      operation, both an acquire and release operation, or a consume operation. A
@@ -1380,8 +1139,7 @@ xviii                         Introduction
      there are relaxed atomic operations, which are not synchronization operations, and
      atomic read-modify-write operations, which have special characteristics.
 

-
-
+
 
6    NOTE 2 For example, a call that acquires a mutex will perform an acquire operation on the locations
      composing the mutex. Correspondingly, a call that releases the same mutex will perform a release
      operation on those same locations. Informally, performing a release operation on A forces prior side effects
@@ -1390,95 +1148,83 @@ xviii                         Introduction
      synchronization operations, they cannot contribute to data races.
 
 

-
-
+
 
7    All modifications to a particular atomic object M occur in some particular total order,
      called the modification order of M . If A and B are modifications of an atomic object M ,
      and A happens before B, then A shall precede B in the modification order of M , which is
      defined below.
 

-
-
+
 
8    NOTE 3     This states that the modification orders must respect the ``happens before'' relation.
 
 

-
-
+
 
9    NOTE 4 There is a separate order for each atomic object. There is no requirement that these can be
      combined into a single total order for all objects. In general this will be impossible since different threads
      may observe modifications to different variables in inconsistent orders.
 
 

-
-
+
 
10   A release sequence headed by a release operation A on an atomic object M is a maximal
      contiguous sub-sequence of side effects in the modification order of M , where the first
      operation is A and every subsequent operation either is performed by the same thread that
      performed the release or is an atomic read-modify-write operation.
 

-
-
+
 
11   Certain library calls synchronize with other library calls performed by another thread. In
      particular, an atomic operation A that performs a release operation on an object M
      synchronizes with an atomic operation B that performs an acquire operation on M and
      reads a value written by any side effect in the release sequence headed by A.
 

-
-
+
 
12   NOTE 5 Except in the specified cases, reading a later value does not necessarily ensure visibility as
      described below. Such a requirement would sometimes interfere with efficient implementation.
 
 

-
-
+
 
13   NOTE 6 The specifications of the synchronization operations define when one reads the value written by
      another. For atomic variables, the definition is clear. All operations on a given mutex occur in a single total
      order. Each mutex acquisition ``reads the value written'' by the last mutex release.
 
 

-
-
-
14   An evaluation A carries a dependency 15) to an evaluation B if:
-
+
+
14   An evaluation A carries a dependency [15] to an evaluation B if:
+

+
+
Footnote 15) The ``carries a dependency'' relation is a subset of the ``sequenced before'' relation, and is similarly
+         strictly intra-thread.
      -- the value of A is used as an operand of B, unless:
-           ·   B is an invocation of the kill_dependency macro,
-           ·   A is the left operand of a && or || operator,
-           ·   A is the left operand of a ? : operator, or
-           ·   A is the left operand of a , operator;
+           \xB7   B is an invocation of the kill_dependency macro,
+           \xB7   A is the left operand of a && or || operator,
+           \xB7   A is the left operand of a ? : operator, or
+           \xB7   A is the left operand of a , operator;
          or
      -- A writes a scalar object or bit-field M , B reads from M the value written by A, and A
         is sequenced before B, or
      -- for some evaluation X , A carries a dependency to X and X carries a dependency to B.
-

-
-
-
Footnote 15) The ``carries a dependency'' relation is a subset of the ``sequenced before'' relation, and is similarly
-         strictly intra-thread.
 

 
-
-
15   An evaluation A is dependency-ordered before16) an evaluation B if:
+
+
15   An evaluation A is dependency-ordered before[16] an evaluation B if:
      -- A performs a release operation on an atomic object M , and, in another thread, B
         performs a consume operation on M and reads a value written by any side effect in
         the release sequence headed by A, or
      -- for some evaluation X , A is dependency-ordered before X and X carries a
         dependency to B.
 

-
 
 
Footnote 16) The ``dependency-ordered before'' relation is analogous to the ``synchronizes with'' relation, but uses
          release/consume in place of release/acquire.
 

 
-
+
 
16   An evaluation A inter-thread happens before an evaluation B if A synchronizes with B, A
      is dependency-ordered before B, or, for some evaluation X :
      -- A synchronizes with X and X is sequenced before B,
      -- A is sequenced before X and X inter-thread happens before B, or
      -- A inter-thread happens before X and X inter-thread happens before B.
 

-
-
+
 
17   NOTE 7 The ``inter-thread happens before'' relation describes arbitrary concatenations of ``sequenced
      before'', ``synchronizes with'', and ``dependency-ordered before'' relationships, with two exceptions. The
      first exception is that a concatenation is not permitted to end with ``dependency-ordered before'' followed
@@ -1492,14 +1238,12 @@ xviii                         Introduction
      consisting entirely of ``sequenced before''.
 
 

-
-
+
 
18   An evaluation A happens before an evaluation B if A is sequenced before B or A inter-
      thread happens before B.
 
 

-
-
+
 
19   A visible side effect A on an object M with respect to a value computation B of M
      satisfies the conditions:
      -- A happens before B, and
@@ -1508,22 +1252,19 @@ xviii                         Introduction
      The value of a non-atomic scalar object M , as determined by evaluation B, shall be the
      value stored by the visible side effect A.
 

-
-
+
 
20   NOTE 8 If there is ambiguity about which side effect to a non-atomic object is visible, then there is a data
      race and the behavior is undefined.
 
 

-
-
+
 
21   NOTE 9 This states that operations on ordinary variables are not visibly reordered. This is not actually
      detectable without data races, but it is necessary to ensure that data races, as defined here, and with suitable
      restrictions on the use of atomics, correspond to data races in a simple interleaved (sequentially consistent)
      execution.
 
 

-
-
+
 
22   The visible sequence of side effects on an atomic object M , with respect to a value
      computation B of M , is a maximal contiguous sub-sequence of side effects in the
      modification order of M , where the first side effect is visible with respect to B, and for
@@ -1535,15 +1276,13 @@ xviii                         Introduction
      computed by B shall either equal the value computed by A, or be the value stored by side
      effect Y , where Y follows X in the modification order of M .
 

-
-
+
 
23   NOTE 10 This effectively disallows compiler reordering of atomic operations to a single object, even if
      both operations are ``relaxed'' loads. By doing so, we effectively make the ``cache coherence'' guarantee
      provided by most hardware available to C atomic operations.
 
 

-
-
+
 
24   NOTE 11 The visible sequence depends on the ``happens before'' relation, which in turn depends on the
      values observed by loads of atomics, which we are restricting here. The intended reading is that there must
      exist an association of atomic loads with modifications they observe that, together with suitably chosen
@@ -1551,14 +1290,12 @@ xviii                         Introduction
      constraints as imposed here.
 
 

-
-
+
 
25   The execution of a program contains a data race if it contains two conflicting actions in
      different threads, at least one of which is not atomic, and neither happens before the
      other. Any such data race results in undefined behavior.
 

-
-
+
 
26   NOTE 12 It can be shown that programs that correctly use simple mutexes and
      memory_order_seq_cst operations to prevent all data races, and use no other synchronization
      operations, behave as though the operations executed by their constituent threads were simply interleaved,
@@ -1569,8 +1306,7 @@ xviii                         Introduction
      any program that behaves differently as a result must contain undefined behavior.
 
 

-
-
+
 
27   NOTE 13 Compiler transformations that introduce assignments to a potentially shared memory location
      that would not be modified by the abstract machine are generally precluded by this standard, since such an
      assignment might overwrite another assignment by a different thread in cases in which an abstract machine
@@ -1580,27 +1316,20 @@ xviii                         Introduction
      "visible sequence" rules.
 
 

-
-
+
 
28   NOTE 14 Transformations that introduce a speculative read of a potentially shared memory location may
      not preserve the semantics of the program as defined in this standard, since they potentially introduce a data
      race. However, they are typically valid in the context of an optimizing compiler that targets a specific
      machine with well-defined semantics for data races. They would be invalid for a hypothetical machine that
      is not tolerant of races or provides hardware race detection.
 

-
-
+
 

 
5.2 [Environmental considerations]

-
 Environmental considerations
-

-
-
+
 

 
5.2.1 [Character sets]

-

-
-
+
 
1   Two sets of characters and their associated collating sequences shall be defined: the set in
     which source files are written (the source character set ), and the set interpreted in the
     execution environment (the execution character set ). Each set is further divided into a
@@ -1609,16 +1338,14 @@ xviii                         Introduction
     extended characters. The combined set is also called the extended character set . The
     values of the members of the execution character set are implementation-defined.
 

-
-
+
 
2   In a character constant or string literal, members of the execution character set shall be
     represented by corresponding members of the source character set or by escape
     sequences consisting of the backslash \ followed by one or more characters. A byte with
     all bits set to 0, called the null character , shall exist in the basic execution character set; it
     is used to terminate a character string.
 

-
-
+
 
3   Both the basic source and basic execution character sets shall have the following
     members: the 26 uppercase letters of the Latin alphabet
             A    B    C     D   E     F   G   H    I    J    K    L    M
@@ -1644,26 +1371,21 @@ xviii                         Introduction
 
     converted to a token), the behavior is undefined.
 

-
-
+
 
4   A letter is an uppercase letter or a lowercase letter as defined above; in this International
     Standard the term does not include other characters that are letters in other alphabets.
 

-
-
+
 
5   The universal character name construct provides a way to name other characters.
-    Forward references: universal character names (6.4.3), character constants (6.4.4.4),
-    preprocessing directives (6.10), string literals (6.4.5), comments (6.4.9), string (7.1.1).
+    Forward references: universal character names (6.4.3), character constants (6.4.4.4),
+    preprocessing directives (6.10), string literals (6.4.5), comments (6.4.9), string (7.1.1).
 

-
-
+
 

 
5.2.1.1 [Trigraph sequences]

-

-
-
+
 
1   Before any other processing takes place, each occurrence of one of the following
-    sequences of three characters (called trigraph sequences17)) is replaced with the
+    sequences of three characters (called trigraph sequences[17]) is replaced with the
     corresponding single character.
            ??=      #                       ??)      ]                       ??!      |
            ??(      [                       ??'      ^                       ??>      }
@@ -1671,43 +1393,9 @@ xviii                         Introduction
     No other trigraph sequences exist. Each ? that does not begin one of the trigraphs listed
     above is not changed.
 

-
 
 
Footnote 17) The trigraph sequences enable the input of characters that are not defined in the Invariant Code Set as
         described in ISO/IEC 646, which is a subset of the seven-bit US ASCII code set.
-

-
-
-
2   EXAMPLE 1
-              ??=define arraycheck(a, b) a??(b??) ??!??! b??(a??)
-    becomes
-              #define arraycheck(a, b) a[b] || b[a]
-
-

-
-
-
3   EXAMPLE 2       The following source line
-              printf("Eh???/n");
-    becomes (after replacement of the trigraph sequence ??/)
-              printf("Eh?\n");
-
-

-
-
-

-
5.2.1.2 [Multibyte characters]

-

-
-
-
1   The source character set may contain multibyte characters, used to represent members of
-    the extended character set. The execution character set may also contain multibyte
-    characters, which need not have the same encoding as for the source character set. For
-    both character sets, the following shall hold:
-    -- The basic character set shall be present and each character shall be encoded as a
-       single byte.
-    -- The presence, meaning, and representation of any additional members is locale-
-       specific.
-
     -- A multibyte character set may have a state-dependent encoding, wherein each
        sequence of multibyte characters begins in an initial shift state and enters other
        locale-specific shift states when specific multibyte characters are encountered in the
@@ -1716,22 +1404,46 @@ xviii                         Introduction
        in the sequence is a function of the current shift state.
     -- A byte with all bits zero shall be interpreted as a null character independent of shift
        state. Such a byte shall not occur as part of any other multibyte character.
-

+

 
-
+
+
2   EXAMPLE 1
+              ??=define arraycheck(a, b) a??(b??) ??!??! b??(a??)
+    becomes
+              #define arraycheck(a, b) a[b] || b[a]
+
+

+
+
3   EXAMPLE 2       The following source line
+              printf("Eh???/n");
+    becomes (after replacement of the trigraph sequence ??/)
+              printf("Eh?\n");
+
+

+
+

+
5.2.1.2 [Multibyte characters]

+
+
1   The source character set may contain multibyte characters, used to represent members of
+    the extended character set. The execution character set may also contain multibyte
+    characters, which need not have the same encoding as for the source character set. For
+    both character sets, the following shall hold:
+    -- The basic character set shall be present and each character shall be encoded as a
+       single byte.
+    -- The presence, meaning, and representation of any additional members is locale-
+       specific.
+

+
 
2   For source files, the following shall hold:
     -- An identifier, comment, string literal, character constant, or header name shall begin
        and end in the initial shift state.
     -- An identifier, comment, string literal, character constant, or header name shall consist
        of a sequence of valid multibyte characters.
 

-
-
+
 

 
5.2.2 [Character display semantics]

-

-
-
+
 
1   The active position is that location on a display device where the next character output by
     the fputc function would appear. The intent of writing a printing character (as defined
     by the isprint function) to a display device is to display a graphic representation of
@@ -1740,8 +1452,7 @@ xviii                         Introduction
     position is at the final position of a line (if there is one), the behavior of the display device
     is unspecified.
 

-
-
+
 
2   Alphabetic escape sequences representing nongraphic characters in the execution
     character set are intended to produce actions on display devices as follows:
     \a ( alert ) Produces an audible or visible alert without changing the active position.
@@ -1759,21 +1470,17 @@ xviii                         Introduction
        tabulation position. If the active position is at or past the last defined vertical
          tabulation position, the behavior of the display device is unspecified.
 

-
-
+
 
3   Each of these escape sequences shall produce a unique implementation-defined value
     which can be stored in a single char object. The external representations in a text file
     need not be identical to the internal representations, and are outside the scope of this
     International Standard.
-    Forward references: the isprint function (7.4.1.8), the fputc function (7.21.7.3).
+    Forward references: the isprint function (7.4.1.8), the fputc function (7.21.7.3).
 

-
-
+
 

 
5.2.3 [Signals and interrupts]

-

-
-
+
 
1   Functions shall be implemented such that they may be interrupted at any time by a signal,
     or may be called by a signal handler, or both, with no alteration to earlier, but still active,
     invocations' control flow (after the interruption), function return values, or objects with
@@ -1781,27 +1488,21 @@ xviii                         Introduction
     image (the instructions that compose the executable representation of a function) on a
     per-invocation basis.
 

-
-
+
 

 
5.2.4 [Environmental limits]

-

-
-
+
 
1   Both the translation and execution environments constrain the implementation of
     language translators and libraries. The following summarizes the language-related
     environmental limits on a conforming implementation; the library-related limits are
     discussed in clause 7.
 

-
-
+
 

 
5.2.4.1 [Translation limits]

-

-
-
+
 
1   The implementation shall be able to translate and execute at least one program that
-    contains at least one instance of every one of the following limits:18)
+    contains at least one instance of every one of the following limits:[18]
     -- 127 nesting levels of blocks
     -- 63 nesting levels of conditional inclusion
     -- 12 pointer, array, and function declarators (in any combinations) modifying an
@@ -1813,7 +1514,9 @@ xviii                         Introduction
        character)
     -- 31 significant initial characters in an external identifier (each universal character name
        specifying a short identifier of 0000FFFF or less is considered 6 characters, each
-
+

+
+
Footnote 18) Implementations should avoid imposing fixed translation limits whenever possible.
          universal character name specifying a short identifier of 00010000 or more is
          considered 10 characters, and each extended source character is considered the same
          number of characters as the corresponding universal character name, if any)19)
@@ -1833,113 +1536,60 @@ xviii                         Introduction
     -- 1023 members in a single structure or union
     -- 1023 enumeration constants in a single enumeration
     -- 63 levels of nested structure or union definitions in a single struct-declaration-list
-

-
-
-
Footnote 19) See ``future language directions'' (6.11.3).
 

 
-
+
 

 
5.2.4.2 [Numerical limits]

-

-
-
+
 
1   An implementation is required to document all the limits specified in this subclause,
     which are specified in the headers <limits.h> and <float.h>. Additional limits are
     specified in <stdint.h>.
-    Forward references: integer types <stdint.h> (7.20).
+    Forward references: integer types <stdint.h> (7.20).
 

-
-
+
 

-
5.2.4.2.1 [Sizes of integer types ]

-

-
-
+
5.2.4.2.1 [Sizes of integer types <limits.h>]

+
 
1   The values given below shall be replaced by constant expressions suitable for use in #if
     preprocessing directives. Moreover, except for CHAR_BIT and MB_LEN_MAX, the
     following shall be replaced by expressions that have the same type as would an
     expression that is an object of the corresponding type converted according to the integer
     promotions. Their implementation-defined values shall be equal or greater in magnitude
-
-    (absolute value) to those shown, with the same sign.
-    -- number of bits for smallest object that is not a bit-field (byte)
-       CHAR_BIT                                            8
-    -- minimum value for an object of type signed char
-       SCHAR_MIN                                -127 // -(27 - 1)
-    -- maximum value for an object of type signed char
-       SCHAR_MAX                                +127 // 27 - 1
-    -- maximum value for an object of type unsigned char
-       UCHAR_MAX                                 255 // 28 - 1
-    -- minimum value for an object of type char
-       CHAR_MIN                               see below
-    -- maximum value for an object of type char
-       CHAR_MAX                              see below
-    -- maximum number of bytes in a multibyte character, for any supported locale
-       MB_LEN_MAX                                    1
-    -- minimum value for an object of type short int
-       SHRT_MIN                               -32767 // -(215 - 1)
-    -- maximum value for an object of type short int
-       SHRT_MAX                               +32767 // 215 - 1
-    -- maximum value for an object of type unsigned short int
-       USHRT_MAX                               65535 // 216 - 1
-    -- minimum value for an object of type int
-       INT_MIN                                 -32767 // -(215 - 1)
-    -- maximum value for an object of type int
-       INT_MAX                                +32767 // 215 - 1
-    -- maximum value for an object of type unsigned int
-       UINT_MAX                                65535 // 216 - 1
-    -- minimum value for an object of type long int
-       LONG_MIN                         -2147483647 // -(231 - 1)
-    -- maximum value for an object of type long int
-       LONG_MAX                         +2147483647 // 231 - 1
-    -- maximum value for an object of type unsigned long int
-       ULONG_MAX                         4294967295 // 232 - 1
-    -- minimum value for an object of type long long int
-       LLONG_MIN          -9223372036854775807 // -(263 - 1)
-    -- maximum value for an object of type long long int
-       LLONG_MAX          +9223372036854775807 // 263 - 1
-    -- maximum value for an object of type unsigned long long int
-       ULLONG_MAX         18446744073709551615 // 264 - 1
 

-
-
+
 
2   If the value of an object of type char is treated as a signed integer when used in an
     expression, the value of CHAR_MIN shall be the same as that of SCHAR_MIN and the
     value of CHAR_MAX shall be the same as that of SCHAR_MAX. Otherwise, the value of
     CHAR_MIN shall be 0 and the value of CHAR_MAX shall be the same as that of
-    UCHAR_MAX.20) The value UCHAR_MAX shall equal 2CHAR_BIT - 1.
-    Forward references: representations of types (6.2.6), conditional inclusion (6.10.1).
+    UCHAR_MAX.[20] The value UCHAR_MAX shall equal 2CHAR_BIT - 1.
+    Forward references: representations of types (6.2.6), conditional inclusion (6.10.1).
 

-
 
-
Footnote 20) See 6.2.5.
+
Footnote 20) See 6.2.5.
 

 
-
+
 

-
5.2.4.2.2 [Characteristics of floating types ]

-

-
-
+
5.2.4.2.2 [Characteristics of floating types <float.h>]

+
 
1   The characteristics of floating types are defined in terms of a model that describes a
     representation of floating-point numbers and values that provide information about an
-    implementation's floating-point arithmetic.21) The following parameters are used to
+    implementation's floating-point arithmetic.[21] The following parameters are used to
     define the model for each floating-point type:
-           s          sign (±1)
+           s          sign (\xB11)
            b          base or radix of exponent representation (an integer > 1)
            e          exponent (an integer between a minimum emin and a maximum emax )
            p          precision (the number of base-b digits in the significand)
             fk        nonnegative integers less than b (the significand digits)
 

-
 
 
Footnote 21) The floating-point model is intended to clarify the description of each floating-point characteristic and
         does not require the floating-point arithmetic of the implementation to be identical.
+    arithmetic operand.22)
 

 
-
+
 
2   A floating-point number ( x ) is defined by the following model:
                        p
            x = sb e
@@ -1947,8 +1597,7 @@ xviii                         Introduction
                            f k b-k ,   emin  e  emax
 
 

-
-
+
 
3   In addition to normalized floating-point numbers ( f 1 > 0 if x  0), floating types may be
     able to contain other kinds of floating-point numbers, such as subnormal floating-point
     numbers ( x  0, e = emin , f 1 = 0) and unnormalized floating-point numbers ( x  0,
@@ -1956,24 +1605,14 @@ xviii                         Introduction
     NaNs. A NaN is an encoding signifying Not-a-Number. A quiet NaN propagates
     through almost every arithmetic operation without raising a floating-point exception; a
     signaling NaN generally raises a floating-point exception when occurring as an
-
-    arithmetic operand.22)
 

-
-
-
Footnote 22) IEC 60559:1989 specifies quiet and signaling NaNs. For implementations that do not support
-        IEC 60559:1989, the terms quiet NaN and signaling NaN are intended to apply to encodings with
-        similar behavior.
-

-
-
+
 
4   An implementation may give zero and values that are not floating-point numbers (such as
     infinities and NaNs) a sign or may leave them unsigned. Wherever such values are
     unsigned, any requirement in this International Standard to retrieve the sign shall produce
     an unspecified sign, and any requirement to set the sign shall be ignored.
 

-
-
+
 
5   The minimum range of representable values for a floating type is the most negative finite
     floating-point number representable in that type through the most positive finite floating-
     point number representable in that type. In addition, if negative infinity is representable
@@ -1981,8 +1620,7 @@ xviii                         Introduction
     positive infinity is representable in a type, the range of that type is extended to all positive
     real numbers.
 

-
-
+
 
6   The accuracy of the floating-point operations (+, -, *, /) and of the library functions in
     <math.h> and <complex.h> that return floating-point results is implementation-
     defined, as is the accuracy of the conversion between floating-point internal
@@ -1990,8 +1628,7 @@ xviii                         Introduction
     <stdio.h>, <stdlib.h>, and <wchar.h>. The implementation may state that the
     accuracy is unknown.
 

-
-
+
 
7   All integer values in the <float.h> header, except FLT_ROUNDS, shall be constant
     expressions suitable for use in #if preprocessing directives; all floating values shall be
     constant expressions. All except DECIMAL_DIG, FLT_EVAL_METHOD, FLT_RADIX,
@@ -1999,10 +1636,9 @@ xviii                         Introduction
     point model representation is provided for all values except FLT_EVAL_METHOD and
     FLT_ROUNDS.
 

-
-
+
 
8   The rounding mode for floating-point addition is characterized by the implementation-
-    defined value of FLT_ROUNDS:23)
+    defined value of FLT_ROUNDS:[23]
           -1      indeterminable
            0      toward zero
            1      to nearest
@@ -2012,18 +1648,17 @@ xviii                         Introduction
     behavior.
 
 

-
 
 
Footnote 23) Evaluation of FLT_ROUNDS correctly reflects any execution-time change of rounding mode through
         the function fesetround in <fenv.h>.
 

 
-
+
 
9    Except for assignment and cast (which remove all extra range and precision), the values
      yielded by operators with floating operands and values subject to the usual arithmetic
      conversions and of floating constants are evaluated to a format whose range and precision
      may be greater than required by the type. The use of evaluation formats is characterized
-     by the implementation-defined value of FLT_EVAL_METHOD:24)
+     by the implementation-defined value of FLT_EVAL_METHOD:[24]
             -1         indeterminable;
               0        evaluate all operations and constants just to the range and precision of the
                        type;
@@ -2036,7 +1671,6 @@ xviii                         Introduction
      All other negative values for FLT_EVAL_METHOD characterize implementation-defined
      behavior.
 

-
 
 
Footnote 24) The evaluation method determines evaluation formats of expressions involving all floating types, not
          just real types. For example, if FLT_EVAL_METHOD is 1, then the product of two float
@@ -2044,15 +1678,14 @@ xviii                         Introduction
          double.
 

 
-
+
 
10   The presence or absence of subnormal numbers is characterized by the implementation-
      defined    values     of    FLT_HAS_SUBNORM,          DBL_HAS_SUBNORM,           and
      LDBL_HAS_SUBNORM:
-            -1       indeterminable25)
-             0       absent26) (type does not support subnormal numbers)
+            -1       indeterminable[25]
+             0       absent[26] (type does not support subnormal numbers)
              1       present (type does support subnormal numbers)
 

-
 
 
Footnote 25) Characterization as indeterminable is intended if floating-point operations do not consistently interpret
          subnormal representations as zero, nor as nonzero.
@@ -2061,15 +1694,6 @@ xviii                         Introduction
 
 
Footnote 26) Characterization as absent is intended if no floating-point operations produce subnormal results from
          non-subnormal inputs, even if the type format includes representations of subnormal numbers.
-

-
-
-
11   The values given in the following list shall be replaced by constant expressions with
-     implementation-defined values that are greater or equal in magnitude (absolute value) to
-     those shown, with the same sign:
-     -- radix of exponent representation, b
-        FLT_RADIX                                                    2
-
       -- number of base-FLT_RADIX digits in the floating-point significand, p
          FLT_MANT_DIG
          DBL_MANT_DIG
@@ -2078,7 +1702,6 @@ xviii                         Introduction
          can be rounded to a floating-point number with n decimal digits and back again
          without change to the value,
                p log10 b         if b is a power of 10
-              
                1 + p log10 b otherwise
          FLT_DECIMAL_DIG                                    6
          DBL_DECIMAL_DIG                                   10
@@ -2087,14 +1710,12 @@ xviii                         Introduction
          supported floating type with pmax radix b digits can be rounded to a floating-point
          number with n decimal digits and back again without change to the value,
                pmax log10 b        if b is a power of 10
-              
                1 + pmax log10 b otherwise
          DECIMAL_DIG                                      10
       -- number of decimal digits, q , such that any floating-point number with q decimal digits
          can be rounded into a floating-point number with p radix b digits and back again
          without change to the q decimal digits,
                p log10 b          if b is a power of 10
-              
                ( p - 1) log10 b otherwise
          FLT_DIG                                           6
          DBL_DIG                                          10
@@ -2105,8 +1726,7 @@ xviii                         Introduction
          DBL_MIN_EXP
          LDBL_MIN_EXP
            -- minimum negative integer such that 10 raised to that power is in the range of
-              normalized floating-point numbers, log10 b emin -1 
-                                                                 
+              normalized floating-point numbers, log10 b emin -1
               FLT_MIN_10_EXP                                 -37
               DBL_MIN_10_EXP                                 -37
               LDBL_MIN_10_EXP                                -37
@@ -2120,9 +1740,16 @@ xviii                         Introduction
           FLT_MAX_10_EXP                                +37
           DBL_MAX_10_EXP                                +37
           LDBL_MAX_10_EXP                               +37
-

+

 
-
+
+
11   The values given in the following list shall be replaced by constant expressions with
+     implementation-defined values that are greater or equal in magnitude (absolute value) to
+     those shown, with the same sign:
+     -- radix of exponent representation, b
+        FLT_RADIX                                                    2
+

+
 
12   The values given in the following list shall be replaced by constant expressions with
      implementation-defined values that are greater than or equal to those shown:
      -- maximum representable finite floating-point number, (1 - b- p )b emax
@@ -2130,8 +1757,7 @@ xviii                         Introduction
           DBL_MAX                                    1E+37
           LDBL_MAX                                   1E+37
 

-
-
+
 
13   The values given in the following list shall be replaced by constant expressions with
      implementation-defined (positive) values that are less than or equal to those shown:
      -- the difference between 1 and the least value greater than 1 that is representable in the
@@ -2143,24 +1769,22 @@ xviii                         Introduction
           FLT_MIN                                    1E-37
           DBL_MIN                                    1E-37
           LDBL_MIN                                   1E-37
-     -- minimum positive floating-point number27)
+     -- minimum positive floating-point number[27]
          FLT_TRUE_MIN                                        1E-37
          DBL_TRUE_MIN                                        1E-37
          LDBL_TRUE_MIN                                       1E-37
      Recommended practice
 

-
 
 
Footnote 27) If the presence or absence of subnormal numbers is indeterminable, then the value is intended to be a
          positive number no greater than the minimum normalized positive number for the type.
 

 
-
+
 
14   Conversion from (at least) double to decimal with DECIMAL_DIG digits and back
      should be the identity function.
 

-
-
+
 
15   EXAMPLE 1 The following describes an artificial floating-point representation that meets the minimum
      requirements of this International Standard, and the appropriate values in a <float.h> header for type
      float:
@@ -2175,17 +1799,16 @@ xviii                         Introduction
              FLT_DECIMAL_DIG                                   9
              FLT_DIG                                           6
              FLT_MIN_EXP                                     -31
-             FLT_MIN                             2.93873588E-39F
+             FLT_MIN                             2.93873588E-39F
              FLT_MIN_10_EXP                                  -38
              FLT_MAX_EXP                                     +32
-             FLT_MAX                             3.40282347E+38F
+             FLT_MAX                             3.40282347E+38F
              FLT_MAX_10_EXP                                  +38
 
 

-
-
+
 
16   EXAMPLE 2 The following describes floating-point representations that also meet the requirements for
-     single-precision and double-precision numbers in IEC 60559,28) and the appropriate values in a
+     single-precision and double-precision numbers in IEC 60559,[28] and the appropriate values in a
      <float.h> header for types float and double:
                         24
            x f = s 2e
@@ -2200,66 +1823,137 @@ xviii                         Introduction
              FLT_RADIX                                         2
              DECIMAL_DIG                                      17
              FLT_MANT_DIG                                     24
-             FLT_EPSILON                         1.19209290E-07F // decimal constant
+             FLT_EPSILON                         1.19209290E-07F // decimal constant
              FLT_EPSILON                                0X1P-23F // hex constant
              FLT_DECIMAL_DIG                                   9
+     [28] The floating-point model in that standard sums powers of b from zero, so the values of the exponent
+         limits are one less than shown here.
 
         FLT_DIG                             6
         FLT_MIN_EXP                      -125
-        FLT_MIN               1.17549435E-38F               //   decimal constant
+        FLT_MIN               1.17549435E-38F               //   decimal constant
         FLT_MIN                     0X1P-126F               //   hex constant
-        FLT_TRUE_MIN          1.40129846E-45F               //   decimal constant
+        FLT_TRUE_MIN          1.40129846E-45F               //   decimal constant
         FLT_TRUE_MIN                0X1P-149F               //   hex constant
         FLT_HAS_SUBNORM                     1
         FLT_MIN_10_EXP                    -37
         FLT_MAX_EXP                      +128
-        FLT_MAX               3.40282347E+38F               // decimal constant
+        FLT_MAX               3.40282347E+38F               // decimal constant
         FLT_MAX               0X1.fffffeP127F               // hex constant
         FLT_MAX_10_EXP                    +38
         DBL_MANT_DIG                       53
-        DBL_EPSILON    2.2204460492503131E-16               // decimal constant
+        DBL_EPSILON    2.2204460492503131E-16               // decimal constant
         DBL_EPSILON                   0X1P-52               // hex constant
         DBL_DECIMAL_DIG                    17
         DBL_DIG                            15
         DBL_MIN_EXP                     -1021
-        DBL_MIN      2.2250738585072014E-308                //   decimal constant
+        DBL_MIN      2.2250738585072014E-308                //   decimal constant
         DBL_MIN                     0X1P-1022               //   hex constant
-        DBL_TRUE_MIN 4.9406564584124654E-324                //   decimal constant
+        DBL_TRUE_MIN 4.9406564584124654E-324                //   decimal constant
         DBL_TRUE_MIN                0X1P-1074               //   hex constant
         DBL_HAS_SUBNORM                     1
         DBL_MIN_10_EXP                   -307
         DBL_MAX_EXP                     +1024
-        DBL_MAX      1.7976931348623157E+308                // decimal constant
+        DBL_MAX      1.7976931348623157E+308                // decimal constant
         DBL_MAX        0X1.fffffffffffffP1023               // hex constant
         DBL_MAX_10_EXP                   +308
 If a type wider than double were supported, then DECIMAL_DIG would be greater than 17. For
 example, if the widest type were to use the minimal-width IEC 60559 double-extended format (64 bits of
 precision), then DECIMAL_DIG would be 21.
 
-Forward references:         conditional inclusion (6.10.1), complex arithmetic
-<complex.h> (7.3), extended multibyte and wide character utilities <wchar.h>
-(7.29), floating-point environment <fenv.h> (7.6), general utilities <stdlib.h>
-(7.22), input/output <stdio.h> (7.21), mathematics <math.h> (7.12).
+Forward references:         conditional inclusion (6.10.1), complex arithmetic
+<complex.h> (7.3), extended multibyte and wide character utilities <wchar.h>
+(7.29), floating-point environment <fenv.h> (7.6), general utilities <stdlib.h>
+(7.22), input/output <stdio.h> (7.21), mathematics <math.h> (7.12).
 
 

+
+
Footnote 28) The floating-point model in that standard sums powers of b from zero, so the values of the exponent
+         limits are one less than shown here.
+        FLT_DIG                             6
+        FLT_MIN_EXP                      -125
+        FLT_MIN               1.17549435E-38F               //   decimal constant
+        FLT_MIN                     0X1P-126F               //   hex constant
+        FLT_TRUE_MIN          1.40129846E-45F               //   decimal constant
+        FLT_TRUE_MIN                0X1P-149F               //   hex constant
+        FLT_HAS_SUBNORM                     1
+        FLT_MIN_10_EXP                    -37
+        FLT_MAX_EXP                      +128
+        FLT_MAX               3.40282347E+38F               // decimal constant
+        FLT_MAX               0X1.fffffeP127F               // hex constant
+        FLT_MAX_10_EXP                    +38
+        DBL_MANT_DIG                       53
+        DBL_EPSILON    2.2204460492503131E-16               // decimal constant
+        DBL_EPSILON                   0X1P-52               // hex constant
+        DBL_DECIMAL_DIG                    17
+        DBL_DIG                            15
+        DBL_MIN_EXP                     -1021
+        DBL_MIN      2.2250738585072014E-308                //   decimal constant
+        DBL_MIN                     0X1P-1022               //   hex constant
+        DBL_TRUE_MIN 4.9406564584124654E-324                //   decimal constant
+        DBL_TRUE_MIN                0X1P-1074               //   hex constant
+        DBL_HAS_SUBNORM                     1
+        DBL_MIN_10_EXP                   -307
+        DBL_MAX_EXP                     +1024
+        DBL_MAX      1.7976931348623157E+308                // decimal constant
+        DBL_MAX        0X1.fffffffffffffP1023               // hex constant
+        DBL_MAX_10_EXP                   +308
+If a type wider than double were supported, then DECIMAL_DIG would be greater than 17. For
+example, if the widest type were to use the minimal-width IEC 60559 double-extended format (64 bits of
+precision), then DECIMAL_DIG would be 21.
+Forward references:         conditional inclusion (6.10.1), complex arithmetic
+<complex.h> (7.3), extended multibyte and wide character utilities <wchar.h>
+(7.29), floating-point environment <fenv.h> (7.6), general utilities <stdlib.h>
+(7.22), input/output <stdio.h> (7.21), mathematics <math.h> (7.12).
+

 
 
 
Footnote 28) The floating-point model in that standard sums powers of b from zero, so the values of the exponent
          limits are one less than shown here.
+        FLT_DIG                             6
+        FLT_MIN_EXP                      -125
+        FLT_MIN               1.17549435E-38F               //   decimal constant
+        FLT_MIN                     0X1P-126F               //   hex constant
+        FLT_TRUE_MIN          1.40129846E-45F               //   decimal constant
+        FLT_TRUE_MIN                0X1P-149F               //   hex constant
+        FLT_HAS_SUBNORM                     1
+        FLT_MIN_10_EXP                    -37
+        FLT_MAX_EXP                      +128
+        FLT_MAX               3.40282347E+38F               // decimal constant
+        FLT_MAX               0X1.fffffeP127F               // hex constant
+        FLT_MAX_10_EXP                    +38
+        DBL_MANT_DIG                       53
+        DBL_EPSILON    2.2204460492503131E-16               // decimal constant
+        DBL_EPSILON                   0X1P-52               // hex constant
+        DBL_DECIMAL_DIG                    17
+        DBL_DIG                            15
+        DBL_MIN_EXP                     -1021
+        DBL_MIN      2.2250738585072014E-308                //   decimal constant
+        DBL_MIN                     0X1P-1022               //   hex constant
+        DBL_TRUE_MIN 4.9406564584124654E-324                //   decimal constant
+        DBL_TRUE_MIN                0X1P-1074               //   hex constant
+        DBL_HAS_SUBNORM                     1
+        DBL_MIN_10_EXP                   -307
+        DBL_MAX_EXP                     +1024
+        DBL_MAX      1.7976931348623157E+308                // decimal constant
+        DBL_MAX        0X1.fffffffffffffP1023               // hex constant
+        DBL_MAX_10_EXP                   +308
+If a type wider than double were supported, then DECIMAL_DIG would be greater than 17. For
+example, if the widest type were to use the minimal-width IEC 60559 double-extended format (64 bits of
+precision), then DECIMAL_DIG would be 21.
+Forward references:         conditional inclusion (6.10.1), complex arithmetic
+<complex.h> (7.3), extended multibyte and wide character utilities <wchar.h>
+(7.29), floating-point environment <fenv.h> (7.6), general utilities <stdlib.h>
+(7.22), input/output <stdio.h> (7.21), mathematics <math.h> (7.12).
 

 
-
+
 

 
6. [Language]

-
 Language
-

-
-
+
 

 
6.1 [Notation]

-

-
-
+
 
1   In the syntax notation used in this clause, syntactic categories (nonterminals) are
     indicated by italic type, and literal words and character set members (terminals) by bold
     type. A colon (:) following a nonterminal introduces its definition. Alternative
@@ -2268,28 +1962,20 @@ Forward references:         conditional inclusion (6.10.1), complex arithmetic
              { expressionopt }
     indicates an optional expression enclosed in braces.
 

-
-
+
 
2   When syntactic categories are referred to in the main text, they are not italicized and
     words are separated by spaces instead of hyphens.
 

-
-
+
 
3   A summary of the language syntax is given in annex A.
 

-
-
+
 

 
6.2 [Concepts]

-
 Concepts
-

-
-
+
 

 
6.2.1 [Scopes of identifiers]

-

-
-
+
 
1   An identifier can denote an object; a function; a tag or a member of a structure, union, or
     enumeration; a typedef name; a label name; a macro name; or a macro parameter. The
     same identifier can denote different entities at different points in the program. A member
@@ -2298,22 +1984,19 @@ Forward references:         conditional inclusion (6.10.1), complex arithmetic
     program translation any occurrences of macro names in the source file are replaced by the
     preprocessing token sequences that constitute their macro definitions.
 

-
-
+
 
2   For each different entity that an identifier designates, the identifier is visible (i.e., can be
     used) only within a region of program text called its scope. Different entities designated
     by the same identifier either have different scopes, or are in different name spaces. There
     are four kinds of scopes: function, file, block, and function prototype. (A function
     prototype is a declaration of a function that declares the types of its parameters.)
 

-
-
+
 
3   A label name is the only kind of identifier that has function scope. It can be used (in a
     goto statement) anywhere in the function in which it appears, and is declared implicitly
     by its syntactic appearance (followed by a : and a statement).
 

-
-
+
 
4   Every other identifier has scope determined by the placement of its declaration (in a
     declarator or type specifier). If the declarator or type specifier that declares the identifier
     appears outside of any block or list of parameters, the identifier has file scope, which
@@ -2330,107 +2013,91 @@ Forward references:         conditional inclusion (6.10.1), complex arithmetic
     identifier designates the entity declared in the inner scope; the entity declared in the outer
     scope is hidden (and not visible) within the inner scope.
 

-
-
+
 
5   Unless explicitly stated otherwise, where this International Standard uses the term
     ``identifier'' to refer to some entity (as opposed to the syntactic construct), it refers to the
     entity in the relevant name space whose declaration is visible at the point the identifier
     occurs.
 

-
-
+
 
6   Two identifiers have the same scope if and only if their scopes terminate at the same
     point.
 

-
-
+
 
7   Structure, union, and enumeration tags have scope that begins just after the appearance of
     the tag in a type specifier that declares the tag. Each enumeration constant has scope that
     begins just after the appearance of its defining enumerator in an enumerator list. Any
     other identifier has scope that begins just after the completion of its declarator.
 

-
-
+
 
8   As a special case, a type name (which is not a declaration of an identifier) is considered to
     have a scope that begins just after the place within the type name where the omitted
     identifier would appear were it not omitted.
-    Forward references: declarations (6.7), function calls (6.5.2.2), function definitions
-    (6.9.1), identifiers (6.4.2), macro replacement (6.10.3), name spaces of identifiers (6.2.3),
-    source file inclusion (6.10.2), statements (6.8).
+    Forward references: declarations (6.7), function calls (6.5.2.2), function definitions
+    (6.9.1), identifiers (6.4.2), macro replacement (6.10.3), name spaces of identifiers (6.2.3),
+    source file inclusion (6.10.2), statements (6.8).
 

-
-
+
 

 
6.2.2 [Linkages of identifiers]

-

-
-
+
 
1   An identifier declared in different scopes or in the same scope more than once can be
-    made to refer to the same object or function by a process called linkage.29) There are
+    made to refer to the same object or function by a process called linkage.[29] There are
     three kinds of linkage: external, internal, and none.
 

-
 
 
Footnote 29) There is no linkage between different identifiers.
 

 
-
+
 
2   In the set of translation units and libraries that constitutes an entire program, each
     declaration of a particular identifier with external linkage denotes the same object or
     function. Within one translation unit, each declaration of an identifier with internal
     linkage denotes the same object or function. Each declaration of an identifier with no
     linkage denotes a unique entity.
 

-
-
+
 
3   If the declaration of a file scope identifier for an object or a function contains the storage-
-    class specifier static, the identifier has internal linkage.30)
+    class specifier static, the identifier has internal linkage.[30]
 
 

-
 
 
Footnote 30) A function declaration can contain the storage-class specifier static only if it is at file scope; see
-        6.7.1.
+        6.7.1.
 

 
-
+
 
4   For an identifier declared with the storage-class specifier extern in a scope in which a
-    prior declaration of that identifier is visible,31) if the prior declaration specifies internal or
+    prior declaration of that identifier is visible,[31] if the prior declaration specifies internal or
     external linkage, the linkage of the identifier at the later declaration is the same as the
     linkage specified at the prior declaration. If no prior declaration is visible, or if the prior
     declaration specifies no linkage, then the identifier has external linkage.
 

-
 
-
Footnote 31) As specified in 6.2.1, the later declaration might hide the prior declaration.
+
Footnote 31) As specified in 6.2.1, the later declaration might hide the prior declaration.
 

 
-
+
 
5   If the declaration of an identifier for a function has no storage-class specifier, its linkage
     is determined exactly as if it were declared with the storage-class specifier extern. If
     the declaration of an identifier for an object has file scope and no storage-class specifier,
     its linkage is external.
 

-
-
+
 
6   The following identifiers have no linkage: an identifier declared to be anything other than
     an object or a function; an identifier declared to be a function parameter; a block scope
     identifier for an object declared without the storage-class specifier extern.
 

-
-
+
 
7   If, within a translation unit, the same identifier appears with both internal and external
     linkage, the behavior is undefined.
-    Forward references: declarations (6.7), expressions (6.5), external definitions (6.9),
-    statements (6.8).
+    Forward references: declarations (6.7), expressions (6.5), external definitions (6.9),
+    statements (6.8).
 

-
-
+
 

 
6.2.3 [Name spaces of identifiers]

-

-
-
+
 
1   If more than one declaration of a particular identifier is visible at any point in a
     translation unit, the syntactic context disambiguates uses that refer to different entities.
     Thus, there are separate name spaces for various categories of identifiers, as follows:
@@ -2442,30 +2109,25 @@ Forward references:         conditional inclusion (6.10.1), complex arithmetic
        member via the . or -> operator);
     -- all other identifiers, called ordinary identifiers (declared in ordinary declarators or as
        enumeration constants).
-    Forward references: enumeration specifiers (6.7.2.2), labeled statements (6.8.1),
-    structure and union specifiers (6.7.2.1), structure and union members (6.5.2.3), tags
-    (6.7.2.3), the goto statement (6.8.6.1).
+    Forward references: enumeration specifiers (6.7.2.2), labeled statements (6.8.1),
+    structure and union specifiers (6.7.2.1), structure and union members (6.5.2.3), tags
+    (6.7.2.3), the goto statement (6.8.6.1).
 
 

-
-
+
 

 
6.2.4 [Storage durations of objects]

-

-
-
+
 
1   An object has a storage duration that determines its lifetime. There are four storage
-    durations: static, thread, automatic, and allocated. Allocated storage is described in 7.22.3.
+    durations: static, thread, automatic, and allocated. Allocated storage is described in 7.22.3.
 

-
-
+
 
2   The lifetime of an object is the portion of program execution during which storage is
-    guaranteed to be reserved for it. An object exists, has a constant address,33) and retains
-    its last-stored value throughout its lifetime.34) If an object is referred to outside of its
+    guaranteed to be reserved for it. An object exists, has a constant address,[33] and retains
+    its last-stored value throughout its lifetime.[34] If an object is referred to outside of its
     lifetime, the behavior is undefined. The value of a pointer becomes indeterminate when
     the object it points to (or just past) reaches the end of its lifetime.
 

-
 
 
Footnote 33) The term ``constant address'' means that two pointers to the object constructed at possibly different
         times will compare equal. The address may be different during two different executions of the same
@@ -2476,14 +2138,13 @@ Forward references:         conditional inclusion (6.10.1), complex arithmetic
 
Footnote 34) In the case of a volatile object, the last store need not be explicit in the program.
 

 
-
+
 
3   An object whose identifier is declared without the storage-class specifier
     _Thread_local, and either with external or internal linkage or with the storage-class
     specifier static, has static storage duration. Its lifetime is the entire execution of the
     program and its stored value is initialized only once, prior to program startup.
 

-
-
+
 
4   An object whose identifier is declared with the storage-class specifier _Thread_local
     has thread storage duration. Its lifetime is the entire execution of the thread for which it
     is created, and its stored value is initialized when the thread is started. There is a distinct
@@ -2492,15 +2153,13 @@ Forward references:         conditional inclusion (6.10.1), complex arithmetic
     indirectly access an object with thread storage duration from a thread other than the one
     with which the object is associated is implementation-defined.
 

-
-
+
 
5   An object whose identifier is declared with no linkage and without the storage-class
     specifier static has automatic storage duration, as do some compound literals. The
     result of attempting to indirectly access an object with automatic storage duration from a
     thread other than the one with which the object is associated is implementation-defined.
 

-
-
+
 
6   For such an object that does not have a variable length array type, its lifetime extends
     from entry into the block with which it is associated until execution of that block ends in
     any way. (Entering an enclosed block or calling a function suspends, but does not end,
@@ -2511,79 +2170,70 @@ Forward references:         conditional inclusion (6.10.1), complex arithmetic
     indeterminate each time the declaration is reached.
 
 

-
-
+
 
7   For such an object that does have a variable length array type, its lifetime extends from
     the declaration of the object until execution of the program leaves the scope of the
-    declaration.35) If the scope is entered recursively, a new instance of the object is created
+    declaration.[35] If the scope is entered recursively, a new instance of the object is created
     each time. The initial value of the object is indeterminate.
 

-
 
 
Footnote 35) Leaving the innermost block containing the declaration, or jumping to a point in that block or an
         embedded block prior to the declaration, leaves the scope of the declaration.
 

 
-
+
 
8   A non-lvalue expression with structure or union type, where the structure or union
     contains a member with array type (including, recursively, members of all contained
     structures and unions) refers to an object with automatic storage duration and temporary
-    lifetime.36) Its lifetime begins when the expression is evaluated and its initial value is the
+    lifetime.[36] Its lifetime begins when the expression is evaluated and its initial value is the
     value of the expression. Its lifetime ends when the evaluation of the containing full
     expression or full declarator ends. Any attempt to modify an object with temporary
     lifetime results in undefined behavior.
-    Forward references: array declarators (6.7.6.2), compound literals (6.5.2.5), declarators
-    (6.7.6), function calls (6.5.2.2), initialization (6.7.9), statements (6.8).
+    Forward references: array declarators (6.7.6.2), compound literals (6.5.2.5), declarators
+    (6.7.6), function calls (6.5.2.2), initialization (6.7.9), statements (6.8).
 

-
 
 
Footnote 36) The address of such an object is taken implicitly when an array member is accessed.
 

 
-
+
 

 
6.2.5 [Types]

-

-
-
+
 
1   The meaning of a value stored in an object or returned by a function is determined by the
     type of the expression used to access it. (An identifier declared to be an object is the
     simplest such expression; the type is specified in the declaration of the identifier.) Types
     are partitioned into object types (types that describe objects) and function types (types
     that describe functions). At various points within a translation unit an object type may be
     incomplete (lacking sufficient information to determine the size of objects of that type) or
-    complete (having sufficient information).37)
+    complete (having sufficient information).[37]
 

-
 
 
Footnote 37) A type may be incomplete or complete throughout an entire translation unit, or it may change states at
         different points within a translation unit.
 

 
-
+
 
2   An object declared as type _Bool is large enough to store the values 0 and 1.
 

-
-
+
 
3   An object declared as type char is large enough to store any member of the basic
     execution character set. If a member of the basic execution character set is stored in a
     char object, its value is guaranteed to be nonnegative. If any other character is stored in
     a char object, the resulting value is implementation-defined but shall be within the range
     of values that can be represented in that type.
 

-
-
+
 
4   There are five standard signed integer types, designated as signed char, short
     int, int, long int, and long long int. (These and other types may be
-    designated in several additional ways, as described in 6.7.2.) There may also be
-    implementation-defined extended signed integer types.38) The standard and extended
-    signed integer types are collectively called signed integer types.39)
+    designated in several additional ways, as described in 6.7.2.) There may also be
+    implementation-defined extended signed integer types.[38] The standard and extended
+    signed integer types are collectively called signed integer types.[39]
 
 

-
 
 
Footnote 38) Implementation-defined keywords shall have the form of an identifier reserved for any use as
-         described in 7.1.3.
+         described in 7.1.3.
 

 
 
@@ -2591,14 +2241,13 @@ Forward references:         conditional inclusion (6.10.1), complex arithmetic
          signed integer types.
 

 
-
+
 
5    An object declared as type signed char occupies the same amount of storage as a
      ``plain'' char object. A ``plain'' int object has the natural size suggested by the
      architecture of the execution environment (large enough to contain any value in the range
      INT_MIN to INT_MAX as defined in the header <limits.h>).
 

-
-
+
 
6    For each of the signed integer types, there is a corresponding (but different) unsigned
      integer type (designated with the keyword unsigned) that uses the same amount of
      storage (including sign information) and has the same alignment requirements. The type
@@ -2606,126 +2255,112 @@ Forward references:         conditional inclusion (6.10.1), complex arithmetic
      types are the standard unsigned integer types. The unsigned integer types that
      correspond to the extended signed integer types are the extended unsigned integer types.
      The standard and extended unsigned integer types are collectively called unsigned integer
-     types.40)
+     types.[40]
 

-
 
 
Footnote 40) Therefore, any statement in this Standard about unsigned integer types also applies to the extended
          unsigned integer types.
 

 
-
+
 
7    The standard signed integer types and standard unsigned integer types are collectively
      called the standard integer types, the extended signed integer types and extended
      unsigned integer types are collectively called the extended integer types.
 

-
-
+
 
8    For any two integer types with the same signedness and different integer conversion rank
-     (see 6.3.1.1), the range of values of the type with smaller integer conversion rank is a
+     (see 6.3.1.1), the range of values of the type with smaller integer conversion rank is a
      subrange of the values of the other type.
 

-
-
+
 
9    The range of nonnegative values of a signed integer type is a subrange of the
      corresponding unsigned integer type, and the representation of the same value in each
-     type is the same.41) A computation involving unsigned operands can never overflow,
+     type is the same.[41] A computation involving unsigned operands can never overflow,
      because a result that cannot be represented by the resulting unsigned integer type is
      reduced modulo the number that is one greater than the largest value that can be
      represented by the resulting type.
 

-
 
 
Footnote 41) The same representation and alignment requirements are meant to imply interchangeability as
          arguments to functions, return values from functions, and members of unions.
 

 
-
+
 
10   There are three real floating types, designated as float, double, and long
-     double.42) The set of values of the type float is a subset of the set of values of the
+     double.[42] The set of values of the type float is a subset of the set of values of the
      type double; the set of values of the type double is a subset of the set of values of the
      type long double.
 
 

-
 
-
Footnote 42) See ``future language directions'' (6.11.1).
+
Footnote 42) See ``future language directions'' (6.11.1).
 

 
-
+
 
11   There are three complex types, designated as float _Complex, double
-     _Complex, and long double _Complex.43) (Complex types are a conditional
-     feature that implementations need not support; see 6.10.8.3.) The real floating and
+     _Complex, and long double _Complex.[43] (Complex types are a conditional
+     feature that implementations need not support; see 6.10.8.3.) The real floating and
      complex types are collectively called the floating types.
 

-
 
 
Footnote 43) A specification for imaginary types is in annex G.
 

 
-
+
 
12   For each floating type there is a corresponding real type, which is always a real floating
      type. For real floating types, it is the same type. For complex types, it is the type given
      by deleting the keyword _Complex from the type name.
 

-
-
+
 
13   Each complex type has the same representation and alignment requirements as an array
      type containing exactly two elements of the corresponding real type; the first element is
      equal to the real part, and the second element to the imaginary part, of the complex
      number.
 

-
-
+
 
14   The type char, the signed and unsigned integer types, and the floating types are
      collectively called the basic types. The basic types are complete object types. Even if the
      implementation defines two or more basic types to have the same representation, they are
-     nevertheless different types.44)
+     nevertheless different types.[44]
 

-
 
 
Footnote 44) An implementation may define new keywords that provide alternative ways to designate a basic (or
          any other) type; this does not violate the requirement that all basic types be different.
          Implementation-defined keywords shall have the form of an identifier reserved for any use as
-         described in 7.1.3.
+         described in 7.1.3.
 

 
-
+
 
15   The three types char, signed char, and unsigned char are collectively called
      the character types. The implementation shall define char to have the same range,
-     representation, and behavior as either signed char or unsigned char.45)
+     representation, and behavior as either signed char or unsigned char.[45]
 

-
 
 
Footnote 45) CHAR_MIN, defined in <limits.h>, will have one of the values 0 or SCHAR_MIN, and this can be
          used to distinguish the two options. Irrespective of the choice made, char is a separate type from the
          other two and is not compatible with either.
 

 
-
+
 
16   An enumeration comprises a set of named integer constant values. Each distinct
      enumeration constitutes a different enumerated type.
 

-
-
+
 
17   The type char, the signed and unsigned integer types, and the enumerated types are
      collectively called integer types. The integer and real floating types are collectively called
      real types.
 

-
-
+
 
18   Integer and floating types are collectively called arithmetic types. Each arithmetic type
      belongs to one type domain: the real type domain comprises the real types, the complex
      type domain comprises the complex types.
 

-
-
+
 
19   The void type comprises an empty set of values; it is an incomplete object type that
      cannot be completed.
 
 

-
-
+
 
20   Any number of derived types can be constructed from the object and function types, as
      follows:
      -- An array type describes a contiguously allocated nonempty set of objects with a
@@ -2753,66 +2388,58 @@ Forward references:         conditional inclusion (6.10.1), complex arithmetic
         object type.
      -- An atomic type describes the type designated by the construct _Atomic ( type-
         name ). (Atomic types are a conditional feature that implementations need not
-        support; see 6.10.8.3.)
+        support; see 6.10.8.3.)
      These methods of constructing derived types can be applied recursively.
 

-
-
+
 
21   Arithmetic types and pointer types are collectively called scalar types. Array and
-     structure types are collectively called aggregate types.46)
+     structure types are collectively called aggregate types.[46]
 

-
 
 
Footnote 46) Note that aggregate type does not include union type because an object with union type can only
          contain one member at a time.
-

-
-
-
22   An array type of unknown size is an incomplete type. It is completed, for an identifier of
-     that type, by specifying the size in a later declaration (with internal or external linkage).
-     A structure or union type of unknown content (as described in 6.7.2.3) is an incomplete
-
      type. It is completed, for all declarations of that type, by declaring the same structure or
      union tag with its defining content later in the same scope.
-

+

 
-
+
+
22   An array type of unknown size is an incomplete type. It is completed, for an identifier of
+     that type, by specifying the size in a later declaration (with internal or external linkage).
+     A structure or union type of unknown content (as described in 6.7.2.3) is an incomplete
+

+
 
23   A type has known constant size if the type is not incomplete and is not a variable length
      array type.
 

-
-
+
 
24   Array, function, and pointer types are collectively called derived declarator types. A
      declarator type derivation from a type T is the construction of a derived declarator type
-     from T by the application of an array-type, a function-type, or a pointer-type derivation to
-     T.
+     from T by the application of an array-type, a function-type, or a pointer-type derivation to T.
 

-
-
+
 
25   A type is characterized by its type category , which is either the outermost derivation of a
      derived type (as noted above in the construction of derived types), or the type itself if the
      type consists of no derived types.
 

-
-
+
 
26   Any type so far mentioned is an unqualified type. Each unqualified type has several
-     qualified versions of its type,47) corresponding to the combinations of one, two, or all
+     qualified versions of its type,[47] corresponding to the combinations of one, two, or all
      three of the const, volatile, and restrict qualifiers. The qualified or unqualified
      versions of a type are distinct types that belong to the same type category and have the
-     same representation and alignment requirements.48) A derived type is not qualified by the
+     same representation and alignment requirements.[48] A derived type is not qualified by the
      qualifiers (if any) of the type from which it is derived.
 

-
 
-
Footnote 47) See 6.7.3 regarding qualified array and function types.
+
Footnote 47) See 6.7.3 regarding qualified array and function types.
 

 
 
 
Footnote 48) The same representation and alignment requirements are meant to imply interchangeability as
          arguments to functions, return values from functions, and members of unions.
+     qualified float'' and is a pointer to a qualified type.
 

 
-
+
 
27   Further, there is the _Atomic qualifier. The presence of the _Atomic qualifier
      designates an atomic type. The size, representation, and alignment of an atomic type
      need not be the same as those of the corresponding unqualified type. Therefore, this
@@ -2821,65 +2448,52 @@ Forward references:         conditional inclusion (6.10.1), complex arithmetic
      The phrase ``qualified or unqualified type'', without specific mention of atomic, does not
      include the atomic types.
 

-
-
+
 
28   A pointer to void shall have the same representation and alignment requirements as a
-     pointer to a character type.48) Similarly, pointers to qualified or unqualified versions of
+     pointer to a character type.[48] Similarly, pointers to qualified or unqualified versions of
      compatible types shall have the same representation and alignment requirements. All
      pointers to structure types shall have the same representation and alignment requirements
      as each other. All pointers to union types shall have the same representation and
      alignment requirements as each other. Pointers to other types need not have the same
      representation or alignment requirements.
 

-
 
 
Footnote 48) The same representation and alignment requirements are meant to imply interchangeability as
          arguments to functions, return values from functions, and members of unions.
+     qualified float'' and is a pointer to a qualified type.
 

 
-
+
 
29   EXAMPLE 1 The type designated as ``float *'' has type ``pointer to float''. Its type category is
      pointer, not a floating type. The const-qualified version of this type is designated as ``float * const''
      whereas the type designated as ``const float *'' is not a qualified type -- its type is ``pointer to const-
 
-     qualified float'' and is a pointer to a qualified type.
-
 

-
-
+
 
30   EXAMPLE 2 The type designated as ``struct tag (*[5])(float)'' has type ``array of pointer to
      function returning struct tag''. The array has length five and the function has a single parameter of type
      float. Its type category is array.
 
-     Forward references: compatible type and composite type (6.2.7), declarations (6.7).
+     Forward references: compatible type and composite type (6.2.7), declarations (6.7).
 

-
-
+
 

 
6.2.6 [Representations of types]

-
 Representations of types
-

-
-
+
 

 
6.2.6.1 [General]

-

-
-
+
 
1    The representations of all types are unspecified except as stated in this subclause.
 

-
-
+
 
2    Except for bit-fields, objects are composed of contiguous sequences of one or more bytes,
      the number, order, and encoding of which are either explicitly specified or
      implementation-defined.
 

-
-
+
 
3    Values stored in unsigned bit-fields and objects of type unsigned char shall be
-     represented using a pure binary notation.49)
+     represented using a pure binary notation.[49]
 

-
 
 
Footnote 49) A positional representation for integers that uses the binary digits 0 and 1, in which the values
          represented by successive bits are additive, begin with 1, and are multiplied by successive integral
@@ -2890,8 +2504,8 @@ Forward references:         conditional inclusion (6.10.1), complex arithmetic
                                                              - 1.
 

 
-
-
4    Values stored in non-bit-field objects of any other object type consist of n × CHAR_BIT
+
+
4    Values stored in non-bit-field objects of any other object type consist of n \xD7 CHAR_BIT
      bits, where n is the size of an object of that type, in bytes. The value may be copied into
      an object of type unsigned char [n] (e.g., by memcpy); the resulting set of bytes is
      called the object representation of the value. Values stored in bit-fields consist of m bits,
@@ -2900,48 +2514,42 @@ Forward references:         conditional inclusion (6.10.1), complex arithmetic
      than NaNs) with the same object representation compare equal, but values that compare
      equal may have different object representations.
 

-
-
+
 
5    Certain object representations need not represent a value of the object type. If the stored
      value of an object has such a representation and is read by an lvalue expression that does
      not have character type, the behavior is undefined. If such a representation is produced
      by a side effect that modifies all or any part of the object by an lvalue expression that
-     does not have character type, the behavior is undefined.50) Such a representation is called
+     does not have character type, the behavior is undefined.[50] Such a representation is called
      a trap representation.
 

-
 
 
Footnote 50) Thus, an automatic variable can be initialized to a trap representation without causing undefined
          behavior, but the value of the variable cannot be used until a proper value is stored in it.
-

-
-
-
6    When a value is stored in an object of structure or union type, including in a member
-     object, the bytes of the object representation that correspond to any padding bytes take
-     unspecified values.51) The value of a structure or union object is never a trap
-
     representation, even though the value of a member of the structure or union object may be
     a trap representation.
-

+

 
+
+
6    When a value is stored in an object of structure or union type, including in a member
+     object, the bytes of the object representation that correspond to any padding bytes take
+     unspecified values.[51] The value of a structure or union object is never a trap
+

 
 
Footnote 51) Thus, for example, structure assignment need not copy any padding bits.
 

 
-
+
 
7   When a value is stored in a member of an object of union type, the bytes of the object
     representation that do not correspond to that member but do correspond to other members
     take unspecified values.
 

-
-
+
 
8   Where an operator is applied to a value that has more than one object representation,
-    which object representation is used shall not affect the value of the result.52) Where a
+    which object representation is used shall not affect the value of the result.[52] Where a
     value is stored in an object using a type that has more than one object representation for
     that value, it is unspecified which representation is used, but a trap representation shall
     not be generated.
 

-
 
 
Footnote 52) It is possible for objects x and y with the same effective type T to have the same value when they are
         accessed as objects of type T, but to have different values in other contexts. In particular, if == is
@@ -2950,43 +2558,29 @@ Forward references:         conditional inclusion (6.10.1), complex arithmetic
         on values of type T may distinguish between them.
 

 
-
+
 
9   Loads and stores of objects with                             atomic      types      are     done      with
     memory_order_seq_cst semantics.
-    Forward references: declarations (6.7), expressions (6.5), lvalues, arrays, and function
-    designators (6.3.2.1), order and consistency (7.17.3).
+    Forward references: declarations (6.7), expressions (6.5), lvalues, arrays, and function
+    designators (6.3.2.1), order and consistency (7.17.3).
 

-
-
+
 

 
6.2.6.2 [Integer types]

-

-
-
+
 
1   For unsigned integer types other than unsigned char, the bits of the object
     representation shall be divided into two groups: value bits and padding bits (there need
     not be any of the latter). If there are N value bits, each bit shall represent a different
     power of 2 between 1 and 2 N -1 , so that objects of that type shall be capable of
     representing values from 0 to 2 N - 1 using a pure binary representation; this shall be
-    known as the value representation. The values of any padding bits are unspecified.53)
+    known as the value representation. The values of any padding bits are unspecified.[53]
 

-
 
 
Footnote 53) Some combinations of padding bits might generate trap representations, for example, if one padding
         bit is a parity bit. Regardless, no arithmetic operation on valid values can generate a trap
         representation other than as part of an exceptional condition such as an overflow, and this cannot occur
         with unsigned types. All other combinations of padding bits are alternative object representations of
         the value specified by the value bits.
-

-
-
-
2   For signed integer types, the bits of the object representation shall be divided into three
-    groups: value bits, padding bits, and the sign bit. There need not be any padding bits;
-    signed char shall not have any padding bits. There shall be exactly one sign bit.
-    Each bit that is a value bit shall have the same value as the same bit in the object
-    representation of the corresponding unsigned type (if there are M value bits in the signed
-    type and N in the unsigned type, then M  N ). If the sign bit is zero, it shall not affect
-
     the resulting value. If the sign bit is one, the value shall be modified in one of the
     following ways:
     -- the corresponding value with sign bit 0 is negated (sign and magnitude);
@@ -2997,9 +2591,17 @@ Forward references:         conditional inclusion (6.10.1), complex arithmetic
     complement), is a trap representation or a normal value. In the case of sign and
     magnitude and ones' complement, if this representation is a normal value it is called a
     negative zero.
-

+

 
-
+
+
2   For signed integer types, the bits of the object representation shall be divided into three
+    groups: value bits, padding bits, and the sign bit. There need not be any padding bits;
+    signed char shall not have any padding bits. There shall be exactly one sign bit.
+    Each bit that is a value bit shall have the same value as the same bit in the object
+    representation of the corresponding unsigned type (if there are M value bits in the signed
+    type and N in the unsigned type, then M  N ). If the sign bit is zero, it shall not affect
+

+
 
3   If the implementation supports negative zeros, they shall be generated only by:
     -- the &, |, ^, ~, <<, and >> operators with operands that produce such a value;
     -- the +, -, *, /, and % operators where one operand is a negative zero and the result is
@@ -3008,20 +2610,17 @@ Forward references:         conditional inclusion (6.10.1), complex arithmetic
     It is unspecified whether these cases actually generate a negative zero or a normal zero,
     and whether a negative zero becomes a normal zero when stored in an object.
 

-
-
+
 
4   If the implementation does not support negative zeros, the behavior of the &, |, ^, ~, <<,
     and >> operators with operands that would produce such a value is undefined.
 

-
-
-
5   The values of any padding bits are unspecified.54) A valid (non-trap) object representation
+
+
5   The values of any padding bits are unspecified.[54] A valid (non-trap) object representation
     of a signed integer type where the sign bit is zero is a valid object representation of the
     corresponding unsigned type, and shall represent the same value. For any integer type,
     the object representation where all the bits are zero shall be a representation of the value
     zero in that type.
 

-
 
 
Footnote 54) Some combinations of padding bits might generate trap representations, for example, if one padding
         bit is a parity bit. Regardless, no arithmetic operation on valid values can generate a trap
@@ -3030,23 +2629,20 @@ Forward references:         conditional inclusion (6.10.1), complex arithmetic
         bits.
 

 
-
+
 
6   The precision of an integer type is the number of bits it uses to represent values,
     excluding any sign and padding bits. The width of an integer type is the same but
     including any sign bit; thus for unsigned integer types the two values are the same, while
     for signed integer types the width is one greater than the precision.
 
 

-
-
+
 

 
6.2.7 [Compatible type and composite type]

-

-
-
+
 
1   Two types have compatible type if their types are the same. Additional rules for
-    determining whether two types are compatible are described in 6.7.2 for type specifiers,
-    in 6.7.3 for type qualifiers, and in 6.7.6 for declarators.55) Moreover, two structure,
+    determining whether two types are compatible are described in 6.7.2 for type specifiers,
+    in 6.7.3 for type qualifiers, and in 6.7.6 for declarators.[55] Moreover, two structure,
     union, or enumerated types declared in separate translation units are compatible if their
     tags and members satisfy the following requirements: If one is declared with a tag, the
     other shall be declared with the same tag. If both are completed anywhere within their
@@ -3059,54 +2655,49 @@ Forward references:         conditional inclusion (6.10.1), complex arithmetic
     same order. For two structures or unions, corresponding bit-fields shall have the same
     widths. For two enumerations, corresponding members shall have the same values.
 

-
 
 
Footnote 55) Two types need not be identical to be compatible.
+    -- If both types are function types with parameter type lists, the type of each parameter
+       in the composite parameter type list is the composite type of the corresponding
+       parameters.
+    These rules apply recursively to the types from which the two types are derived.
 

 
-
+
 
2   All declarations that refer to the same object or function shall have compatible type;
     otherwise, the behavior is undefined.
 

-
-
+
 
3   A composite type can be constructed from two types that are compatible; it is a type that
     is compatible with both of the two types and satisfies the following conditions:
     -- If both types are array types, the following rules are applied:
-          ·   If one type is an array of known constant size, the composite type is an array of
+          \xB7   If one type is an array of known constant size, the composite type is an array of
               that size.
-          ·   Otherwise, if one type is a variable length array whose size is specified by an
+          \xB7   Otherwise, if one type is a variable length array whose size is specified by an
               expression that is not evaluated, the behavior is undefined.
-          ·   Otherwise, if one type is a variable length array whose size is specified, the
+          \xB7   Otherwise, if one type is a variable length array whose size is specified, the
               composite type is a variable length array of that size.
-          ·   Otherwise, if one type is a variable length array of unspecified size, the composite
+          \xB7   Otherwise, if one type is a variable length array of unspecified size, the composite
               type is a variable length array of unspecified size.
-          ·   Otherwise, both types are arrays of unknown size and the composite type is an
+          \xB7   Otherwise, both types are arrays of unknown size and the composite type is an
               array of unknown size.
         The element type of the composite type is the composite type of the two element
         types.
     -- If only one type is a function type with a parameter type list (a function prototype),
        the composite type is a function prototype with the parameter type list.
-
-    -- If both types are function types with parameter type lists, the type of each parameter
-       in the composite parameter type list is the composite type of the corresponding
-       parameters.
-    These rules apply recursively to the types from which the two types are derived.
 

-
-
+
 
4   For an identifier with internal or external linkage declared in a scope in which a prior
-    declaration of that identifier is visible,56) if the prior declaration specifies internal or
+    declaration of that identifier is visible,[56] if the prior declaration specifies internal or
     external linkage, the type of the identifier at the later declaration becomes the composite
     type.
-    Forward references: array declarators (6.7.6.2).
+    Forward references: array declarators (6.7.6.2).
 

-
 
-
Footnote 56) As specified in 6.2.1, the later declaration might hide the prior declaration.
+
Footnote 56) As specified in 6.2.1, the later declaration might hide the prior declaration.
 

 
-
+
 
5   EXAMPLE        Given the following two file scope declarations:
              int f(int (*)(), double (*)[3]);
              int f(int (*)(char *), double (*)[]);
@@ -3114,13 +2705,10 @@ Forward references:         conditional inclusion (6.10.1), complex arithmetic
              int f(int (*)(char *), double (*)[3]);
 
 

-
-
+
 

 
6.2.8 [Alignment of objects]

-

-
-
+
 
1   Complete object types have alignment requirements which place restrictions on the
     addresses at which objects of that type may be allocated. An alignment is an
     implementation-defined integer value representing the number of bytes between
@@ -3128,83 +2716,67 @@ Forward references:         conditional inclusion (6.10.1), complex arithmetic
     alignment requirement on every object of that type: stricter alignment can be requested
     using the _Alignas keyword.
 

-
-
+
 
2   A fundamental alignment is represented by an alignment less than or equal to the greatest
     alignment supported by the implementation in all contexts, which is equal to
     _Alignof (max_align_t).
 

-
-
+
 
3   An extended alignment is represented by an alignment greater than
     _Alignof (max_align_t). It is implementation-defined whether any extended
     alignments are supported and the contexts in which they are supported. A type having an
-    extended alignment requirement is an over-aligned type.57)
+    extended alignment requirement is an over-aligned type.[57]
 

-
 
 
Footnote 57) Every over-aligned type is, or contains, a structure or union type with a member to which an extended
         alignment has been applied.
 

 
-
+
 
4   Alignments are represented as values of the type size_t. Valid alignments include only
     those values returned by an _Alignof expression for fundamental types, plus an
     additional implementation-defined set of values, which may be empty. Every valid
     alignment value shall be a nonnegative integral power of two.
 
 

-
-
+
 
5   Alignments have an order from weaker to stronger or stricter alignments. Stricter
     alignments have larger alignment values. An address that satisfies an alignment
     requirement also satisfies any weaker valid alignment requirement.
 

-
-
+
 
6   The alignment requirement of a complete type can be queried using an _Alignof
     expression. The types char, signed char, and unsigned char shall have the
     weakest alignment requirement.
 

-
-
+
 
7   Comparing alignments is meaningful and provides the obvious results:
     -- Two alignments are equal when their numeric values are equal.
     -- Two alignments are different when their numeric values are not equal.
     -- When an alignment is larger than another it represents a stricter alignment.
 

-
-
+
 

 
6.3 [Conversions]

-

-
-
+
 
1   Several operators convert operand values from one type to another automatically. This
     subclause specifies the result required from such an implicit conversion, as well as those
-    that result from a cast operation (an explicit conversion). The list in 6.3.1.8 summarizes
+    that result from a cast operation (an explicit conversion). The list in 6.3.1.8 summarizes
     the conversions performed by most ordinary operators; it is supplemented as required by
-    the discussion of each operator in 6.5.
+    the discussion of each operator in 6.5.
 

-
-
+
 
2   Conversion of an operand value to a compatible type causes no change to the value or the
     representation.
-    Forward references: cast operators (6.5.4).
+    Forward references: cast operators (6.5.4).
 

-
-
+
 

 
6.3.1 [Arithmetic operands]

-
 Arithmetic operands
-

-
-
+
 

 
6.3.1.1 [Boolean, characters, and integers]

-

-
-
+
 
1   Every integer type has an integer conversion rank defined as follows:
     -- No two signed integer types shall have the same rank, even if they have the same
        representation.
@@ -3220,15 +2792,14 @@ Forward references:         conditional inclusion (6.10.1), complex arithmetic
     -- The rank of char shall equal the rank of signed char and unsigned char.
     -- The rank of _Bool shall be less than the rank of all other standard integer types.
     -- The rank of any enumerated type shall equal the rank of the compatible integer type
-       (see 6.7.2.2).
+       (see 6.7.2.2).
     -- The rank of any extended signed integer type relative to another extended signed
        integer type with the same precision is implementation-defined, but still subject to the
        other rules for determining the integer conversion rank.
     -- For all integer types T1, T2, and T3, if T1 has greater rank than T2 and T2 has
        greater rank than T3, then T1 has greater rank than T3.
 

-
-
+
 
2   The following may be used in an expression wherever an int or unsigned int may
     be used:
 
@@ -3238,81 +2809,68 @@ Forward references:         conditional inclusion (6.10.1), complex arithmetic
     -- A bit-field of type _Bool, int, signed int, or unsigned int.
     If an int can represent all values of the original type (as restricted by the width, for a
     bit-field), the value is converted to an int; otherwise, it is converted to an unsigned
-    int. These are called the integer promotions.58) All other types are unchanged by the
+    int. These are called the integer promotions.[58] All other types are unchanged by the
     integer promotions.
 

-
 
 
Footnote 58) The integer promotions are applied only: as part of the usual arithmetic conversions, to certain
         argument expressions, to the operands of the unary +, -, and ~ operators, and to both operands of the
         shift operators, as specified by their respective subclauses.
 

 
-
+
 
3   The integer promotions preserve value including sign. As discussed earlier, whether a
     ``plain'' char is treated as signed is implementation-defined.
-    Forward references: enumeration specifiers (6.7.2.2), structure and union specifiers
-    (6.7.2.1).
+    Forward references: enumeration specifiers (6.7.2.2), structure and union specifiers
+    (6.7.2.1).
 

-
-
+
 

 
6.3.1.2 [Boolean type]

-

-
-
+
 
1   When any scalar value is converted to _Bool, the result is 0 if the value compares equal
-    to 0; otherwise, the result is 1.59)
+    to 0; otherwise, the result is 1.[59]
 

-
 
 
Footnote 59) NaNs do not compare equal to 0 and thus convert to 1.
 

 
-
+
 

 
6.3.1.3 [Signed and unsigned integers]

-

-
-
+
 
1   When a value with integer type is converted to another integer type other than _Bool, if
     the value can be represented by the new type, it is unchanged.
 

-
-
+
 
2   Otherwise, if the new type is unsigned, the value is converted by repeatedly adding or
     subtracting one more than the maximum value that can be represented in the new type
-    until the value is in the range of the new type.60)
+    until the value is in the range of the new type.[60]
 

-
 
 
Footnote 60) The rules describe arithmetic on the mathematical value, not the value of a given type of expression.
 

 
-
+
 
3   Otherwise, the new type is signed and the value cannot be represented in it; either the
     result is implementation-defined or an implementation-defined signal is raised.
 

-
-
+
 

 
6.3.1.4 [Real floating and integer]

-

-
-
+
 
1   When a finite value of real floating type is converted to an integer type other than _Bool,
     the fractional part is discarded (i.e., the value is truncated toward zero). If the value of
-    the integral part cannot be represented by the integer type, the behavior is undefined.61)
+    the integral part cannot be represented by the integer type, the behavior is undefined.[61]
 
 

-
 
 
Footnote 61) The remaindering operation performed when a value of integer type is converted to unsigned type
         need not be performed when a value of real floating type is converted to unsigned type. Thus, the
         range of portable real floating values is (-1, Utype_MAX+1).
 

 
-
+
 
2   When a value of integer type is converted to a real floating type, if the value being
     converted can be represented exactly in the new type, it is unchanged. If the value being
     converted is in the range of values that can be represented but cannot be represented
@@ -3320,15 +2878,12 @@ Forward references:         conditional inclusion (6.10.1), complex arithmetic
     in an implementation-defined manner. If the value being converted is outside the range of
     values that can be represented, the behavior is undefined. Results of some implicit
     conversions may be represented in greater range and precision than that required by the
-    new type (see 6.3.1.8 and 6.8.6.4).
+    new type (see 6.3.1.8 and 6.8.6.4).
 

-
-
+
 

 
6.3.1.5 [Real floating types]

-

-
-
+
 
1   When a value of real floating type is converted to a real floating type, if the value being
     converted can be represented exactly in the new type, it is unchanged. If the value being
     converted is in the range of values that can be represented but cannot be represented
@@ -3336,42 +2891,32 @@ Forward references:         conditional inclusion (6.10.1), complex arithmetic
     in an implementation-defined manner. If the value being converted is outside the range of
     values that can be represented, the behavior is undefined. Results of some implicit
     conversions may be represented in greater range and precision than that required by the
-    new type (see 6.3.1.8 and 6.8.6.4).
+    new type (see 6.3.1.8 and 6.8.6.4).
 

-
-
+
 

 
6.3.1.6 [Complex types]

-

-
-
+
 
1   When a value of complex type is converted to another complex type, both the real and
     imaginary parts follow the conversion rules for the corresponding real types.
 

-
-
+
 

 
6.3.1.7 [Real and complex]

-

-
-
+
 
1   When a value of real type is converted to a complex type, the real part of the complex
     result value is determined by the rules of conversion to the corresponding real type and
     the imaginary part of the complex result value is a positive zero or an unsigned zero.
 

-
-
+
 
2   When a value of complex type is converted to a real type, the imaginary part of the
     complex value is discarded and the value of the real part is converted according to the
     conversion rules for the corresponding real type.
 

-
-
+
 

 
6.3.1.8 [Usual arithmetic conversions]

-

-
-
+
 
1   Many operators that expect operands of arithmetic type cause conversions and yield result
     types in a similar way. The purpose is to determine a common real type for the operands
     and result. For the specified operands, each operand is converted, without change of type
@@ -3388,7 +2933,7 @@ Forward references:         conditional inclusion (6.10.1), complex arithmetic
            corresponding real type is double.
            Otherwise, if the corresponding real type of either operand is float, the other
            operand is converted, without change of type domain, to a type whose
-           corresponding real type is float.62)
+           corresponding real type is float.[62]
            Otherwise, the integer promotions are performed on both operands. Then the
            following rules are applied to the promoted operands:
                   If both operands have the same type, then no further conversion is needed.
@@ -3406,37 +2951,30 @@ Forward references:         conditional inclusion (6.10.1), complex arithmetic
                   Otherwise, both operands are converted to the unsigned integer type
                   corresponding to the type of the operand with signed integer type.
 

-
 
 
Footnote 62) For example, addition of a double _Complex and a float entails just the conversion of the
         float operand to double (and yields a double _Complex result).
 

 
-
+
 
2   The values of floating operands and of the results of floating expressions may be
     represented in greater range and precision than that required by the type; the types are not
-    changed thereby.63)
+    changed thereby.[63]
 
 

-
 
 
Footnote 63) The cast and assignment operators are still required to remove extra range and precision.
 

 
-
+
 

 
6.3.2 [Other operands]

-
 Other operands
-

-
-
+
 

 
6.3.2.1 [Lvalues, arrays, and function designators]

-

-
-
+
 
1   An lvalue is an expression (with an object type other than void) that potentially
-    designates an object;64) if an lvalue does not designate an object when it is evaluated, the
+    designates an object;[64] if an lvalue does not designate an object when it is evaluated, the
     behavior is undefined. When an object is said to have a particular type, the type is
     specified by the lvalue used to designate the object. A modifiable lvalue is an lvalue that
     does not have array type, does not have an incomplete type, does not have a const-
@@ -3444,7 +2982,6 @@ Forward references:         conditional inclusion (6.10.1), complex arithmetic
     recursively, any member or element of all contained aggregates or unions) with a const-
     qualified type.
 

-
 
 
Footnote 64) The name ``lvalue'' comes originally from the assignment expression E1 = E2, in which the left
         operand E1 is required to be a (modifiable) lvalue. It is perhaps better considered as representing an
@@ -3454,7 +2991,7 @@ Forward references:         conditional inclusion (6.10.1), complex arithmetic
          expression that is a pointer to an object, *E is an lvalue that designates the object to which E points.
 

 
-
+
 
2   Except when it is the operand of the sizeof operator, the _Alignof operator, the
     unary & operator, the ++ operator, the -- operator, or the left operand of the . operator
     or an assignment operator, an lvalue that does not have array type is converted to the
@@ -3468,130 +3005,112 @@ Forward references:         conditional inclusion (6.10.1), complex arithmetic
     is uninitialized (not declared with an initializer and no assignment to it has been
     performed prior to use), the behavior is undefined.
 

-
-
+
 
3   Except when it is the operand of the sizeof operator, the _Alignof operator, or the
     unary & operator, or is a string literal used to initialize an array, an expression that has
     type ``array of type'' is converted to an expression with type ``pointer to type'' that points
     to the initial element of the array object and is not an lvalue. If the array object has
     register storage class, the behavior is undefined.
 

-
-
+
 
4   A function designator is an expression that has function type. Except when it is the
-    operand of the sizeof operator, the _Alignof operator,65) or the unary & operator, a
+    operand of the sizeof operator, the _Alignof operator,[65] or the unary & operator, a
     function designator with type ``function returning type'' is converted to an expression that
-
-    has type ``pointer to function returning type''.
-    Forward references: address and indirection operators (6.5.3.2), assignment operators
-    (6.5.16), common definitions <stddef.h> (7.19), initialization (6.7.9), postfix
-    increment and decrement operators (6.5.2.4), prefix increment and decrement operators
-    (6.5.3.1), the sizeof and _Alignof operators (6.5.3.4), structure and union members
-    (6.5.2.3).
 

-
 
 
Footnote 65) Because this conversion does not occur, the operand of the sizeof or _Alignof operator remains
-        a function designator and violates the constraints in 6.5.3.4.
+        a function designator and violates the constraints in 6.5.3.4.
+    has type ``pointer to function returning type''.
+    Forward references: address and indirection operators (6.5.3.2), assignment operators
+    (6.5.16), common definitions <stddef.h> (7.19), initialization (6.7.9), postfix
+    increment and decrement operators (6.5.2.4), prefix increment and decrement operators
+    (6.5.3.1), the sizeof and _Alignof operators (6.5.3.4), structure and union members
+    (6.5.2.3).
 

 
-
+
 

 
6.3.2.2 [void]

-

-
-
+
 
1   The (nonexistent) value of a void expression (an expression that has type void) shall not
     be used in any way, and implicit or explicit conversions (except to void) shall not be
     applied to such an expression. If an expression of any other type is evaluated as a void
     expression, its value or designator is discarded. (A void expression is evaluated for its
     side effects.)
 

-
-
+
 

 
6.3.2.3 [Pointers]

-

-
-
+
 
1   A pointer to void may be converted to or from a pointer to any object type. A pointer to
     any object type may be converted to a pointer to void and back again; the result shall
     compare equal to the original pointer.
 

-
-
+
 
2   For any qualifier q , a pointer to a non-q -qualified type may be converted to a pointer to
     the q -qualified version of the type; the values stored in the original and converted pointers
     shall compare equal.
 

-
-
+
 
3   An integer constant expression with the value 0, or such an expression cast to type
-    void *, is called a null pointer constant .66) If a null pointer constant is converted to a
+    void *, is called a null pointer constant .[66] If a null pointer constant is converted to a
     pointer type, the resulting pointer, called a null pointer , is guaranteed to compare unequal
     to a pointer to any object or function.
 

-
 
-
Footnote 66) The macro NULL is defined in <stddef.h> (and other headers) as a null pointer constant; see 7.19.
+
Footnote 66) The macro NULL is defined in <stddef.h> (and other headers) as a null pointer constant; see 7.19.
 

 
-
+
 
4   Conversion of a null pointer to another pointer type yields a null pointer of that type.
     Any two null pointers shall compare equal.
 

-
-
+
 
5   An integer may be converted to any pointer type. Except as previously specified, the
     result is implementation-defined, might not be correctly aligned, might not point to an
-    entity of the referenced type, and might be a trap representation.67)
+    entity of the referenced type, and might be a trap representation.[67]
 

-
 
 
Footnote 67) The mapping functions for converting a pointer to an integer or an integer to a pointer are intended to
         be consistent with the addressing structure of the execution environment.
 

 
-
+
 
6   Any pointer type may be converted to an integer type. Except as previously specified, the
     result is implementation-defined. If the result cannot be represented in the integer type,
     the behavior is undefined. The result need not be in the range of values of any integer
     type.
 
 

-
-
+
 
7   A pointer to an object type may be converted to a pointer to a different object type. If the
-    resulting pointer is not correctly aligned68) for the referenced type, the behavior is
+    resulting pointer is not correctly aligned[68] for the referenced type, the behavior is
     undefined. Otherwise, when converted back again, the result shall compare equal to the
     original pointer. When a pointer to an object is converted to a pointer to a character type,
     the result points to the lowest addressed byte of the object. Successive increments of the
     result, up to the size of the object, yield pointers to the remaining bytes of the object.
 

-
 
 
Footnote 68) In general, the concept ``correctly aligned'' is transitive: if a pointer to type A is correctly aligned for a
         pointer to type B, which in turn is correctly aligned for a pointer to type C, then a pointer to type A is
         correctly aligned for a pointer to type C.
 

 
-
+
 
8   A pointer to a function of one type may be converted to a pointer to a function of another
     type and back again; the result shall compare equal to the original pointer. If a converted
     pointer is used to call a function whose type is not compatible with the referenced type,
     the behavior is undefined.
-    Forward references: cast operators (6.5.4), equality operators (6.5.9), integer types
-    capable of holding object pointers (7.20.1.4), simple assignment (6.5.16.1).
+    Forward references: cast operators (6.5.4), equality operators (6.5.9), integer types
+    capable of holding object pointers (7.20.1.4), simple assignment (6.5.16.1).
 
 

-
-
+
 

 
6.4 [Lexical elements]

-

-
-
-
1            token:
+
+
1 Syntax
+            token:
                       keyword
                       identifier
                       constant
@@ -3607,37 +3126,34 @@ Forward references:         conditional inclusion (6.10.1), complex arithmetic
                     each non-white-space character that cannot be one of the above
     Constraints
 

-
-
+
 
2   Each preprocessing token that is converted to a token shall have the lexical form of a
     keyword, an identifier, a constant, a string literal, or a punctuator.
     Semantics
 

-
-
+
 
3   A token is the minimal lexical element of the language in translation phases 7 and 8. The
     categories of tokens are: keywords, identifiers, constants, string literals, and punctuators.
     A preprocessing token is the minimal lexical element of the language in translation
     phases 3 through 6. The categories of preprocessing tokens are: header names,
     identifiers, preprocessing numbers, character constants, string literals, punctuators, and
     single non-white-space characters that do not lexically match the other preprocessing
-    token categories.69) If a ' or a " character matches the last category, the behavior is
+    token categories.[69] If a ' or a " character matches the last category, the behavior is
     undefined. Preprocessing tokens can be separated by white space; this consists of
     comments (described later), or white-space characters (space, horizontal tab, new-line,
-    vertical tab, and form-feed), or both. As described in 6.10, in certain circumstances
+    vertical tab, and form-feed), or both. As described in 6.10, in certain circumstances
     during translation phase 4, white space (or the absence thereof) serves as more than
     preprocessing token separation. White space may appear within a preprocessing token
     only as part of a header name or between the quotation characters in a character constant
     or string literal.
 
 

-
 
-
Footnote 69) An additional category, placemarkers, is used internally in translation phase 4 (see 6.10.3.3); it cannot
+
Footnote 69) An additional category, placemarkers, is used internally in translation phase 4 (see 6.10.3.3); it cannot
         occur in source files.
 

 
-
+
 
4   If the input stream has been parsed into preprocessing tokens up to a given character, the
     next preprocessing token is the longest sequence of characters that could constitute a
     preprocessing token. There is one exception to this rule: header name preprocessing
@@ -3646,8 +3162,7 @@ Forward references:         conditional inclusion (6.10.1), complex arithmetic
     sequence of characters that could be either a header name or a string literal is recognized
     as the former.
 

-
-
+
 
5   EXAMPLE 1 The program fragment 1Ex is parsed as a preprocessing number token (one that is not a
     valid floating or integer constant token), even though a parse as the pair of preprocessing tokens 1 and Ex
     might produce a valid expression (for example, if Ex were a macro defined as +1). Similarly, the program
@@ -3655,25 +3170,22 @@ Forward references:         conditional inclusion (6.10.1), complex arithmetic
     not E is a macro name.
 
 

-
-
+
 
6   EXAMPLE 2 The program fragment x+++++y is parsed as x ++ ++ + y, which violates a constraint on
     increment operators, even though the parse x ++ + ++ y might yield a correct expression.
 
-    Forward references: character constants (6.4.4.4), comments (6.4.9), expressions (6.5),
-    floating constants (6.4.4.2), header names (6.4.7), macro replacement (6.10.3), postfix
-    increment and decrement operators (6.5.2.4), prefix increment and decrement operators
-    (6.5.3.1), preprocessing directives (6.10), preprocessing numbers (6.4.8), string literals
-    (6.4.5).
+    Forward references: character constants (6.4.4.4), comments (6.4.9), expressions (6.5),
+    floating constants (6.4.4.2), header names (6.4.7), macro replacement (6.10.3), postfix
+    increment and decrement operators (6.5.2.4), prefix increment and decrement operators
+    (6.5.3.1), preprocessing directives (6.10), preprocessing numbers (6.4.8), string literals
+    (6.4.5).
 

-
-
+
 

 
6.4.1 [Keywords]

-

-
-
-
1            keyword: one of
+
+
1 Syntax
+            keyword: one of
                    auto                          if                              unsigned
                    break                         inline                          void
                    case                          int                             volatile
@@ -3691,30 +3203,24 @@ Forward references:         conditional inclusion (6.10.1), complex arithmetic
                    goto                          union
     Semantics
 

-
-
+
 
2   The above tokens (case sensitive) are reserved (in translation phases 7 and 8) for use as
     keywords, and shall not be used otherwise. The keyword _Imaginary is reserved for
-    specifying imaginary types.70)
+    specifying imaginary types.[70]
 

-
 
 
Footnote 70) One possible specification for imaginary types appears in annex G.
 

 
-
+
 

 
6.4.2 [Identifiers]

-
 Identifiers
-

-
-
+
 

 
6.4.2.1 [General]

-

-
-
-
1            identifier:
+
+
1 Syntax
+            identifier:
                      identifier-nondigit
                      identifier identifier-nondigit
                      identifier digit
@@ -3731,24 +3237,21 @@ Forward references:         conditional inclusion (6.10.1), complex arithmetic
                     0 1        2     3    4    5    6     7    8    9
     Semantics
 

-
-
+
 
2   An identifier is a sequence of nondigit characters (including the underscore _, the
     lowercase and uppercase Latin letters, and other characters) and digits, which designates
-    one or more entities as described in 6.2.1. Lowercase and uppercase letters are distinct.
+    one or more entities as described in 6.2.1. Lowercase and uppercase letters are distinct.
     There is no specific limit on the maximum length of an identifier.
 

-
-
+
 
3   Each universal character name in an identifier shall designate a character whose encoding
-    in ISO/IEC 10646 falls into one of the ranges specified in D.1.71) The initial character
+    in ISO/IEC 10646 falls into one of the ranges specified in D.1.[71] The initial character
     shall not be a universal character name designating a character whose encoding falls into
-    one of the ranges specified in D.2. An implementation may allow multibyte characters
+    one of the ranges specified in D.2. An implementation may allow multibyte characters
     that are not part of the basic source character set to appear in identifiers; which characters
     and their correspondence to universal character names is implementation-defined.
 
 

-
 
 
Footnote 71) On systems in which linkers cannot accept extended characters, an encoding of the universal character
         name may be used in forming valid external identifiers. For example, some otherwise unused
@@ -3756,51 +3259,45 @@ Forward references:         conditional inclusion (6.10.1), complex arithmetic
         Extended characters may produce a long external identifier.
 

 
-
+
 
4   When preprocessing tokens are converted to tokens during translation phase 7, if a
     preprocessing token could be converted to either a keyword or an identifier, it is converted
     to a keyword.
     Implementation limits
 

-
-
-
5   As discussed in 5.2.4.1, an implementation may limit the number of significant initial
+
+
5   As discussed in 5.2.4.1, an implementation may limit the number of significant initial
     characters in an identifier; the limit for an external name (an identifier that has external
     linkage) may be more restrictive than that for an internal name (a macro name or an
     identifier that does not have external linkage). The number of significant characters in an
     identifier is implementation-defined.
 

-
-
+
 
6   Any identifiers that differ in a significant character are different identifiers. If two
     identifiers differ only in nonsignificant characters, the behavior is undefined.
-    Forward references: universal character names (6.4.3), macro replacement (6.10.3).
+    Forward references: universal character names (6.4.3), macro replacement (6.10.3).
 

-
-
+
 

 
6.4.2.2 [Predefined identifiers]

-

-
-
-
1   The identifier _ _func_ _ shall be implicitly declared by the translator as if,
+
+
1 Semantics
+   The identifier _ _func_ _ shall be implicitly declared by the translator as if,
     immediately following the opening brace of each function definition, the declaration
              static const char _ _func_ _[] = "function-name";
-    appeared, where function-name is the name of the lexically-enclosing function.72)
+    appeared, where function-name is the name of the lexically-enclosing function.[72]
 

-
 
-
Footnote 72) Since the name _ _func_ _ is reserved for any use by the implementation (7.1.3), if any other
+
Footnote 72) Since the name _ _func_ _ is reserved for any use by the implementation (7.1.3), if any other
         identifier is explicitly declared using the name _ _func_ _, the behavior is undefined.
 

 
-
+
 
2   This name is encoded as if the implicit declaration had been written in the source
     character set and then translated into the execution character set as indicated in translation
     phase 5.
 

-
-
+
 
3   EXAMPLE        Consider the code fragment:
              #include <stdio.h>
              void myfunc(void)
@@ -3811,17 +3308,15 @@ Forward references:         conditional inclusion (6.10.1), complex arithmetic
     Each time the function is called, it will print to the standard output stream:
              myfunc
 
-    Forward references: function definitions (6.9.1).
+    Forward references: function definitions (6.9.1).
 
 

-
-
+
 

 
6.4.3 [Universal character names]

-

-
-
-
1            universal-character-name:
+
+
1 Syntax
+            universal-character-name:
                     \u hex-quad
                     \U hex-quad hex-quad
              hex-quad:
@@ -3829,69 +3324,60 @@ Forward references:         conditional inclusion (6.10.1), complex arithmetic
                                  hexadecimal-digit hexadecimal-digit
     Constraints
 

-
-
+
 
2   A universal character name shall not specify a character whose short identifier is less than
     00A0 other than 0024 ($), 0040 (@), or 0060 (`), nor one in the range D800 through
-    DFFF inclusive.73)
+    DFFF inclusive.[73]
     Description
 

-
 
 
Footnote 73) The disallowed characters are the characters in the basic character set and the code positions reserved
         by ISO/IEC 10646 for control characters, the character DELETE, and the S-zone (reserved for use by
         UTF-16).
 

 
-
+
 
3   Universal character names may be used in identifiers, character constants, and string
     literals to designate characters that are not in the basic character set.
     Semantics
 

-
-
+
 
4   The universal character name \Unnnnnnnn designates the character whose eight-digit
-    short identifier (as specified by ISO/IEC 10646) is nnnnnnnn.74) Similarly, the universal
+    short identifier (as specified by ISO/IEC 10646) is nnnnnnnn.[74] Similarly, the universal
     character name \unnnn designates the character whose four-digit short identifier is nnnn
     (and whose eight-digit short identifier is 0000 nnnn).
 
 

-
 
 
Footnote 74) Short identifiers for characters were first specified in ISO/IEC 10646-1/AMD9:1997.
 

 
-
+
 

 
6.4.4 [Constants]

-

-
-
-
1            constant:
+
+
1 Syntax
+            constant:
                     integer-constant
                     floating-constant
                     enumeration-constant
                     character-constant
     Constraints
 

-
-
+
 
2   Each constant shall have a type and the value of a constant shall be in the range of
     representable values for its type.
     Semantics
 

-
-
+
 
3   Each constant has a type, determined by its form and value, as detailed later.
 

-
-
+
 

 
6.4.4.1 [Integer constants]

-

-
-
-
1            integer-constant:
+
+
1 Syntax
+            integer-constant:
                      decimal-constant integer-suffixopt
                      octal-constant integer-suffixopt
                      hexadecimal-constant integer-suffixopt
@@ -3927,13 +3413,11 @@ Forward references:         conditional inclusion (6.10.1), complex arithmetic
                    ll LL
     Description
 

-
-
+
 
2   An integer constant begins with a digit, but has no period or exponent part. It may have a
     prefix that specifies its base and a suffix that specifies its type.
 

-
-
+
 
3   A decimal constant begins with a nonzero digit and consists of a sequence of decimal
     digits. An octal constant consists of the prefix 0 optionally followed by a sequence of the
     digits 0 through 7 only. A hexadecimal constant consists of the prefix 0x or 0X followed
@@ -3941,13 +3425,11 @@ Forward references:         conditional inclusion (6.10.1), complex arithmetic
     10 through 15 respectively.
     Semantics
 

-
-
+
 
4   The value of a decimal constant is computed base 10; that of an octal constant, base 8;
     that of a hexadecimal constant, base 16. The lexically first digit is the most significant.
 

-
-
+
 
5   The type of an integer constant is the first of the corresponding list in which its value can
     be represented.
                                                                      Octal or Hexadecimal
@@ -3978,8 +3460,7 @@ Forward references:         conditional inclusion (6.10.1), complex arithmetic
     Both u or U         unsigned long long int                 unsigned long long int
     and ll or LL
 

-
-
+
 
6   If an integer constant cannot be represented by any type in its list, it may have an
     extended integer type, if the extended integer type can represent its value. If all of the
     types in the list for the constant are signed, the extended integer type shall be signed. If
@@ -3988,14 +3469,12 @@ Forward references:         conditional inclusion (6.10.1), complex arithmetic
     may be signed or unsigned. If an integer constant cannot be represented by any type in
     its list and has no extended integer type, then the integer constant has no type.
 

-
-
+
 

 
6.4.4.2 [Floating constants]

-

-
-
-
1            floating-constant:
+
+
1 Syntax
+            floating-constant:
                      decimal-floating-constant
                      hexadecimal-floating-constant
              decimal-floating-constant:
@@ -4032,8 +3511,7 @@ Forward references:         conditional inclusion (6.10.1), complex arithmetic
 
     Description
 

-
-
+
 
2   A floating constant has a significand part that may be followed by an exponent part and a
     suffix that specifies its type. The components of the significand part may include a digit
     sequence representing the whole-number part, followed by a period (.), followed by a
@@ -4043,8 +3521,7 @@ Forward references:         conditional inclusion (6.10.1), complex arithmetic
     constants, either the period or the exponent part has to be present.
     Semantics
 

-
-
+
 
3   The significand part is interpreted as a (decimal or hexadecimal) rational number; the
     digit sequence in the exponent part is interpreted as a decimal integer. For decimal
     floating constants, the exponent indicates the power of 10 by which the significand part is
@@ -4056,67 +3533,58 @@ Forward references:         conditional inclusion (6.10.1), complex arithmetic
     For hexadecimal floating constants when FLT_RADIX is a power of 2, the result is
     correctly rounded.
 

-
-
+
 
4   An unsuffixed floating constant has type double. If suffixed by the letter f or F, it has
     type float. If suffixed by the letter l or L, it has type long double.
 

-
-
+
 
5   Floating constants are converted to internal format as if at translation-time. The
     conversion of a floating constant shall not raise an exceptional condition or a floating-
-    point exception at execution time. All floating constants of the same source form75) shall
+    point exception at execution time. All floating constants of the same source form[75] shall
     convert to the same internal format with the same value.
     Recommended practice
 

-
 
-
Footnote 75) 1.23, 1.230, 123e-2, 123e-02, and 1.23L are all different source forms and thus need not
+
Footnote 75) 1.23, 1.230, 123e-2, 123e-02, and 1.23L are all different source forms and thus need not
         convert to the same internal format and value.
 

 
-
+
 
6   The implementation should produce a diagnostic message if a hexadecimal constant
     cannot be represented exactly in its evaluation format; the implementation should then
     proceed with the translation of the program.
 

-
-
+
 
7   The translation-time conversion of floating constants should match the execution-time
     conversion of character strings by library functions, such as strtod, given matching
     inputs suitable for both conversions, the same result format, and default execution-time
-    rounding.76)
+    rounding.[76]
 
 

-
 
 
Footnote 76) The specification for the library functions recommends more accurate conversion than required for
-        floating constants (see 7.22.1.3).
+        floating constants (see 7.22.1.3).
 

 
-
+
 

 
6.4.4.3 [Enumeration constants]

-

-
-
-
1            enumeration-constant:
+
+
1 Syntax
+            enumeration-constant:
                    identifier
     Semantics
 

-
-
+
 
2   An identifier declared as an enumeration constant has type int.
-    Forward references: enumeration specifiers (6.7.2.2).
+    Forward references: enumeration specifiers (6.7.2.2).
 

-
-
+
 

 
6.4.4.4 [Character constants]

-

-
-
-
1            character-constant:
+
+
1 Syntax
+            character-constant:
                     ' c-char-sequence '
                     L' c-char-sequence '
                     u' c-char-sequence '
@@ -4145,16 +3613,14 @@ Forward references:         conditional inclusion (6.10.1), complex arithmetic
                  hexadecimal-escape-sequence hexadecimal-digit
     Description
 

-
-
+
 
2   An integer character constant is a sequence of one or more multibyte characters enclosed
     in single-quotes, as in 'x'. A wide character constant is the same, except prefixed by the
     letter L, u, or U. With a few exceptions detailed later, the elements of the sequence are
     any members of the source character set; they are mapped in an implementation-defined
     manner to members of the execution character set.
 

-
-
+
 
3   The single-quote ', the double-quote ", the question-mark ?, the backslash \, and
     arbitrary integer values are representable according to the following table of escape
     sequences:
@@ -4165,48 +3631,42 @@ Forward references:         conditional inclusion (6.10.1), complex arithmetic
           octal character           \octal digits
           hexadecimal character     \x hexadecimal digits
 

-
-
+
 
4   The double-quote " and question-mark ? are representable either by themselves or by the
     escape sequences \" and \?, respectively, but the single-quote ' and the backslash \
     shall be represented, respectively, by the escape sequences \' and \\.
 

-
-
+
 
5   The octal digits that follow the backslash in an octal escape sequence are taken to be part
     of the construction of a single character for an integer character constant or of a single
     wide character for a wide character constant. The numerical value of the octal integer so
     formed specifies the value of the desired character or wide character.
 

-
-
+
 
6   The hexadecimal digits that follow the backslash and the letter x in a hexadecimal escape
     sequence are taken to be part of the construction of a single character for an integer
     character constant or of a single wide character for a wide character constant. The
     numerical value of the hexadecimal integer so formed specifies the value of the desired
     character or wide character.
 

-
-
+
 
7   Each octal or hexadecimal escape sequence is the longest sequence of characters that can
     constitute the escape sequence.
 

-
-
+
 
8   In addition, characters not in the basic character set are representable by universal
     character names and certain nongraphic characters are representable by escape sequences
     consisting of the backslash \ followed by a lowercase letter: \a, \b, \f, \n, \r, \t,
-    and \v.77)
+    and \v.[77]
 
      Constraints
 

-
 
-
Footnote 77) The semantics of these characters were discussed in 5.2.2. If any other character follows a backslash,
-         the result is not a token and a diagnostic is required. See ``future language directions'' (6.11.4).
+
Footnote 77) The semantics of these characters were discussed in 5.2.2. If any other character follows a backslash,
+         the result is not a token and a diagnostic is required. See ``future language directions'' (6.11.4).
 

 
-
+
 
9    The value of an octal or hexadecimal escape sequence shall be in the range of
      representable values for the corresponding type:
             Prefix     Corresponding Type
@@ -4216,8 +3676,7 @@ Forward references:         conditional inclusion (6.10.1), complex arithmetic
             U          char32_t
      Semantics
 

-
-
+
 
10   An integer character constant has type int. The value of an integer character constant
      containing a single character that maps to a single-byte execution character is the
      numerical value of the representation of the mapped character interpreted as an integer.
@@ -4228,8 +3687,7 @@ Forward references:         conditional inclusion (6.10.1), complex arithmetic
      type char whose value is that of the single character or escape sequence is converted to
      type int.
 

-
-
+
 
11   A wide character constant prefixed by the letter L has type wchar_t, an integer type
      defined in the <stddef.h> header; a wide character constant prefixed by the letter u or
      U has type char16_t or char32_t, respectively, unsigned integer types defined in the
@@ -4243,21 +3701,18 @@ Forward references:         conditional inclusion (6.10.1), complex arithmetic
      escape sequence not represented in the extended execution character set, is
      implementation-defined.
 

-
-
+
 
12   EXAMPLE 1       The construction '\0' is commonly used to represent the null character.
 
 

-
-
+
 
13   EXAMPLE 2 Consider implementations that use two's complement representation for integers and eight
      bits for objects that have type char. In an implementation in which type char has the same range of
      values as signed char, the integer character constant '\xFF' has the value -1; if type char has the
      same range of values as unsigned char, the character constant '\xFF' has the value +255.
 
 

-
-
+
 
14   EXAMPLE 3 Even if eight bits are used for objects that have type char, the construction '\x123'
      specifies an integer character constant containing only one character, since a hexadecimal escape sequence
      is terminated only by a non-hexadecimal character. To specify an integer character constant containing the
@@ -4266,23 +3721,20 @@ Forward references:         conditional inclusion (6.10.1), complex arithmetic
      constant is implementation-defined.)
 
 

-
-
+
 
15   EXAMPLE 4 Even if 12 or more bits are used for objects that have type wchar_t, the construction
      L'\1234' specifies the implementation-defined value that results from the combination of the values
      0123 and '4'.
 
-     Forward references: common definitions <stddef.h> (7.19), the mbtowc function
-     (7.22.7.2), Unicode utilities <uchar.h> (7.28).
+     Forward references: common definitions <stddef.h> (7.19), the mbtowc function
+     (7.22.7.2), Unicode utilities <uchar.h> (7.28).
 

-
-
+
 

 
6.4.5 [String literals]

-

-
-
-
1             string-literal:
+
+
1 Syntax
+             string-literal:
                       encoding-prefixopt " s-char-sequenceopt "
               encoding-prefix:
                      u8
@@ -4298,20 +3750,17 @@ Forward references:         conditional inclusion (6.10.1), complex arithmetic
                         escape-sequence
      Constraints
 

-
-
+
 
2    A sequence of adjacent string literal tokens shall not include both a wide string literal and
      a UTF-8 string literal.
      Description
 

-
-
+
 
3    A character string literal is a sequence of zero or more multibyte characters enclosed in
      double-quotes, as in "xyz". A UTF-8 string literal is the same, except prefixed by u8.
      A wide string literal is the same, except prefixed by the letter L, u, or U.
 

-
-
+
 
4    The same considerations apply to each element of the sequence in a string literal as if it
      were in an integer character constant (for a character or UTF-8 string literal) or a wide
      character constant (for a wide string literal), except that the single-quote ' is
@@ -4319,8 +3768,7 @@ Forward references:         conditional inclusion (6.10.1), complex arithmetic
     be represented by the escape sequence \".
     Semantics
 

-
-
+
 
5   In translation phase 6, the multibyte character sequences specified by any sequence of
     adjacent character and identically-prefixed string literal tokens are concatenated into a
     single multibyte character sequence. If any of the tokens has an encoding prefix, the
@@ -4329,10 +3777,9 @@ Forward references:         conditional inclusion (6.10.1), complex arithmetic
     tokens can be concatenated and, if so, the treatment of the resulting multibyte character
     sequence are implementation-defined.
 

-
-
+
 
6   In translation phase 7, a byte or code of value zero is appended to each multibyte
-    character sequence that results from a string literal or literals.78) The multibyte character
+    character sequence that results from a string literal or literals.[78] The multibyte character
     sequence is then used to initialize an array of static storage duration and length just
     sufficient to contain the sequence. For character string literals, the array elements have
     type char, and are initialized with the individual bytes of the multibyte character
@@ -4349,30 +3796,9 @@ Forward references:         conditional inclusion (6.10.1), complex arithmetic
     containing a multibyte character or escape sequence not represented in the execution
     character set is implementation-defined.
 

-
 
-
Footnote 78) A string literal need not be a string (see 7.1.1), because a null character may be embedded in it by a
+
Footnote 78) A string literal need not be a string (see 7.1.1), because a null character may be embedded in it by a
         \0 escape sequence.
-

-
-
-
7   It is unspecified whether these arrays are distinct provided their elements have the
-    appropriate values. If the program attempts to modify such an array, the behavior is
-    undefined.
-

-
-
-
8   EXAMPLE 1      This pair of adjacent character string literals
-             "\x12" "3"
-    produces a single character string literal containing the two characters whose values are '\x12' and '3',
-    because escape sequences are converted into single members of the execution character set just prior to
-    adjacent string literal concatenation.
-
-

-
-
-
9   EXAMPLE 2      Each of the sequences of adjacent string literal tokens
-
              "a" "b" L"c"
              "a" L"b" "c"
              L"a" "b" L"c"
@@ -4386,18 +3812,32 @@ Forward references:         conditional inclusion (6.10.1), complex arithmetic
              u"a" u"b" u"c"
     is equivalent to
              u"abc"
-
-    Forward references: common definitions <stddef.h> (7.19), the mbstowcs
-    function (7.22.8.1), Unicode utilities <uchar.h> (7.28).
-

+    Forward references: common definitions <stddef.h> (7.19), the mbstowcs
+    function (7.22.8.1), Unicode utilities <uchar.h> (7.28).
+

 
-
+
+
7   It is unspecified whether these arrays are distinct provided their elements have the
+    appropriate values. If the program attempts to modify such an array, the behavior is
+    undefined.
+

+
+
8   EXAMPLE 1      This pair of adjacent character string literals
+             "\x12" "3"
+    produces a single character string literal containing the two characters whose values are '\x12' and '3',
+    because escape sequences are converted into single members of the execution character set just prior to
+    adjacent string literal concatenation.
+
+

+
+
9   EXAMPLE 2      Each of the sequences of adjacent string literal tokens
+

+
 

 
6.4.6 [Punctuators]

-

-
-
-
1            punctuator: one of
+
+
1 Syntax
+            punctuator: one of
                     [ ] ( ) { } . ->
                     ++ -- & * + - ~ !
                     / % << >> < > <= >=                              ==       !=    ^    |   &&   ||
@@ -4407,41 +3847,40 @@ Forward references:         conditional inclusion (6.10.1), complex arithmetic
                     <: :> <% %> %: %:%:
     Semantics
 

-
-
+
 
2   A punctuator is a symbol that has independent syntactic and semantic significance.
     Depending on context, it may specify an operation to be performed (which in turn may
     yield a value or a function designator, produce a side effect, or some combination thereof)
     in which case it is known as an operator (other forms of operator also exist in some
     contexts). An operand is an entity on which an operator acts.
 

-
-
-
3   In all aspects of the language, the six tokens79)
+
+
3   In all aspects of the language, the six tokens[79]
              <:    :>      <%    %>     %:     %:%:
     behave, respectively, the same as the six tokens
              [     ]       {     }      #      ##
-    except for their spelling.80)
-    Forward references: expressions (6.5), declarations (6.7), preprocessing directives
-    (6.10), statements (6.8).
+    except for their spelling.[80]
+    Forward references: expressions (6.5), declarations (6.7), preprocessing directives
+    (6.10), statements (6.8).
 

-
 
 
Footnote 79) These tokens are sometimes called ``digraphs''.
 

 
 
-
Footnote 80) Thus [ and <: behave differently when ``stringized'' (see 6.10.3.2), but can otherwise be freely
+
Footnote 80) Thus [ and <: behave differently when ``stringized'' (see 6.10.3.2), but can otherwise be freely
         interchanged.
+    sequence between the " delimiters, the behavior is undefined.81) Header name
+    preprocessing tokens are recognized only within #include preprocessing directives and
+    in implementation-defined locations within #pragma directives.82)
 

 
-
+
 

 
6.4.7 [Header names]

-

-
-
-
1            header-name:
+
+
1 Syntax
+            header-name:
                     < h-char-sequence >
                     " q-char-sequence "
              h-char-sequence:
@@ -4458,30 +3897,15 @@ Forward references:         conditional inclusion (6.10.1), complex arithmetic
                                     the new-line character and "
     Semantics
 

-
-
+
 
2   The sequences in both forms of header names are mapped in an implementation-defined
-    manner to headers or external source file names as specified in 6.10.2.
+    manner to headers or external source file names as specified in 6.10.2.
 

-
-
+
 
3   If the characters ', \, ", //, or /* occur in the sequence between the < and > delimiters,
     the behavior is undefined. Similarly, if the characters ', \, //, or /* occur in the
-
-    sequence between the " delimiters, the behavior is undefined.81) Header name
-    preprocessing tokens are recognized only within #include preprocessing directives and
-    in implementation-defined locations within #pragma directives.82)
 

-
-
-
Footnote 81) Thus, sequences of characters that resemble escape sequences cause undefined behavior.
-

-
-
-
Footnote 82) For an example of a header name preprocessing token used in a #pragma directive, see 6.10.9.
-

-
-
+
 
4   EXAMPLE       The following sequence of characters:
              0x3<1/a.h>1e2
              #include <1/a.h>
@@ -4492,16 +3916,14 @@ Forward references:         conditional inclusion (6.10.1), complex arithmetic
              {#}{include} {<1/a.h>}
              {#}{define} {const}{.}{member}{@}{$}
 
-    Forward references: source file inclusion (6.10.2).
+    Forward references: source file inclusion (6.10.2).
 

-
-
+
 

 
6.4.8 [Preprocessing numbers]

-

-
-
-
1            pp-number:
+
+
1 Syntax
+            pp-number:
                    digit
                    . digit
                    pp-number       digit
@@ -4513,48 +3935,40 @@ Forward references:         conditional inclusion (6.10.1), complex arithmetic
                    pp-number       .
     Description
 

-
-
+
 
2   A preprocessing number begins with a digit optionally preceded by a period (.) and may
     be followed by valid identifier characters and the character sequences e+, e-, E+, E-,
     p+, p-, P+, or P-.
 

-
-
+
 
3   Preprocessing number tokens lexically include all floating and integer constant tokens.
     Semantics
 

-
-
+
 
4   A preprocessing number does not have type or a value; it acquires both after a successful
     conversion (as part of translation phase 7) to a floating constant token or an integer
     constant token.
 
 

-
-
+
 

 
6.4.9 [Comments]

-

-
-
+
 
1   Except within a character constant, a string literal, or a comment, the characters /*
     introduce a comment. The contents of such a comment are examined only to identify
-    multibyte characters and to find the characters */ that terminate it.83)
+    multibyte characters and to find the characters */ that terminate it.[83]
 

-
 
 
Footnote 83) Thus, /* ... */ comments do not nest.
 

 
-
+
 
2   Except within a character constant, a string literal, or a comment, the characters //
     introduce a comment that includes all multibyte characters up to, but not including, the
     next new-line character. The contents of such a comment are examined only to identify
     multibyte characters and to find the terminating new-line character.
 

-
-
+
 
3   EXAMPLE
              "a//b"                             //   four-character string literal
              #include "//e"                     //   undefined behavior
@@ -4571,27 +3985,22 @@ Forward references:         conditional inclusion (6.10.1), complex arithmetic
                 + p;                            // equivalent to m = n + p;
 
 

-
-
+
 

 
6.5 [Expressions]

-

-
-
+
 
1   An expression is a sequence of operators and operands that specifies computation of a
     value, or that designates an object or a function, or that generates side effects, or that
     performs a combination thereof. The value computations of the operands of an operator
     are sequenced before the value computation of the result of the operator.
 

-
-
+
 
2   If a side effect on a scalar object is unsequenced relative to either a different side effect
     on the same scalar object or a value computation using the value of the same scalar
     object, the behavior is undefined. If there are multiple allowable orderings of the
     subexpressions of an expression, the behavior is undefined if such an unsequenced side
-    effect occurs in any of the orderings.84)
+    effect occurs in any of the orderings.[84]
 

-
 
 
Footnote 84) This paragraph renders undefined statement expressions such as
                   i = ++i + 1;
@@ -4601,19 +4010,18 @@ Forward references:         conditional inclusion (6.10.1), complex arithmetic
                   a[i] = i;
 

 
-
-
3   The grouping of operators and operands is indicated by the syntax.85) Except as specified
-    later, side effects and value computations of subexpressions are unsequenced.86)
+
+
3   The grouping of operators and operands is indicated by the syntax.[85] Except as specified
+    later, side effects and value computations of subexpressions are unsequenced.[86]
 

-
 
 
Footnote 85) The syntax specifies the precedence of operators in the evaluation of an expression, which is the same
         as the order of the major subclauses of this subclause, highest precedence first. Thus, for example, the
-        expressions allowed as the operands of the binary + operator (6.5.6) are those expressions defined in
-        6.5.1 through 6.5.6. The exceptions are cast expressions (6.5.4) as operands of unary operators
-        (6.5.3), and an operand contained between any of the following pairs of operators: grouping
-        parentheses () (6.5.1), subscripting brackets [] (6.5.2.1), function-call parentheses () (6.5.2.2), and
-        the conditional operator ? : (6.5.15).
+        expressions allowed as the operands of the binary + operator (6.5.6) are those expressions defined in
+        6.5.1 through 6.5.6. The exceptions are cast expressions (6.5.4) as operands of unary operators
+        (6.5.3), and an operand contained between any of the following pairs of operators: grouping
+        parentheses () (6.5.1), subscripting brackets [] (6.5.2.1), function-call parentheses () (6.5.2.2), and
+        the conditional operator ? : (6.5.15).
          Within each major subclause, the operators have the same precedence. Left- or right-associativity is
          indicated in each subclause by the syntax for the expressions discussed therein.
 

@@ -4624,23 +4032,21 @@ Forward references:         conditional inclusion (6.10.1), complex arithmetic
         different evaluations.
 

 
-
+
 
4   Some operators (the unary operator ~, and the binary operators <<, >>, &, ^, and |,
     collectively described as bitwise operators) are required to have operands that have
     integer type. These operators yield values that depend on the internal representations of
     integers, and have implementation-defined and undefined aspects for signed types.
 

-
-
+
 
5   If an exceptional condition occurs during the evaluation of an expression (that is, if the
     result is not mathematically defined or not in the range of representable values for its
     type), the behavior is undefined.
 
 

-
-
+
 
6   The effective type of an object for an access to its stored value is the declared type of the
-    object, if any.87) If a value is stored into an object having no declared type through an
+    object, if any.[87] If a value is stored into an object having no declared type through an
     lvalue having a type that is not a character type, then the type of the lvalue becomes the
     effective type of the object for that access and for subsequent accesses that do not modify
     the stored value. If a value is copied into an object having no declared type using
@@ -4650,14 +4056,13 @@ Forward references:         conditional inclusion (6.10.1), complex arithmetic
     all other accesses to an object having no declared type, the effective type of the object is
     simply the type of the lvalue used for the access.
 

-
 
 
Footnote 87) Allocated objects have no declared type.
 

 
-
+
 
7   An object shall have its stored value accessed only by an lvalue expression that has one of
-    the following types:88)
+    the following types:[88]
     -- a type compatible with the effective type of the object,
     -- a qualified version of a type compatible with the effective type of the object,
     -- a type that is the signed or unsigned type corresponding to the effective type of the
@@ -4668,21 +4073,19 @@ Forward references:         conditional inclusion (6.10.1), complex arithmetic
        members (including, recursively, a member of a subaggregate or contained union), or
     -- a character type.
 

-
 
 
Footnote 88) The intent of this list is to specify those circumstances in which an object may or may not be aliased.
 

 
-
+
 
8   A floating expression may be contracted , that is, evaluated as though it were a single
     operation, thereby omitting rounding errors implied by the source code and the
-    expression evaluation method.89) The FP_CONTRACT pragma in <math.h> provides a
+    expression evaluation method.[89] The FP_CONTRACT pragma in <math.h> provides a
     way to disallow contracted expressions. Otherwise, whether and how expressions are
-    contracted is implementation-defined.90)
-    Forward references: the FP_CONTRACT pragma (7.12.2), copying functions (7.24.2).
+    contracted is implementation-defined.[90]
+    Forward references: the FP_CONTRACT pragma (7.12.2), copying functions (7.24.2).
 
 

-
 
 
Footnote 89) The intermediate operations in the contracted expression are evaluated as if to infinite range and
         precision, while the final operation is rounded to the format determined by the expression evaluation
@@ -4696,13 +4099,12 @@ Forward references:         conditional inclusion (6.10.1), complex arithmetic
         documented.
 

 
-
+
 

 
6.5.1 [Primary expressions]

-

-
-
-
1            primary-expression:
+
+
1 Syntax
+            primary-expression:
                     identifier
                     constant
                     string-literal
@@ -4710,45 +4112,39 @@ Forward references:         conditional inclusion (6.10.1), complex arithmetic
                     generic-selection
     Semantics
 

-
-
+
 
2   An identifier is a primary expression, provided it has been declared as designating an
     object (in which case it is an lvalue) or a function (in which case it is a function
-    designator).91)
+    designator).[91]
 

-
 
 
Footnote 91) Thus, an undeclared identifier is a violation of the syntax.
+    Constraints
 

 
-
-
3   A constant is a primary expression. Its type depends on its form and value, as detailed in 6.4.4.
+
+
3   A constant is a primary expression. Its type depends on its form and value, as detailed in 6.4.4.
 

-
-
-
4   A string literal is a primary expression. It is an lvalue with type as detailed in 6.4.5.
+
+
4   A string literal is a primary expression. It is an lvalue with type as detailed in 6.4.5.
 

-
-
+
 
5   A parenthesized expression is a primary expression. Its type and value are identical to
     those of the unparenthesized expression. It is an lvalue, a function designator, or a void
     expression if the unparenthesized expression is, respectively, an lvalue, a function
     designator, or a void expression.
 

-
-
+
 
6   A generic selection is a primary expression. Its type and value depend on the selected
     generic association, as detailed in the following subclause.
-    Forward references: declarations (6.7).
+    Forward references: declarations (6.7).
 

-
-
+
 

 
6.5.1.1 [Generic selection]

-

-
-
-
1            generic-selection:
+
+
1 Syntax
+            generic-selection:
                     _Generic ( assignment-expression , generic-assoc-list )
              generic-assoc-list:
                     generic-association
@@ -4756,11 +4152,8 @@ Forward references:         conditional inclusion (6.10.1), complex arithmetic
              generic-association:
                     type-name : assignment-expression
                     default : assignment-expression
-
-    Constraints
 

-
-
+
 
2   A generic selection shall have no more than one default generic association. The type
     name in a generic association shall specify a complete object type other than a variably
     modified type. No two generic associations in the same generic selection shall specify
@@ -4770,8 +4163,7 @@ Forward references:         conditional inclusion (6.10.1), complex arithmetic
     have type compatible with exactly one of the types named in its generic association list.
     Semantics
 

-
-
+
 
3   The controlling expression of a generic selection is not evaluated. If a generic selection
     has a generic association with a type name that is compatible with the type of the
     controlling expression, then the result expression of the generic selection is the
@@ -4779,14 +4171,12 @@ Forward references:         conditional inclusion (6.10.1), complex arithmetic
     selection is the expression in the default generic association. None of the expressions
     from any other generic association of the generic selection is evaluated.
 

-
-
+
 
4   The type and value of a generic selection are identical to those of its result expression. It
     is an lvalue, a function designator, or a void expression if its result expression is,
     respectively, an lvalue, a function designator, or a void expression.
 

-
-
+
 
5   EXAMPLE      The cbrt type-generic macro could be implemented as follows:
              #define cbrt(X) _Generic((X),                                      \
                                      long double: cbrtl,                        \
@@ -4795,14 +4185,12 @@ Forward references:         conditional inclusion (6.10.1), complex arithmetic
                                      )(X)
 
 

-
-
+
 

 
6.5.2 [Postfix operators]

-

-
-
-
1            postfix-expression:
+
+
1 Syntax
+            postfix-expression:
                      primary-expression
                      postfix-expression [ expression ]
                      postfix-expression ( argument-expression-listopt )
@@ -4816,19 +4204,16 @@ Forward references:         conditional inclusion (6.10.1), complex arithmetic
                    assignment-expression
                    argument-expression-list , assignment-expression
 

-
-
+
 

 
6.5.2.1 [Array subscripting]

-

-
-
-
1   One of the expressions shall have type ``pointer to complete object type'', the other
+
+
1 Constraints
+   One of the expressions shall have type ``pointer to complete object type'', the other
     expression shall have integer type, and the result has type ``type''.
     Semantics
 

-
-
+
 
2   A postfix expression followed by an expression in square brackets [] is a subscripted
     designation of an element of an array object. The definition of the subscript operator []
     is that E1[E2] is identical to (*((E1)+(E2))). Because of the conversion rules that
@@ -4836,21 +4221,19 @@ Forward references:         conditional inclusion (6.10.1), complex arithmetic
     initial element of an array object) and E2 is an integer, E1[E2] designates the E2-th
     element of E1 (counting from zero).
 

-
-
+
 
3   Successive subscript operators designate an element of a multidimensional array object.
-    If E is an n-dimensional array ( n  2) with dimensions i × j × . . . × k , then E (used as
+    If E is an n-dimensional array ( n  2) with dimensions i \xD7 j \xD7 . . . \xD7 k , then E (used as
     other than an lvalue) is converted to a pointer to an ( n - 1)-dimensional array with
-    dimensions j × . . . × k . If the unary * operator is applied to this pointer explicitly, or
+    dimensions j \xD7 . . . \xD7 k . If the unary * operator is applied to this pointer explicitly, or
     implicitly as a result of subscripting, the result is the referenced ( n - 1)-dimensional
     array, which itself is converted into a pointer if used as other than an lvalue. It follows
     from this that arrays are stored in row-major order (last subscript varies fastest).
 

-
-
+
 
4   EXAMPLE        Consider the array object defined by the declaration
              int x[3][5];
-    Here x is a 3 × 5 array of ints; more precisely, x is an array of three element objects, each of which is an
+    Here x is a 3 \xD7 5 array of ints; more precisely, x is an array of three element objects, each of which is an
     array of five ints. In the expression x[i], which is equivalent to (*((x)+(i))), x is first converted to
     a pointer to the initial array of five ints. Then i is adjusted according to the type of x, which conceptually
     entails multiplying i by the size of the object to which the pointer points, namely an array of five int
@@ -4858,58 +4241,53 @@ Forward references:         conditional inclusion (6.10.1), complex arithmetic
     expression x[i][j], that array is in turn converted to a pointer to the first of the ints, so x[i][j]
     yields an int.
 
-    Forward references: additive operators (6.5.6), address and indirection operators
-    (6.5.3.2), array declarators (6.7.6.2).
+    Forward references: additive operators (6.5.6), address and indirection operators
+    (6.5.3.2), array declarators (6.7.6.2).
 

-
-
+
 

 
6.5.2.2 [Function calls]

-

-
-
-
1   The expression that denotes the called function92) shall have type pointer to function
+
+
1 Constraints
+   The expression that denotes the called function[92] shall have type pointer to function
     returning void or returning a complete object type other than an array type.
 

-
 
 
Footnote 92) Most often, this is the result of converting an identifier that is a function designator.
 

 
-
+
 
2   If the expression that denotes the called function has a type that includes a prototype, the
     number of arguments shall agree with the number of parameters. Each argument shall
     have a type such that its value may be assigned to an object with the unqualified version
     of the type of its corresponding parameter.
     Semantics
 

-
-
+
 
3   A postfix expression followed by parentheses () containing a possibly empty, comma-
     separated list of expressions is a function call. The postfix expression denotes the called
     function. The list of expressions specifies the arguments to the function.
 

-
-
+
 
4   An argument may be an expression of any complete object type. In preparing for the call
     to a function, the arguments are evaluated, and each parameter is assigned the value of the
-    corresponding argument.93)
+    corresponding argument.[93]
 

-
 
 
Footnote 93) A function may change the values of its parameters, but these changes cannot affect the values of the
         arguments. On the other hand, it is possible to pass a pointer to an object, and the function may
         change the value of the object pointed to. A parameter declared to have array or function type is
-        adjusted to have a pointer type as described in 6.9.1.
+        adjusted to have a pointer type as described in 6.9.1.
+     -- both types are pointers to qualified or unqualified versions of a character type or
+        void.
 

 
-
+
 
5   If the expression that denotes the called function has type pointer to function returning an
     object type, the function call expression has the same type as that object type, and has the
-    value determined as specified in 6.8.6.4. Otherwise, the function call has type void.
+    value determined as specified in 6.8.6.4. Otherwise, the function call has type void.
 

-
-
+
 
6   If the expression that denotes the called function has a type that does not include a
     prototype, the integer promotions are performed on each argument, and arguments that
     have type float are promoted to double. These are called the default argument
@@ -4922,12 +4300,8 @@ Forward references:         conditional inclusion (6.10.1), complex arithmetic
     promotion, the behavior is undefined, except for the following cases:
     -- one promoted type is a signed integer type, the other promoted type is the
        corresponding unsigned integer type, and the value is representable in both types;
-
-     -- both types are pointers to qualified or unqualified versions of a character type or
-        void.
 

-
-
+
 
7    If the expression that denotes the called function has a type that does include a prototype,
      the arguments are implicitly converted, as if by assignment, to the types of the
      corresponding parameters, taking the type of each parameter to be the unqualified version
@@ -4935,103 +4309,96 @@ Forward references:         conditional inclusion (6.10.1), complex arithmetic
      argument type conversion to stop after the last declared parameter. The default argument
      promotions are performed on trailing arguments.
 

-
-
+
 
8    No other conversions are performed implicitly; in particular, the number and types of
      arguments are not compared with those of the parameters in a function definition that
      does not include a function prototype declarator.
 

-
-
+
 
9    If the function is defined with a type that is not compatible with the type (of the
      expression) pointed to by the expression that denotes the called function, the behavior is
      undefined.
 

-
-
+
 
10   There is a sequence point after the evaluations of the function designator and the actual
      arguments but before the actual call. Every evaluation in the calling function (including
      other function calls) that is not otherwise specifically sequenced before or after the
      execution of the body of the called function is indeterminately sequenced with respect to
-     the execution of the called function.94)
+     the execution of the called function.[94]
 

-
 
 
Footnote 94) In other words, function executions do not ``interleave'' with each other.
+    Semantics
 

 
-
+
 
11   Recursive function calls shall be permitted, both directly and indirectly through any chain
      of other functions.
 

-
-
+
 
12   EXAMPLE        In the function call
               (*pf[f1()]) (f2(), f3() + f4())
      the functions f1, f2, f3, and f4 may be called in any order. All side effects have to be completed before
      the function pointed to by pf[f1()] is called.
 
-     Forward references: function declarators (including prototypes) (6.7.6.3), function
-     definitions (6.9.1), the return statement (6.8.6.4), simple assignment (6.5.16.1).
+     Forward references: function declarators (including prototypes) (6.7.6.3), function
+     definitions (6.9.1), the return statement (6.8.6.4), simple assignment (6.5.16.1).
 

-
-
+
 

 
6.5.2.3 [Structure and union members]

-

-
-
-
1    The first operand of the . operator shall have an atomic, qualified, or unqualified
+
+
1 Constraints
+    The first operand of the . operator shall have an atomic, qualified, or unqualified
      structure or union type, and the second operand shall name a member of that type.
 

-
-
+
 
2    The first operand of the -> operator shall have type ``pointer to atomic, qualified, or
      unqualified structure'' or ``pointer to atomic, qualified, or unqualified union'', and the
      second operand shall name a member of the type pointed to.
-
-    Semantics
 

-
-
+
 
3   A postfix expression followed by the . operator and an identifier designates a member of
-    a structure or union object. The value is that of the named member,95) and is an lvalue if
+    a structure or union object. The value is that of the named member,[95] and is an lvalue if
     the first expression is an lvalue. If the first expression has qualified type, the result has
     the so-qualified version of the type of the designated member.
 

-
 
 
Footnote 95) If the member used to read the contents of a union object is not the same as the member last used to
         store a value in the object, the appropriate part of the object representation of the value is reinterpreted
-        as an object representation in the new type as described in 6.2.6 (a process sometimes called ``type
+        as an object representation in the new type as described in 6.2.6 (a process sometimes called ``type
         punning''). This might be a trap representation.
 

 
-
+
 
4   A postfix expression followed by the -> operator and an identifier designates a member
     of a structure or union object. The value is that of the named member of the object to
-    which the first expression points, and is an lvalue.96) If the first expression is a pointer to
+    which the first expression points, and is an lvalue.[96] If the first expression is a pointer to
     a qualified type, the result has the so-qualified version of the type of the designated
     member.
 

-
 
 
Footnote 96) If &E is a valid pointer expression (where & is the ``address-of '' operator, which generates a pointer to
-        its operand), the expression (&E)->MOS is the same as E.MOS.
+        its operand), the expression (&E)->MOS is the same as E.MOS.
 

 
-
+
 
5   Accessing a member of an atomic structure or union object results in undefined
-    behavior.97)
+    behavior.[97]
 

-
 
 
Footnote 97) For example, a data race would occur if access to the entire structure or union in one thread conflicts
         with access to a member from another thread, where at least one access is a modification. Members
         can be safely accessed using a non-atomic object which is assigned to or from the atomic object.
+             s.i        int
+             s.ci       const int
+             cs.i       const int
+             cs.ci      const int
+             vs.i       volatile int
+             vs.ci      volatile const int
 

 
-
+
 
6   One special guarantee is made in order to simplify the use of unions: if a union contains
     several structures that share a common initial sequence (see below), and if the union
     object currently contains one of these structures, it is permitted to inspect the common
@@ -5040,14 +4407,12 @@ Forward references:         conditional inclusion (6.10.1), complex arithmetic
     have compatible types (and, for bit-fields, the same widths) for a sequence of one or more
     initial members.
 

-
-
+
 
7   EXAMPLE 1 If f is a function returning a structure or union, and x is a member of that structure or
     union, f().x is a valid postfix expression but is not an lvalue.
 
 

-
-
+
 
8   EXAMPLE 2       In:
              struct s { int i; const int ci; };
              struct s s;
@@ -5055,16 +4420,8 @@ Forward references:         conditional inclusion (6.10.1), complex arithmetic
              volatile struct s vs;
     the various members have the types:
 
-             s.i        int
-             s.ci       const int
-             cs.i       const int
-             cs.ci      const int
-             vs.i       volatile int
-             vs.ci      volatile const int
-
 

-
-
+
 
9   EXAMPLE 3       The following is a valid fragment:
              union {
                      struct {
@@ -5080,7 +4437,7 @@ Forward references:         conditional inclusion (6.10.1), complex arithmetic
                      } nf;
              } u;
              u.nf.type = 1;
-             u.nf.doublenode = 3.14;
+             u.nf.doublenode = 3.14;
              /* ... */
              if (u.n.alltypes == 1)
                      if (sin(u.nf.doublenode) == 0.0)
@@ -5104,23 +4461,20 @@ Forward references:         conditional inclusion (6.10.1), complex arithmetic
                    return f(&u.s1, &u.s2);
              }
 
-    Forward references: address and indirection operators (6.5.3.2), structure and union
-    specifiers (6.7.2.1).
+    Forward references: address and indirection operators (6.5.3.2), structure and union
+    specifiers (6.7.2.1).
 
 

-
-
+
 

 
6.5.2.4 [Postfix increment and decrement operators]

-

-
-
-
1   The operand of the postfix increment or decrement operator shall have atomic, qualified,
+
+
1 Constraints
+   The operand of the postfix increment or decrement operator shall have atomic, qualified,
     or unqualified real or pointer type, and shall be a modifiable lvalue.
     Semantics
 

-
-
+
 
2   The result of the postfix ++ operator is the value of the operand. As a side effect, the
     value of the operand object is incremented (that is, the value 1 of the appropriate type is
     added to it). See the discussions of additive operators and compound assignment for
@@ -5129,9 +4483,8 @@ Forward references:         conditional inclusion (6.10.1), complex arithmetic
     updating the stored value of the operand. With respect to an indeterminately-sequenced
     function call, the operation of postfix ++ is a single evaluation. Postfix ++ on an object
     with atomic type is a read-modify-write operation with memory_order_seq_cst
-    memory order semantics.98)
+    memory order semantics.[98]
 

-
 
 
Footnote 98) Where a pointer to an atomic object can be formed and E has integer type, E++ is equivalent to the
         following code sequence where T is the type of E:
@@ -5142,77 +4495,65 @@ Forward references:         conditional inclusion (6.10.1), complex arithmetic
                          new = old + 1;
                   } while (!atomic_compare_exchange_strong(addr, &old, new));
          with old being the result of the operation.
-         Special care must be taken if E has floating type; see 6.5.16.2.
+         Special care must be taken if E has floating type; see 6.5.16.2.
+     value is given by the initializer list.99)
 

 
-
+
 
3   The postfix -- operator is analogous to the postfix ++ operator, except that the value of
     the operand is decremented (that is, the value 1 of the appropriate type is subtracted from
     it).
-    Forward references: additive operators (6.5.6), compound assignment (6.5.16.2).
+    Forward references: additive operators (6.5.6), compound assignment (6.5.16.2).
 

-
-
+
 

 
6.5.2.5 [Compound literals]

-

-
-
-
1   The type name shall specify a complete object type or an array of unknown size, but not a
+
+
1 Constraints
+   The type name shall specify a complete object type or an array of unknown size, but not a
     variable length array type.
 

-
-
-
2   All the constraints for initializer lists in 6.7.9 also apply to compound literals.
+
+
2   All the constraints for initializer lists in 6.7.9 also apply to compound literals.
     Semantics
 

-
-
+
 
3   A postfix expression that consists of a parenthesized type name followed by a brace-
     enclosed list of initializers is a compound literal . It provides an unnamed object whose
-
-     value is given by the initializer list.99)
 

-
-
-
Footnote 99) Note that this differs from a cast expression. For example, a cast specifies a conversion to scalar types
-         or void only, and the result of a cast expression is not an lvalue.
-

-
-
+
 
4    If the type name specifies an array of unknown size, the size is determined by the
-     initializer list as specified in 6.7.9, and the type of the compound literal is that of the
+     initializer list as specified in 6.7.9, and the type of the compound literal is that of the
      completed array type. Otherwise (when the type name specifies an object type), the type
      of the compound literal is that specified by the type name. In either case, the result is an
      lvalue.
 

-
-
+
 
5    The value of the compound literal is that of an unnamed object initialized by the
      initializer list. If the compound literal occurs outside the body of a function, the object
      has static storage duration; otherwise, it has automatic storage duration associated with
      the enclosing block.
 

-
-
-
6    All the semantic rules for initializer lists in 6.7.9 also apply to compound literals.100)
+
+
6    All the semantic rules for initializer lists in 6.7.9 also apply to compound literals.[100]
 

-
 
 
Footnote 100) For example, subobjects without explicit initializers are initialized to zero.
 

 
-
+
 
7    String literals, and compound literals with const-qualified types, need not designate
-     distinct objects.101)
+     distinct objects.[101]
 

-
 
 
Footnote 101) This allows implementations to share storage for string literals and constant compound literals with
           the same or overlapping representations.
+     Or, if drawline instead expected pointers to struct point:
+              drawline(&(struct point){.x=1, .y=1},
+                    &(struct point){.x=3, .y=4});
 

 
-
+
 
8    EXAMPLE 1       The file scope definition
               int *p = (int []){2, 4};
      initializes p to point to the first element of an array of two ints, the first having the value two and the
@@ -5220,8 +4561,7 @@ Forward references:         conditional inclusion (6.10.1), complex arithmetic
      has static storage duration.
 
 

-
-
+
 
9    EXAMPLE 2       In contrast, in
               void f(void)
               {
@@ -5235,26 +4575,19 @@ Forward references:         conditional inclusion (6.10.1), complex arithmetic
      unnamed object has automatic storage duration.
 
 

-
-
+
 
10   EXAMPLE 3 Initializers with designations can be combined with compound literals. Structure objects
      created using compound literals can be passed to functions without depending on member order:
               drawline((struct point){.x=1, .y=1},
                     (struct point){.x=3, .y=4});
 
-     Or, if drawline instead expected pointers to struct point:
-              drawline(&(struct point){.x=1, .y=1},
-                    &(struct point){.x=3, .y=4});
-
 

-
-
+
 
11   EXAMPLE 4        A read-only compound literal can be specified through constructions like:
               (const float []){1e0, 1e1, 1e2, 1e3, 1e4, 1e5, 1e6}
 
 

-
-
+
 
12   EXAMPLE 5        The following three expressions have different meanings:
               "/tmp/fileXXXXXX"
               (char []){"/tmp/fileXXXXXX"}
@@ -5264,16 +4597,14 @@ Forward references:         conditional inclusion (6.10.1), complex arithmetic
      two is modifiable.
 
 

-
-
+
 
13   EXAMPLE 6 Like string literals, const-qualified compound literals can be placed into read-only memory
      and can even be shared. For example,
               (const char []){"abc"} == "abc"
      might yield 1 if the literals' storage is shared.
 
 

-
-
+
 
14   EXAMPLE 7 Since compound literals are unnamed, a single compound literal cannot specify a circularly
      linked object. For example, there is no way to write a self-referential compound literal that could be used
      as the function argument in place of the named object endless_zeros below:
@@ -5282,8 +4613,7 @@ Forward references:         conditional inclusion (6.10.1), complex arithmetic
               eval(endless_zeros);
 
 

-
-
+
 
15   EXAMPLE 8        Each compound literal creates only a single object in a given scope:
               struct s { int i; };
               int f (void)
@@ -5297,22 +4627,19 @@ Forward references:         conditional inclusion (6.10.1), complex arithmetic
               }
      The function f() always returns the value 1.
 

-
-
+
 
16   Note that if an iteration statement were used instead of an explicit goto and a labeled statement, the
      lifetime of the unnamed object would be the body of the loop only, and on entry next time around p would
      have an indeterminate value, which would result in undefined behavior.
 
-     Forward references: type names (6.7.7), initialization (6.7.9).
+     Forward references: type names (6.7.7), initialization (6.7.9).
 

-
-
+
 

 
6.5.3 [Unary operators]

-

-
-
-
1            unary-expression:
+
+
1 Syntax
+            unary-expression:
                     postfix-expression
                     ++ unary-expression
                     -- unary-expression
@@ -5323,48 +4650,40 @@ Forward references:         conditional inclusion (6.10.1), complex arithmetic
              unary-operator: one of
                     & * + - ~             !
 

-
-
+
 

 
6.5.3.1 [Prefix increment and decrement operators]

-

-
-
-
1   The operand of the prefix increment or decrement operator shall have atomic, qualified,
+
+
1 Constraints
+   The operand of the prefix increment or decrement operator shall have atomic, qualified,
     or unqualified real or pointer type, and shall be a modifiable lvalue.
     Semantics
 

-
-
+
 
2   The value of the operand of the prefix ++ operator is incremented. The result is the new
     value of the operand after incrementation. The expression ++E is equivalent to (E+=1).
     See the discussions of additive operators and compound assignment for information on
     constraints, types, side effects, and conversions and the effects of operations on pointers.
 

-
-
+
 
3   The prefix -- operator is analogous to the prefix ++ operator, except that the value of the
     operand is decremented.
-    Forward references: additive operators (6.5.6), compound assignment (6.5.16.2).
+    Forward references: additive operators (6.5.6), compound assignment (6.5.16.2).
 

-
-
+
 

 
6.5.3.2 [Address and indirection operators]

-

-
-
-
1   The operand of the unary & operator shall be either a function designator, the result of a
+
+
1 Constraints
+   The operand of the unary & operator shall be either a function designator, the result of a
     [] or unary * operator, or an lvalue that designates an object that is not a bit-field and is
     not declared with the register storage-class specifier.
 

-
-
+
 
2   The operand of the unary * operator shall have pointer type.
     Semantics
 

-
-
+
 
3   The unary & operator yields the address of its operand. If the operand has type ``type'',
     the result has type ``pointer to type''. If the operand is the result of a unary * operator,
     neither that operator nor the & operator is evaluated and the result is as if both were
@@ -5375,17 +4694,15 @@ Forward references:         conditional inclusion (6.10.1), complex arithmetic
     were removed and the [] operator were changed to a + operator. Otherwise, the result is
     a pointer to the object or function designated by its operand.
 

-
-
+
 
4   The unary * operator denotes indirection. If the operand points to a function, the result is
     a function designator; if it points to an object, the result is an lvalue designating the
     object. If the operand has type ``pointer to type'', the result has type ``type''. If an
     invalid value has been assigned to the pointer, the behavior of the unary * operator is
-    undefined.102)
-    Forward references: storage-class specifiers (6.7.1), structure and union specifiers
-    (6.7.2.1).
+    undefined.[102]
+    Forward references: storage-class specifiers (6.7.1), structure and union specifiers
+    (6.7.2.1).
 

-
 
 
Footnote 102) Thus, &*E is equivalent to E (even if E is a null pointer), and &(E1[E2]) to ((E1)+(E2)). It is
          always true that if E is a function designator or an lvalue that is a valid operand of the unary &
@@ -5396,109 +4713,69 @@ Forward references:         conditional inclusion (6.10.1), complex arithmetic
          end of its lifetime.
 

 
-
+
 

 
6.5.3.3 [Unary arithmetic operators]

-

-
-
-
1   The operand of the unary + or - operator shall have arithmetic type; of the ~ operator,
+
+
1 Constraints
+   The operand of the unary + or - operator shall have arithmetic type; of the ~ operator,
     integer type; of the ! operator, scalar type.
     Semantics
 

-
-
+
 
2   The result of the unary + operator is the value of its (promoted) operand. The integer
     promotions are performed on the operand, and the result has the promoted type.
 

-
-
+
 
3   The result of the unary - operator is the negative of its (promoted) operand. The integer
     promotions are performed on the operand, and the result has the promoted type.
 

-
-
+
 
4   The result of the ~ operator is the bitwise complement of its (promoted) operand (that is,
     each bit in the result is set if and only if the corresponding bit in the converted operand is
     not set). The integer promotions are performed on the operand, and the result has the
     promoted type. If the promoted type is an unsigned type, the expression ~E is equivalent
     to the maximum value representable in that type minus E.
 

-
-
+
 
5   The result of the logical negation operator ! is 0 if the value of its operand compares
     unequal to 0, 1 if the value of its operand compares equal to 0. The result has type int.
     The expression !E is equivalent to (0==E).
 
 

-
-
+
 

 
6.5.3.4 [The sizeof and _Alignof operators]

-

-
-
-
1   The sizeof operator shall not be applied to an expression that has function type or an
+
+
1 Constraints
+   The sizeof operator shall not be applied to an expression that has function type or an
     incomplete type, to the parenthesized name of such a type, or to an expression that
     designates a bit-field member. The _Alignof operator shall not be applied to a
     function type or an incomplete type.
     Semantics
 

-
-
+
 
2   The sizeof operator yields the size (in bytes) of its operand, which may be an
     expression or the parenthesized name of a type. The size is determined from the type of
     the operand. The result is an integer. If the type of the operand is a variable length array
     type, the operand is evaluated; otherwise, the operand is not evaluated and the result is an
     integer constant.
 

-
-
+
 
3   The _Alignof operator yields the alignment requirement of its operand type. The
     operand is not evaluated and the result is an integer constant. When applied to an array
     type, the result is the alignment requirement of the element type.
 

-
-
+
 
4   When sizeof is applied to an operand that has type char, unsigned char, or
     signed char, (or a qualified version thereof) the result is 1. When applied to an
-    operand that has array type, the result is the total number of bytes in the array.103) When
+    operand that has array type, the result is the total number of bytes in the array.[103] When
     applied to an operand that has structure or union type, the result is the total number of
     bytes in such an object, including internal and trailing padding.
 

-
 
 
Footnote 103) When applied to a parameter declared to have array or function type, the sizeof operator yields the
-         size of the adjusted (pointer) type (see 6.9.1).
-

-
-
-
5   The value of the result of both operators is implementation-defined, and its type (an
-    unsigned integer type) is size_t, defined in <stddef.h> (and other headers).
-

-
-
-
6   EXAMPLE 1 A principal use of the sizeof operator is in communication with routines such as storage
-    allocators and I/O systems. A storage-allocation function might accept a size (in bytes) of an object to
-    allocate and return a pointer to void. For example:
-            extern void *alloc(size_t);
-            double *dp = alloc(sizeof *dp);
-    The implementation of the alloc function should ensure that its return value is aligned suitably for
-    conversion to a pointer to double.
-
-

-
-
-
7   EXAMPLE 2      Another use of the sizeof operator is to compute the number of elements in an array:
-            sizeof array / sizeof array[0]
-
-

-
-
-
8   EXAMPLE 3      In this example, the size of a variable length array is computed and returned from a
-    function:
-            #include <stddef.h>
-
+         size of the adjusted (pointer) type (see 6.9.1).
              size_t fsize3(int n)
              {
                    char b[n+3];                   // variable length array
@@ -5510,127 +4787,112 @@ Forward references:         conditional inclusion (6.10.1), complex arithmetic
                    size = fsize3(10); // fsize3 returns 13
                    return 0;
              }
-
-    Forward references: common definitions <stddef.h> (7.19), declarations (6.7),
-    structure and union specifiers (6.7.2.1), type names (6.7.7), array declarators (6.7.6.2).
-

+    Forward references: common definitions <stddef.h> (7.19), declarations (6.7),
+    structure and union specifiers (6.7.2.1), type names (6.7.7), array declarators (6.7.6.2).
+

 
-
+
+
5   The value of the result of both operators is implementation-defined, and its type (an
+    unsigned integer type) is size_t, defined in <stddef.h> (and other headers).
+

+
+
6   EXAMPLE 1 A principal use of the sizeof operator is in communication with routines such as storage
+    allocators and I/O systems. A storage-allocation function might accept a size (in bytes) of an object to
+    allocate and return a pointer to void. For example:
+            extern void *alloc(size_t);
+            double *dp = alloc(sizeof *dp);
+    The implementation of the alloc function should ensure that its return value is aligned suitably for
+    conversion to a pointer to double.
+
+

+
+
7   EXAMPLE 2      Another use of the sizeof operator is to compute the number of elements in an array:
+            sizeof array / sizeof array[0]
+
+

+
+
8   EXAMPLE 3      In this example, the size of a variable length array is computed and returned from a
+    function:
+            #include <stddef.h>
+

+
 

 
6.5.4 [Cast operators]

-

-
-
-
1            cast-expression:
+
+
1 Syntax
+            cast-expression:
                     unary-expression
                     ( type-name ) cast-expression
     Constraints
 

-
-
+
 
2   Unless the type name specifies a void type, the type name shall specify atomic, qualified,
     or unqualified scalar type, and the operand shall have scalar type.
 

-
-
-
3   Conversions that involve pointers, other than where permitted by the constraints of 6.5.16.1, 
+
+
3   Conversions that involve pointers, other than where permitted by the constraints of 6.5.16.1,
     shall be specified by means of an explicit cast.
 

-
-
+
 
4   A pointer type shall not be converted to any floating type. A floating type shall not be
     converted to any pointer type.
     Semantics
 

-
-
+
 
5   Preceding an expression by a parenthesized type name converts the value of the
-    expression to the named type. This construction is called a cast .104) A cast that specifies
+    expression to the named type. This construction is called a cast .[104] A cast that specifies
     no conversion has no effect on the type or value of an expression.
 

-
 
 
Footnote 104) A cast does not yield an lvalue. Thus, a cast to a qualified type has the same effect as a cast to the
          unqualified version of the type.
 

 
-
+
 
6   If the value of the expression is represented with greater range or precision than required
-    by the type named by the cast (6.3.1.8), then the cast specifies a conversion even if the
+    by the type named by the cast (6.3.1.8), then the cast specifies a conversion even if the
     type of the expression is the same as the named type and removes any extra range and
     precision.
-    Forward references: equality operators (6.5.9), function declarators (including
-    prototypes) (6.7.6.3), simple assignment (6.5.16.1), type names (6.7.7).
+    Forward references: equality operators (6.5.9), function declarators (including
+    prototypes) (6.7.6.3), simple assignment (6.5.16.1), type names (6.7.7).
 
 

-
-
+
 

 
6.5.5 [Multiplicative operators]

-

-
-
-
1            multiplicative-expression:
+
+
1 Syntax
+            multiplicative-expression:
                      cast-expression
                      multiplicative-expression * cast-expression
                      multiplicative-expression / cast-expression
                      multiplicative-expression % cast-expression
     Constraints
 

-
-
+
 
2   Each of the operands shall have arithmetic type. The operands of the % operator shall
     have integer type.
     Semantics
 

-
-
+
 
3   The usual arithmetic conversions are performed on the operands.
 

-
-
+
 
4   The result of the binary * operator is the product of the operands.
 

-
-
+
 
5   The result of the / operator is the quotient from the division of the first operand by the
     second; the result of the % operator is the remainder. In both operations, if the value of
     the second operand is zero, the behavior is undefined.
 

-
-
+
 
6   When integers are divided, the result of the / operator is the algebraic quotient with any
-    fractional part discarded.105) If the quotient a/b is representable, the expression
+    fractional part discarded.[105] If the quotient a/b is representable, the expression
     (a/b)*b + a%b shall equal a; otherwise, the behavior of both a/b and a%b is
     undefined.
 

-
 
 
Footnote 105) This is often called ``truncation toward zero''.
-

-
-
-

-
6.5.6 [Additive operators]

-

-
-
-
1            additive-expression:
-                    multiplicative-expression
-                    additive-expression + multiplicative-expression
-                    additive-expression - multiplicative-expression
-    Constraints
-

-
-
-
2   For addition, either both operands shall have arithmetic type, or one operand shall be a
-    pointer to a complete object type and the other shall have integer type. (Incrementing is
-    equivalent to adding 1.)
-

-
-
-
3   For subtraction, one of the following shall hold:
-
     -- both operands have arithmetic type;
     -- both operands are pointers to qualified or unqualified versions of compatible complete
        object types; or
@@ -5638,29 +4900,44 @@ Forward references:         conditional inclusion (6.10.1), complex arithmetic
        integer type.
     (Decrementing is equivalent to subtracting 1.)
     Semantics
-

+

 
-
+
+

+
6.5.6 [Additive operators]

+
+
1 Syntax
+            additive-expression:
+                    multiplicative-expression
+                    additive-expression + multiplicative-expression
+                    additive-expression - multiplicative-expression
+    Constraints
+

+
+
2   For addition, either both operands shall have arithmetic type, or one operand shall be a
+    pointer to a complete object type and the other shall have integer type. (Incrementing is
+    equivalent to adding 1.)
+

+
+
3   For subtraction, one of the following shall hold:
+

+
 
4   If both operands have arithmetic type, the usual arithmetic conversions are performed on
     them.
 

-
-
+
 
5   The result of the binary + operator is the sum of the operands.
 

-
-
+
 
6   The result of the binary - operator is the difference resulting from the subtraction of the
     second operand from the first.
 

-
-
+
 
7   For the purposes of these operators, a pointer to an object that is not an element of an
     array behaves the same as a pointer to the first element of an array of length one with the
     type of the object as its element type.
 

-
-
+
 
8   When an expression that has integer type is added to or subtracted from a pointer, the
     result has the type of the pointer operand. If the pointer operand points to an element of
     an array object, and the array is large enough, the result points to an element offset from
@@ -5677,8 +4954,7 @@ Forward references:         conditional inclusion (6.10.1), complex arithmetic
     behavior is undefined. If the result points one past the last element of the array object, it
     shall not be used as the operand of a unary * operator that is evaluated.
 

-
-
+
 
9   When two pointers are subtracted, both shall point to elements of the same array object,
     or one past the last element of the array object; the result is the difference of the
     subscripts of the two array elements. The size of the result is implementation-defined,
@@ -5692,9 +4968,8 @@ Forward references:         conditional inclusion (6.10.1), complex arithmetic
      to the last element of the same array object, the expression ((Q)+1)-(P) has the same
      value as ((Q)-(P))+1 and as -((P)-((Q)+1)), and has the value zero if the
      expression P points one past the last element of the array object, even though the
-     expression (Q)+1 does not point to an element of the array object.106)
+     expression (Q)+1 does not point to an element of the array object.[106]
 

-
 
 
Footnote 106) Another way to approach pointer arithmetic is first to convert the pointer(s) to character pointer(s): In
           this scheme the integer expression added to or subtracted from the converted pointer is first multiplied
@@ -5704,9 +4979,10 @@ Forward references:         conditional inclusion (6.10.1), complex arithmetic
           When viewed in this way, an implementation need only provide one extra byte (which may overlap
           another object in the program) just after the end of the object in order to satisfy the ``one past the last
           element'' requirements.
+    greater than or equal to the width of the promoted left operand, the behavior is undefined.
 

 
-
+
 
10   EXAMPLE        Pointer arithmetic is well defined with pointers to variable length array types.
               {
                        int n = 4, m = 3;
@@ -5717,63 +4993,52 @@ Forward references:         conditional inclusion (6.10.1), complex arithmetic
                        n = p - a;                  //   n == 1
               }
 

-
-
+
 
11   If array a in the above example were declared to be an array of known constant size, and pointer p were
      declared to be a pointer to an array of the same known constant size (pointing to a), the results would be
      the same.
 
-     Forward references: array declarators (6.7.6.2), common definitions <stddef.h>
-     (7.19).
+     Forward references: array declarators (6.7.6.2), common definitions <stddef.h>
+     (7.19).
 

-
-
+
 

 
6.5.7 [Bitwise shift operators]

-

-
-
-
1             shift-expression:
+
+
1 Syntax
+             shift-expression:
                       additive-expression
                       shift-expression << additive-expression
                       shift-expression >> additive-expression
      Constraints
 

-
-
+
 
2    Each of the operands shall have integer type.
      Semantics
 

-
-
+
 
3    The integer promotions are performed on each of the operands. The type of the result is
      that of the promoted left operand. If the value of the right operand is negative or is
-
-    greater than or equal to the width of the promoted left operand, the behavior is undefined.
 

-
-
+
 
4   The result of E1 << E2 is E1 left-shifted E2 bit positions; vacated bits are filled with
-    zeros. If E1 has an unsigned type, the value of the result is E1 × 2E2 , reduced modulo
+    zeros. If E1 has an unsigned type, the value of the result is E1 \xD7 2E2 , reduced modulo
     one more than the maximum value representable in the result type. If E1 has a signed
-    type and nonnegative value, and E1 × 2E2 is representable in the result type, then that is
+    type and nonnegative value, and E1 \xD7 2E2 is representable in the result type, then that is
     the resulting value; otherwise, the behavior is undefined.
 

-
-
+
 
5   The result of E1 >> E2 is E1 right-shifted E2 bit positions. If E1 has an unsigned type
     or if E1 has a signed type and a nonnegative value, the value of the result is the integral
     part of the quotient of E1 / 2E2 . If E1 has a signed type and a negative value, the
     resulting value is implementation-defined.
 

-
-
+
 

 
6.5.8 [Relational operators]

-

-
-
-
1            relational-expression:
+
+
1 Syntax
+            relational-expression:
                      shift-expression
                      relational-expression   <    shift-expression
                      relational-expression   >    shift-expression
@@ -5781,27 +5046,23 @@ Forward references:         conditional inclusion (6.10.1), complex arithmetic
                      relational-expression   >=   shift-expression
     Constraints
 

-
-
+
 
2   One of the following shall hold:
     -- both operands have real type; or
     -- both operands are pointers to qualified or unqualified versions of compatible object
        types.
     Semantics
 

-
-
+
 
3   If both of the operands have arithmetic type, the usual arithmetic conversions are
     performed.
 

-
-
+
 
4   For the purposes of these operators, a pointer to an object that is not an element of an
     array behaves the same as a pointer to the first element of an array of length one with the
     type of the object as its element type.
 

-
-
+
 
5   When two pointers are compared, the result depends on the relative locations in the
     address space of the objects pointed to. If two pointers to object types both point to the
     same object, or both point one past the last element of the same array object, they
@@ -5812,35 +5073,31 @@ Forward references:         conditional inclusion (6.10.1), complex arithmetic
 
     values. All pointers to members of the same union object compare equal. If the
     expression P points to an element of an array object and the expression Q points to the
-    last element of the same array object, the pointer expression Q+1 compares greater than P. 
+    last element of the same array object, the pointer expression Q+1 compares greater than P.
     In all other cases, the behavior is undefined.
 

-
-
+
 
6   Each of the operators < (less than), > (greater than), <= (less than or equal to), and >=
     (greater than or equal to) shall yield 1 if the specified relation is true and 0 if it is
-    false.107) The result has type int.
+    false.[107] The result has type int.
 

-
 
 
Footnote 107) The expression a<b<c is not interpreted as in ordinary mathematics. As the syntax indicates, it
          means (a<b)<c; in other words, ``if a is less than b, compare 1 to c; otherwise, compare 0 to c''.
 

 
-
+
 

 
6.5.9 [Equality operators]

-

-
-
-
1            equality-expression:
+
+
1 Syntax
+            equality-expression:
                     relational-expression
                     equality-expression == relational-expression
                     equality-expression != relational-expression
     Constraints
 

-
-
+
 
2   One of the following shall hold:
     -- both operands have arithmetic type;
     -- both operands are pointers to qualified or unqualified versions of compatible types;
@@ -5849,19 +5106,17 @@ Forward references:         conditional inclusion (6.10.1), complex arithmetic
     -- one operand is a pointer and the other is a null pointer constant.
     Semantics
 

-
-
+
 
3   The == (equal to) and != (not equal to) operators are analogous to the relational
-    operators except for their lower precedence.108) Each of the operators yields 1 if the
+    operators except for their lower precedence.[108] Each of the operators yields 1 if the
     specified relation is true and 0 if it is false. The result has type int. For any pair of
     operands, exactly one of the relations is true.
 

-
 
 
Footnote 108) Because of the precedences, a<b == c<d is 1 whenever a<b and c<d have the same truth-value.
 

 
-
+
 
4   If both of the operands have arithmetic type, the usual arithmetic conversions are
     performed. Values of complex types are equal if and only if both their real parts are equal
     and also their imaginary parts are equal. Any two values of arithmetic types from
@@ -5869,23 +5124,20 @@ Forward references:         conditional inclusion (6.10.1), complex arithmetic
     (complex) result type determined by the usual arithmetic conversions are equal.
 
 

-
-
+
 
5   Otherwise, at least one operand is a pointer. If one operand is a pointer and the other is a
     null pointer constant, the null pointer constant is converted to the type of the pointer. If
     one operand is a pointer to an object type and the other is a pointer to a qualified or
     unqualified version of void, the former is converted to the type of the latter.
 

-
-
+
 
6   Two pointers compare equal if and only if both are null pointers, both are pointers to the
     same object (including a pointer to an object and a subobject at its beginning) or function,
     both are pointers to one past the last element of the same array object, or one is a pointer
     to one past the end of one array object and the other is a pointer to the start of a different
     array object that happens to immediately follow the first array object in the address
-    space.109)
+    space.[109]
 

-
 
 
Footnote 109) Two objects may be adjacent in memory because they are adjacent elements of a larger array or
          adjacent members of a structure with no padding between them, or because the implementation chose
@@ -5894,169 +5146,140 @@ Forward references:         conditional inclusion (6.10.1), complex arithmetic
          behavior.
 

 
-
+
 
7   For the purposes of these operators, a pointer to an object that is not an element of an
     array behaves the same as a pointer to the first element of an array of length one with the
     type of the object as its element type.
 

-
-
+
 

 
6.5.10 [Bitwise AND operator]

-

-
-
-
1            AND-expression:
+
+
1 Syntax
+            AND-expression:
                    equality-expression
                    AND-expression & equality-expression
     Constraints
 

-
-
+
 
2   Each of the operands shall have integer type.
     Semantics
 

-
-
+
 
3   The usual arithmetic conversions are performed on the operands.
 

-
-
+
 
4   The result of the binary & operator is the bitwise AND of the operands (that is, each bit in
     the result is set if and only if each of the corresponding bits in the converted operands is
     set).
 
 

-
-
+
 

 
6.5.11 [Bitwise exclusive OR operator]

-

-
-
-
1            exclusive-OR-expression:
+
+
1 Syntax
+            exclusive-OR-expression:
                      AND-expression
                      exclusive-OR-expression ^ AND-expression
     Constraints
 

-
-
+
 
2   Each of the operands shall have integer type.
     Semantics
 

-
-
+
 
3   The usual arithmetic conversions are performed on the operands.
 

-
-
+
 
4   The result of the ^ operator is the bitwise exclusive OR of the operands (that is, each bit
     in the result is set if and only if exactly one of the corresponding bits in the converted
     operands is set).
 

-
-
+
 

 
6.5.12 [Bitwise inclusive OR operator]

-

-
-
-
1            inclusive-OR-expression:
+
+
1 Syntax
+            inclusive-OR-expression:
                      exclusive-OR-expression
                      inclusive-OR-expression | exclusive-OR-expression
     Constraints
 

-
-
+
 
2   Each of the operands shall have integer type.
     Semantics
 

-
-
+
 
3   The usual arithmetic conversions are performed on the operands.
 

-
-
+
 
4   The result of the | operator is the bitwise inclusive OR of the operands (that is, each bit in
     the result is set if and only if at least one of the corresponding bits in the converted
     operands is set).
 

-
-
+
 

 
6.5.13 [Logical AND operator]

-

-
-
-
1             logical-AND-expression:
+
+
1 Syntax
+             logical-AND-expression:
                       inclusive-OR-expression
                       logical-AND-expression && inclusive-OR-expression
     Constraints
 

-
-
+
 
2   Each of the operands shall have scalar type.
     Semantics
 

-
-
+
 
3   The && operator shall yield 1 if both of its operands compare unequal to 0; otherwise, it
     yields 0. The result has type int.
 

-
-
+
 
4   Unlike the bitwise binary & operator, the && operator guarantees left-to-right evaluation;
     if the second operand is evaluated, there is a sequence point between the evaluations of
     the first and second operands. If the first operand compares equal to 0, the second
     operand is not evaluated.
 

-
-
+
 

 
6.5.14 [Logical OR operator]

-

-
-
-
1             logical-OR-expression:
+
+
1 Syntax
+             logical-OR-expression:
                       logical-AND-expression
                       logical-OR-expression || logical-AND-expression
     Constraints
 

-
-
+
 
2   Each of the operands shall have scalar type.
     Semantics
 

-
-
+
 
3   The || operator shall yield 1 if either of its operands compare unequal to 0; otherwise, it
     yields 0. The result has type int.
 

-
-
+
 
4   Unlike the bitwise | operator, the || operator guarantees left-to-right evaluation; if the
     second operand is evaluated, there is a sequence point between the evaluations of the first
     and second operands. If the first operand compares unequal to 0, the second operand is
     not evaluated.
 

-
-
+
 

 
6.5.15 [Conditional operator]

-

-
-
-
1            conditional-expression:
+
+
1 Syntax
+            conditional-expression:
                     logical-OR-expression
                     logical-OR-expression ? expression : conditional-expression
     Constraints
 

-
-
+
 
2   The first operand shall have scalar type.
 

-
-
+
 
3   One of the following shall hold for the second and third operands:
     -- both operands have arithmetic type;
     -- both operands have the same structure or union type;
@@ -6067,27 +5290,24 @@ Forward references:         conditional inclusion (6.10.1), complex arithmetic
        unqualified version of void.
     Semantics
 

-
-
+
 
4   The first operand is evaluated; there is a sequence point between its evaluation and the
     evaluation of the second or third operand (whichever is evaluated). The second operand
     is evaluated only if the first compares unequal to 0; the third operand is evaluated only if
     the first compares equal to 0; the result is the value of the second or third operand
-    (whichever is evaluated), converted to the type described below.110)
+    (whichever is evaluated), converted to the type described below.[110]
 

-
 
 
Footnote 110) A conditional expression does not yield an lvalue.
 

 
-
+
 
5   If both the second and third operands have arithmetic type, the result type that would be
     determined by the usual arithmetic conversions, were they applied to those two operands,
     is the type of the result. If both the operands have structure or union type, the result has
     that type. If both operands have void type, the result has void type.
 

-
-
+
 
6   If both the second and third operands are pointers or one is a null pointer constant and the
     other is a pointer, the result type is a pointer to a type qualified with all the type qualifiers
     of the types referenced by both operands. Furthermore, if both operands are pointers to
@@ -6098,14 +5318,12 @@ Forward references:         conditional inclusion (6.10.1), complex arithmetic
     pointer to an appropriately qualified version of void.
 
 

-
-
+
 
7   EXAMPLE The common type that results when the second and third operands are pointers is determined
     in two independent stages. The appropriate qualifiers, for example, do not depend on whether the two
     pointers have compatible types.
 

-
-
+
 
8   Given the declarations
               const void *c_vp;
               void *vp;
@@ -6123,48 +5341,42 @@ Forward references:         conditional inclusion (6.10.1), complex arithmetic
               vp      ip        void *
 
 

-
-
+
 

 
6.5.16 [Assignment operators]

-

-
-
-
1            assignment-expression:
+
+
1 Syntax
+            assignment-expression:
                     conditional-expression
                     unary-expression assignment-operator assignment-expression
              assignment-operator: one of
                     = *= /= %= +=                       -=     <<=      >>=      &=     ^=     |=
     Constraints
 

-
-
+
 
2   An assignment operator shall have a modifiable lvalue as its left operand.
     Semantics
 

-
-
+
 
3   An assignment operator stores a value in the object designated by the left operand. An
-    assignment expression has the value of the left operand after the assignment,111) but is not
+    assignment expression has the value of the left operand after the assignment,[111] but is not
     an lvalue. The type of an assignment expression is the type the left operand would have
     after lvalue conversion. The side effect of updating the stored value of the left operand is
     sequenced after the value computations of the left and right operands. The evaluations of
     the operands are unsequenced.
 
 

-
 
 
Footnote 111) The implementation is permitted to read the object to determine the value but is not required to, even
          when the object has volatile-qualified type.
 

 
-
+
 

 
6.5.16.1 [Simple assignment]

-

-
-
-
1   One of the following shall hold:112)
+
+
1 Constraints
+   One of the following shall hold:[112]
     -- the left operand has atomic, qualified, or unqualified arithmetic type, and the right has
        arithmetic type;
     -- the left operand has an atomic, qualified, or unqualified version of a structure or union
@@ -6184,30 +5396,11 @@ Forward references:         conditional inclusion (6.10.1), complex arithmetic
        pointer.
     Semantics
 

-
 
 
Footnote 112) The asymmetric appearance of these constraints with respect to type qualifiers is due to the conversion
-         (specified in 6.3.2.1) that changes lvalues to ``the value of the expression'' and thus removes any type
+         (specified in 6.3.2.1) that changes lvalues to ``the value of the expression'' and thus removes any type
          qualifiers that were applied to the type category of the expression (for example, it removes const but
          not volatile from the type int volatile * const).
-

-
-
-
2   In simple assignment (=), the value of the right operand is converted to the type of the
-    assignment expression and replaces the value stored in the object designated by the left
-    operand.
-

-
-
-
3   If the value being stored in an object is read from another object that overlaps in any way
-    the storage of the first object, then the overlap shall be exact and the two objects shall
-    have qualified or unqualified versions of a compatible type; otherwise, the behavior is
-    undefined.
-

-
-
-
4   EXAMPLE 1       In the program fragment
-
             int f(void);
             char c;
             /* ... */
@@ -6218,10 +5411,24 @@ Forward references:         conditional inclusion (6.10.1), complex arithmetic
     values as unsigned char (and char is narrower than int), the result of the conversion cannot be
     negative, so the operands of the comparison can never compare equal. Therefore, for full portability, the
     variable c should be declared as int.
+

+
+
+
2   In simple assignment (=), the value of the right operand is converted to the type of the
+    assignment expression and replaces the value stored in the object designated by the left
+    operand.
+

+
+
3   If the value being stored in an object is read from another object that overlaps in any way
+    the storage of the first object, then the overlap shall be exact and the two objects shall
+    have qualified or unqualified versions of a compatible type; otherwise, the behavior is
+    undefined.
+

+
+
4   EXAMPLE 1       In the program fragment
 
 

-
-
+
 
5   EXAMPLE 2       In the fragment:
             char c;
             int i;
@@ -6232,8 +5439,7 @@ Forward references:         conditional inclusion (6.10.1), complex arithmetic
     that is, long int type.
 
 

-
-
+
 
6   EXAMPLE 3       Consider the fragment:
             const char **cpp;
             char *p;
@@ -6245,34 +5451,34 @@ Forward references:         conditional inclusion (6.10.1), complex arithmetic
     value of the const object c.
 
 

-
-
+
 

 
6.5.16.2 [Compound assignment]

-

-
-
-
1   For the operators += and -= only, either the left operand shall be an atomic, qualified, or
+
+
1 Constraints
+   For the operators += and -= only, either the left operand shall be an atomic, qualified, or
     unqualified pointer to a complete object type, and the right shall have integer type; or the
     left operand shall have atomic, qualified, or unqualified arithmetic type, and the right
     shall have arithmetic type.
 

-
-
+
 
2   For the other operators, the left operand shall have atomic, qualified, or unqualified
     arithmetic type, and (considering the type the left operand would have after lvalue
     conversion) each operand shall have arithmetic type consistent with those allowed by the
     corresponding binary operator.
     Semantics
 

-
-
+
 
3   A compound assignment of the form E1 op = E2 is equivalent to the simple assignment
     expression E1 = E1 op (E2), except that the lvalue E1 is evaluated only once, and with
     respect to an indeterminately-sequenced function call, the operation of a compound
     assignment is a single evaluation. If E1 has an atomic type, compound assignment is a
     read-modify-write operation with memory_order_seq_cst memory order
-    semantics.113)
+    semantics.[113]
+
+

+
+
Footnote 113) Where a pointer to an atomic object can be formed and E1 and E2 have integer type, this is equivalent
      to the following code sequence where T1 is the type of E1 and T2 is the type of E2:
                T1 *addr = &E1;
                T2 val = (E2);
@@ -6304,36 +5510,28 @@ Forward references:         conditional inclusion (6.10.1), complex arithmetic
                        feupdateenv(&fenv);
       If FLT_EVAL_METHOD is not 0, then T2 must be a type with the range and precision to which E2 is
       evaluated in order to satisfy the equivalence.
-
-

-
-
-
Footnote 113) Where a pointer to an atomic object can be formed and E1 and E2 have integer type, this is equivalent
 

 
-
+
 

 
6.5.17 [Comma operator]

-

-
-
-
1            expression:
+
+
1 Syntax
+            expression:
                     assignment-expression
                     expression , assignment-expression
     Semantics
 

-
-
+
 
2   The left operand of a comma operator is evaluated as a void expression; there is a
     sequence point between its evaluation and that of the right operand. Then the right
-    operand is evaluated; the result has its type and value.114)
+    operand is evaluated; the result has its type and value.[114]
 

-
 
 
Footnote 114) A comma operator does not yield an lvalue.
 

 
-
+
 
3   EXAMPLE As indicated by the syntax, the comma operator (as described in this subclause) cannot
     appear in contexts where a comma is used to separate items in a list (such as arguments to functions or lists
     of initializers). On the other hand, it can be used within a parenthesized expression or within the second
@@ -6341,83 +5539,73 @@ Forward references:         conditional inclusion (6.10.1), complex arithmetic
               f(a, (t=3, t+2), c)
     the function has three arguments, the second of which has the value 5.
 
-    Forward references: initialization (6.7.9).
+    Forward references: initialization (6.7.9).
 
 

-
-
+
 

 
6.6 [Constant expressions]

-

-
-
-
1            constant-expression:
+
+
1 Syntax
+            constant-expression:
                     conditional-expression
     Description
 

-
-
+
 
2   A constant expression can be evaluated during translation rather than runtime, and
     accordingly may be used in any place that a constant may be.
     Constraints
 

-
-
+
 
3   Constant expressions shall not contain assignment, increment, decrement, function-call,
     or comma operators, except when they are contained within a subexpression that is not
-    evaluated.115)
+    evaluated.[115]
 

-
 
-
Footnote 115) The operand of a sizeof or _Alignof operator is usually not evaluated (6.5.3.4).
+
Footnote 115) The operand of a sizeof or _Alignof operator is usually not evaluated (6.5.3.4).
 

 
-
+
 
4   Each constant expression shall evaluate to a constant that is in the range of representable
     values for its type.
     Semantics
 

-
-
+
 
5   An expression that evaluates to a constant is required in several contexts. If a floating
     expression is evaluated in the translation environment, the arithmetic range and precision
     shall be at least as great as if the expression were being evaluated in the execution
-    environment.116)
+    environment.[116]
 

-
 
 
Footnote 116) The use of evaluation formats as characterized by FLT_EVAL_METHOD also applies to evaluation in
          the translation environment.
 

 
-
-
6   An integer constant expression117) shall have integer type and shall only have operands
+
+
6   An integer constant expression[117] shall have integer type and shall only have operands
     that are integer constants, enumeration constants, character constants, sizeof
     expressions whose results are integer constants, _Alignof expressions, and floating
     constants that are the immediate operands of casts. Cast operators in an integer constant
     expression shall only convert arithmetic types to integer types, except as part of an
     operand to the sizeof or _Alignof operator.
 

-
 
 
Footnote 117) An integer constant expression is required in a number of contexts such as the size of a bit-field
          member of a structure, the value of an enumeration constant, and the size of a non-variable length
          array. Further constraints that apply to the integer constant expressions used in conditional-inclusion
-         preprocessing directives are discussed in 6.10.1.
-

-
-
-
7   More latitude is permitted for constant expressions in initializers. Such a constant
-    expression shall be, or evaluate to, one of the following:
-    -- an arithmetic constant expression,
-
+         preprocessing directives are discussed in 6.10.1.
      -- a null pointer constant,
      -- an address constant, or
      -- an address constant for a complete object type plus or minus an integer constant
         expression.
-

+

 
-
+
+
7   More latitude is permitted for constant expressions in initializers. Such a constant
+    expression shall be, or evaluate to, one of the following:
+    -- an arithmetic constant expression,
+

+
 
8    An arithmetic constant expression shall have arithmetic type and shall only have
      operands that are integer constants, floating constants, enumeration constants, character
      constants, sizeof expressions whose results are integer constants, and _Alignof
@@ -6425,8 +5613,7 @@ Forward references:         conditional inclusion (6.10.1), complex arithmetic
      arithmetic types to arithmetic types, except as part of an operand to a sizeof or
      _Alignof operator.
 

-
-
+
 
9    An address constant is a null pointer, a pointer to an lvalue designating an object of static
      storage duration, or a pointer to a function designator; it shall be created explicitly using
      the unary & operator or an integer constant cast to pointer type, or implicitly by the use of
@@ -6435,31 +5622,27 @@ Forward references:         conditional inclusion (6.10.1), complex arithmetic
      be used in the creation of an address constant, but the value of an object shall not be
      accessed by use of these operators.
 

-
-
+
 
10   An implementation may accept other forms of constant expressions.
 

-
-
+
 
11   The semantic rules for the evaluation of a constant expression are the same as for
-     nonconstant expressions.118)
-     Forward references: array declarators (6.7.6.2), initialization (6.7.9).
+     nonconstant expressions.[118]
+     Forward references: array declarators (6.7.6.2), initialization (6.7.9).
 
 

-
 
 
Footnote 118) Thus, in the following initialization,
                      static int i = 2 || 1 / 0;
             the expression is a valid integer constant expression with value one.
 

 
-
+
 

 
6.7 [Declarations]

-

-
-
-
1            declaration:
+
+
1 Syntax
+            declaration:
                     declaration-specifiers init-declarator-listopt ;
                     static_assert-declaration
              declaration-specifiers:
@@ -6476,65 +5659,57 @@ Forward references:         conditional inclusion (6.10.1), complex arithmetic
                      declarator = initializer
     Constraints
 

-
-
+
 
2   A declaration other than a static_assert declaration shall declare at least a declarator
     (other than the parameters of a function or the members of a structure or union), a tag, or
     the members of an enumeration.
 

-
-
+
 
3   If an identifier has no linkage, there shall be no more than one declaration of the identifier
     (in a declarator or type specifier) with the same scope and in the same name space, except
     that:
     -- a typedef name may be redefined to denote the same type as it currently does,
        provided that type is not a variably modified type;
-    -- tags may be redeclared as specified in 6.7.2.3.
+    -- tags may be redeclared as specified in 6.7.2.3.
 

-
-
+
 
4   All declarations in the same scope that refer to the same object or function shall specify
     compatible types.
     Semantics
 

-
-
+
 
5   A declaration specifies the interpretation and attributes of a set of identifiers. A definition
     of an identifier is a declaration for that identifier that:
     -- for an object, causes storage to be reserved for that object;
-    -- for a function, includes the function body;119)
+    -- for a function, includes the function body;[119]
     -- for an enumeration constant, is the (only) declaration of the identifier;
     -- for a typedef name, is the first (or only) declaration of the identifier.
 

-
 
-
Footnote 119) Function definitions have a different syntax, described in 6.9.1.
+
Footnote 119) Function definitions have a different syntax, described in 6.9.1.
 

 
-
+
 
6   The declaration specifiers consist of a sequence of specifiers that indicate the linkage,
     storage duration, and part of the type of the entities that the declarators denote. The init-
     declarator-list is a comma-separated sequence of declarators, each of which may have
     additional type information, or an initializer, or both. The declarators contain the
     identifiers (if any) being declared.
 

-
-
+
 
7   If an identifier for an object is declared with no linkage, the type for the object shall be
     complete by the end of its declarator, or by the end of its init-declarator if it has an
     initializer; in the case of function parameters (including in prototypes), it is the adjusted
-    type (see 6.7.6.3) that is required to be complete.
-    Forward references: declarators (6.7.6), enumeration specifiers (6.7.2.2), initialization
-    (6.7.9), type names (6.7.7), type qualifiers (6.7.3).
+    type (see 6.7.6.3) that is required to be complete.
+    Forward references: declarators (6.7.6), enumeration specifiers (6.7.2.2), initialization
+    (6.7.9), type names (6.7.7), type qualifiers (6.7.3).
 

-
-
+
 

 
6.7.1 [Storage-class specifiers]

-

-
-
-
1            storage-class-specifier:
+
+
1 Syntax
+            storage-class-specifier:
                     typedef
                     extern
                     static
@@ -6543,70 +5718,60 @@ Forward references:         conditional inclusion (6.10.1), complex arithmetic
                     register
     Constraints
 

-
-
+
 
2   At most, one storage-class specifier may be given in the declaration specifiers in a
-    declaration, except that _Thread_local may appear with static or extern.120)
+    declaration, except that _Thread_local may appear with static or extern.[120]
 

-
 
-
Footnote 120) See ``future language directions'' (6.11.5).
+
Footnote 120) See ``future language directions'' (6.11.5).
+    Semantics
 

 
-
+
 
3   In the declaration of an object with block scope, if the declaration specifiers include
     _Thread_local, they shall also include either static or extern. If
     _Thread_local appears in any declaration of an object, it shall be present in every
     declaration of that object.
 

-
-
+
 
4   _Thread_local shall not appear in the declaration specifiers of a function declaration.
-
-    Semantics
 

-
-
+
 
5   The typedef specifier is called a ``storage-class specifier'' for syntactic convenience
-    only; it is discussed in 6.7.8. The meanings of the various linkages and storage durations
-    were discussed in 6.2.2 and 6.2.4.
+    only; it is discussed in 6.7.8. The meanings of the various linkages and storage durations
+    were discussed in 6.2.2 and 6.2.4.
 

-
-
+
 
6   A declaration of an identifier for an object with storage-class specifier register
     suggests that access to the object be as fast as possible. The extent to which such
-    suggestions are effective is implementation-defined.121)
+    suggestions are effective is implementation-defined.[121]
 

-
 
 
Footnote 121) The implementation may treat any register declaration simply as an auto declaration. However,
          whether or not addressable storage is actually used, the address of any part of an object declared with
          storage-class specifier register cannot be computed, either explicitly (by use of the unary &
-         operator as discussed in 6.5.3.2) or implicitly (by converting an array name to a pointer as discussed in
-         6.3.2.1). Thus, the only operators that can be applied to an array declared with storage-class specifier
+         operator as discussed in 6.5.3.2) or implicitly (by converting an array name to a pointer as discussed in
+         6.3.2.1). Thus, the only operators that can be applied to an array declared with storage-class specifier
          register are sizeof and _Alignof.
 

 
-
+
 
7   The declaration of an identifier for a function that has block scope shall have no explicit
     storage-class specifier other than extern.
 

-
-
+
 
8   If an aggregate or union object is declared with a storage-class specifier other than
     typedef, the properties resulting from the storage-class specifier, except with respect to
     linkage, also apply to the members of the object, and so on recursively for any aggregate
     or union member objects.
-    Forward references: type definitions (6.7.8).
+    Forward references: type definitions (6.7.8).
 

-
-
+
 

 
6.7.2 [Type specifiers]

-

-
-
-
1            type-specifier:
+
+
1 Syntax
+            type-specifier:
                     void
                     char
                     short
@@ -6624,8 +5789,7 @@ Forward references:         conditional inclusion (6.10.1), complex arithmetic
                     typedef-name
     Constraints
 

-
-
+
 
2   At least one type specifier shall be given in the declaration specifiers in each declaration,
     and in the specifier-qualifier list in each struct declaration and type name. Each list of
     type specifiers shall be one of the following multisets (delimited by commas, when there
@@ -6657,34 +5821,29 @@ Forward references:         conditional inclusion (6.10.1), complex arithmetic
     -- enum specifier
     -- typedef name
 

-
-
+
 
3   The type specifier _Complex shall not be used if the implementation does not support
-    complex types (see 6.10.8.3).
+    complex types (see 6.10.8.3).
     Semantics
 

-
-
-
4   Specifiers for structures, unions, enumerations, and atomic types are discussed in 6.7.2.1
-    through 6.7.2.4. Declarations of typedef names are discussed in 6.7.8. The
-    characteristics of the other types are discussed in 6.2.5.
+
+
4   Specifiers for structures, unions, enumerations, and atomic types are discussed in 6.7.2.1
+    through 6.7.2.4. Declarations of typedef names are discussed in 6.7.8. The
+    characteristics of the other types are discussed in 6.2.5.
 

-
-
+
 
5   Each of the comma-separated multisets designates the same type, except that for bit-
     fields, it is implementation-defined whether the specifier int designates the same type as
     signed int or the same type as unsigned int.
-    Forward references: atomic type specifiers (6.7.2.4), enumeration specifiers (6.7.2.2),
-    structure and union specifiers (6.7.2.1), tags (6.7.2.3), type definitions (6.7.8).
+    Forward references: atomic type specifiers (6.7.2.4), enumeration specifiers (6.7.2.2),
+    structure and union specifiers (6.7.2.1), tags (6.7.2.3), type definitions (6.7.8).
 

-
-
+
 

 
6.7.2.1 [Structure and union specifiers]

-

-
-
-
1            struct-or-union-specifier:
+
+
1 Syntax
+            struct-or-union-specifier:
                      struct-or-union identifieropt { struct-declaration-list }
                      struct-or-union identifier
             struct-or-union:
@@ -6707,13 +5866,11 @@ Forward references:         conditional inclusion (6.10.1), complex arithmetic
                     declaratoropt : constant-expression
     Constraints
 

-
-
+
 
2   A struct-declaration that does not declare an anonymous structure or anonymous union
     shall contain a struct-declarator-list.
 

-
-
+
 
3   A structure or union shall not contain a member with incomplete or function type (hence,
     a structure shall not contain an instance of itself, but may contain a pointer to an instance
     of itself), except that the last member of a structure with more than one named member
@@ -6721,39 +5878,33 @@ Forward references:         conditional inclusion (6.10.1), complex arithmetic
     recursively, a member that is such a structure) shall not be a member of a structure or an
     element of an array.
 

-
-
+
 
4   The expression that specifies the width of a bit-field shall be an integer constant
     expression with a nonnegative value that does not exceed the width of an object of the
-    type that would be specified were the colon and expression omitted.122) If the value is
+    type that would be specified were the colon and expression omitted.[122] If the value is
     zero, the declaration shall have no declarator.
 

-
 
 
Footnote 122) While the number of bits in a _Bool object is at least CHAR_BIT, the width (number of sign and
          value bits) of a _Bool may be just 1 bit.
+     Semantics
 

 
-
+
 
5   A bit-field shall have a type that is a qualified or unqualified version of _Bool, signed
     int, unsigned int, or some other implementation-defined type. It is
     implementation-defined whether atomic types are permitted.
-
-     Semantics
 

-
-
-
6    As discussed in 6.2.5, a structure is a type consisting of a sequence of members, whose
+
+
6    As discussed in 6.2.5, a structure is a type consisting of a sequence of members, whose
      storage is allocated in an ordered sequence, and a union is a type consisting of a sequence
      of members whose storage overlap.
 

-
-
+
 
7    Structure and union specifiers have the same form. The keywords struct and union
      indicate that the type being specified is, respectively, a structure type or a union type.
 

-
-
+
 
8    The presence of a struct-declaration-list in a struct-or-union-specifier declares a new type,
      within a translation unit. The struct-declaration-list is a sequence of declarations for the
      members of the structure or union. If the struct-declaration-list does not contain any
@@ -6761,17 +5912,15 @@ Forward references:         conditional inclusion (6.10.1), complex arithmetic
      behavior is undefined. The type is incomplete until immediately after the } that
      terminates the list, and complete thereafter.
 

-
-
+
 
9    A member of a structure or union may have any complete object type other than a
-     variably modified type.123) In addition, a member may be declared to consist of a
+     variably modified type.[123] In addition, a member may be declared to consist of a
      specified number of bits (including a sign bit, if any). Such a member is called a
-     bit-field ;124) its width is preceded by a colon.
+     bit-field ;[124] its width is preceded by a colon.
 

-
 
 
Footnote 123) A structure or union cannot contain a member with a variably modified type because member names
-          are not ordinary identifiers as defined in 6.2.3.
+          are not ordinary identifiers as defined in 6.2.3.
 

 
 
@@ -6779,19 +5928,18 @@ Forward references:         conditional inclusion (6.10.1), complex arithmetic
           or arrays of bit-field objects.
 

 
-
+
 
10   A bit-field is interpreted as having a signed or unsigned integer type consisting of the
-     specified number of bits.125) If the value 0 or 1 is stored into a nonzero-width bit-field of
+     specified number of bits.[125] If the value 0 or 1 is stored into a nonzero-width bit-field of
      type _Bool, the value of the bit-field shall compare equal to the value stored; a _Bool
      bit-field has the semantics of a _Bool.
 

-
 
-
Footnote 125) As specified in 6.7.2 above, if the actual type specifier used is int or a typedef-name defined as int,
+
Footnote 125) As specified in 6.7.2 above, if the actual type specifier used is int or a typedef-name defined as int,
           then it is implementation-defined whether the bit-field is signed or unsigned.
 

 
-
+
 
11   An implementation may allocate any addressable storage unit large enough to hold a bit-
      field. If enough space remains, a bit-field that immediately follows another bit-field in a
      structure shall be packed into adjacent bits of the same unit. If insufficient space remains,
@@ -6800,53 +5948,45 @@ Forward references:         conditional inclusion (6.10.1), complex arithmetic
      low-order or low-order to high-order) is implementation-defined. The alignment of the
      addressable storage unit is unspecified.
 

-
-
+
 
12   A bit-field declaration with no declarator, but only a colon and a width, indicates an
-     unnamed bit-field.126) As a special case, a bit-field structure member with a width of 0
-
-     indicates that no further bit-field is to be packed into the unit in which the previous bit-
-     field, if any, was placed.
+     unnamed bit-field.[126] As a special case, a bit-field structure member with a width of 0
 

-
 
 
Footnote 126) An unnamed bit-field structure member is useful for padding to conform to externally imposed
           layouts.
+     indicates that no further bit-field is to be packed into the unit in which the previous bit-
+     field, if any, was placed.
 

 
-
+
 
13   An unnamed member whose type specifier is a structure specifier with no tag is called an
      anonymous structure; an unnamed member whose type specifier is a union specifier with
      no tag is called an anonymous union. The members of an anonymous structure or union
      are considered to be members of the containing structure or union. This applies
      recursively if the containing structure or union is also anonymous.
 

-
-
+
 
14   Each non-bit-field member of a structure or union object is aligned in an implementation-
      defined manner appropriate to its type.
 

-
-
+
 
15   Within a structure object, the non-bit-field members and the units in which bit-fields
      reside have addresses that increase in the order in which they are declared. A pointer to a
      structure object, suitably converted, 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 may be unnamed
      padding within a structure object, but not at its beginning.
 

-
-
+
 
16   The size of a union is sufficient to contain the largest of its members. The value of at
      most one of the members can be stored in a union object at any time. A pointer to a
      union object, suitably converted, points to each of its members (or if a member is a bit-
      field, then to the unit in which it resides), and vice versa.
 

-
-
+
 
17   There may be unnamed padding at the end of a structure or union.
 

-
-
+
 
18   As a special case, the last element of a structure with more than one named member may
      have an incomplete array type; this is called a flexible array member . In most situations,
      the flexible array member is ignored. In particular, the size of the structure is as if the
@@ -6860,8 +6000,7 @@ Forward references:         conditional inclusion (6.10.1), complex arithmetic
      it had one element but the behavior is undefined if any attempt is made to access that
      element or to generate a pointer one past it.
 

-
-
+
 
19   EXAMPLE 1    The following illustrates anonymous structures and unions:
              struct v {
                    union {      // anonymous union
@@ -6875,8 +6014,7 @@ Forward references:         conditional inclusion (6.10.1), complex arithmetic
               v1.w.k = 5; // valid
 
 

-
-
+
 
20   EXAMPLE 2          After the declaration:
               struct s { int n; double d[]; };
      the structure struct s has a flexible array member d. A typical way to use this is:
@@ -6888,8 +6026,7 @@ Forward references:         conditional inclusion (6.10.1), complex arithmetic
      (there are circumstances in which this equivalence is broken; in particular, the offsets of member d might
      not be the same).
 

-
-
+
 
21   Following the above declaration:
               struct s t1 = { 0 };                         //   valid
               struct s t2 = { 1, { 4.2 }};                 //   invalid
@@ -6901,8 +6038,7 @@ Forward references:         conditional inclusion (6.10.1), complex arithmetic
      in which case the assignment would be legitimate. Nevertheless, it cannot appear in strictly conforming
      code.
 

-
-
+
 
22   After the further declaration:
               struct ss { int n; };
      the expressions:
@@ -6910,8 +6046,7 @@ Forward references:         conditional inclusion (6.10.1), complex arithmetic
               sizeof (struct s) >= offsetof(struct s, d)
      are always equal to 1.
 

-
-
+
 
23   If sizeof (double) is 8, then after the following code is executed:
               struct s *s1;
               struct s *s2;
@@ -6922,8 +6057,7 @@ Forward references:         conditional inclusion (6.10.1), complex arithmetic
               struct { int n; double d[8]; } *s1;
               struct { int n; double d[5]; } *s2;
 

-
-
+
 
24   Following the further successful assignments:
               s1 = malloc(sizeof (struct s) + 10);
               s2 = malloc(sizeof (struct s) + 6);
@@ -6936,16 +6070,14 @@ Forward references:         conditional inclusion (6.10.1), complex arithmetic
               dp = &(s2->d[0]);          //   valid
               *dp = 42;                  //   undefined behavior
 

-
-
+
 
25   The assignment:
               *s1 = *s2;
      only copies the member n; if any of the array elements are within the first sizeof (struct s) bytes
      of the structure, they might be copied or simply overwritten with indeterminate values.
 
 

-
-
+
 
26   EXAMPLE 3 Because members of anonymous structures and unions are considered to be members of the
      containing structure or union, struct s in the following example has more than one named member and
      thus the use of a flexible array member is valid:
@@ -6954,16 +6086,14 @@ Forward references:         conditional inclusion (6.10.1), complex arithmetic
                     int a[];
               };
 
-     Forward references: declarators (6.7.6), tags (6.7.2.3).
+     Forward references: declarators (6.7.6), tags (6.7.2.3).
 

-
-
+
 

 
6.7.2.2 [Enumeration specifiers]

-

-
-
-
1             enum-specifier:
+
+
1 Syntax
+             enum-specifier:
                     enum identifieropt { enumerator-list }
                     enum identifieropt { enumerator-list , }
                     enum identifier
@@ -6975,17 +6105,15 @@ Forward references:         conditional inclusion (6.10.1), complex arithmetic
                     enumeration-constant = constant-expression
      Constraints
 

-
-
+
 
2    The expression that defines the value of an enumeration constant shall be an integer
      constant expression that has a value representable as an int.
 
     Semantics
 

-
-
+
 
3   The identifiers in an enumerator list are declared as constants that have type int and
-    may appear wherever such are permitted.127) An enumerator with = defines its
+    may appear wherever such are permitted.[127] An enumerator with = defines its
     enumeration constant as the value of the constant expression. If the first enumerator has
     no =, the value of its enumeration constant is 0. Each subsequent enumerator with no =
     defines its enumeration constant as the value of the constant expression obtained by
@@ -6993,26 +6121,25 @@ Forward references:         conditional inclusion (6.10.1), complex arithmetic
     = may produce enumeration constants with values that duplicate other values in the same
     enumeration.) The enumerators of an enumeration are also known as its members.
 

-
 
 
Footnote 127) Thus, the identifiers of enumeration constants declared in the same scope shall all be distinct from
          each other and from other identifiers declared in ordinary declarators.
 

 
-
+
 
4   Each enumerated type shall be compatible with char, a signed integer type, or an
-    unsigned integer type. The choice of type is implementation-defined,128) but shall be
+    unsigned integer type. The choice of type is implementation-defined,[128] but shall be
     capable of representing the values of all the members of the enumeration. The
     enumerated type is incomplete until immediately after the } that terminates the list of
     enumerator declarations, and complete thereafter.
 

-
 
 
Footnote 128) An implementation may delay the choice of which integer type until all enumeration constants have
          been seen.
+    Semantics
 

 
-
+
 
5   EXAMPLE       The following fragment:
             enum hue { chartreuse, burgundy, claret=20, winedark };
             enum hue col, *cp;
@@ -7023,53 +6150,44 @@ Forward references:         conditional inclusion (6.10.1), complex arithmetic
     makes hue the tag of an enumeration, and then declares col as an object that has that type and cp as a
     pointer to an object that has that type. The enumerated values are in the set { 0, 1, 20, 21 }.
 
-    Forward references: tags (6.7.2.3).
+    Forward references: tags (6.7.2.3).
 

-
-
+
 

 
6.7.2.3 [Tags]

-

-
-
-
1   A specific type shall have its content defined at most once.
+
+
1 Constraints
+   A specific type shall have its content defined at most once.
 

-
-
+
 
2   Where two declarations that use the same tag declare the same type, they shall both use
     the same choice of struct, union, or enum.
 

-
-
+
 
3   A type specifier of the form
             enum identifier
     without an enumerator list shall only appear after the type it specifies is complete.
-
-    Semantics
 

-
-
+
 
4   All declarations of structure, union, or enumerated types that have the same scope and
     use the same tag declare the same type. Irrespective of whether there is a tag or what
-    other declarations of the type are in the same translation unit, the type is incomplete129)
+    other declarations of the type are in the same translation unit, the type is incomplete[129]
     until immediately after the closing brace of the list defining the content, and complete
     thereafter.
 

-
 
 
Footnote 129) An incomplete type may only by used when the size of an object of that type is not needed. It is not
          needed, for example, when a typedef name is declared to be a specifier for a structure or union, or
          when a pointer to or a function returning a structure or union is being declared. (See incomplete types
-         in 6.2.5.) The specification has to be complete before such a function is called or defined.
+         in 6.2.5.) The specification has to be complete before such a function is called or defined.
 

 
-
+
 
5   Two declarations of structure, union, or enumerated types which are in different scopes or
     use different tags declare distinct types. Each declaration of a structure, union, or
     enumerated type which does not include a tag declares a distinct type.
 

-
-
+
 
6   A type specifier of the form
              struct-or-union identifieropt { struct-declaration-list }
     or
@@ -7077,10 +6195,9 @@ Forward references:         conditional inclusion (6.10.1), complex arithmetic
     or
              enum identifieropt { enumerator-list , }
     declares a structure, union, or enumerated type. The list defines the structure content ,
-    union content , or enumeration content . If an identifier is provided,130) the type specifier
+    union content , or enumeration content . If an identifier is provided,[130] the type specifier
     also declares the identifier to be the tag of that type.
 

-
 
 
Footnote 130) If there is no identifier, the type can, within the translation unit, only be referred to by the declaration
          of which it is a part. Of course, when the declaration is of a typedef name, subsequent declarations
@@ -7088,30 +6205,28 @@ Forward references:         conditional inclusion (6.10.1), complex arithmetic
          enumerated type.
 

 
-
+
 
7   A declaration of the form
              struct-or-union identifier ;
-    specifies a structure or union type and declares the identifier as a tag of that type.131)
+    specifies a structure or union type and declares the identifier as a tag of that type.[131]
 

-
 
 
Footnote 131) A similar construction with enum does not exist.
 

 
-
+
 
8   If a type specifier of the form
              struct-or-union identifier
     occurs other than as part of one of the above forms, and no other declaration of the
     identifier as a tag is visible, then it declares an incomplete structure or union type, and
-    declares the identifier as the tag of that type.131)
+    declares the identifier as the tag of that type.[131]
 
 

-
 
 
Footnote 131) A similar construction with enum does not exist.
 

 
-
+
 
9    If a type specifier of the form
               struct-or-union identifier
      or
@@ -7120,8 +6235,7 @@ Forward references:         conditional inclusion (6.10.1), complex arithmetic
      tag is visible, then it specifies the same type as that other declaration, and does not
      redeclare the tag.
 

-
-
+
 
10   EXAMPLE 1       This mechanism allows declaration of a self-referential structure.
               struct tnode {
                     int count;
@@ -7135,8 +6249,7 @@ Forward references:         conditional inclusion (6.10.1), complex arithmetic
      which sp points; the expression s.right->count designates the count member of the right struct
      tnode pointed to from s.
 

-
-
+
 
11   The following alternative formulation uses the typedef mechanism:
               typedef struct tnode TNODE;
               struct tnode {
@@ -7146,8 +6259,7 @@ Forward references:         conditional inclusion (6.10.1), complex arithmetic
               TNODE s, *sp;
 
 

-
-
+
 
12   EXAMPLE 2 To illustrate the use of prior declaration of a tag to specify a pair of mutually referential
      structures, the declarations
               struct s1 { struct s2 *s2p; /* ... */ }; // D1
@@ -7159,104 +6271,89 @@ Forward references:         conditional inclusion (6.10.1), complex arithmetic
      may be inserted ahead of D1. This declares a new tag s2 in the inner scope; the declaration D2 then
      completes the specification of the new type.
 
-     Forward references: declarators (6.7.6), type definitions (6.7.8).
+     Forward references: declarators (6.7.6), type definitions (6.7.8).
 

-
-
+
 

 
6.7.2.4 [Atomic type specifiers]

-

-
-
-
1            atomic-type-specifier:
+
+
1 Syntax
+            atomic-type-specifier:
                     _Atomic ( type-name )
     Constraints
 

-
-
+
 
2   Atomic type specifiers shall not be used if the implementation does not support atomic
-    types (see 6.10.8.3).
+    types (see 6.10.8.3).
 

-
-
+
 
3   The type name in an atomic type specifier shall not refer to an array type, a function type,
     an atomic type, or a qualified type.
     Semantics
 

-
-
+
 
4   The properties associated with atomic types are meaningful only for expressions that are
     lvalues. If the _Atomic keyword is immediately followed by a left parenthesis, it is
     interpreted as a type specifier (with a type name), not as a type qualifier.
 

-
-
+
 

 
6.7.3 [Type qualifiers]

-

-
-
-
1            type-qualifier:
+
+
1 Syntax
+            type-qualifier:
                     const
                     restrict
                     volatile
                     _Atomic
     Constraints
 

-
-
+
 
2   Types other than pointer types whose referenced type is an object type shall not be
     restrict-qualified.
 

-
-
+
 
3   The type modified by the _Atomic qualifier shall not be an array type or a function
     type.
     Semantics
 

-
-
+
 
4   The properties associated with qualified types are meaningful only for expressions that
-    are lvalues.132)
+    are lvalues.[132]
 

-
 
 
Footnote 132) The implementation may place a const object that is not volatile in a read-only region of
          storage. Moreover, the implementation need not allocate storage for such an object if its address is
          never used.
+     list , the resulting type is the so-qualified atomic type.
 

 
-
+
 
5   If the same qualifier appears more than once in the same specifier-qualifier-list , either
     directly or via one or more typedefs, the behavior is the same as if it appeared only
     once. If other qualifiers appear along with the _Atomic qualifier in a specifier-qualifier-
-
-     list , the resulting type is the so-qualified atomic type.
 

-
-
+
 
6    If an attempt is made to modify an object defined with a const-qualified type through use
      of an lvalue with non-const-qualified type, the behavior is undefined. If an attempt is
      made to refer to an object defined with a volatile-qualified type through use of an lvalue
-     with non-volatile-qualified type, the behavior is undefined.133)
+     with non-volatile-qualified type, the behavior is undefined.[133]
 

-
 
 
Footnote 133) This applies to those objects that behave as if they were defined with qualified types, even if they are
           never actually defined as objects in the program (such as an object at a memory-mapped input/output
           address).
 

 
-
+
 
7    An object that has volatile-qualified type may be modified in ways unknown to the
      implementation or have other unknown side effects. Therefore any expression referring
      to such an object shall be evaluated strictly according to the rules of the abstract machine,
-     as described in 5.1.2.3. Furthermore, at every sequence point the value last stored in the
+     as described in 5.1.2.3. Furthermore, at every sequence point the value last stored in the
      object shall agree with that prescribed by the abstract machine, except as modified by the
-     unknown factors mentioned previously.134) What constitutes an access to an object that
+     unknown factors mentioned previously.[134] What constitutes an access to an object that
      has volatile-qualified type is implementation-defined.
 

-
 
 
Footnote 134) A volatile declaration may be used to describe an object corresponding to a memory-mapped
           input/output port or an object accessed by an asynchronously interrupting function. Actions on
@@ -7264,46 +6361,41 @@ Forward references:         conditional inclusion (6.10.1), complex arithmetic
           permitted by the rules for evaluating expressions.
 

 
-
+
 
8    An object that is accessed through a restrict-qualified pointer has a special association
-     with that pointer. This association, defined in 6.7.3.1 below, requires that all accesses to
-     that object use, directly or indirectly, the value of that particular pointer.135) The intended
+     with that pointer. This association, defined in 6.7.3.1 below, requires that all accesses to
+     that object use, directly or indirectly, the value of that particular pointer.[135] The intended
      use of the restrict qualifier (like the register storage class) is to promote
      optimization, and deleting all instances of the qualifier from all preprocessing translation
      units composing a conforming program does not change its meaning (i.e., observable
      behavior).
 

-
 
 
Footnote 135) For example, a statement that assigns a value returned by malloc to a single pointer establishes this
           association between the allocated object and the pointer.
 

 
-
+
 
9    If the specification of an array type includes any type qualifiers, the element type is so-
      qualified, not the array type. If the specification of a function type includes any type
-     qualifiers, the behavior is undefined.136)
+     qualifiers, the behavior is undefined.[136]
 

-
 
 
Footnote 136) Both of these can occur through the use of typedefs.
+     may be modifiable by hardware, but cannot be assigned to, incremented, or decremented.
 

 
-
+
 
10   For two qualified types to be compatible, both shall have the identically qualified version
      of a compatible type; the order of type qualifiers within a list of specifiers or qualifiers
      does not affect the specified type.
 

-
-
+
 
11   EXAMPLE 1       An object declared
               extern const volatile int real_time_clock;
 
-     may be modifiable by hardware, but cannot be assigned to, incremented, or decremented.
-
 

-
-
+
 
12   EXAMPLE 2 The following declarations and expressions illustrate the behavior when type qualifiers
      modify an aggregate type:
               const struct s { int mem; } cs = { 1 };
@@ -7320,68 +6412,57 @@ Forward references:         conditional inclusion (6.10.1), complex arithmetic
               pi = a[0];              //   invalid: a[0] has type ``const int *''
 
 

-
-
+
 
13   EXAMPLE 3        The declaration
               _Atomic volatile int *p;
      specifies that p has the type ``pointer to volatile atomic int'', a pointer to a volatile-qualified atomic type.
 

-
-
+
 

 
6.7.3.1 [Formal definition of restrict]

-

-
-
+
 
1    Let D be a declaration of an ordinary identifier that provides a means of designating an
      object P as a restrict-qualified pointer to type T.
 

-
-
+
 
2    If D appears inside a block and does not have storage class extern, let B denote the
      block. If D appears in the list of parameter declarations of a function definition, let B
      denote the associated block. Otherwise, let B denote the block of main (or the block of
      whatever function is called at program startup in a freestanding environment).
 

-
-
+
 
3    In what follows, a pointer expression E is said to be based on object P if (at some
      sequence point in the execution of B prior to the evaluation of E) modifying P to point to
-     a copy of the array object into which it formerly pointed would change the value of E.137)
+     a copy of the array object into which it formerly pointed would change the value of E.[137]
      Note that ``based'' is defined only for expressions with pointer types.
 

-
 
 
Footnote 137) In other words, E depends on the value of P itself rather than on the value of an object referenced
           indirectly through P. For example, if identifier p has type (int **restrict), then the pointer
           expressions p and p+1 are based on the restricted pointer object designated by p, but the pointer
           expressions *p and p[1] are not.
+     object P2, associated with block B2, then either the execution of B2 shall begin before
+     the execution of B, or the execution of B2 shall end prior to the assignment. If these
+     requirements are not met, then the behavior is undefined.
 

 
-
+
 
4    During each execution of B, let L be any lvalue that has &L based on P. If L is used to
      access the value of the object X that it designates, and X is also modified (by any means),
      then the following requirements apply: T shall not be const-qualified. Every other lvalue
      used to access the value of X shall also have its address based on P. Every access that
      modifies X shall be considered also to modify P, for the purposes of this subclause. If P
      is assigned the value of a pointer expression E that is based on another restricted pointer
-
-     object P2, associated with block B2, then either the execution of B2 shall begin before
-     the execution of B, or the execution of B2 shall end prior to the assignment. If these
-     requirements are not met, then the behavior is undefined.
 

-
-
+
 
5    Here an execution of B means that portion of the execution of the program that would
      correspond to the lifetime of an object with scalar type and automatic storage duration
      associated with B.
 

-
-
+
 
6    A translator is free to ignore any or all aliasing implications of uses of restrict.
 

-
-
+
 
7    EXAMPLE 1       The file scope declarations
               int * restrict a;
               int * restrict b;
@@ -7390,8 +6471,7 @@ Forward references:         conditional inclusion (6.10.1), complex arithmetic
      program, then it is never accessed using either of the other two.
 
 

-
-
+
 
8    EXAMPLE 2       The function parameter declarations in the following example
               void f(int n, int * restrict p, int * restrict q)
               {
@@ -7401,8 +6481,7 @@ Forward references:         conditional inclusion (6.10.1), complex arithmetic
      assert that, during each execution of the function, if an object is accessed through one of the pointer
      parameters, then it is not also accessed through the other.
 

-
-
+
 
9    The benefit of the restrict qualifiers is that they enable a translator to make an effective dependence
      analysis of function f without examining any of the calls of f in the program. The cost is that the
      programmer has to examine all of those calls to ensure that none give undefined behavior. For example, the
@@ -7416,8 +6495,7 @@ Forward references:         conditional inclusion (6.10.1), complex arithmetic
               }
 
 

-
-
+
 
10   EXAMPLE 3       The function parameter declarations
               void h(int n, int * restrict p, int * restrict q, int * restrict r)
               {
@@ -7429,8 +6507,7 @@ Forward references:         conditional inclusion (6.10.1), complex arithmetic
      are disjoint arrays, a call of the form h(100, a, b, b) has defined behavior, because array b is not
      modified within function h.
 

-
-
+
 
11   EXAMPLE 4 The rule limiting assignments between restricted pointers does not distinguish between a
      function call and an equivalent nested block. With one exception, only ``outer-to-inner'' assignments
      between restricted pointers declared in nested blocks have defined behavior.
@@ -7446,8 +6523,7 @@ Forward references:         conditional inclusion (6.10.1), complex arithmetic
                        }
               }
 

-
-
+
 
12   The one exception allows the value of a restricted pointer to be carried out of the block in which it (or, more
      precisely, the ordinary identifier used to designate it) is declared when that block finishes execution. For
      example, this permits new_vector to return a vector.
@@ -7460,46 +6536,38 @@ Forward references:         conditional inclusion (6.10.1), complex arithmetic
                     return t;
               }
 

-
-
+
 

 
6.7.4 [Function specifiers]

-

-
-
-
1             function-specifier:
+
+
1 Syntax
+             function-specifier:
                      inline
                      _Noreturn
      Constraints
 

-
-
+
 
2    Function specifiers shall be used only in the declaration of an identifier for a function.
 

-
-
+
 
3    An inline definition of a function with external linkage shall not contain a definition of a
      modifiable object with static or thread storage duration, and shall not contain a reference
      to an identifier with internal linkage.
 

-
-
+
 
4    In a hosted environment, no function specifier(s) shall appear in a declaration of main.
      Semantics
 

-
-
+
 
5    A function specifier may appear more than once; the behavior is the same as if it
      appeared only once.
 

-
-
+
 
6    A function declared with an inline function specifier is an inline function. Making a
-     function an inline function suggests that calls to the function be as fast as possible.138)
+     function an inline function suggests that calls to the function be as fast as possible.[138]
 
-     The extent to which such suggestions are effective is implementation-defined.139)
+     The extent to which such suggestions are effective is implementation-defined.[139]
 

-
 
 
Footnote 138) By using, for example, an alternative to the usual function call mechanism, such as ``inline
           substitution''. Inline substitution is not textual substitution, nor does it create a new function.
@@ -7515,7 +6583,7 @@ Forward references:         conditional inclusion (6.10.1), complex arithmetic
           substitutions to calls in the scope of an inline declaration.
 

 
-
+
 
7    Any function with internal linkage can be an inline function. For a function with external
      linkage, the following restrictions apply: If a function is declared with an inline
      function specifier, then it shall also be defined in the same translation unit. If all of the
@@ -7525,26 +6593,28 @@ Forward references:         conditional inclusion (6.10.1), complex arithmetic
      and does not forbid an external definition in another translation unit. An inline definition
      provides an alternative to an external definition, which a translator may use to implement
      any call to the function in the same translation unit. It is unspecified whether a call to the
-     function uses the inline definition or the external definition.140)
+     function uses the inline definition or the external definition.[140]
 

-
 
 
Footnote 140) Since an inline definition is distinct from the corresponding external definition and from any other
           corresponding inline definitions in other translation units, all corresponding objects with static storage
           duration are also distinct in each of the definitions.
+              double convert(int is_fahr, double temp)
+              {
+                    /* A translator may perform inline substitutions */
+                    return is_fahr ? cels(temp) : fahr(temp);
+              }
 

 
-
+
 
8    A function declared with a _Noreturn function specifier shall not return to its caller.
      Recommended practice
 

-
-
+
 
9    The implementation should produce a diagnostic message for a function declared with a
      _Noreturn function specifier that appears to be capable of returning to its caller.
 

-
-
+
 
10   EXAMPLE 1 The declaration of an inline function with external linkage can result in either an external
      definition, or a definition available for use only within the translation unit. A file scope declaration with
      extern creates an external definition. The following example shows an entire translation unit.
@@ -7557,23 +6627,15 @@ Forward references:         conditional inclusion (6.10.1), complex arithmetic
                     return (5.0 * (t - 32.0)) / 9.0;
               }
               extern double fahr(double);                   // creates an external definition
-
-              double convert(int is_fahr, double temp)
-              {
-                    /* A translator may perform inline substitutions */
-                    return is_fahr ? cels(temp) : fahr(temp);
-              }
 

-
-
+
 
11   Note that the definition of fahr is an external definition because fahr is also declared with extern, but
      the definition of cels is an inline definition. Because cels has external linkage and is referenced, an
-     external definition has to appear in another translation unit (see 6.9); the inline definition and the external
+     external definition has to appear in another translation unit (see 6.9); the inline definition and the external
      definition are distinct and either may be used for the call.
 
 

-
-
+
 
12   EXAMPLE 2
               _Noreturn void f () {
                     abort(); // ok
@@ -7582,72 +6644,66 @@ Forward references:         conditional inclusion (6.10.1), complex arithmetic
                     if (i > 0) abort();
               }
 
-     Forward references: function definitions (6.9.1).
+     Forward references: function definitions (6.9.1).
 

-
-
+
 

 
6.7.5 [Alignment specifier]

-

-
-
-
1             alignment-specifier:
+
+
1 Syntax
+             alignment-specifier:
                      _Alignas ( type-name )
                     _Alignas ( constant-expression )
      Constraints
 

-
-
+
 
2    An alignment attribute shall not be specified in a declaration of a typedef, or a bit-field, or
      a function, or a parameter, or an object declared with the register storage-class
      specifier.
 

-
-
+
 
3    The constant expression shall be an integer constant expression. It shall evaluate to a
      valid fundamental alignment, or to a valid extended alignment supported by the
      implementation in the context in which it appears, or to zero.
 

-
-
+
 
4    The combined effect of all alignment attributes in a declaration shall not specify an
      alignment that is less strict than the alignment that would otherwise be required for the
      type of the object or member being declared.
      Semantics
 

-
-
+
 
5    The first form is equivalent to _Alignas (_Alignof (type-name)).
 

-
-
+
 
6    The alignment requirement of the declared object or member is taken to be the specified
-     alignment. An alignment specification of zero has no effect.141) When multiple
+     alignment. An alignment specification of zero has no effect.[141] When multiple
      alignment specifiers occur in a declaration, the effective alignment requirement is the
      strictest specified alignment.
 
 

-
 
 
Footnote 141) An alignment specification of zero also does not affect other alignment specifications in the same
          declaration.
+             identifier-list:
+                     identifier
+                     identifier-list , identifier
+    Semantics
 

 
-
+
 
7   If the definition of an object has an alignment specifier, any other declaration of that
     object shall either specify equivalent alignment or have no alignment specifier. If the
     definition of an object does not have an alignment specifier, any other declaration of that
     object shall also have no alignment specifier. If declarations of an object in different
     translation units have different alignment specifiers, the behavior is undefined.
 

-
-
+
 

 
6.7.6 [Declarators]

-

-
-
-
1            declarator:
+
+
1 Syntax
+            declarator:
                     pointeropt direct-declarator
              direct-declarator:
                      identifier
@@ -7673,42 +6729,32 @@ Forward references:         conditional inclusion (6.10.1), complex arithmetic
              parameter-declaration:
                    declaration-specifiers declarator
                    declaration-specifiers abstract-declaratoropt
-
-             identifier-list:
-                     identifier
-                     identifier-list , identifier
-    Semantics
 

-
-
+
 
2   Each declarator declares one identifier, and asserts that when an operand of the same
     form as the declarator appears in an expression, it designates a function or object with the
     scope, storage duration, and type indicated by the declaration specifiers.
 

-
-
+
 
3   A full declarator is a declarator that is not part of another declarator. The end of a full
     declarator is a sequence point. If, in the nested sequence of declarators in a full
     declarator, there is a declarator specifying a variable length array type, the type specified
     by the full declarator is said to be variably modified . Furthermore, any type derived by
     declarator type derivation from a variably modified type is itself variably modified.
 

-
-
+
 
4   In the following subclauses, consider a declaration
              T D1
     where T contains the declaration specifiers that specify a type T (such as int) and D1 is
     a declarator that contains an identifier ident . The type specified for the identifier ident in
     the various forms of declarator is described inductively using this notation.
 

-
-
+
 
5   If, in the declaration ``T D1'', D1 has the form
              identifier
     then the type specified for ident is T .
 

-
-
+
 
6   If, in the declaration ``T D1'', D1 has the form
              ( D )
     then ident has the type specified by the declaration ``T D''. Thus, a declarator in
@@ -7716,33 +6762,28 @@ Forward references:         conditional inclusion (6.10.1), complex arithmetic
     declarators may be altered by parentheses.
     Implementation limits
 

-
-
-
7   As discussed in 5.2.4.1, an implementation may limit the number of pointer, array, and
+
+
7   As discussed in 5.2.4.1, an implementation may limit the number of pointer, array, and
     function declarators that modify an arithmetic, structure, union, or void type, either
     directly or via one or more typedefs.
-    Forward references: array declarators (6.7.6.2), type definitions (6.7.8).
+    Forward references: array declarators (6.7.6.2), type definitions (6.7.8).
 

-
-
+
 

 
6.7.6.1 [Pointer declarators]

-

-
-
-
1   If, in the declaration ``T D1'', D1 has the form
+
+
1 Semantics
+   If, in the declaration ``T D1'', D1 has the form
             * type-qualifier-listopt D
     and the type specified for ident in the declaration ``T D'' is `` derived-declarator-type-list
     T '', then the type specified for ident is `` derived-declarator-type-list type-qualifier-list
     pointer to T ''. For each type qualifier in the list, ident is a so-qualified pointer.
 

-
-
+
 
2   For two pointer types to be compatible, both shall be identically qualified and both shall
     be pointers to compatible types.
 

-
-
+
 
3   EXAMPLE The following pair of declarations demonstrates the difference between a ``variable pointer
     to a constant value'' and a ``constant pointer to a variable value''.
             const int *ptr_to_constant;
@@ -7752,8 +6793,7 @@ Forward references:         conditional inclusion (6.10.1), complex arithmetic
     int pointed to by constant_ptr may be modified, but constant_ptr itself shall always point to the
     same location.
 

-
-
+
 
4   The declaration of the constant pointer constant_ptr may be clarified by including a definition for the
     type ``pointer to int''.
             typedef int *int_ptr;
@@ -7761,14 +6801,12 @@ Forward references:         conditional inclusion (6.10.1), complex arithmetic
     declares constant_ptr as an object that has type ``const-qualified pointer to int''.
 
 

-
-
+
 

 
6.7.6.2 [Array declarators]

-

-
-
-
1   In addition to optional type qualifiers and the keyword static, the [ and ] may delimit
+
+
1 Constraints
+   In addition to optional type qualifiers and the keyword static, the [ and ] may delimit
     an expression or *. If they delimit an expression (which specifies the size of an array), the
     expression shall have an integer type. If the expression is a constant expression, it shall
     have a value greater than zero. The element type shall not be an incomplete or function
@@ -7776,45 +6814,45 @@ Forward references:         conditional inclusion (6.10.1), complex arithmetic
     declaration of a function parameter with an array type, and then only in the outermost
     array type derivation.
 

-
-
+
 
2   If an identifier is declared as having a variably modified type, it shall be an ordinary
-    identifier (as defined in 6.2.3), have no linkage, and have either block scope or function
+    identifier (as defined in 6.2.3), have no linkage, and have either block scope or function
     prototype scope. If an identifier is declared to be an object with static or thread storage
     duration, it shall not have a variable length array type.
     Semantics
 

-
-
+
 
3   If, in the declaration ``T D1'', D1 has one of the forms:
              D[ type-qualifier-listopt assignment-expressionopt ]
              D[ static type-qualifier-listopt assignment-expression ]
              D[ type-qualifier-list static assignment-expression ]
              D[ type-qualifier-listopt * ]
     and the type specified for ident in the declaration ``T D'' is `` derived-declarator-type-list
-    T '', then the type specified for ident is `` derived-declarator-type-list array of T ''.142)
-    (See 6.7.6.3 for the meaning of the optional type qualifiers and the keyword static.)
+    T '', then the type specified for ident is `` derived-declarator-type-list array of T ''.[142]
+    (See 6.7.6.3 for the meaning of the optional type qualifiers and the keyword static.)
 

-
 
 
Footnote 142) When several ``array of'' specifications are adjacent, a multidimensional array is declared.
 

 
-
+
 
4   If the size is not present, the array type is an incomplete type. If the size is * instead of
     being an expression, the array type is a variable length array type of unspecified size,
-    which can only be used in declarations or type names with function prototype scope;143)
+    which can only be used in declarations or type names with function prototype scope;[143]
     such arrays are nonetheless complete types. If the size is an integer constant expression
     and the element type has a known constant size, the array type is not a variable length
     array type; otherwise, the array type is a variable length array type. (Variable length
-    arrays are a conditional feature that implementations need not support; see 6.10.8.3.)
+    arrays are a conditional feature that implementations need not support; see 6.10.8.3.)
 

-
 
-
Footnote 143) Thus, * can be used only in function declarations that are not definitions (see 6.7.6.3).
+
Footnote 143) Thus, * can be used only in function declarations that are not definitions (see 6.7.6.3).
+              extern int *x;
+              extern int y[];
+     The first declares x to be a pointer to int; the second declares y to be an array of int of unspecified size
+     (an incomplete type), the storage for which is defined elsewhere.
 

 
-
+
 
5   If the size is an expression that is not an integer constant expression: if it occurs in a
     declaration at function prototype scope, it is treated as if it were replaced by *; otherwise,
     each time it is evaluated it shall have a value greater than zero. The size of each instance
@@ -7823,33 +6861,24 @@ Forward references:         conditional inclusion (6.10.1), complex arithmetic
     size expression would not affect the result of the operator, it is unspecified whether or not
     the size expression is evaluated.
 

-
-
+
 
6   For two array types to be compatible, both shall have compatible element types, and if
     both size specifiers are present, and are integer constant expressions, then both size
     specifiers shall have the same constant value. If the two array types are used in a context
     which requires them to be compatible, it is undefined behavior if the two size specifiers
     evaluate to unequal values.
 

-
-
+
 
7   EXAMPLE 1
              float fa[11], *afp[17];
     declares an array of float numbers and an array of pointers to float numbers.
 
 

-
-
+
 
8   EXAMPLE 2       Note the distinction between the declarations
 
-              extern int *x;
-              extern int y[];
-     The first declares x to be a pointer to int; the second declares y to be an array of int of unspecified size
-     (an incomplete type), the storage for which is defined elsewhere.
-
 

-
-
+
 
9    EXAMPLE 3       The following declarations demonstrate the compatibility rules for variably modified types.
               extern int n;
               extern int m;
@@ -7865,8 +6894,7 @@ Forward references:         conditional inclusion (6.10.1), complex arithmetic
               }
 
 

-
-
+
 
10   EXAMPLE 4 All declarations of variably modified (VM) types have to be at either block scope or
      function prototype scope. Array objects declared with the _Thread_local, static, or extern
      storage-class specifier cannot have a variable length array (VLA) type. However, an object declared with
@@ -7893,36 +6921,30 @@ Forward references:         conditional inclusion (6.10.1), complex arithmetic
                        static int (*q)[m] = &B;                     //   valid: q is a static block pointer to VLA
               }
 
-     Forward references:           function declarators (6.7.6.3), function definitions (6.9.1),
-     initialization (6.7.9).
+     Forward references:           function declarators (6.7.6.3), function definitions (6.9.1),
+     initialization (6.7.9).
 

-
-
+
 

 
6.7.6.3 [Function declarators (including prototypes)]

-

-
-
-
1    A function declarator shall not specify a return type that is a function type or an array
+
+
1 Constraints
+    A function declarator shall not specify a return type that is a function type or an array
      type.
 

-
-
+
 
2    The only storage-class specifier that shall occur in a parameter declaration is register.
 

-
-
+
 
3    An identifier list in a function declarator that is not part of a definition of that function
      shall be empty.
 

-
-
+
 
4    After adjustment, the parameters in a parameter type list in a function declarator that is
      part of a definition of that function shall not have incomplete type.
      Semantics
 

-
-
+
 
5    If, in the declaration ``T D1'', D1 has the form
              D( parameter-type-list )
      or
@@ -7931,13 +6953,11 @@ Forward references:         conditional inclusion (6.10.1), complex arithmetic
      T '', then the type specified for ident is `` derived-declarator-type-list function returning
      T ''.
 

-
-
+
 
6    A parameter type list specifies the types of, and may declare identifiers for, the
      parameters of the function.
 

-
-
+
 
7    A declaration of a parameter as ``array of type'' shall be adjusted to ``qualified pointer to
      type'', where the type qualifiers (if any) are those specified within the [ and ] of the
      array type derivation. If the keyword static also appears within the [ and ] of the
@@ -7945,59 +6965,51 @@ Forward references:         conditional inclusion (6.10.1), complex arithmetic
      actual argument shall provide access to the first element of an array with at least as many
      elements as specified by the size expression.
 

-
-
+
 
8    A declaration of a parameter as ``function returning type'' shall be adjusted to ``pointer to
-     function returning type'', as in 6.3.2.1.
+     function returning type'', as in 6.3.2.1.
 

-
-
+
 
9    If the list terminates with an ellipsis (, ...), no information about the number or types
-     of the parameters after the comma is supplied.144)
+     of the parameters after the comma is supplied.[144]
 

-
 
-
Footnote 144) The macros defined in the <stdarg.h> header (7.16) may be used to access arguments that
+
Footnote 144) The macros defined in the <stdarg.h> header (7.16) may be used to access arguments that
           correspond to the ellipsis.
 

 
-
+
 
10   The special case of an unnamed parameter of type void as the only item in the list
      specifies that the function has no parameters.
 
 

-
-
+
 
11   If, in a parameter declaration, an identifier can be treated either as a typedef name or as a
      parameter name, it shall be taken as a typedef name.
 

-
-
+
 
12   If the function declarator is not part of a definition of that function, parameters may have
      incomplete type and may use the [*] notation in their sequences of declarator specifiers
      to specify variable length array types.
 

-
-
+
 
13   The storage-class specifier in the declaration specifiers for a parameter declaration, if
      present, is ignored unless the declared parameter is one of the members of the parameter
      type list for a function definition.
 

-
-
+
 
14   An identifier list declares only the identifiers of the parameters of the function. An empty
      list in a function declarator that is part of a definition of that function specifies that the
      function has no parameters. The empty list in a function declarator that is not part of a
      definition of that function specifies that no information about the number or types of the
-     parameters is supplied.145)
+     parameters is supplied.[145]
 

-
 
-
Footnote 145) See ``future language directions'' (6.11.6).
+
Footnote 145) See ``future language directions'' (6.11.6).
 

 
-
-
15   For two function types to be compatible, both shall specify compatible return types.146)
+
+
15   For two function types to be compatible, both shall specify compatible return types.[146]
      Moreover, the parameter type lists, if both are present, shall agree in the number of
      parameters and in use of the ellipsis terminator; corresponding parameters shall have
      compatible types. If one type has a parameter type list and the other type is specified by a
@@ -8013,12 +7025,12 @@ Forward references:         conditional inclusion (6.10.1), complex arithmetic
      type is taken as having the adjusted type and each parameter declared with qualified type
      is taken as having the unqualified version of its declared type.)
 

-
 
 
Footnote 146) If both function types are ``old style'', parameter types are not compared.
+     designator, which is then used to call the function; it returns an int.
 

 
-
+
 
16   EXAMPLE 1       The declaration
               int f(void), *fip(), (*pfi)();
      declares a function f with no parameters returning an int, a function fip with no parameter specification
@@ -8027,19 +7039,15 @@ Forward references:         conditional inclusion (6.10.1), complex arithmetic
      declaration suggests, and the same construction in an expression requires, the calling of a function fip,
      and then using indirection through the pointer result to yield an int. In the declarator (*pfi)(), the
      extra parentheses are necessary to indicate that indirection through a pointer to a function yields a function
-
-     designator, which is then used to call the function; it returns an int.
 

-
-
+
 
17   If the declaration occurs outside of any function, the identifiers have file scope and external linkage. If the
      declaration occurs inside a function, the identifiers of the functions f and fip have block scope and either
      internal or external linkage (depending on what file scope declarations for these identifiers are visible), and
      the identifier of the pointer pfi has block scope and no linkage.
 
 

-
-
+
 
18   EXAMPLE 2        The declaration
                int (*apfi[3])(int *x, int *y);
      declares an array apfi of three pointers to functions returning int. Each of these functions has two
@@ -8047,8 +7055,7 @@ Forward references:         conditional inclusion (6.10.1), complex arithmetic
      go out of scope at the end of the declaration of apfi.
 
 

-
-
+
 
19   EXAMPLE 3        The declaration
                int (*fpfi(int (*)(long), int))(int, ...);
      declares a function fpfi that returns a pointer to a function returning an int. The function fpfi has two
@@ -8057,8 +7064,7 @@ Forward references:         conditional inclusion (6.10.1), complex arithmetic
      additional arguments of any type.
 
 

-
-
+
 
20   EXAMPLE 4        The following prototype has a variably modified parameter.
                void addscalar(int n, int m,
                      double a[n][n*m+300], double x);
@@ -8078,8 +7084,7 @@ Forward references:         conditional inclusion (6.10.1), complex arithmetic
                }
 
 

-
-
+
 
21   EXAMPLE 5        The following are all compatible function prototype declarators.
                double    maximum(int       n,   int   m,   double     a[n][m]);
                double    maximum(int       n,   int   m,   double     a[*][*]);
@@ -8093,16 +7098,14 @@ Forward references:         conditional inclusion (6.10.1), complex arithmetic
     (Note that the last declaration also specifies that the argument corresponding to a in any call to f must be a
     non-null pointer to the first of at least three arrays of 5 doubles, which the others do not.)
 
-    Forward references: function definitions (6.9.1), type names (6.7.7).
+    Forward references: function definitions (6.9.1), type names (6.7.7).
 

-
-
+
 

 
6.7.7 [Type names]

-

-
-
-
1            type-name:
+
+
1 Syntax
+            type-name:
                     specifier-qualifier-list abstract-declaratoropt
              abstract-declarator:
                     pointer
@@ -8119,19 +7122,20 @@ Forward references:         conditional inclusion (6.10.1), complex arithmetic
                      direct-abstract-declaratoropt ( parameter-type-listopt )
     Semantics
 

-
-
+
 
2   In several contexts, it is necessary to specify a type. This is accomplished using a type
     name, which is syntactically a declaration for a function or an object of that type that
-    omits the identifier.147)
+    omits the identifier.[147]
 

-
 
 
Footnote 147) As indicated by the syntax, empty parentheses in a type name are interpreted as ``function with no
          parameter specification'', rather than redundant parentheses around the omitted identifier.
+    returning an int, and (h) array of an unspecified number of constant pointers to functions, each with one
+    parameter that has type unsigned int and an unspecified number of other parameters, returning an
+    int.
 

 
-
+
 
3   EXAMPLE        The constructions
              (a)      int
              (b)      int   *
@@ -8145,32 +7149,24 @@ Forward references:         conditional inclusion (6.10.1), complex arithmetic
     array of three ints, (e) pointer to a variable length array of an unspecified number of ints, (f) function
     with no parameter specification returning a pointer to int, (g) pointer to function with no parameters
 
-    returning an int, and (h) array of an unspecified number of constant pointers to functions, each with one
-    parameter that has type unsigned int and an unspecified number of other parameters, returning an
-    int.
-
 

-
-
+
 

 
6.7.8 [Type definitions]

-

-
-
-
1            typedef-name:
+
+
1 Syntax
+            typedef-name:
                     identifier
     Constraints
 

-
-
+
 
2   If a typedef name specifies a variably modified type then it shall have block scope.
     Semantics
 

-
-
+
 
3   In a declaration whose storage-class specifier is typedef, each declarator defines an
     identifier to be a typedef name that denotes the type specified for the identifier in the way
-    described in 6.7.6. Any array size expressions associated with variable length array
+    described in 6.7.6. Any array size expressions associated with variable length array
     declarators are evaluated each time the declaration of the typedef name is reached in the
     order of execution. A typedef declaration does not introduce a new type, only a
     synonym for the type so specified. That is, in the following declarations:
@@ -8182,8 +7178,7 @@ Forward references:         conditional inclusion (6.10.1), complex arithmetic
     typedef name shares the same name space as other identifiers declared in ordinary
     declarators.
 

-
-
+
 
4   EXAMPLE 1       After
              typedef int MILES, KLICKSP();
              typedef struct { double hi, lo; } range;
@@ -8197,8 +7192,7 @@ Forward references:         conditional inclusion (6.10.1), complex arithmetic
     such a structure. The object distance has a type compatible with any other int object.
 
 

-
-
+
 
5   EXAMPLE 2       After the declarations
              typedef struct s1 { int x; } t1, *tp1;
              typedef struct s2 { int x; } t2, *tp2;
@@ -8207,8 +7201,7 @@ Forward references:         conditional inclusion (6.10.1), complex arithmetic
     s1, but not compatible with the types struct s2, t2, the type pointed to by tp2, or int.
 
 

-
-
+
 
6   EXAMPLE 3       The following obscure constructions
              typedef signed int t;
              typedef int plain;
@@ -8232,8 +7225,7 @@ Forward references:         conditional inclusion (6.10.1), complex arithmetic
     int'', and an identifier t with type long int.
 
 

-
-
+
 
7   EXAMPLE 4 On the other hand, typedef names can be used to improve code readability. All three of the
     following declarations of the signal function specify exactly the same type, the first without making use
     of any typedef names.
@@ -8243,8 +7235,7 @@ Forward references:         conditional inclusion (6.10.1), complex arithmetic
              pfv signal(int, pfv);
 
 

-
-
+
 
8   EXAMPLE 5 If a typedef name denotes a variable length array type, the length of the array is fixed at the
     time the typedef name is defined, not each time it is used:
              void copyt(int n)
@@ -8257,14 +7248,12 @@ Forward references:         conditional inclusion (6.10.1), complex arithmetic
                          a[i-1] = b[i];
              }
 

-
-
+
 

 
6.7.9 [Initialization]

-

-
-
-
1            initializer:
+
+
1 Syntax
+            initializer:
                       assignment-expression
                       { initializer-list }
                       { initializer-list , }
@@ -8281,54 +7270,45 @@ Forward references:         conditional inclusion (6.10.1), complex arithmetic
                     . identifier
     Constraints
 

-
-
+
 
2   No initializer shall attempt to provide a value for an object not contained within the entity
     being initialized.
 

-
-
+
 
3   The type of the entity to be initialized shall be an array of unknown size or a complete
     object type that is not a variable length array type.
 

-
-
+
 
4   All the expressions in an initializer for an object that has static or thread storage duration
     shall be constant expressions or string literals.
 

-
-
+
 
5   If the declaration of an identifier has block scope, and the identifier has external or
     internal linkage, the declaration shall have no initializer for the identifier.
 

-
-
+
 
6   If a designator has the form
              [ constant-expression ]
     then the current object (defined below) shall have array type and the expression shall be
     an integer constant expression. If the array is of unknown size, any nonnegative value is
     valid.
 

-
-
+
 
7   If a designator has the form
              . identifier
     then the current object (defined below) shall have structure or union type and the
     identifier shall be the name of a member of that type.
      Semantics
 

-
-
+
 
8    An initializer specifies the initial value stored in an object.
 

-
-
+
 
9    Except where explicitly stated otherwise, for the purposes of this subclause unnamed
      members of objects of structure and union type do not participate in initialization.
      Unnamed members of structure objects have indeterminate value even after initialization.
 

-
-
+
 
10   If an object that has automatic storage duration is not initialized explicitly, its value is
      indeterminate. If an object that has static or thread storage duration is not initialized
      explicitly, then:
@@ -8339,34 +7319,29 @@ Forward references:         conditional inclusion (6.10.1), complex arithmetic
      -- if it is a union, the first named member is initialized (recursively) according to these
         rules, and any padding is initialized to zero bits;
 

-
-
+
 
11   The initializer for a scalar shall be a single expression, optionally enclosed in braces. The
      initial value of the object is that of the expression (after conversion); the same type
      constraints and conversions as for simple assignment apply, taking the type of the scalar
      to be the unqualified version of its declared type.
 

-
-
+
 
12   The rest of this subclause deals with initializers for objects that have aggregate or union
      type.
 

-
-
+
 
13   The initializer for a structure or union object that has automatic storage duration shall be
      either an initializer list as described below, or a single expression that has compatible
      structure or union type. In the latter case, the initial value of the object, including
      unnamed members, is that of the expression.
 

-
-
+
 
14   An array of character type may be initialized by a character string literal or UTF-8 string
      literal, optionally enclosed in braces. Successive bytes of the string literal (including the
      terminating null character if there is room or if the array is of unknown size) initialize the
      elements of the array.
 

-
-
+
 
15   An array with element type compatible with a qualified or unqualified version of
      wchar_t, char16_t, or char32_t may be initialized by a wide string literal with
      the corresponding encoding prefix (L, u, or U, respectively), optionally enclosed in
@@ -8374,23 +7349,20 @@ Forward references:         conditional inclusion (6.10.1), complex arithmetic
      null wide character if there is room or if the array is of unknown size) initialize the
      elements of the array.
 

-
-
+
 
16   Otherwise, the initializer for an object that has aggregate or union type shall be a brace-
      enclosed list of initializers for the elements or named members.
 
 

-
-
+
 
17   Each brace-enclosed initializer list has an associated current object . When no
      designations are present, subobjects of the current object are initialized in order according
      to the type of the current object: array elements in increasing subscript order, structure
-     members in declaration order, and the first named member of a union.148) In contrast, a
+     members in declaration order, and the first named member of a union.[148] In contrast, a
      designation causes the following initializer to begin initialization of the subobject
      described by the designator. Initialization then continues forward in order, beginning
-     with the next subobject after that described by the designator.149)
+     with the next subobject after that described by the designator.[149]
 

-
 
 
Footnote 148) If the initializer list for a subaggregate or contained union does not begin with a left brace, its
           subobjects are initialized as usual, but the subaggregate or contained union does not become the
@@ -8402,32 +7374,30 @@ Forward references:         conditional inclusion (6.10.1), complex arithmetic
           the next subobject of an object containing the union.
 

 
-
+
 
18   Each designator list begins its description with the current object associated with the
      closest surrounding brace pair. Each item in the designator list (in order) specifies a
      particular member of its current object and changes the current object for the next
-     designator (if any) to be that member.150) The current object that results at the end of the
+     designator (if any) to be that member.[150] The current object that results at the end of the
      designator list is the subobject to be initialized by the following initializer.
 

-
 
 
Footnote 150) Thus, a designator can only specify a strict subobject of the aggregate or union that is associated with
           the surrounding brace pair. Note, too, that each separate designator list is independent.
 

 
-
+
 
19   The initialization shall occur in initializer list order, each initializer provided for a
-     particular subobject overriding any previously listed initializer for the same subobject;151)
+     particular subobject overriding any previously listed initializer for the same subobject;[151]
      all subobjects that are not initialized explicitly shall be initialized implicitly the same as
      objects that have static storage duration.
 

-
 
 
Footnote 151) Any initializer for the subobject which is overridden and so not used to initialize that subobject might
           not be evaluated at all.
 

 
-
+
 
20   If the aggregate or union contains elements or members that are aggregates or unions,
      these rules apply recursively to the subaggregates or contained unions. If the initializer of
      a subaggregate or contained union begins with a left brace, the initializers enclosed by
@@ -8437,48 +7407,43 @@ Forward references:         conditional inclusion (6.10.1), complex arithmetic
      the contained union; any remaining initializers are left to initialize the next element or
      member of the aggregate of which the current subaggregate or contained union is a part.
 

-
-
+
 
21   If there are fewer initializers in a brace-enclosed list than there are elements or members
      of an aggregate, or fewer characters in a string literal used to initialize an array of known
      size than there are elements in the array, the remainder of the aggregate shall be
      initialized implicitly the same as objects that have static storage duration.
 
 

-
-
+
 
22   If an array of unknown size is initialized, its size is determined by the largest indexed
      element with an explicit initializer. The array type is completed at the end of its
      initializer list.
 

-
-
+
 
23   The evaluations of the initialization list expressions are indeterminately sequenced with
      respect to one another and thus the order in which any side effects occur is
-     unspecified.152)
+     unspecified.[152]
 

-
 
 
Footnote 152) In particular, the evaluation order need not be the same as the order of subobject initialization.
+     structures: w[0].a[0] is 1 and w[1].a[0] is 2; all the other elements are zero.
 

 
-
+
 
24   EXAMPLE 1        Provided that <complex.h> has been #included, the declarations
-              int i = 3.5;
+              int i = 3.5;
               double complex c = 5 + 3 * I;
      define and initialize i with the value 3 and c with the value 5. 0 + i 3. 0.
 
 

-
-
+
 
25   EXAMPLE 2        The declaration
               int x[] = { 1, 3, 5 };
      defines and initializes x as a one-dimensional array object that has three elements, as no size was specified
      and there are three initializers.
 
 

-
-
+
 
26   EXAMPLE 3        The declaration
               int y[4][3] =          {
                     { 1, 3,          5 },
@@ -8496,8 +7461,7 @@ Forward references:         conditional inclusion (6.10.1), complex arithmetic
      next three are taken successively for y[1] and y[2].
 
 

-
-
+
 
27   EXAMPLE 4        The declaration
               int z[4][3] = {
                     { 1 }, { 2 }, { 3 }, { 4 }
@@ -8505,17 +7469,13 @@ Forward references:         conditional inclusion (6.10.1), complex arithmetic
      initializes the first column of z as specified and initializes the rest with zeros.
 
 

-
-
+
 
28   EXAMPLE 5        The declaration
               struct { int a[3], b; } w[] = { { 1 }, 2 };
      is a definition with an inconsistently bracketed initialization. It defines an array with two element
 
-     structures: w[0].a[0] is 1 and w[1].a[0] is 2; all the other elements are zero.
-
 

-
-
+
 
29   EXAMPLE 6         The declaration
                short q[4][3][2] = {
                      { 1 },
@@ -8550,14 +7510,12 @@ Forward references:         conditional inclusion (6.10.1), complex arithmetic
                };
      in a fully bracketed form.
 

-
-
+
 
30   Note that the fully bracketed and minimally bracketed forms of initialization are, in general, less likely to
      cause confusion.
 
 

-
-
+
 
31   EXAMPLE 7         One form of initialization that completes array types involves typedef names. Given the
      declaration
                typedef int A[];            // OK - declared with block scope
@@ -8568,8 +7526,7 @@ Forward references:         conditional inclusion (6.10.1), complex arithmetic
      due to the rules for incomplete types.
 
 

-
-
+
 
32   EXAMPLE 8       The declaration
               char s[] = "abc", t[3] = "abc";
      defines ``plain'' char array objects s and t whose elements are initialized with character string literals.
@@ -8583,8 +7540,7 @@ Forward references:         conditional inclusion (6.10.1), complex arithmetic
      modify the contents of the array, the behavior is undefined.
 
 

-
-
+
 
33   EXAMPLE 9       Arrays can be initialized to correspond to the elements of an enumeration by using
      designators:
               enum { member_one,           member_two };
@@ -8594,73 +7550,62 @@ Forward references:         conditional inclusion (6.10.1), complex arithmetic
               };
 
 

-
-
+
 
34   EXAMPLE 10       Structure members can be initialized to nonzero values without depending on their order:
               div_t answer = { .quot = 2, .rem = -1 };
 
 

-
-
+
 
35   EXAMPLE 11 Designators can be used to provide explicit initialization when unadorned initializer lists
      might be misunderstood:
               struct { int a[3], b; } w[] =
                     { [0].a = {1}, [1].a[0] = 2 };
 
 

-
-
+
 
36   EXAMPLE 12       Space can be ``allocated'' from both ends of an array by using a single designator:
               int a[MAX] = {
                     1, 3, 5, 7, 9, [MAX-5] = 8, 6, 4, 2, 0
               };
 

-
-
+
 
37   In the above, if MAX is greater than ten, there will be some zero-valued elements in the middle; if it is less
      than ten, some of the values provided by the first five initializers will be overridden by the second five.
 
 

-
-
+
 
38   EXAMPLE 13       Any member of a union can be initialized:
               union { /* ... */ } u = { .any_member = 42 };
 
-     Forward references: common definitions <stddef.h> (7.19).
+     Forward references: common definitions <stddef.h> (7.19).
 

-
-
+
 

 
6.7.10 [Static assertions]

-

-
-
-
1            static_assert-declaration:
+
+
1 Syntax
+            static_assert-declaration:
                      _Static_assert ( constant-expression , string-literal ) ;
     Constraints
 

-
-
+
 
2   The constant expression shall compare unequal to 0.
     Semantics
 

-
-
+
 
3   The constant expression shall be an integer constant expression. If the value of the
     constant expression compares unequal to 0, the declaration has no effect. Otherwise, the
     constraint is violated and the implementation shall produce a diagnostic message that
     includes the text of the string literal, except that characters not in the basic source
     character set are not required to appear in the message.
-    Forward references: diagnostics (7.2).
+    Forward references: diagnostics (7.2).
 

-
-
+
 

 
6.8 [Statements and blocks]

-

-
-
-
1            statement:
+
+
1 Syntax
+            statement:
                     labeled-statement
                     compound-statement
                     expression-statement
@@ -8669,13 +7614,11 @@ Forward references:         conditional inclusion (6.10.1), complex arithmetic
                     jump-statement
     Semantics
 

-
-
+
 
2   A statement specifies an action to be performed. Except as indicated, statements are
     executed in sequence.
 

-
-
+
 
3   A block allows a set of declarations and statements to be grouped into one syntactic unit.
     The initializers of objects that have automatic storage duration, and the variable length
     array declarators of ordinary identifiers with block scope, are evaluated and the values are
@@ -8683,8 +7626,7 @@ Forward references:         conditional inclusion (6.10.1), complex arithmetic
     initializer) each time the declaration is reached in the order of execution, as if it were a
     statement, and within each declaration in the order that declarators appear.
 

-
-
+
 
4   A full expression is an expression that is not part of another expression or of a declarator.
     Each of the following is a full expression: an initializer that is not part of a compound
     literal; the expression in an expression statement; the controlling expression of a selection
@@ -8692,48 +7634,41 @@ Forward references:         conditional inclusion (6.10.1), complex arithmetic
     of the (optional) expressions of a for statement; the (optional) expression in a return
     statement. There is a sequence point between the evaluation of a full expression and the
     evaluation of the next full expression to be evaluated.
-    Forward references: expression and null statements (6.8.3), selection statements
-    (6.8.4), iteration statements (6.8.5), the return statement (6.8.6.4).
+    Forward references: expression and null statements (6.8.3), selection statements
+    (6.8.4), iteration statements (6.8.5), the return statement (6.8.6.4).
 

-
-
+
 

 
6.8.1 [Labeled statements]

-

-
-
-
1            labeled-statement:
+
+
1 Syntax
+            labeled-statement:
                     identifier : statement
                     case constant-expression : statement
                     default : statement
     Constraints
 

-
-
+
 
2   A case or default label shall appear only in a switch statement. Further
     constraints on such labels are discussed under the switch statement.
 
 

-
-
+
 
3   Label names shall be unique within a function.
     Semantics
 

-
-
+
 
4   Any statement may be preceded by a prefix that declares an identifier as a label name.
     Labels in themselves do not alter the flow of control, which continues unimpeded across
     them.
-    Forward references: the goto statement (6.8.6.1), the switch statement (6.8.4.2).
+    Forward references: the goto statement (6.8.6.1), the switch statement (6.8.4.2).
 

-
-
+
 

 
6.8.2 [Compound statement]

-

-
-
-
1            compound-statement:
+
+
1 Syntax
+            compound-statement:
                    { block-item-listopt }
              block-item-list:
                      block-item
@@ -8743,36 +7678,30 @@ Forward references:         conditional inclusion (6.10.1), complex arithmetic
                      statement
     Semantics
 

-
-
+
 
2   A compound statement is a block.
 

-
-
+
 

 
6.8.3 [Expression and null statements]

-

-
-
-
1            expression-statement:
+
+
1 Syntax
+            expression-statement:
                     expressionopt ;
     Semantics
 

-
-
+
 
2   The expression in an expression statement is evaluated as a void expression for its side
-    effects.153)
+    effects.[153]
 

-
 
 
Footnote 153) Such as assignments, and function calls which have side effects.
 

 
-
+
 
3   A null statement (consisting of just a semicolon) performs no operations.
 

-
-
+
 
4   EXAMPLE 1 If a function call is evaluated as an expression statement for its side effects only, the
     discarding of its value may be made explicit by converting the expression to a void expression by means of
     a cast:
@@ -8781,8 +7710,7 @@ Forward references:         conditional inclusion (6.10.1), complex arithmetic
              (void)p(0);
 
 

-
-
+
 
5   EXAMPLE 2       In the program fragment
              char *s;
              /* ... */
@@ -8791,8 +7719,7 @@ Forward references:         conditional inclusion (6.10.1), complex arithmetic
     a null statement is used to supply an empty loop body to the iteration statement.
 
 

-
-
+
 
6   EXAMPLE 3       A null statement may also be used to carry a label just before the closing } of a compound
     statement.
              while (loop1) {
@@ -8807,76 +7734,64 @@ Forward references:         conditional inclusion (6.10.1), complex arithmetic
              end_loop1: ;
              }
 
-    Forward references: iteration statements (6.8.5).
+    Forward references: iteration statements (6.8.5).
 

-
-
+
 

 
6.8.4 [Selection statements]

-

-
-
-
1            selection-statement:
+
+
1 Syntax
+            selection-statement:
                      if ( expression ) statement
                      if ( expression ) statement else statement
                      switch ( expression ) statement
     Semantics
 

-
-
+
 
2   A selection statement selects among a set of statements depending on the value of a
     controlling expression.
 

-
-
+
 
3   A selection statement is a block whose scope is a strict subset of the scope of its
     enclosing block. Each associated substatement is also a block whose scope is a strict
     subset of the scope of the selection statement.
 

-
-
+
 

 
6.8.4.1 [The if statement]

-

-
-
-
1   The controlling expression of an if statement shall have scalar type.
+
+
1 Constraints
+   The controlling expression of an if statement shall have scalar type.
     Semantics
 

-
-
+
 
2   In both forms, the first substatement is executed if the expression compares unequal to 0.
     In the else form, the second substatement is executed if the expression compares equal
     to 0. If the first substatement is reached via a label, the second substatement is not
     executed.
 

-
-
+
 
3   An else is associated with the lexically nearest preceding if that is allowed by the
     syntax.
 

-
-
+
 

 
6.8.4.2 [The switch statement]

-

-
-
-
1   The controlling expression of a switch statement shall have integer type.
+
+
1 Constraints
+   The controlling expression of a switch statement shall have integer type.
 

-
-
+
 
2   If a switch statement has an associated case or default label within the scope of an
     identifier with a variably modified type, the entire switch statement shall be within the
-    scope of that identifier.154)
+    scope of that identifier.[154]
 

-
 
 
Footnote 154) That is, the declaration either precedes the switch statement, or it follows the last case or
          default label associated with the switch that is in the block containing the declaration.
 

 
-
+
 
3   The expression of each case label shall be an integer constant expression and no two of
     the case constant expressions in the same switch statement shall have the same value
     after conversion. There may be at most one default label in a switch statement.
@@ -8885,15 +7800,13 @@ Forward references:         conditional inclusion (6.10.1), complex arithmetic
     switch statement.)
     Semantics
 

-
-
+
 
4   A switch statement causes control to jump to, into, or past the statement that is the
     switch body , depending on the value of a controlling expression, and on the presence of a
     default label and the values of any case labels on or in the switch body. A case or
     default label is accessible only within the closest enclosing switch statement.
 

-
-
+
 
5   The integer promotions are performed on the controlling expression. The constant
     expression in each case label is converted to the promoted type of the controlling
     expression. If a converted value matches that of the promoted controlling expression,
@@ -8903,14 +7816,12 @@ Forward references:         conditional inclusion (6.10.1), complex arithmetic
     executed.
     Implementation limits
 

-
-
-
6   As discussed in 5.2.4.1, the implementation may limit the number of case values in a
+
+
6   As discussed in 5.2.4.1, the implementation may limit the number of case values in a
     switch statement.
 
 

-
-
+
 
7   EXAMPLE        In the artificial program fragment
              switch (expr)
              {
@@ -8927,92 +7838,70 @@ Forward references:         conditional inclusion (6.10.1), complex arithmetic
     access an indeterminate value. Similarly, the call to the function f cannot be reached.
 
 

-
-
+
 

 
6.8.5 [Iteration statements]

-

-
-
-
1            iteration-statement:
+
+
1 Syntax
+            iteration-statement:
                      while ( expression ) statement
                      do statement while ( expression ) ;
                      for ( expressionopt ; expressionopt ; expressionopt ) statement
                      for ( declaration expressionopt ; expressionopt ) statement
     Constraints
 

-
-
+
 
2   The controlling expression of an iteration statement shall have scalar type.
 

-
-
+
 
3   The declaration part of a for statement shall only declare identifiers for objects having
     storage class auto or register.
     Semantics
 

-
-
+
 
4   An iteration statement causes a statement called the loop body to be executed repeatedly
     until the controlling expression compares equal to 0. The repetition occurs regardless of
-    whether the loop body is entered from the iteration statement or by a jump.155)
+    whether the loop body is entered from the iteration statement or by a jump.[155]
 

-
 
 
Footnote 155) Code jumped over is not executed. In particular, the controlling expression of a for or while
          statement is not evaluated before entering the loop body, nor is clause-1 of a for statement.
 

 
-
+
 
5   An iteration statement is a block whose scope is a strict subset of the scope of its
     enclosing block. The loop body is also a block whose scope is a strict subset of the scope
     of the iteration statement.
 

-
-
-
6   An iteration statement whose controlling expression is not a constant expression,156) that
+
+
6   An iteration statement whose controlling expression is not a constant expression,[156] that
     performs no input/output operations, does not access volatile objects, and performs no
     synchronization or atomic operations in its body, controlling expression, or (in the case of
-
-    a for statement) its expression-3, may be assumed by the implementation to
-    terminate.157)
 

-
 
 
Footnote 156) An omitted controlling expression is replaced by a nonzero constant, which is a constant expression.
+    a for statement) its expression-3, may be assumed by the implementation to
+    terminate.157)
 

 
-
-
Footnote 157) This is intended to allow compiler transformations such as removal of empty loops even when
-         termination cannot be proven.
-

-
-
+
 

 
6.8.5.1 [The while statement]

-

-
-
+
 
1   The evaluation of the controlling expression takes place before each execution of the loop
     body.
 

-
-
+
 

 
6.8.5.2 [The do statement]

-

-
-
+
 
1   The evaluation of the controlling expression takes place after each execution of the loop
     body.
 

-
-
+
 

 
6.8.5.3 [The for statement]

-

-
-
+
 
1   The statement
              for ( clause-1 ; expression-2 ; expression-3 ) statement
     behaves as follows: The expression expression-2 is the controlling expression that is
@@ -9021,58 +7910,49 @@ Forward references:         conditional inclusion (6.10.1), complex arithmetic
     declaration, the scope of any identifiers it declares is the remainder of the declaration and
     the entire loop, including the other two expressions; it is reached in the order of execution
     before the first evaluation of the controlling expression. If clause-1 is an expression, it is
-    evaluated as a void expression before the first evaluation of the controlling expression.158)
+    evaluated as a void expression before the first evaluation of the controlling expression.[158]
 

-
 
 
Footnote 158) Thus, clause-1 specifies initialization for the loop, possibly declaring one or more variables for use in
          the loop; the controlling expression, expression-2, specifies an evaluation made before each iteration,
          such that execution of the loop continues until the expression compares equal to 0; and expression-3
          specifies an operation (such as incrementing) that is performed after each iteration.
+    Semantics
 

 
-
+
 
2   Both clause-1 and expression-3 can be omitted. An omitted expression-2 is replaced by a
     nonzero constant.
 

-
-
+
 

 
6.8.6 [Jump statements]

-

-
-
-
1            jump-statement:
+
+
1 Syntax
+            jump-statement:
                     goto identifier ;
                     continue ;
                     break ;
                     return expressionopt ;
-
-    Semantics
 

-
-
+
 
2   A jump statement causes an unconditional jump to another place.
 

-
-
+
 

 
6.8.6.1 [The goto statement]

-

-
-
-
1   The identifier in a goto statement shall name a label located somewhere in the enclosing
+
+
1 Constraints
+   The identifier in a goto statement shall name a label located somewhere in the enclosing
     function. A goto statement shall not jump from outside the scope of an identifier having
     a variably modified type to inside the scope of that identifier.
     Semantics
 

-
-
+
 
2   A goto statement causes an unconditional jump to the statement prefixed by the named
     label in the enclosing function.
 

-
-
+
 
3   EXAMPLE 1 It is sometimes convenient to jump into the middle of a complicated set of statements. The
     following outline presents one possible approach to a problem based on these three assumptions:
       1.   The general initialization code accesses objects only visible to the current function.
@@ -9096,8 +7976,7 @@ Forward references:         conditional inclusion (6.10.1), complex arithmetic
                     /* ... */
             }
 

-
-
+
 
4   EXAMPLE 2 A goto statement is not allowed to jump past any declarations of objects with variably
     modified types. A jump within the scope, however, is permitted.
             goto lab3;                         // invalid: going INTO scope of VLA.
@@ -9105,27 +7984,24 @@ Forward references:         conditional inclusion (6.10.1), complex arithmetic
                   double a[n];
                   a[j] = 4.4;
             lab3:
-                  a[j] = 3.3;
+                  a[j] = 3.3;
                   goto lab4;                   // valid: going WITHIN scope of VLA.
                   a[j] = 5.5;
             lab4:
-                  a[j] = 6.6;
+                  a[j] = 6.6;
             }
             goto lab4;                         // invalid: going INTO scope of VLA.
 
 

-
-
+
 

 
6.8.6.2 [The continue statement]

-

-
-
-
1   A continue statement shall appear only in or as a loop body.
+
+
1 Constraints
+   A continue statement shall appear only in or as a loop body.
     Semantics
 

-
-
+
 
2   A continue statement causes a jump to the loop-continuation portion of the smallest
     enclosing iteration statement; that is, to the end of the loop body. More precisely, in each
     of the statements
@@ -9136,60 +8012,52 @@ Forward references:         conditional inclusion (6.10.1), complex arithmetic
     contin: ;                            contin: ;                            contin: ;
     }                                    } while (/* ... */);                 }
     unless the continue statement shown is in an enclosed iteration statement (in which
-    case it is interpreted within that statement), it is equivalent to goto contin;.159)
+    case it is interpreted within that statement), it is equivalent to goto contin;.[159]
 

-
 
 
Footnote 159) Following the contin: label is a null statement.
 

 
-
+
 

 
6.8.6.3 [The break statement]

-

-
-
-
1   A break statement shall appear only in or as a switch body or loop body.
+
+
1 Constraints
+   A break statement shall appear only in or as a switch body or loop body.
     Semantics
 

-
-
+
 
2   A break statement terminates execution of the smallest enclosing switch or iteration
     statement.
 
 

-
-
+
 

 
6.8.6.4 [The return statement]

-

-
-
-
1   A return statement with an expression shall not appear in a function whose return type
+
+
1 Constraints
+   A return statement with an expression shall not appear in a function whose return type
     is void. A return statement without an expression shall only appear in a function
     whose return type is void.
     Semantics
 

-
-
+
 
2   A return statement terminates execution of the current function and returns control to
     its caller. A function may have any number of return statements.
 

-
-
+
 
3   If a return statement with an expression is executed, the value of the expression is
     returned to the caller as the value of the function call expression. If the expression has a
     type different from the return type of the function in which it appears, the value is
-    converted as if by assignment to an object having the return type of the function.160)
+    converted as if by assignment to an object having the return type of the function.[160]
 

-
 
-
Footnote 160) The return statement is not an assignment. The overlap restriction of subclause 6.5.16.1 does not
+
Footnote 160) The return statement is not an assignment. The overlap restriction of subclause 6.5.16.1 does not
          apply to the case of function return. The representation of floating-point values may have wider range
          or precision than implied by the type; a cast may be used to remove this extra range and precision.
 

 
-
+
 
4   EXAMPLE       In:
             struct s { double i; } f(void);
             union {
@@ -9212,14 +8080,12 @@ Forward references:         conditional inclusion (6.10.1), complex arithmetic
     a function call to fetch the value).
 
 

-
-
+
 

 
6.9 [External definitions]

-

-
-
-
1            translation-unit:
+
+
1 Syntax
+            translation-unit:
                      external-declaration
                      translation-unit external-declaration
              external-declaration:
@@ -9227,13 +8093,11 @@ Forward references:         conditional inclusion (6.10.1), complex arithmetic
                     declaration
     Constraints
 

-
-
+
 
2   The storage-class specifiers auto and register shall not appear in the declaration
     specifiers in an external declaration.
 

-
-
+
 
3   There shall be no more than one external definition for each identifier declared with
     internal linkage in a translation unit. Moreover, if an identifier declared with internal
     linkage is used in an expression (other than as a part of the operand of a sizeof or
@@ -9241,49 +8105,43 @@ Forward references:         conditional inclusion (6.10.1), complex arithmetic
     external definition for the identifier in the translation unit.
     Semantics
 

-
-
-
4   As discussed in 5.1.1.1, the unit of program text after preprocessing is a translation unit,
+
+
4   As discussed in 5.1.1.1, the unit of program text after preprocessing is a translation unit,
     which consists of a sequence of external declarations. These are described as ``external''
     because they appear outside any function (and hence have file scope). As discussed in
-     6.7, a declaration that also causes storage to be reserved for an object or a function named
+     6.7, a declaration that also causes storage to be reserved for an object or a function named
     by the identifier is a definition.
 

-
-
+
 
5   An external definition is an external declaration that is also a definition of a function
     (other than an inline definition) or an object. If an identifier declared with external
     linkage is used in an expression (other than as part of the operand of a sizeof or
     _Alignof operator whose result is an integer constant), somewhere in the entire
     program there shall be exactly one external definition for the identifier; otherwise, there
-    shall be no more than one.161)
+    shall be no more than one.[161]
 
 

-
 
 
Footnote 161) Thus, if an identifier declared with external linkage is not used in an expression, there need be no
          external definition for it.
 

 
-
+
 

 
6.9.1 [Function definitions]

-

-
-
-
1            function-definition:
+
+
1 Syntax
+            function-definition:
                     declaration-specifiers declarator declaration-listopt compound-statement
              declaration-list:
                     declaration
                     declaration-list declaration
     Constraints
 

-
-
+
 
2   The identifier declared in a function definition (which is the name of the function) shall
-    have a function type, as specified by the declarator portion of the function definition.162)
+    have a function type, as specified by the declarator portion of the function definition.[162]
 

-
 
 
Footnote 162) The intent is that the type category in a function definition cannot be inherited from a typedef:
                   typedef int F(void);                          //   type F is ``function with no parameters
@@ -9297,82 +8155,80 @@ Forward references:         conditional inclusion (6.10.1), complex arithmetic
                   F *((e))(void) { /* ... */ }                  //   same: parentheses irrelevant
                   int (*fp)(void);                              //   fp points to a function that has type F
                   F *Fp;                                        //   Fp points to a function that has type F
+     Semantics
 

 
-
+
 
3   The return type of a function shall be void or a complete object type other than array
     type.
 

-
-
+
 
4   The storage-class specifier, if any, in the declaration specifiers shall be either extern or
     static.
 

-
-
+
 
5   If the declarator includes a parameter type list, the declaration of each parameter shall
     include an identifier, except for the special case of a parameter list consisting of a single
     parameter of type void, in which case there shall not be an identifier. No declaration list
     shall follow.
 

-
-
+
 
6   If the declarator includes an identifier list, each declaration in the declaration list shall
     have at least one declarator, those declarators shall declare only identifiers from the
     identifier list, and every identifier in the identifier list shall be declared. An identifier
     declared as a typedef name shall not be redeclared as a parameter. The declarations in the
     declaration list shall contain no storage-class specifier other than register and no
     initializations.
-     Semantics
 

-
-
+
 
7    The declarator in a function definition specifies the name of the function being defined
      and the identifiers of its parameters. If the declarator includes a parameter type list, the
      list also specifies the types of all the parameters; such a declarator also serves as a
      function prototype for later calls to the same function in the same translation unit. If the
-     declarator includes an identifier list,163) the types of the parameters shall be declared in a
+     declarator includes an identifier list,[163] the types of the parameters shall be declared in a
      following declaration list. In either case, the type of each parameter is adjusted as
-     described in 6.7.6.3 for a parameter type list; the resulting type shall be a complete object
+     described in 6.7.6.3 for a parameter type list; the resulting type shall be a complete object
      type.
 

-
 
-
Footnote 163) See ``future language directions'' (6.11.7).
+
Footnote 163) See ``future language directions'' (6.11.7).
 

 
-
+
 
8    If a function that accepts a variable number of arguments is defined without a parameter
      type list that ends with the ellipsis notation, the behavior is undefined.
 

-
-
-
9    Each parameter has automatic storage duration; its identifier is an lvalue.164) The layout
+
+
9    Each parameter has automatic storage duration; its identifier is an lvalue.[164] The layout
      of the storage for parameters is unspecified.
 

-
 
 
Footnote 164) A parameter identifier cannot be redeclared in the function body except in an enclosed block.
+              extern int max(a, b)
+              int a, b;
+              {
+                    return a > b ? a : b;
+              }
+     Here int a, b; is the declaration list for the parameters. The difference between these two definitions is
+     that the first form acts as a prototype declaration that forces conversion of the arguments of subsequent calls
+     to the function, whereas the second form does not.
 

 
-
+
 
10   On entry to the function, the size expressions of each variably modified parameter are
      evaluated and the value of each argument expression is converted to the type of the
      corresponding parameter as if by assignment. (Array expressions and function
      designators as arguments were converted to pointers before the call.)
 

-
-
+
 
11   After all parameters have been assigned, the compound statement that constitutes the
      body of the function definition is executed.
 

-
-
+
 
12   If the } that terminates a function is reached, and the value of the function call is used by
      the caller, the behavior is undefined.
 

-
-
+
 
13   EXAMPLE 1       In the following:
               extern int max(int a, int b)
               {
@@ -9384,18 +8240,8 @@ Forward references:         conditional inclusion (6.10.1), complex arithmetic
      is the function body. The following similar definition uses the identifier-list form for the parameter
      declarations:
 
-              extern int max(a, b)
-              int a, b;
-              {
-                    return a > b ? a : b;
-              }
-     Here int a, b; is the declaration list for the parameters. The difference between these two definitions is
-     that the first form acts as a prototype declaration that forces conversion of the arguments of subsequent calls
-     to the function, whereas the second form does not.
-
 

-
-
+
 
14   EXAMPLE 2           To pass one function to another, one might say
                           int f(void);
                           /* ... */
@@ -9413,18 +8259,15 @@ Forward references:         conditional inclusion (6.10.1), complex arithmetic
                     func(); /* or (*func)(); ...                   */
               }
 

-
-
+
 

 
6.9.2 [External object definitions]

-

-
-
-
1    If the declaration of an identifier for an object has file scope and an initializer, the
+
+
1 Semantics
+    If the declaration of an identifier for an object has file scope and an initializer, the
      declaration is an external definition for the identifier.
 

-
-
+
 
2    A declaration of an identifier for an object that has file scope without an initializer, and
      without a storage-class specifier or with the storage-class specifier static, constitutes a
      tentative definition. If a translation unit contains one or more tentative definitions for an
@@ -9433,13 +8276,11 @@ Forward references:         conditional inclusion (6.10.1), complex arithmetic
      identifier, with the composite type as of the end of the translation unit, with an initializer
      equal to 0.
 

-
-
+
 
3    If the declaration of an identifier for an object is a tentative definition and has internal
      linkage, the declared type shall not be an incomplete type.
 

-
-
+
 
4   EXAMPLE 1
              int i1 = 1;                    // definition, external linkage
              static int i2 = 2;             // definition, internal linkage
@@ -9447,10 +8288,10 @@ Forward references:         conditional inclusion (6.10.1), complex arithmetic
              int i4;                        // tentative definition, external linkage
              static int i5;                 // tentative definition, internal linkage
              int   i1;                      // valid tentative definition, refers to previous
-             int   i2;                      // 6.2.2 renders undefined, linkage disagreement
+             int   i2;                      // 6.2.2 renders undefined, linkage disagreement
              int   i3;                      // valid tentative definition, refers to previous
              int   i4;                      // valid tentative definition, refers to previous
-             int   i5;                      // 6.2.2 renders undefined, linkage disagreement
+             int   i5;                      // 6.2.2 renders undefined, linkage disagreement
              extern    int   i1;            // refers to previous, whose linkage is external
              extern    int   i2;            // refers to previous, whose linkage is internal
              extern    int   i3;            // refers to previous, whose linkage is external
@@ -9458,21 +8299,18 @@ Forward references:         conditional inclusion (6.10.1), complex arithmetic
              extern    int   i5;            // refers to previous, whose linkage is internal
 
 

-
-
+
 
5   EXAMPLE 2       If at the end of the translation unit containing
              int i[];
     the array i still has incomplete type, the implicit initializer causes it to have one element, which is set to
     zero on program startup.
 

-
-
+
 

 
6.10 [Preprocessing directives]

-

-
-
-
1            preprocessing-file:
+
+
1 Syntax
+            preprocessing-file:
                     groupopt
              group:
                       group-part
@@ -9525,32 +8363,33 @@ Forward references:         conditional inclusion (6.10.1), complex arithmetic
                     the new-line character
     Description
 

-
-
+
 
2   A preprocessing directive consists of a sequence of preprocessing tokens that satisfies the
     following constraints: The first token in the sequence is a # preprocessing token that (at
     the start of translation phase 4) is either the first character in the source file (optionally
     after white space containing no new-line characters) or that follows white space
     containing at least one new-line character. The last token in the sequence is the first new-
-    line character that follows the first token in the sequence.165) A new-line character ends
+    line character that follows the first token in the sequence.[165] A new-line character ends
     the preprocessing directive even if it occurs within what would otherwise be an
-
-    invocation of a function-like macro.
 

+
+
Footnote 165) Thus, preprocessing directives are commonly called ``lines''. These ``lines'' have no other syntactic
+         significance, as all white space is equivalent except in certain situations during preprocessing (see the
+         # character string literal creation operator in 6.10.3.2, for example).
+    invocation of a function-like macro.
+

 
-
+
 
3   A text line shall not begin with a # preprocessing token. A non-directive shall not begin
     with any of the directive names appearing in the syntax.
 

-
-
-
4   When in a group that is skipped (6.10.1), the directive syntax is relaxed to allow any
+
+
4   When in a group that is skipped (6.10.1), the directive syntax is relaxed to allow any
     sequence of preprocessing tokens to occur between the directive name and the following
     new-line character.
     Constraints
 

-
-
+
 
5   The only white-space characters that shall appear between preprocessing tokens within a
     preprocessing directive (from just after the introducing # preprocessing token through
     just before the terminating new-line character) are space and horizontal-tab (including
@@ -9558,19 +8397,16 @@ Forward references:         conditional inclusion (6.10.1), complex arithmetic
     translation phase 3).
     Semantics
 

-
-
+
 
6   The implementation can process and skip sections of source files conditionally, include
     other source files, and replace macros. These capabilities are called preprocessing,
     because conceptually they occur before translation of the resulting translation unit.
 

-
-
+
 
7   The preprocessing tokens within a preprocessing directive are not subject to macro
     expansion unless otherwise stated.
 

-
-
+
 
8   EXAMPLE        In:
              #define EMPTY
              EMPTY # include <file.h>
@@ -9579,45 +8415,39 @@ Forward references:         conditional inclusion (6.10.1), complex arithmetic
     replaced.
 
 

-
-
+
 

 
6.10.1 [Conditional inclusion]

-

-
-
-
1   The expression that controls conditional inclusion shall be an integer constant expression
+
+
1 Constraints
+   The expression that controls conditional inclusion shall be an integer constant expression
     except that: identifiers (including those lexically identical to keywords) are interpreted as
-    described below;166) and it may contain unary operator expressions of the form
+    described below;[166] and it may contain unary operator expressions of the form
          defined identifier
     or
          defined ( identifier )
     which evaluate to 1 if the identifier is currently defined as a macro name (that is, if it is
-
-    predefined or if it has been the subject of a #define preprocessing directive without an
-    intervening #undef directive with the same subject identifier), 0 if it is not.
 

-
 
 
Footnote 166) Because the controlling constant expression is evaluated during translation phase 4, all identifiers
          either are or are not macro names -- there simply are no keywords, enumeration constants, etc.
+    predefined or if it has been the subject of a #define preprocessing directive without an
+    intervening #undef directive with the same subject identifier), 0 if it is not.
 

 
-
+
 
2   Each preprocessing token that remains (in the list of preprocessing tokens that will
     become the controlling expression) after all macro replacements have occurred shall be in
-    the lexical form of a token (6.4).
+    the lexical form of a token (6.4).
     Semantics
 

-
-
+
 
3   Preprocessing directives of the forms
        # if   constant-expression new-line groupopt
        # elif constant-expression new-line groupopt
     check whether the controlling constant expression evaluates to nonzero.
 

-
-
+
 
4   Prior to evaluation, macro invocations in the list of preprocessing tokens that will become
     the controlling constant expression are replaced (except for those macro names modified
     by the defined unary operator), just as in normal text. If the token defined is
@@ -9627,17 +8457,16 @@ Forward references:         conditional inclusion (6.10.1), complex arithmetic
     operator have been performed, all remaining identifiers (including those lexically
     identical to keywords) are replaced with the pp-number 0, and then each preprocessing
     token is converted into a token. The resulting tokens compose the controlling constant
-    expression which is evaluated according to the rules of 6.6. For the purposes of this
+    expression which is evaluated according to the rules of 6.6. For the purposes of this
     token conversion and evaluation, all signed integer types and all unsigned integer types
     act as if they have the same representation as, respectively, the types intmax_t and
-    uintmax_t defined in the header <stdint.h>.167) This includes interpreting
+    uintmax_t defined in the header <stdint.h>.[167] This includes interpreting
     character constants, which may involve converting escape sequences into execution
     character set members. Whether the numeric value for these character constants matches
     the value obtained when an identical character constant occurs in an expression (other
-    than within a #if or #elif directive) is implementation-defined.168) Also, whether a
+    than within a #if or #elif directive) is implementation-defined.[168] Also, whether a
     single-character character constant may have a negative value is implementation-defined.
 

-
 
 
Footnote 167) Thus, on an implementation where INT_MAX is 0x7FFF and UINT_MAX is 0xFFFF, the constant
          0x8000 is signed and positive within a #if expression even though it would be unsigned in
@@ -9651,7 +8480,7 @@ Forward references:         conditional inclusion (6.10.1), complex arithmetic
             if ('z' - 'a' == 25)
 

 
-
+
 
5   Preprocessing directives of the forms
        # ifdef identifier new-line groupopt
        # ifndef identifier new-line groupopt
@@ -9659,8 +8488,7 @@ Forward references:         conditional inclusion (6.10.1), complex arithmetic
     conditions are equivalent to #if defined identifier and #if !defined identifier
     respectively.
 

-
-
+
 
6   Each directive's condition is checked in order. If it evaluates to false (zero), the group
     that it controls is skipped: directives are processed only through the name that determines
     the directive in order to keep track of the level of nested conditionals; the rest of the
@@ -9668,29 +8496,31 @@ Forward references:         conditional inclusion (6.10.1), complex arithmetic
     group. Only the first group whose control condition evaluates to true (nonzero) is
     processed. If none of the conditions evaluates to true, and there is a #else directive, the
     group controlled by the #else is processed; lacking a #else directive, all the groups
-    until the #endif are skipped.169)
-    Forward references: macro replacement (6.10.3), source file inclusion (6.10.2), largest
-    integer types (7.20.1.5).
+    until the #endif are skipped.[169]
+    Forward references: macro replacement (6.10.3), source file inclusion (6.10.2), largest
+    integer types (7.20.1.5).
 

-
 
 
Footnote 169) As indicated by the syntax, a preprocessing token shall not follow a #else or #endif directive
          before the terminating new-line character. However, comments may appear anywhere in a source file,
          including within a preprocessing directive.
+    for in an implementation-defined manner. If this search is not supported, or if the search
+    fails, the directive is reprocessed as if it read
+       # include <h-char-sequence> new-line
+    with the identical contained sequence (including > characters, if any) from the original
+    directive.
 

 
-
+
 

 
6.10.2 [Source file inclusion]

-

-
-
-
1   A #include directive shall identify a header or source file that can be processed by the
+
+
1 Constraints
+   A #include directive shall identify a header or source file that can be processed by the
     implementation.
     Semantics
 

-
-
+
 
2   A preprocessing directive of the form
        # include <h-char-sequence> new-line
     searches a sequence of implementation-defined places for a header identified uniquely by
@@ -9698,59 +8528,47 @@ Forward references:         conditional inclusion (6.10.1), complex arithmetic
     directive by the entire contents of the header. How the places are specified or the header
     identified is implementation-defined.
 

-
-
+
 
3   A preprocessing directive of the form
        # include "q-char-sequence" new-line
     causes the replacement of that directive by the entire contents of the source file identified
     by the specified sequence between the " delimiters. The named source file is searched
-
-    for in an implementation-defined manner. If this search is not supported, or if the search
-    fails, the directive is reprocessed as if it read
-       # include <h-char-sequence> new-line
-    with the identical contained sequence (including > characters, if any) from the original
-    directive.
 

-
-
+
 
4   A preprocessing directive of the form
        # include pp-tokens new-line
     (that does not match one of the two previous forms) is permitted. The preprocessing
     tokens after include in the directive are processed just as in normal text. (Each
     identifier currently defined as a macro name is replaced by its replacement list of
     preprocessing tokens.) The directive resulting after all replacements shall match one of
-    the two previous forms.170) The method by which a sequence of preprocessing tokens
+    the two previous forms.[170] The method by which a sequence of preprocessing tokens
     between a < and a > preprocessing token pair or a pair of " characters is combined into a
     single header name preprocessing token is implementation-defined.
 

-
 
 
Footnote 170) Note that adjacent string literals are not concatenated into a single string literal (see the translation
-         phases in 5.1.1.2); thus, an expansion that results in two string literals is an invalid directive.
+         phases in 5.1.1.2); thus, an expansion that results in two string literals is an invalid directive.
 

 
-
+
 
5   The implementation shall provide unique mappings for sequences consisting of one or
-    more nondigits or digits (6.4.2.1) followed by a period (.) and a single nondigit. The
+    more nondigits or digits (6.4.2.1) followed by a period (.) and a single nondigit. The
     first character shall not be a digit. The implementation may ignore distinctions of
     alphabetical case and restrict the mapping to eight significant characters before the
     period.
 

-
-
+
 
6   A #include preprocessing directive may appear in a source file that has been read
     because of a #include directive in another file, up to an implementation-defined
-    nesting limit (see 5.2.4.1).
+    nesting limit (see 5.2.4.1).
 

-
-
+
 
7   EXAMPLE 1       The most common uses of #include preprocessing directives are as in the following:
               #include <stdio.h>
               #include "myprog.h"
 
 

-
-
+
 
8   EXAMPLE 2     This illustrates macro-replaced #include directives:
            #if VERSION == 1
                  #define INCFILE            "vers1.h"
@@ -9761,21 +8579,18 @@ Forward references:         conditional inclusion (6.10.1), complex arithmetic
            #endif
            #include INCFILE
 
-    Forward references: macro replacement (6.10.3).
+    Forward references: macro replacement (6.10.3).
 

-
-
+
 

 
6.10.3 [Macro replacement]

-

-
-
-
1   Two replacement lists are identical if and only if the preprocessing tokens in both have
+
+
1 Constraints
+   Two replacement lists are identical if and only if the preprocessing tokens in both have
     the same number, ordering, spelling, and white-space separation, where all white-space
     separations are considered identical.
 

-
-
+
 
2   An identifier currently defined as an object-like macro shall not be redefined by another
     #define preprocessing directive unless the second definition is an object-like macro
     definition and the two replacement lists are identical. Likewise, an identifier currently
@@ -9784,13 +8599,11 @@ Forward references:         conditional inclusion (6.10.1), complex arithmetic
     that has the same number and spelling of parameters, and the two replacement lists are
     identical.
 

-
-
+
 
3   There shall be white-space between the identifier and the replacement list in the definition
     of an object-like macro.
 

-
-
+
 
4   If the identifier-list in the macro definition does not end with an ellipsis, the number of
     arguments (including those arguments consisting of no preprocessing tokens) in an
     invocation of a function-like macro shall equal the number of parameters in the macro
@@ -9798,47 +8611,41 @@ Forward references:         conditional inclusion (6.10.1), complex arithmetic
     parameters in the macro definition (excluding the ...). There shall exist a )
     preprocessing token that terminates the invocation.
 

-
-
+
 
5   The identifier _ _VA_ARGS_ _ shall occur only in the replacement-list of a function-like
     macro that uses the ellipsis notation in the parameters.
 

-
-
+
 
6   A parameter identifier in a function-like macro shall be uniquely declared within its
     scope.
     Semantics
 

-
-
+
 
7   The identifier immediately following the define is called the macro name. There is one
     name space for macro names. Any white-space characters preceding or following the
     replacement list of preprocessing tokens are not considered part of the replacement list
 
      for either form of macro.
 

-
-
+
 
8    If a # preprocessing token, followed by an identifier, occurs lexically at the point at which
      a preprocessing directive could begin, the identifier is not subject to macro replacement.
 

-
-
+
 
9    A preprocessing directive of the form
         # define identifier replacement-list new-line
-     defines an object-like macro that causes each subsequent instance of the macro name171)
+     defines an object-like macro that causes each subsequent instance of the macro name[171]
      to be replaced by the replacement list of preprocessing tokens that constitute the
      remainder of the directive. The replacement list is then rescanned for more macro names
      as specified below.
 

-
 
 
Footnote 171) Since, by macro-replacement time, all character constants and string literals are preprocessing tokens,
-          not sequences possibly containing identifier-like subsequences (see 5.1.1.2, translation phases), they
+          not sequences possibly containing identifier-like subsequences (see 5.1.1.2, translation phases), they
           are never scanned for macro names or parameters.
 

 
-
+
 
10   A preprocessing directive of the form
         # define identifier lparen identifier-listopt ) replacement-list new-line
         # define identifier lparen ... ) replacement-list new-line
@@ -9855,35 +8662,29 @@ Forward references:         conditional inclusion (6.10.1), complex arithmetic
      tokens making up an invocation of a function-like macro, new-line is considered a normal
      white-space character.
 

-
-
+
 
11   The sequence of preprocessing tokens bounded by the outside-most matching parentheses
      forms the list of arguments for the function-like macro. The individual arguments within
      the list are separated by comma preprocessing tokens, but comma preprocessing tokens
      between matching inner parentheses do not separate arguments. If there are sequences of
      preprocessing tokens within the list of arguments that would otherwise act as
-     preprocessing directives,172) the behavior is undefined.
+     preprocessing directives,[172] the behavior is undefined.
 

-
 
 
Footnote 172) Despite the name, a non-directive is a preprocessing directive.
-

-
-
-
12   If there is a ... in the identifier-list in the macro definition, then the trailing arguments,
-     including any separating comma preprocessing tokens, are merged to form a single item:
-
     the variable arguments. The number of arguments so combined is such that, following
     merger, the number of arguments is one more than the number of parameters in the macro
     definition (excluding the ...).
-

+

 
-
+
+
12   If there is a ... in the identifier-list in the macro definition, then the trailing arguments,
+     including any separating comma preprocessing tokens, are merged to form a single item:
+

+
 

 
6.10.3.1 [Argument substitution]

-

-
-
+
 
1   After the arguments for the invocation of a function-like macro have been identified,
     argument substitution takes place. A parameter in the replacement list, unless preceded
     by a # or ## preprocessing token or followed by a ## preprocessing token (see below), is
@@ -9892,25 +8693,21 @@ Forward references:         conditional inclusion (6.10.1), complex arithmetic
     completely macro replaced as if they formed the rest of the preprocessing file; no other
     preprocessing tokens are available.
 

-
-
+
 
2   An identifier _ _VA_ARGS_ _ that occurs in the replacement list shall be treated as if it
     were a parameter, and the variable arguments shall form the preprocessing tokens used to
     replace it.
 

-
-
+
 

 
6.10.3.2 [The # operator]

-

-
-
-
1   Each # preprocessing token in the replacement list for a function-like macro shall be
+
+
1 Constraints
+   Each # preprocessing token in the replacement list for a function-like macro shall be
     followed by a parameter as the next preprocessing token in the replacement list.
     Semantics
 

-
-
+
 
2   If, in the replacement list, a parameter is immediately preceded by a # preprocessing
     token, both are replaced by a single character string literal preprocessing token that
     contains the spelling of the preprocessing token sequence for the corresponding
@@ -9927,32 +8724,28 @@ Forward references:         conditional inclusion (6.10.1), complex arithmetic
     string literal corresponding to an empty argument is "". The order of evaluation of # and
     ## operators is unspecified.
 

-
-
+
 

 
6.10.3.3 [The ## operator]

-

-
-
-
1   A ## preprocessing token shall not occur at the beginning or at the end of a replacement
+
+
1 Constraints
+   A ## preprocessing token shall not occur at the beginning or at the end of a replacement
     list for either form of macro definition.
     Semantics
 

-
-
+
 
2   If, in the replacement list of a function-like macro, a parameter is immediately preceded
     or followed by a ## preprocessing token, the parameter is replaced by the corresponding
     argument's preprocessing token sequence; however, if an argument consists of no
     preprocessing tokens, the parameter is replaced by a placemarker preprocessing token
-    instead.173)
+    instead.[173]
 

-
 
 
Footnote 173) Placemarker preprocessing tokens do not appear in the syntax because they are temporary entities that
          exist only within translation phase 4.
 

 
-
+
 
3   For both object-like and function-like macro invocations, before the replacement list is
     reexamined for more macro names to replace, each instance of a ## preprocessing token
     in the replacement list (not from an argument) is deleted and the preceding preprocessing
@@ -9964,8 +8757,7 @@ Forward references:         conditional inclusion (6.10.1), complex arithmetic
     token is available for further macro replacement. The order of evaluation of ## operators
     is unspecified.
 

-
-
+
 
4   EXAMPLE       In the following fragment:
             #define     hash_hash # ## #
             #define     mkstr(a) # a
@@ -9983,20 +8775,16 @@ Forward references:         conditional inclusion (6.10.1), complex arithmetic
     this new token is not the ## operator.
 
 

-
-
+
 

 
6.10.3.4 [Rescanning and further replacement]

-

-
-
+
 
1   After all parameters in the replacement list have been substituted and # and ##
     processing has taken place, all placemarker preprocessing tokens are removed. The
     resulting preprocessing token sequence is then rescanned, along with all subsequent
     preprocessing tokens of the source file, for more macro names to replace.
 

-
-
+
 
2   If the name of the macro being replaced is found during this scan of the replacement list
     (not including the rest of the source file's preprocessing tokens), it is not replaced.
     Furthermore, if any nested replacements encounter the name of the macro being replaced,
@@ -10004,14 +8792,12 @@ Forward references:         conditional inclusion (6.10.1), complex arithmetic
     available for further replacement even if they are later (re)examined in contexts in which
     that macro name preprocessing token would otherwise have been replaced.
 

-
-
+
 
3   The resulting completely macro-replaced preprocessing token sequence is not processed
     as a preprocessing directive even if it resembles one, but all pragma unary operator
-    expressions within it are then processed as specified in 6.10.9 below.
+    expressions within it are then processed as specified in 6.10.9 below.
 

-
-
+
 
4   EXAMPLE There are cases where it is not clear whether a replacement is nested or not. For example,
     given the following macro definitions:
             #define f(a) a*g
@@ -10025,33 +8811,27 @@ Forward references:         conditional inclusion (6.10.1), complex arithmetic
     Strictly conforming programs are not permitted to depend on such unspecified behavior.
 
 

-
-
+
 

 
6.10.3.5 [Scope of macro definitions]

-

-
-
+
 
1   A macro definition lasts (independent of block structure) until a corresponding #undef
     directive is encountered or (if none is encountered) until the end of the preprocessing
     translation unit. Macro definitions have no significance after translation phase 4.
 

-
-
+
 
2   A preprocessing directive of the form
          # undef identifier new-line
     causes the specified identifier no longer to be defined as a macro name. It is ignored if
     the specified identifier is not currently defined as a macro name.
 

-
-
+
 
3   EXAMPLE 1        The simplest use of this facility is to define a ``manifest constant'', as in
             #define TABSIZE 100
              int table[TABSIZE];
 
 

-
-
+
 
4   EXAMPLE 2 The following defines a function-like macro whose value is the maximum of its arguments.
     It has the advantages of working for any compatible types of the arguments and of generating in-line code
     without the overhead of function calling. It has the disadvantages of evaluating one or the other of its
@@ -10061,8 +8841,7 @@ Forward references:         conditional inclusion (6.10.1), complex arithmetic
     The parentheses ensure that the arguments and the resulting expression are bound properly.
 
 

-
-
+
 
5   EXAMPLE 3      To illustrate the rules for redefinition and reexamination, the sequence
              #define    x          3
              #define    f(a)       f(x * (a))
@@ -10090,8 +8869,7 @@ Forward references:         conditional inclusion (6.10.1), complex arithmetic
              char c[2][6] = { "hello", "" };
 
 

-
-
+
 
6   EXAMPLE 4      To illustrate the rules for creating character string literals and concatenating tokens, the
     sequence
              #define str(s)      # s
@@ -10128,8 +8906,7 @@ Forward references:         conditional inclusion (6.10.1), complex arithmetic
     Space around the # and ## tokens in the macro definition is optional.
 
 

-
-
+
 
7   EXAMPLE 5        To illustrate the rules for placemarker preprocessing tokens, the sequence
              #define t(x,y,z) x ## y ## z
              int j[] = { t(1,2,3), t(,4,5), t(6,,7), t(8,9,),
@@ -10139,8 +8916,7 @@ Forward references:         conditional inclusion (6.10.1), complex arithmetic
                          10, 11, 12, };
 
 

-
-
+
 
8   EXAMPLE 6        To demonstrate the redefinition rules, the following sequence is valid.
              #define      OBJ_LIKE      (1-1)
              #define      OBJ_LIKE      /* white space */ (1-1) /* other */
@@ -10155,8 +8931,7 @@ Forward references:         conditional inclusion (6.10.1), complex arithmetic
              #define      FUNC_LIKE(b) ( b ) // different parameter spelling
 
 

-
-
+
 
9   EXAMPLE 7        Finally, to show the variable argument list macro facilities:
              #define debug(...)       fprintf(stderr, _ _VA_ARGS_ _)
              #define showlist(...)    puts(#_ _VA_ARGS_ _)
@@ -10174,39 +8949,33 @@ Forward references:         conditional inclusion (6.10.1), complex arithmetic
                          printf("x is %d but y is %d", x, y));
 
 

-
-
+
 

 
6.10.4 [Line control]

-

-
-
-
1   The string literal of a #line directive, if present, shall be a character string literal.
+
+
1 Constraints
+   The string literal of a #line directive, if present, shall be a character string literal.
     Semantics
 

-
-
+
 
2   The line number of the current source line is one greater than the number of new-line
-    characters read or introduced in translation phase 1 (5.1.1.2) while processing the source
+    characters read or introduced in translation phase 1 (5.1.1.2) while processing the source
     file to the current token.
 

-
-
+
 
3   A preprocessing directive of the form
        # line digit-sequence new-line
     causes the implementation to behave as if the following sequence of source lines begins
     with a source line that has a line number as specified by the digit sequence (interpreted as
     a decimal integer). The digit sequence shall not specify zero, nor a number greater than 2147483647.
 

-
-
+
 
4   A preprocessing directive of the form
        # line digit-sequence "s-char-sequenceopt" new-line
     sets the presumed line number similarly and changes the presumed name of the source
     file to be the contents of the character string literal.
 

-
-
+
 
5   A preprocessing directive of the form
        # line pp-tokens new-line
     (that does not match one of the two previous forms) is permitted. The preprocessing
@@ -10215,34 +8984,29 @@ Forward references:         conditional inclusion (6.10.1), complex arithmetic
     tokens). The directive resulting after all replacements shall match one of the two
     previous forms and is then processed as appropriate.
 

-
-
+
 

 
6.10.5 [Error directive]

-

-
-
-
1   A preprocessing directive of the form
+
+
1 Semantics
+   A preprocessing directive of the form
        # error pp-tokensopt new-line
     causes the implementation to produce a diagnostic message that includes the specified
     sequence of preprocessing tokens.
 

-
-
+
 

 
6.10.6 [Pragma directive]

-

-
-
-
1   A preprocessing directive of the form
+
+
1 Semantics
+   A preprocessing directive of the form
        # pragma pp-tokensopt new-line
     where the preprocessing token STDC does not immediately follow pragma in the
-    directive (prior to any macro replacement)174) causes the implementation to behave in an
+    directive (prior to any macro replacement)[174] causes the implementation to behave in an
     implementation-defined manner. The behavior might cause translation to fail or cause the
     translator or the resulting program to behave in a non-conforming manner. Any such
     pragma that is not recognized by the implementation is ignored.
 

-
 
 
Footnote 174) An implementation is not required to perform macro replacement in pragmas, but it is permitted
          except for in standard pragmas (where STDC immediately follows pragma). If the result of macro
@@ -10251,69 +9015,59 @@ Forward references:         conditional inclusion (6.10.1), complex arithmetic
          but is not required to.
 

 
-
+
 
2   If the preprocessing token STDC does immediately follow pragma in the directive (prior
     to any macro replacement), then no macro replacement is performed on the directive, and
-    the directive shall have one of the following forms175) whose meanings are described
+    the directive shall have one of the following forms[175] whose meanings are described
     elsewhere:
        #pragma STDC FP_CONTRACT on-off-switch
        #pragma STDC FENV_ACCESS on-off-switch
        #pragma STDC CX_LIMITED_RANGE on-off-switch
        on-off-switch: one of
                    ON     OFF           DEFAULT
-    Forward references: the FP_CONTRACT pragma (7.12.2), the FENV_ACCESS pragma
-    (7.6.1), the CX_LIMITED_RANGE pragma (7.3.4).
+    Forward references: the FP_CONTRACT pragma (7.12.2), the FENV_ACCESS pragma
+    (7.6.1), the CX_LIMITED_RANGE pragma (7.3.4).
 
 

-
 
-
Footnote 175) See ``future language directions'' (6.11.8).
+
Footnote 175) See ``future language directions'' (6.11.8).
 

 
-
+
 

 
6.10.7 [Null directive]

-

-
-
-
1   A preprocessing directive of the form
+
+
1 Semantics
+   A preprocessing directive of the form
        # new-line
     has no effect.
 

-
-
+
 

 
6.10.8 [Predefined macro names]

-

-
-
-
1   The values of the predefined macros listed in the following subclauses176) (except for
+
+
1   The values of the predefined macros listed in the following subclauses[176] (except for
     _ _FILE_ _ and _ _LINE_ _) remain constant throughout the translation unit.
 

-
 
-
Footnote 176) See ``future language directions'' (6.11.9).
+
Footnote 176) See ``future language directions'' (6.11.9).
 

 
-
+
 
2   None of these macro names, nor the identifier defined, shall be the subject of a
     #define or a #undef preprocessing directive. Any other predefined macro names
     shall begin with a leading underscore followed by an uppercase letter or a second
     underscore.
 

-
-
+
 
3   The implementation shall not predefine the macro _ _cplusplus, nor shall it define it
     in any standard header.
-    Forward references: standard headers (7.1.2).
+    Forward references: standard headers (7.1.2).
 

-
-
+
 

 
6.10.8.1 [Mandatory macros]

-

-
-
+
 
1   The following macro names shall be defined by the implementation:
     _ _DATE_ _ The date of translation of the preprocessing translation unit: a character
                string literal of the form "Mmm dd yyyy", where the names of the
@@ -10321,42 +9075,37 @@ Forward references:         conditional inclusion (6.10.1), complex arithmetic
                first character of dd is a space character if the value is less than 10. If the
                date of translation is not available, an implementation-defined valid date
                shall be supplied.
-    _ _FILE_ _ The presumed name of the current source file (a character string literal).177)
+    _ _FILE_ _ The presumed name of the current source file (a character string literal).[177]
     _ _LINE_ _ The presumed line number (within the current source file) of the current
-               source line (an integer constant).177)
+               source line (an integer constant).[177]
     _ _STDC_ _ The integer constant 1, intended to indicate a conforming implementation.
     _ _STDC_HOSTED_ _ The integer constant 1 if the implementation is a hosted
               implementation or the integer constant 0 if it is not.
-
+

+
+
Footnote 177) The presumed source file name and line number can be changed by the #line directive.
     _ _STDC_VERSION_ _ The integer constant 201ymmL.178)
     _ _TIME_ _ The time of translation of the preprocessing translation unit: a character
                string literal of the form "hh:mm:ss" as in the time generated by the
                asctime function. If the time of translation is not available, an
                implementation-defined valid time shall be supplied.
-    Forward references: the asctime function (7.27.3.1).
-

-
-
-
Footnote 177) The presumed source file name and line number can be changed by the #line directive.
+    Forward references: the asctime function (7.27.3.1).
 

 
 
 
Footnote 177) The presumed source file name and line number can be changed by the #line directive.
+    _ _STDC_VERSION_ _ The integer constant 201ymmL.178)
+    _ _TIME_ _ The time of translation of the preprocessing translation unit: a character
+               string literal of the form "hh:mm:ss" as in the time generated by the
+               asctime function. If the time of translation is not available, an
+               implementation-defined valid time shall be supplied.
+    Forward references: the asctime function (7.27.3.1).
 

 
-
-
Footnote 178) This macro was not specified in ISO/IEC 9899:1990 and was specified as 199409L in
-         ISO/IEC 9899/AMD1:1995 and as 199901L in ISO/IEC 9899:1999. The intention is that this will
-         remain an integer constant of type long int that is increased with each revision of this International
-         Standard.
-

-
-
+
 

 
6.10.8.2 [Environment macros]

-

-
-
+
 
1   The following macro names are conditionally defined by the implementation:
     _ _STDC_ISO_10646_ _ An integer constant of the form yyyymmL (for example,
               199712L). If this symbol is defined, then every character in the Unicode
@@ -10378,16 +9127,13 @@ Forward references:         conditional inclusion (6.10.1), complex arithmetic
               char32_t are UTF-32 encoded. If some other encoding is used, the
               macro shall not be defined and the actual encoding used is implementation-
               defined.
-    Forward references: common definitions (7.19), unicode utilities (7.28).
+    Forward references: common definitions (7.19), unicode utilities (7.28).
 
 

-
-
+
 

 
6.10.8.3 [Conditional feature macros]

-

-
-
+
 
1   The following macro names are conditionally defined by the implementation:
     _ _STDC_ANALYZABLE_ _ The integer constant 1, intended to indicate conformance to
               the specifications in annex L (Analyzability).
@@ -10397,7 +9143,7 @@ Forward references:         conditional inclusion (6.10.1), complex arithmetic
               adherence to the specifications in annex G (IEC 60559 compatible complex
               arithmetic).
     _ _STDC_LIB_EXT1_ _ The integer constant 201ymmL, intended to indicate support
-              for the extensions defined in annex K (Bounds-checking interfaces).179)
+              for the extensions defined in annex K (Bounds-checking interfaces).[179]
     _ _STDC_NO_ATOMICS_ _ The integer constant 1, intended to indicate that the
               implementation does not support atomic types (including the _Atomic
               type qualifier) and the <stdatomic.h> header.
@@ -10410,25 +9156,22 @@ Forward references:         conditional inclusion (6.10.1), complex arithmetic
               implementation does not support variable length arrays or variably
               modified types.
 

-
 
 
Footnote 179) The intention is that this will remain an integer constant of type long int that is increased with
          each revision of this International Standard.
 

 
-
+
 
2   An implementation that defines _ _STDC_NO_COMPLEX_ _ shall not define
     _ _STDC_IEC_559_COMPLEX_ _.
 
 

-
-
+
 

 
6.10.9 [Pragma operator]

-

-
-
-
1   A unary operator expression of the form:
+
+
1 Semantics
+   A unary operator expression of the form:
        _Pragma ( string-literal )
     is processed as follows: The string literal is destringized by deleting any encoding prefix,
     deleting the leading and trailing double-quotes, replacing each escape sequence \" by a
@@ -10438,8 +9181,7 @@ Forward references:         conditional inclusion (6.10.1), complex arithmetic
     directive. The original four preprocessing tokens in the unary operator expression are
     removed.
 

-
-
+
 
2   EXAMPLE       A directive of the form:
              #pragma listing on "..\listing.dir"
     can also be expressed as:
@@ -10450,121 +9192,82 @@ Forward references:         conditional inclusion (6.10.1), complex arithmetic
              #define PRAGMA(x) _Pragma(#x)
              LISTING ( ..\listing.dir )
 

-
-
+
 

 
6.11 [Future language directions]

-
 Future language directions
-

-
-
+
 

 
6.11.1 [Floating types]

-

-
-
+
 
1   Future standardization may include additional floating-point types, including those with
     greater range, precision, or both than long double.
 

-
-
+
 

 
6.11.2 [Linkages of identifiers]

-

-
-
+
 
1   Declaring an identifier with internal linkage at file scope without the static storage-
     class specifier is an obsolescent feature.
 

-
-
+
 

 
6.11.3 [External names]

-

-
-
+
 
1   Restriction of the significance of an external name to fewer than 255 characters
     (considering each universal character name or extended source character as a single
     character) is an obsolescent feature that is a concession to existing implementations.
 

-
-
+
 

 
6.11.4 [Character escape sequences]

-

-
-
+
 
1   Lowercase letters as escape sequences are reserved for future standardization. Other
     characters may be used in extensions.
 

-
-
+
 

 
6.11.5 [Storage-class specifiers]

-

-
-
+
 
1   The placement of a storage-class specifier other than at the beginning of the declaration
     specifiers in a declaration is an obsolescent feature.
 

-
-
+
 

 
6.11.6 [Function declarators]

-

-
-
+
 
1   The use of function declarators with empty parentheses (not prototype-format parameter
     type declarators) is an obsolescent feature.
 

-
-
+
 

 
6.11.7 [Function definitions]

-

-
-
+
 
1   The use of function definitions with separate parameter identifier and declaration lists
     (not prototype-format parameter type and identifier declarators) is an obsolescent feature.
 

-
-
+
 

 
6.11.8 [Pragma directives]

-

-
-
+
 
1   Pragmas whose first preprocessing token is STDC are reserved for future standardization.
 

-
-
+
 

 
6.11.9 [Predefined macro names]

-

-
-
+
 
1   Macro names beginning with _ _STDC_ are reserved for future standardization.
 
 

-
-
+
 

 
7. [Library]

-
 Library
-

-
-
+
 

 
7.1 [Introduction]

-
 Introduction
-

-
-
+
 

 
7.1.1 [Definitions of terms]

-

-
-
+
 
1   A string is a contiguous sequence of characters terminated by and including the first null
     character. The term multibyte string is sometimes used instead to emphasize special
     processing given to multibyte characters contained in the string or to avoid confusion
@@ -10572,40 +9275,35 @@ Forward references:         conditional inclusion (6.10.1), complex arithmetic
     character. The length of a string is the number of bytes preceding the null character and
     the value of a string is the sequence of the values of the contained characters, in order.
 

-
-
+
 
2   The decimal-point character is the character used by functions that convert floating-point
     numbers to or from character sequences to denote the beginning of the fractional part of
-    such character sequences.180) It is represented in the text and examples by a period, but
+    such character sequences.[180] It is represented in the text and examples by a period, but
     may be changed by the setlocale function.
 

-
 
 
Footnote 180) The functions that make use of the decimal-point character are the numeric conversion functions
-         (7.22.1, 7.29.4.1) and the formatted input/output functions (7.21.6, 7.29.2).
+         (7.22.1, 7.29.4.1) and the formatted input/output functions (7.21.6, 7.29.2).
 

 
-
+
 
3   A null wide character is a wide character with code value zero.
 

-
-
+
 
4   A wide string is a contiguous sequence of wide characters terminated by and including
     the first null wide character. A pointer to a wide string is a pointer to its initial (lowest
     addressed) wide character. The length of a wide string is the number of wide characters
     preceding the null wide character and the value of a wide string is the sequence of code
     values of the contained wide characters, in order.
 

-
-
+
 
5   A shift sequence is a contiguous sequence of bytes within a multibyte string that
-    (potentially) causes a change in shift state (see 5.2.1.2). A shift sequence shall not have a
+    (potentially) causes a change in shift state (see 5.2.1.2). A shift sequence shall not have a
     corresponding wide character; it is instead taken to be an adjunct to an adjacent multibyte
-    character.181)
-    Forward references: character handling (7.4), the setlocale function (7.11.1.1).
+    character.[181]
+    Forward references: character handling (7.4), the setlocale function (7.11.1.1).
 
 

-
 
 
Footnote 181) For state-dependent encodings, the values for MB_CUR_MAX and MB_LEN_MAX shall thus be large
          enough to count all the bytes in any complete multibyte character plus at least one adjacent shift
@@ -10613,26 +9311,23 @@ Forward references:         conditional inclusion (6.10.1), complex arithmetic
          implementation's choice.
 

 
-
+
 

 
7.1.2 [Standard headers]

-

-
-
-
1   Each library function is declared, with a type that includes a prototype, in a header ,182)
+
+
1   Each library function is declared, with a type that includes a prototype, in a header ,[182]
     whose contents are made available by the #include preprocessing directive. The
     header declares a set of related functions, plus any necessary types and additional macros
     needed to facilitate their use. Declarations of types described in this clause shall not
     include type qualifiers, unless explicitly stated otherwise.
 

-
 
 
Footnote 182) A header is not necessarily a source file, nor are the < and > delimited sequences in header names
          necessarily valid source file names.
 

 
-
-
2   The standard headers are183)
+
+
2   The standard headers are[183]
            <assert.h>                      <math.h>                        <stdlib.h>
            <complex.h>                     <setjmp.h>                      <stdnoreturn.h>
            <ctype.h>                       <signal.h>                      <string.h>
@@ -10644,22 +9339,20 @@ Forward references:         conditional inclusion (6.10.1), complex arithmetic
            <limits.h>                      <stdint.h>                      <wctype.h>
            <locale.h>                      <stdio.h>
 

-
 
 
Footnote 183) The headers <complex.h>, <stdatomic.h>, and <threads.h> are conditional features that
-         implementations need not support; see 6.10.8.3.
+         implementations need not support; see 6.10.8.3.
 

 
-
+
 
3   If a file with the same name as one of the above < and > delimited sequences, not
     provided as part of the implementation, is placed in any of the standard places that are
     searched for included source files, the behavior is undefined.
 

-
-
+
 
4   Standard headers may be included in any order; each may be included more than once in
     a given scope, with no effect different from being included only once, except that the
-    effect of including <assert.h> depends on the definition of NDEBUG (see 7.2). If
+    effect of including <assert.h> depends on the definition of NDEBUG (see 7.2). If
     used, a header shall be included outside of any external declaration or definition, and it
     shall first be included before the first reference to any of the functions or objects it
     declares, or to any of the types or macros it defines. However, if an identifier is declared
@@ -10668,29 +9361,23 @@ Forward references:         conditional inclusion (6.10.1), complex arithmetic
     macros with names lexically identical to keywords currently defined prior to the inclusion
     of the header or when any macro defined in the header is expanded.
 

-
-
+
 
5   Any definition of an object-like macro described in this clause shall expand to code that is
     fully protected by parentheses where necessary, so that it groups in an arbitrary
     expression as if it were a single identifier.
 
 

-
-
+
 
6   Any declaration of a library function shall have external linkage.
 

-
-
+
 
7   A summary of the contents of the standard headers is given in annex B.
-    Forward references: diagnostics (7.2).
+    Forward references: diagnostics (7.2).
 

-
-
+
 

 
7.1.3 [Reserved identifiers]

-

-
-
+
 
1   Each header declares or defines all identifiers listed in its associated subclause, and
     optionally declares or defines identifiers listed in its associated future library directions
     subclause and identifiers which are always reserved either for any use or for use as file
@@ -10701,38 +9388,33 @@ Forward references:         conditional inclusion (6.10.1), complex arithmetic
        with file scope in both the ordinary and tag name spaces.
     -- Each macro name in any of the following subclauses (including the future library
        directions) is reserved for use as specified if any of its associated headers is included;
-       unless explicitly stated otherwise (see 7.1.4).
+       unless explicitly stated otherwise (see 7.1.4).
     -- All identifiers with external linkage in any of the following subclauses (including the
        future library directions) and errno are always reserved for use as identifiers with
-       external linkage.184)
+       external linkage.[184]
     -- Each identifier with file scope listed in any of the following subclauses (including the
        future library directions) is reserved for use as a macro name and as an identifier with
        file scope in the same name space if any of its associated headers is included.
 

-
 
 
Footnote 184) The list of reserved identifiers with external linkage includes math_errhandling, setjmp,
          va_copy, and va_end.
 

 
-
+
 
2   No other identifiers are reserved. If the program declares or defines an identifier in a
-    context in which it is reserved (other than as allowed by 7.1.4), or defines a reserved
+    context in which it is reserved (other than as allowed by 7.1.4), or defines a reserved
     identifier as a macro name, the behavior is undefined.
 

-
-
+
 
3   If the program removes (with #undef) any macro definition of an identifier in the first
     group listed above, the behavior is undefined.
 
 

-
-
+
 

 
7.1.4 [Use of library functions]

-

-
-
+
 
1   Each of the following statements applies unless explicitly stated otherwise in the detailed
     descriptions that follow: If an argument to a function has an invalid value (such as a value
     outside the domain of the function, or a pointer outside the address space of the program,
@@ -10749,18 +9431,14 @@ Forward references:         conditional inclusion (6.10.1), complex arithmetic
     the name of the function in parentheses, because the name is then not followed by the left
     parenthesis that indicates expansion of a macro function name. For the same syntactic
     reason, it is permitted to take the address of a library function even if it is also defined as
-    a macro.185) The use of #undef to remove any macro definition will also ensure that an
+    a macro.[185] The use of #undef to remove any macro definition will also ensure that an
     actual function is referred to. Any invocation of a library function that is implemented as
     a macro shall expand to code that evaluates each of its arguments exactly once, fully
     protected by parentheses where necessary, so it is generally safe to use arbitrary
-    expressions as arguments.186) Likewise, those function-like macros described in the
+    expressions as arguments.[186] Likewise, those function-like macros described in the
     following subclauses may be invoked in an expression anywhere a function with a
-    compatible return type could be called.187) All object-like macros listed as expanding to
-
-    integer constant expressions shall additionally be suitable for use in #if preprocessing
-    directives.
+    compatible return type could be called.[187] All object-like macros listed as expanding to
 

-
 
 
Footnote 185) This means that an implementation shall provide an actual function for each library function, even if it
          also provides a macro for that function.
@@ -10783,38 +9461,36 @@ Forward references:         conditional inclusion (6.10.1), complex arithmetic
          whether the implementation's header provides a macro implementation of abs or a built-in
          implementation. The prototype for the function, which precedes and is hidden by any macro
          definition, is thereby revealed also.
+    integer constant expressions shall additionally be suitable for use in #if preprocessing
+    directives.
 

 
-
+
 
2   Provided that a library function can be declared without reference to any type defined in a
     header, it is also permissible to declare the function and use it without including its
     associated header.
 

-
-
+
 
3   There is a sequence point immediately before a library function returns.
 

-
-
+
 
4   The functions in the standard library are not guaranteed to be reentrant and may modify
-    objects with static or thread storage duration.188)
+    objects with static or thread storage duration.[188]
 

-
 
 
Footnote 188) Thus, a signal handler cannot, in general, call standard library functions.
 

 
-
+
 
5   Unless explicitly stated otherwise in the detailed descriptions that follow, library
     functions shall prevent data races as follows: A library function shall not directly or
     indirectly access objects accessible by threads other than the current thread unless the
     objects are accessed directly or indirectly via the function's arguments. A library
     function shall not directly or indirectly modify objects accessible by threads other than
     the current thread unless the objects are accessed directly or indirectly via the function's
-    non-const arguments.189) Implementations may share their own internal objects between
+    non-const arguments.[189] Implementations may share their own internal objects between
     threads if the objects are not visible to users and are protected against data races.
 

-
 
 
Footnote 189) This means, for example, that an implementation is not permitted to use a static object for internal
          purposes without synchronization because it could cause a data race even in programs that do not
@@ -10823,24 +9499,12 @@ Forward references:         conditional inclusion (6.10.1), complex arithmetic
          because it could cause a data race if the program shared those bytes between threads.
 

 
-
+
 
6   Unless otherwise specified, library functions shall perform all operations solely within the
-    current thread if those operations have effects that are visible to users.190)
+    current thread if those operations have effects that are visible to users.[190]
 

-
 
 
Footnote 190) This allows implementations to parallelize operations if there are no visible side effects.
-

-
-
-
7   EXAMPLE        The function atoi may be used in any of several ways:
-    -- by use of its associated header (possibly generating a macro expansion)
-                 #include <stdlib.h>
-                 const char *str;
-                 /* ... */
-                 i = atoi(str);
-    -- by use of its associated header (assuredly generating a true function reference)
-
             #include <stdlib.h>
             #undef atoi
             const char *str;
@@ -10856,14 +9520,21 @@ Forward references:         conditional inclusion (6.10.1), complex arithmetic
             const char *str;
             /* ... */
             i = atoi(str);
+

+
+
+
7   EXAMPLE        The function atoi may be used in any of several ways:
+    -- by use of its associated header (possibly generating a macro expansion)
+                 #include <stdlib.h>
+                 const char *str;
+                 /* ... */
+                 i = atoi(str);
+    -- by use of its associated header (assuredly generating a true function reference)
 

-
-
+
 

-
7.2 [Diagnostics ]

-

-
-
+
7.2 [Diagnostics <assert.h>]

+
 
1   The header <assert.h> defines the assert and static_assert macros and
     refers to another macro,
             NDEBUG
@@ -10874,147 +9545,119 @@ Forward references:         conditional inclusion (6.10.1), complex arithmetic
     The assert macro is redefined according to the current state of NDEBUG each time that
     <assert.h> is included.
 

-
-
+
 
2   The assert macro shall be implemented as a macro, not as an actual function. If the
     macro definition is suppressed in order to access an actual function, the behavior is
     undefined.
 

-
-
+
 
3   The macro
             static_assert
     expands to _Static_assert.
 

-
-
+
 

 
7.2.1 [Program diagnostics]

-
 Program diagnostics
-

-
-
+
 

 
7.2.1.1 [The assert macro]

-

-
-
-
1           #include <assert.h>
+
+
1 Synopsis
+           #include <assert.h>
             void assert(scalar expression);
     Description
 

-
-
+
 
2   The assert macro puts diagnostic tests into programs; it expands to a void expression.
     When it is executed, if expression (which shall have a scalar type) is false (that is,
     compares equal to 0), the assert macro writes information about the particular call that
     failed (including the text of the argument, the name of the source file, the source line
     number, and the name of the enclosing function -- the latter are respectively the values of
     the preprocessing macros _ _FILE_ _ and _ _LINE_ _ and of the identifier
-    _ _func_ _) on the standard error stream in an implementation-defined format.191) It
+    _ _func_ _) on the standard error stream in an implementation-defined format.[191] It
     then calls the abort function.
-    Returns
 

-
 
 
Footnote 191) The message written might be of the form:
           Assertion failed: expression, function abc, file xyz, line nnn.
+    Returns
 

 
-
+
 
3   The assert macro returns no value.
-    Forward references: the abort function (7.22.4.1).
+    Forward references: the abort function (7.22.4.1).
 

-
-
+
 

-
7.3 [Complex arithmetic ]

-
 Complex arithmetic 
-

-
-
+
7.3 [Complex arithmetic <complex.h>]

+
 

 
7.3.1 [Introduction]

-

-
-
+
 
1   The header <complex.h> defines macros and declares functions that support complex
-    arithmetic.192)
+    arithmetic.[192]
 

-
 
-
Footnote 192) See ``future library directions'' (7.31.1).
+
Footnote 192) See ``future library directions'' (7.31.1).
 

 
-
+
 
2   Implementations that define the macro _ _STDC_NO_COMPLEX_ _ need not provide
     this header nor support any of its facilities.
 

-
-
+
 
3   Each synopsis specifies a family of functions consisting of a principal function with one
     or more double complex parameters and a double complex or double return
     value; and other functions with the same name but with f and l suffixes which are
     corresponding functions with float and long double parameters and return values.
 

-
-
+
 
4   The macro
              complex
     expands to _Complex; the macro
              _Complex_I
     expands to a constant expression of type const float _Complex, with the value of
-    the imaginary unit.193)
+    the imaginary unit.[193]
 

-
 
 
Footnote 193) The imaginary unit is a number i such that i 2   = -1.
 

 
-
+
 
5   The macros
              imaginary
     and
              _Imaginary_I
-    are defined if and only if the implementation supports imaginary types;194) if defined,
+    are defined if and only if the implementation supports imaginary types;[194] if defined,
     they expand to _Imaginary and a constant expression of type const float
     _Imaginary with the value of the imaginary unit.
 

-
 
 
Footnote 194) A specification for imaginary types is in informative annex G.
+    Forward references: IEC 60559-compatible complex arithmetic (annex G).
 

 
-
+
 
6   The macro
              I
     expands to either _Imaginary_I or _Complex_I. If _Imaginary_I is not
     defined, I shall expand to _Complex_I.
 

-
-
-
7   Notwithstanding the provisions of 7.1.3, a program may undefine and perhaps then
+
+
7   Notwithstanding the provisions of 7.1.3, a program may undefine and perhaps then
     redefine the macros complex, imaginary, and I.
-
-    Forward references: IEC 60559-compatible complex arithmetic (annex G).
 

-
-
+
 

 
7.3.2 [Conventions]

-

-
-
+
 
1   Values are interpreted as radians, not degrees. An implementation may set errno but is
     not required to.
 

-
-
+
 

 
7.3.3 [Branch cuts]

-

-
-
+
 
1   Some of the functions below have branch cuts, across which the function is
     discontinuous. For implementations with a signed zero (including all IEC 60559
     implementations) that follow the specifications of annex G, the sign of zero distinguishes
@@ -11024,8 +9667,7 @@ Forward references:         conditional inclusion (6.10.1), complex arithmetic
     imaginary part +0, maps to the positive imaginary axis, and the bottom of the cut, with
     imaginary part -0, maps to the negative imaginary axis.
 

-
-
+
 
2   Implementations that do not support a signed zero (see annex F) cannot distinguish the
     sides of branch cuts. These implementations shall map a cut so the function is continuous
     as the cut is approached coming around the finite endpoint of the cut in a counter
@@ -11034,24 +9676,21 @@ Forward references:         conditional inclusion (6.10.1), complex arithmetic
     the finite endpoint of the cut along the negative real axis approaches the cut from above,
     so the cut maps to the positive imaginary axis.
 

-
-
+
 

 
7.3.4 [The CX_LIMITED_RANGE pragma]

-

-
-
-
1            #include <complex.h>
+
+
1 Synopsis
+            #include <complex.h>
              #pragma STDC CX_LIMITED_RANGE on-off-switch
     Description
 

-
-
+
 
2   The usual mathematical formulas for complex multiply, divide, and absolute value are
     problematic because of their treatment of infinities and because of undue overflow and
     underflow. The CX_LIMITED_RANGE pragma can be used to inform the
     implementation that (where the state is ``on'') the usual mathematical formulas are
-    acceptable.195) The pragma can occur either outside external declarations or preceding all
+    acceptable.[195] The pragma can occur either outside external declarations or preceding all
     explicit declarations and statements inside a compound statement. When outside external
     declarations, the pragma takes effect from its occurrence until another
     CX_LIMITED_RANGE pragma is encountered, or until the end of the translation unit.
@@ -11063,524 +9702,427 @@ Forward references:         conditional inclusion (6.10.1), complex arithmetic
     compound statement. If this pragma is used in any other context, the behavior is
     undefined. The default state for the pragma is ``off''.
 

-
 
 
Footnote 195) The purpose of the pragma is to allow the implementation to use the formulas:
-             ( x + iy ) × (u + iv ) = ( xu - yv ) + i ( yu + xv )
+             ( x + iy ) \xD7 (u + iv ) = ( xu - yv ) + i ( yu + xv )
              ( x + iy ) / (u + iv ) = [( xu + yv ) + i ( yu - xv )]/(u2 + v 2 )
              | x + iy | =  x 2 + y2
           where the programmer can determine they are safe.
+    along the real axis.
 

 
-
+
 

 
7.3.5 [Trigonometric functions]

-
 Trigonometric functions
-

-
-
+
 

 
7.3.5.1 [The cacos functions]

-

-
-
-
1            #include <complex.h>
+
+
1 Synopsis
+            #include <complex.h>
              double complex cacos(double complex z);
              float complex cacosf(float complex z);
              long double complex cacosl(long double complex z);
     Description
 

-
-
+
 
2   The cacos functions compute the complex arc cosine of z, with branch cuts outside the
     interval [-1, +1] along the real axis.
     Returns
 

-
-
+
 
3   The cacos functions return the complex arc cosine value, in the range of a strip
     mathematically unbounded along the imaginary axis and in the interval [0,  ] along the
     real axis.
 

-
-
+
 

 
7.3.5.2 [The casin functions]

-

-
-
-
1            #include <complex.h>
+
+
1 Synopsis
+            #include <complex.h>
              double complex casin(double complex z);
              float complex casinf(float complex z);
              long double complex casinl(long double complex z);
     Description
 

-
-
+
 
2   The casin functions compute the complex arc sine of z, with branch cuts outside the
     interval [-1, +1] along the real axis.
     Returns
 

-
-
+
 
3   The casin functions return the complex arc sine value, in the range of a strip
     mathematically unbounded along the imaginary axis and in the interval [- /2, + /2]
-
-    along the real axis.
 

-
-
+
 

 
7.3.5.3 [The catan functions]

-

-
-
-
1           #include <complex.h>
+
+
1 Synopsis
+           #include <complex.h>
             double complex catan(double complex z);
             float complex catanf(float complex z);
             long double complex catanl(long double complex z);
     Description
 

-
-
+
 
2   The catan functions compute the complex arc tangent of z, with branch cuts outside the
     interval [-i , +i ] along the imaginary axis.
     Returns
 

-
-
+
 
3   The catan functions return the complex arc tangent value, in the range of a strip
     mathematically unbounded along the imaginary axis and in the interval [- /2, + /2]
     along the real axis.
 

-
-
+
 

 
7.3.5.4 [The ccos functions]

-

-
-
-
1           #include <complex.h>
+
+
1 Synopsis
+           #include <complex.h>
             double complex ccos(double complex z);
             float complex ccosf(float complex z);
             long double complex ccosl(long double complex z);
     Description
 

-
-
+
 
2   The ccos functions compute the complex cosine of z.
     Returns
 

-
-
+
 
3   The ccos functions return the complex cosine value.
 

-
-
+
 

 
7.3.5.5 [The csin functions]

-

-
-
-
1           #include <complex.h>
+
+
1 Synopsis
+           #include <complex.h>
             double complex csin(double complex z);
             float complex csinf(float complex z);
             long double complex csinl(long double complex z);
     Description
 

-
-
+
 
2   The csin functions compute the complex sine of z.
 
     Returns
 

-
-
+
 
3   The csin functions return the complex sine value.
 

-
-
+
 

 
7.3.5.6 [The ctan functions]

-

-
-
-
1          #include <complex.h>
+
+
1 Synopsis
+          #include <complex.h>
            double complex ctan(double complex z);
            float complex ctanf(float complex z);
            long double complex ctanl(long double complex z);
     Description
 

-
-
+
 
2   The ctan functions compute the complex tangent of z.
     Returns
 

-
-
+
 
3   The ctan functions return the complex tangent value.
 

-
-
+
 

 
7.3.6 [Hyperbolic functions]

-
 Hyperbolic functions
-

-
-
+
 

 
7.3.6.1 [The cacosh functions]

-

-
-
-
1          #include <complex.h>
+
+
1 Synopsis
+          #include <complex.h>
            double complex cacosh(double complex z);
            float complex cacoshf(float complex z);
            long double complex cacoshl(long double complex z);
     Description
 

-
-
+
 
2   The cacosh functions compute the complex arc hyperbolic cosine of z, with a branch
     cut at values less than 1 along the real axis.
     Returns
 

-
-
+
 
3   The cacosh functions return the complex arc hyperbolic cosine value, in the range of a
     half-strip of nonnegative values along the real axis and in the interval [-i , +i ] along the
     imaginary axis.
 

-
-
+
 

 
7.3.6.2 [The casinh functions]

-

-
-
-
1          #include <complex.h>
+
+
1 Synopsis
+          #include <complex.h>
            double complex casinh(double complex z);
            float complex casinhf(float complex z);
            long double complex casinhl(long double complex z);
 
     Description
 

-
-
+
 
2   The casinh functions compute the complex arc hyperbolic sine of z, with branch cuts
     outside the interval [-i , +i ] along the imaginary axis.
     Returns
 

-
-
+
 
3   The casinh functions return the complex arc hyperbolic sine value, in the range of a
     strip mathematically unbounded along the real axis and in the interval [-i /2, +i /2]
     along the imaginary axis.
 

-
-
+
 

 
7.3.6.3 [The catanh functions]

-

-
-
-
1           #include <complex.h>
+
+
1 Synopsis
+           #include <complex.h>
             double complex catanh(double complex z);
             float complex catanhf(float complex z);
             long double complex catanhl(long double complex z);
     Description
 

-
-
+
 
2   The catanh functions compute the complex arc hyperbolic tangent of z, with branch
     cuts outside the interval [-1, +1] along the real axis.
     Returns
 

-
-
+
 
3   The catanh functions return the complex arc hyperbolic tangent value, in the range of a
     strip mathematically unbounded along the real axis and in the interval [-i /2, +i /2]
     along the imaginary axis.
 

-
-
+
 

 
7.3.6.4 [The ccosh functions]

-

-
-
-
1           #include <complex.h>
+
+
1 Synopsis
+           #include <complex.h>
             double complex ccosh(double complex z);
             float complex ccoshf(float complex z);
             long double complex ccoshl(long double complex z);
     Description
 

-
-
+
 
2   The ccosh functions compute the complex hyperbolic cosine of z.
     Returns
 

-
-
+
 
3   The ccosh functions return the complex hyperbolic cosine value.
 

-
-
+
 

 
7.3.6.5 [The csinh functions]

-

-
-
-
1          #include <complex.h>
+
+
1 Synopsis
+          #include <complex.h>
            double complex csinh(double complex z);
            float complex csinhf(float complex z);
            long double complex csinhl(long double complex z);
     Description
 

-
-
+
 
2   The csinh functions compute the complex hyperbolic sine of z.
     Returns
 

-
-
+
 
3   The csinh functions return the complex hyperbolic sine value.
 

-
-
+
 

 
7.3.6.6 [The ctanh functions]

-

-
-
-
1          #include <complex.h>
+
+
1 Synopsis
+          #include <complex.h>
            double complex ctanh(double complex z);
            float complex ctanhf(float complex z);
            long double complex ctanhl(long double complex z);
     Description
 

-
-
+
 
2   The ctanh functions compute the complex hyperbolic tangent of z.
     Returns
 

-
-
+
 
3   The ctanh functions return the complex hyperbolic tangent value.
 

-
-
+
 

 
7.3.7 [Exponential and logarithmic functions]

-
 Exponential and logarithmic functions
-

-
-
+
 

 
7.3.7.1 [The cexp functions]

-

-
-
-
1          #include <complex.h>
+
+
1 Synopsis
+          #include <complex.h>
            double complex cexp(double complex z);
            float complex cexpf(float complex z);
            long double complex cexpl(long double complex z);
     Description
 

-
-
+
 
2   The cexp functions compute the complex base-e exponential of z.
     Returns
 

-
-
+
 
3   The cexp functions return the complex base-e exponential value.
 
 

-
-
+
 

 
7.3.7.2 [The clog functions]

-

-
-
-
1           #include <complex.h>
+
+
1 Synopsis
+           #include <complex.h>
             double complex clog(double complex z);
             float complex clogf(float complex z);
             long double complex clogl(long double complex z);
     Description
 

-
-
+
 
2   The clog functions compute the complex natural (base-e) logarithm of z, with a branch
     cut along the negative real axis.
     Returns
 

-
-
+
 
3   The clog functions return the complex natural logarithm value, in the range of a strip
     mathematically unbounded along the real axis and in the interval [-i , +i ] along the
     imaginary axis.
 

-
-
+
 

 
7.3.8 [Power and absolute-value functions]

-
 Power and absolute-value functions
-

-
-
+
 

 
7.3.8.1 [The cabs functions]

-

-
-
-
1           #include <complex.h>
+
+
1 Synopsis
+           #include <complex.h>
             double cabs(double complex z);
             float cabsf(float complex z);
             long double cabsl(long double complex z);
     Description
 

-
-
+
 
2   The cabs functions compute the complex absolute value (also called norm, modulus, or
     magnitude) of z.
     Returns
 

-
-
+
 
3   The cabs functions return the complex absolute value.
 

-
-
+
 

 
7.3.8.2 [The cpow functions]

-

-
-
-
1           #include <complex.h>
+
+
1 Synopsis
+           #include <complex.h>
             double complex cpow(double complex x, double complex y);
             float complex cpowf(float complex x, float complex y);
             long double complex cpowl(long double complex x,
                  long double complex y);
     Description
 

-
-
+
 
2   The cpow functions compute the complex power function xy , with a branch cut for the
     first parameter along the negative real axis.
     Returns
 

-
-
+
 
3   The cpow functions return the complex power function value.
 

-
-
+
 

 
7.3.8.3 [The csqrt functions]

-

-
-
-
1          #include <complex.h>
+
+
1 Synopsis
+          #include <complex.h>
            double complex csqrt(double complex z);
            float complex csqrtf(float complex z);
            long double complex csqrtl(long double complex z);
     Description
 

-
-
+
 
2   The csqrt functions compute the complex square root of z, with a branch cut along the
     negative real axis.
     Returns
 

-
-
+
 
3   The csqrt functions return the complex square root value, in the range of the right half-
     plane (including the imaginary axis).
 

-
-
+
 

 
7.3.9 [Manipulation functions]

-
 Manipulation functions
-

-
-
+
 

 
7.3.9.1 [The carg functions]

-

-
-
-
1          #include <complex.h>
+
+
1 Synopsis
+          #include <complex.h>
            double carg(double complex z);
            float cargf(float complex z);
            long double cargl(long double complex z);
     Description
 

-
-
+
 
2   The carg functions compute the argument (also called phase angle) of z, with a branch
     cut along the negative real axis.
     Returns
 

-
-
+
 
3   The carg functions return the value of the argument in the interval [- , + ].
 

-
-
+
 

 
7.3.9.2 [The cimag functions]

-

-
-
-
1           #include <complex.h>
+
+
1 Synopsis
+           #include <complex.h>
             double cimag(double complex z);
             float cimagf(float complex z);
             long double cimagl(long double complex z);
     Description
 

-
-
-
2   The cimag functions compute the imaginary part of z.196)
+
+
2   The cimag functions compute the imaginary part of z.[196]
     Returns
 

-
 
 
Footnote 196) For a variable z of complex type, z == creal(z) + cimag(z)*I.
 

 
-
+
 
3   The cimag functions return the imaginary part value (as a real).
 

-
-
+
 

 
7.3.9.3 [The CMPLX macros]

-

-
-
-
1           #include <complex.h>
+
+
1 Synopsis
+           #include <complex.h>
             double complex CMPLX(double x, double y);
             float complex CMPLXF(float x, float y);
             long double complex CMPLXL(long double x, long double y);
     Description
 

-
-
+
 
2   The CMPLX macros expand to an expression of the specified complex type, with the real
     part having the (converted) value of x and the imaginary part having the (converted)
     value of y. The resulting expression shall be suitable for use as an initializer for an object
     with static or thread storage duration, provided both arguments are likewise suitable.
     Returns
 

-
-
+
 
3   The CMPLX macros return the complex value x + i y.
 

-
-
+
 
4   NOTE    These macros act as if the implementation supported imaginary types and the definitions were:
          #define CMPLX(x, y)  ((double complex)((double)(x) + \
                                        _Imaginary_I * (double)(y)))
@@ -11590,44 +10132,37 @@ Forward references:         conditional inclusion (6.10.1), complex arithmetic
                                        _Imaginary_I * (long double)(y)))
 
 

-
-
+
 

 
7.3.9.4 [The conj functions]

-

-
-
-
1          #include <complex.h>
+
+
1 Synopsis
+          #include <complex.h>
            double complex conj(double complex z);
            float complex conjf(float complex z);
            long double complex conjl(long double complex z);
     Description
 

-
-
+
 
2   The conj functions compute the complex conjugate of z, by reversing the sign of its
     imaginary part.
     Returns
 

-
-
+
 
3   The conj functions return the complex conjugate value.
 

-
-
+
 

 
7.3.9.5 [The cproj functions]

-

-
-
-
1          #include <complex.h>
+
+
1 Synopsis
+          #include <complex.h>
            double complex cproj(double complex z);
            float complex cprojf(float complex z);
            long double complex cprojl(long double complex z);
     Description
 

-
-
+
 
2   The cproj functions compute a projection of z onto the Riemann sphere: z projects to
     z except that all complex infinities (even those with one infinite part and one NaN part)
     project to positive infinity on the real axis. If z has an infinite part, then cproj(z) is
@@ -11635,250 +10170,199 @@ Forward references:         conditional inclusion (6.10.1), complex arithmetic
            INFINITY + I * copysign(0.0, cimag(z))
     Returns
 

-
-
+
 
3   The cproj functions return the value of the projection onto the Riemann sphere.
 

-
-
+
 

 
7.3.9.6 [The creal functions]

-

-
-
-
1          #include <complex.h>
+
+
1 Synopsis
+          #include <complex.h>
            double creal(double complex z);
            float crealf(float complex z);
            long double creall(long double complex z);
     Description
 

-
-
-
2   The creal functions compute the real part of z.197)
+
+
2   The creal functions compute the real part of z.[197]
     Returns
 

-
 
 
Footnote 197) For a variable z of complex type, z == creal(z) + cimag(z)*I.
 

 
-
+
 
3   The creal functions return the real part value.
 
 

-
-
+
 

-
7.4 [Character handling ]

-

-
-
+
7.4 [Character handling <ctype.h>]

+
 
1   The header <ctype.h> declares several functions useful for classifying and mapping
-    characters.198) In all cases the argument is an int, the value of which shall be
+    characters.[198] In all cases the argument is an int, the value of which shall be
     representable as an unsigned char or shall equal the value of the macro EOF. If the
     argument has any other value, the behavior is undefined.
 

-
 
-
Footnote 198) See ``future library directions'' (7.31.2).
+
Footnote 198) See ``future library directions'' (7.31.2).
 

 
-
+
 
2   The behavior of these functions is affected by the current locale. Those functions that
     have locale-specific aspects only when not in the "C" locale are noted below.
 

-
-
+
 
3   The term printing character refers to a member of a locale-specific set of characters, each
     of which occupies one printing position on a display device; the term control character
     refers to a member of a locale-specific set of characters that are not printing
-    characters.199) All letters and digits are printing characters.
-    Forward references: EOF (7.21.1), localization (7.11).
+    characters.[199] All letters and digits are printing characters.
+    Forward references: EOF (7.21.1), localization (7.11).
 

-
 
 
Footnote 199) In an implementation that uses the seven-bit US ASCII character set, the printing characters are those
          whose values lie from 0x20 (space) through 0x7E (tilde); the control characters are those whose
          values lie from 0 (NUL) through 0x1F (US), and the character 0x7F (DEL).
+    none of iscntrl, isdigit, ispunct, or isspace is true.200) In the "C" locale,
+    isalpha returns true only for the characters for which isupper or islower is true.
 

 
-
+
 

 
7.4.1 [Character classification functions]

-

-
-
+
 
1   The functions in this subclause return nonzero (true) if and only if the value of the
     argument c conforms to that in the description of the function.
 

-
-
+
 

 
7.4.1.1 [The isalnum function]

-

-
-
-
1            #include <ctype.h>
+
+
1 Synopsis
+            #include <ctype.h>
              int isalnum(int c);
     Description
 

-
-
+
 
2   The isalnum function tests for any character for which isalpha or isdigit is true.
 

-
-
+
 

 
7.4.1.2 [The isalpha function]

-

-
-
-
1            #include <ctype.h>
+
+
1 Synopsis
+            #include <ctype.h>
              int isalpha(int c);
     Description
 

-
-
+
 
2   The isalpha function tests for any character for which isupper or islower is true,
     or any character that is one of a locale-specific set of alphabetic characters for which
-
-    none of iscntrl, isdigit, ispunct, or isspace is true.200) In the "C" locale,
-    isalpha returns true only for the characters for which isupper or islower is true.
 

-
-
-
Footnote 200) The functions islower and isupper test true or false separately for each of these additional
-         characters; all four combinations are possible.
-

-
-
+
 

 
7.4.1.3 [The isblank function]

-

-
-
-
1           #include <ctype.h>
+
+
1 Synopsis
+           #include <ctype.h>
             int isblank(int c);
     Description
 

-
-
+
 
2   The isblank function tests for any character that is a standard blank character or is one
     of a locale-specific set of characters for which isspace is true and that is used to
     separate words within a line of text. The standard blank characters are the following:
     space (' '), and horizontal tab ('\t'). In the "C" locale, isblank returns true only
     for the standard blank characters.
 

-
-
+
 

 
7.4.1.4 [The iscntrl function]

-

-
-
-
1           #include <ctype.h>
+
+
1 Synopsis
+           #include <ctype.h>
             int iscntrl(int c);
     Description
 

-
-
+
 
2   The iscntrl function tests for any control character.
 

-
-
+
 

 
7.4.1.5 [The isdigit function]

-

-
-
-
1           #include <ctype.h>
+
+
1 Synopsis
+           #include <ctype.h>
             int isdigit(int c);
     Description
 

-
-
-
2   The isdigit function tests for any decimal-digit character (as defined in 5.2.1).
+
+
2   The isdigit function tests for any decimal-digit character (as defined in 5.2.1).
 

-
-
+
 

 
7.4.1.6 [The isgraph function]

-

-
-
-
1           #include <ctype.h>
+
+
1 Synopsis
+           #include <ctype.h>
             int isgraph(int c);
-
-    Description
 

-
-
+
 
2   The isgraph function tests for any printing character except space (' ').
 

-
-
+
 

 
7.4.1.7 [The islower function]

-

-
-
-
1          #include <ctype.h>
+
+
1 Synopsis
+          #include <ctype.h>
            int islower(int c);
     Description
 

-
-
+
 
2   The islower function tests for any character that is a lowercase letter or is one of a
     locale-specific set of characters for which none of iscntrl, isdigit, ispunct, or
     isspace is true. In the "C" locale, islower returns true only for the lowercase
-    letters (as defined in 5.2.1).
+    letters (as defined in 5.2.1).
 

-
-
+
 

 
7.4.1.8 [The isprint function]

-

-
-
-
1          #include <ctype.h>
+
+
1 Synopsis
+          #include <ctype.h>
            int isprint(int c);
     Description
 

-
-
+
 
2   The isprint function tests for any printing character including space (' ').
 

-
-
+
 

 
7.4.1.9 [The ispunct function]

-

-
-
-
1          #include <ctype.h>
+
+
1 Synopsis
+          #include <ctype.h>
            int ispunct(int c);
     Description
 

-
-
+
 
2   The ispunct function tests for any printing character that is one of a locale-specific set
     of punctuation characters for which neither isspace nor isalnum is true. In the "C"
     locale, ispunct returns true for every printing character for which neither isspace
     nor isalnum is true.
 

-
-
+
 

 
7.4.1.10 [The isspace function]

-

-
-
-
1          #include <ctype.h>
+
+
1 Synopsis
+          #include <ctype.h>
            int isspace(int c);
     Description
 

-
-
+
 
2   The isspace function tests for any character that is a standard white-space character or
     is one of a locale-specific set of characters for which isalnum is false. The standard
 
@@ -11886,103 +10370,82 @@ Forward references:         conditional inclusion (6.10.1), complex arithmetic
     ('\n'), carriage return ('\r'), horizontal tab ('\t'), and vertical tab ('\v'). In the
     "C" locale, isspace returns true only for the standard white-space characters.
 

-
-
+
 

 
7.4.1.11 [The isupper function]

-

-
-
-
1           #include <ctype.h>
+
+
1 Synopsis
+           #include <ctype.h>
             int isupper(int c);
     Description
 

-
-
+
 
2   The isupper function tests for any character that is an uppercase letter or is one of a
     locale-specific set of characters for which none of iscntrl, isdigit, ispunct, or
     isspace is true. In the "C" locale, isupper returns true only for the uppercase
-    letters (as defined in 5.2.1).
+    letters (as defined in 5.2.1).
 

-
-
+
 

 
7.4.1.12 [The isxdigit function]

-

-
-
-
1           #include <ctype.h>
+
+
1 Synopsis
+           #include <ctype.h>
             int isxdigit(int c);
     Description
 

-
-
-
2   The isxdigit function tests for any hexadecimal-digit character (as defined in 6.4.4.1).
+
+
2   The isxdigit function tests for any hexadecimal-digit character (as defined in 6.4.4.1).
 

-
-
+
 

 
7.4.2 [Character case mapping functions]

-
 Character case mapping functions
-

-
-
+
 

 
7.4.2.1 [The tolower function]

-

-
-
-
1           #include <ctype.h>
+
+
1 Synopsis
+           #include <ctype.h>
             int tolower(int c);
     Description
 

-
-
+
 
2   The tolower function converts an uppercase letter to a corresponding lowercase letter.
     Returns
 

-
-
+
 
3   If the argument is a character for which isupper is true and there are one or more
     corresponding characters, as specified by the current locale, for which islower is true,
     the tolower function returns one of the corresponding characters (always the same one
     for any given locale); otherwise, the argument is returned unchanged.
 

-
-
+
 

 
7.4.2.2 [The toupper function]

-

-
-
-
1          #include <ctype.h>
+
+
1 Synopsis
+          #include <ctype.h>
            int toupper(int c);
     Description
 

-
-
+
 
2   The toupper function converts a lowercase letter to a corresponding uppercase letter.
     Returns
 

-
-
+
 
3   If the argument is a character for which islower is true and there are one or more
     corresponding characters, as specified by the current locale, for which isupper is true,
     the toupper function returns one of the corresponding characters (always the same one
     for any given locale); otherwise, the argument is returned unchanged.
 

-
-
+
 

-
7.5 [Errors ]

-

-
-
+
7.5 [Errors <errno.h>]

+
 
1   The header <errno.h> defines several macros, all relating to the reporting of error
     conditions.
 

-
-
+
 
2   The macros are
              EDOM
              EILSEQ
@@ -11990,25 +10453,23 @@ Forward references:         conditional inclusion (6.10.1), complex arithmetic
     which expand to integer constant expressions with type int, distinct positive values, and
     which are suitable for use in #if preprocessing directives; and
              errno
-    which expands to a modifiable lvalue201) that has type int and thread local storage
+    which expands to a modifiable lvalue[201] that has type int and thread local storage
     duration, the value of which is set to a positive error number by several library functions.
     If a macro definition is suppressed in order to access an actual object, or a program
     defines an identifier with the name errno, the behavior is undefined.
 

-
 
 
Footnote 201) The macro errno need not be the identifier of an object. It might expand to a modifiable lvalue
          resulting from a function call (for example, *errno()).
 

 
-
+
 
3   The value of errno in the initial thread is zero at program startup (the initial value of
     errno in other threads is an indeterminate value), but is never set to zero by any library
-    function.202) The value of errno may be set to nonzero by a library function call
+    function.[202] The value of errno may be set to nonzero by a library function call
     whether or not there is an error, provided the use of errno is not documented in the
     description of the function in this International Standard.
 

-
 
 
Footnote 202) Thus, a program that uses errno for error checking should set it to zero before a library function call,
          then inspect it before a subsequent library function call. Of course, a library function can save the
@@ -12016,32 +10477,28 @@ Forward references:         conditional inclusion (6.10.1), complex arithmetic
          value is still zero just before the return.
 

 
-
+
 
4   Additional macro definitions, beginning with E and a digit or E and an uppercase
-    letter,203) may also be specified by the implementation.
+    letter,[203] may also be specified by the implementation.
 
 

-
 
-
Footnote 203) See ``future library directions'' (7.31.3).
+
Footnote 203) See ``future library directions'' (7.31.3).
 

 
-
+
 

-
7.6 [Floating-point environment ]

-

-
-
+
7.6 [Floating-point environment <fenv.h>]

+
 
1   The header <fenv.h> defines several macros, and declares types and functions that
     provide access to the floating-point environment. The floating-point environment refers
     collectively to any floating-point status flags and control modes supported by the
-    implementation.204) A floating-point status flag is a system variable whose value is set
+    implementation.[204] A floating-point status flag is a system variable whose value is set
     (but never cleared) when a floating-point exception is raised, which occurs as a side effect
-    of exceptional floating-point arithmetic to provide auxiliary information.205) A floating-
+    of exceptional floating-point arithmetic to provide auxiliary information.[205] A floating-
     point control mode is a system variable whose value may be set by the user to affect the
     subsequent behavior of floating-point arithmetic.
 

-
 
 
Footnote 204) This header is designed to support the floating-point exception status flags and directed-rounding
          control modes required by IEC 60559, and other similar floating-point state information. It is also
@@ -12052,15 +10509,14 @@ Forward references:         conditional inclusion (6.10.1), complex arithmetic
 
Footnote 205) A floating-point status flag is not an object and can be set more than once within an expression.
 

 
-
+
 
2   The floating-point environment has thread storage duration. The initial state for a
     thread's floating-point environment is the current state of the floating-point environment
     of the thread that creates it at the time of creation.
 

-
-
+
 
3   Certain programming conventions support the intended model of use for the floating-
-    point environment:206)
+    point environment:[206]
     -- a function call does not alter its caller's floating-point control modes, clear its caller's
        floating-point status flags, nor depend on the state of its caller's floating-point status
        flags unless the function is so documented;
@@ -12069,28 +10525,25 @@ Forward references:         conditional inclusion (6.10.1), complex arithmetic
     -- a function call is assumed to have the potential for raising floating-point exceptions,
        unless its documentation promises otherwise.
 

-
 
 
Footnote 206) With these conventions, a programmer can safely assume default floating-point control modes (or be
          unaware of them). The responsibilities associated with accessing the floating-point environment fall
          on the programmer or program that does so explicitly.
 

 
-
+
 
4   The type
              fenv_t
     represents the entire floating-point environment.
 

-
-
+
 
5   The type
              fexcept_t
     represents the floating-point status flags collectively, including any status the
     implementation associates with the flags.
 
 

-
-
+
 
6   Each of the macros
              FE_DIVBYZERO
              FE_INEXACT
@@ -12098,36 +10551,34 @@ Forward references:         conditional inclusion (6.10.1), complex arithmetic
              FE_OVERFLOW
              FE_UNDERFLOW
     is defined if and only if the implementation supports the floating-point exception by
-    means of the functions in 7.6.2.207) Additional implementation-defined floating-point
-    exceptions, with macro definitions beginning with FE_ and an uppercase letter,208) may
+    means of the functions in 7.6.2.[207] Additional implementation-defined floating-point
+    exceptions, with macro definitions beginning with FE_ and an uppercase letter,[208] may
     also be specified by the implementation. The defined macros expand to integer constant
     expressions with values such that bitwise ORs of all combinations of the macros result in
     distinct values, and furthermore, bitwise ANDs of all combinations of the macros result in
-    zero.209)
+    zero.[209]
 

-
 
 
Footnote 207) The implementation supports a floating-point exception if there are circumstances where a call to at
-         least one of the functions in 7.6.2, using the macro as the appropriate argument, will succeed. It is not
+         least one of the functions in 7.6.2, using the macro as the appropriate argument, will succeed. It is not
          necessary for all the functions to succeed all the time.
 

 
 
-
Footnote 208) See ``future library directions'' (7.31.4).
+
Footnote 208) See ``future library directions'' (7.31.4).
 

 
 
 
Footnote 209) The macros should be distinct powers of two.
 

 
-
+
 
7   The macro
              FE_ALL_EXCEPT
     is simply the bitwise OR of all floating-point exception macros defined by the
     implementation. If no such macros are defined, FE_ALL_EXCEPT shall be defined as 0.
 

-
-
+
 
8   Each of the macros
              FE_DOWNWARD
              FE_TONEAREST
@@ -12136,14 +10587,13 @@ Forward references:         conditional inclusion (6.10.1), complex arithmetic
     is defined if and only if the implementation supports getting and setting the represented
     rounding direction by means of the fegetround and fesetround functions.
     Additional implementation-defined rounding directions, with macro definitions beginning
-    with FE_ and an uppercase letter,210) may also be specified by the implementation. The
+    with FE_ and an uppercase letter,[210] may also be specified by the implementation. The
     defined macros expand to integer constant expressions whose values are distinct
-    nonnegative values.211)
+    nonnegative values.[211]
 
 

-
 
-
Footnote 210) See ``future library directions'' (7.31.4).
+
Footnote 210) See ``future library directions'' (7.31.4).
 

 
 
@@ -12151,39 +10601,35 @@ Forward references:         conditional inclusion (6.10.1), complex arithmetic
          FLT_ROUNDS, they are not required to do so.
 

 
-
+
 
9    The macro
               FE_DFL_ENV
      represents the default floating-point environment -- the one installed at program startup
      -- and has type ``pointer to const-qualified fenv_t''. It can be used as an argument to
      <fenv.h> functions that manage the floating-point environment.
 

-
-
+
 
10   Additional implementation-defined environments, with macro definitions beginning with
-     FE_ and an uppercase letter,212) and having type ``pointer to const-qualified fenv_t'',
+     FE_ and an uppercase letter,[212] and having type ``pointer to const-qualified fenv_t'',
      may also be specified by the implementation.
 

-
 
-
Footnote 212) See ``future library directions'' (7.31.4).
+
Footnote 212) See ``future library directions'' (7.31.4).
 

 
-
+
 

 
7.6.1 [The FENV_ACCESS pragma]

-

-
-
-
1             #include <fenv.h>
+
+
1 Synopsis
+             #include <fenv.h>
               #pragma STDC FENV_ACCESS on-off-switch
      Description
 

-
-
+
 
2    The FENV_ACCESS pragma provides a means to inform the implementation when a
      program might access the floating-point environment to test floating-point status flags or
-     run under non-default floating-point control modes.213) The pragma shall occur either
+     run under non-default floating-point control modes.[213] The pragma shall occur either
      outside external declarations or preceding all explicit declarations and statements inside a
      compound statement. When outside external declarations, the pragma takes effect from
      its occurrence until another FENV_ACCESS pragma is encountered, or until the end of
@@ -12201,7 +10647,6 @@ Forward references:         conditional inclusion (6.10.1), complex arithmetic
      floating-point control modes have their default settings.)
 
 

-
 
 
Footnote 213) The purpose of the FENV_ACCESS pragma is to allow certain optimizations that could subvert flag
           tests and mode changes (e.g., global common subexpression elimination, code motion, and constant
@@ -12209,7 +10654,7 @@ Forward references:         conditional inclusion (6.10.1), complex arithmetic
           modes are in effect and the flags are not tested.
 

 
-
+
 
3   EXAMPLE
             #include <fenv.h>
             void f(double x)
@@ -12223,33 +10668,28 @@ Forward references:         conditional inclusion (6.10.1), complex arithmetic
                   /* ... */
             }
 

-
-
+
 
4   If the function g might depend on status flags set as a side effect of the first x + 1, or if the second
     x + 1 might depend on control modes set as a side effect of the call to function g, then the program shall
-    contain an appropriately placed invocation of #pragma STDC FENV_ACCESS ON.214)
+    contain an appropriately placed invocation of #pragma STDC FENV_ACCESS ON.[214]
 
 

-
 
 
Footnote 214) The side effects impose a temporal ordering that requires two evaluations of x + 1. On the other
          hand, without the #pragma STDC FENV_ACCESS ON pragma, and assuming the default state is
          ``off'', just one evaluation of x + 1 would suffice.
 

 
-
+
 

 
7.6.2 [Floating-point exceptions]

-

-
-
-
1   The following functions provide access to the floating-point status flags.215) The int
+
+
1   The following functions provide access to the floating-point status flags.[215] The int
     input argument for the functions represents a subset of floating-point exceptions, and can
     be zero or the bitwise OR of one or more floating-point exception macros, for example
     FE_OVERFLOW | FE_INEXACT. For other argument values the behavior of these
     functions is undefined.
 

-
 
 
Footnote 215) The functions fetestexcept, feraiseexcept, and feclearexcept support the basic
          abstraction of flags that are either set or clear. An implementation may endow floating-point status
@@ -12258,98 +10698,84 @@ Forward references:         conditional inclusion (6.10.1), complex arithmetic
          content of flags.
 

 
-
+
 

 
7.6.2.1 [The feclearexcept function]

-

-
-
-
1           #include <fenv.h>
+
+
1 Synopsis
+           #include <fenv.h>
             int feclearexcept(int excepts);
     Description
 

-
-
+
 
2   The feclearexcept function attempts to clear the supported floating-point exceptions
     represented by its argument.
     Returns
 

-
-
+
 
3   The feclearexcept function returns zero if the excepts argument is zero or if all
     the specified exceptions were successfully cleared. Otherwise, it returns a nonzero value.
 
 

-
-
+
 

 
7.6.2.2 [The fegetexceptflag function]

-

-
-
-
1            #include <fenv.h>
+
+
1 Synopsis
+            #include <fenv.h>
              int fegetexceptflag(fexcept_t *flagp,
                   int excepts);
     Description
 

-
-
+
 
2   The fegetexceptflag function attempts to store an implementation-defined
     representation of the states of the floating-point status flags indicated by the argument
     excepts in the object pointed to by the argument flagp.
     Returns
 

-
-
+
 
3   The fegetexceptflag function returns zero if the representation was successfully
     stored. Otherwise, it returns a nonzero value.
 

-
-
+
 

 
7.6.2.3 [The feraiseexcept function]

-

-
-
-
1            #include <fenv.h>
+
+
1 Synopsis
+            #include <fenv.h>
              int feraiseexcept(int excepts);
     Description
 

-
-
+
 
2   The feraiseexcept function attempts to raise the supported floating-point exceptions
-    represented by its argument.216) The order in which these floating-point exceptions are
-    raised is unspecified, except as stated in F.8.6. Whether the feraiseexcept function
+    represented by its argument.[216] The order in which these floating-point exceptions are
+    raised is unspecified, except as stated in F.8.6. Whether the feraiseexcept function
     additionally raises the ``inexact'' floating-point exception whenever it raises the
     ``overflow'' or ``underflow'' floating-point exception is implementation-defined.
     Returns
 

-
 
 
Footnote 216) The effect is intended to be similar to that of floating-point exceptions raised by arithmetic operations.
          Hence, enabled traps for floating-point exceptions raised by this function are taken. The specification
-         in F.8.6 is in the same spirit.
+         in F.8.6 is in the same spirit.
 

 
-
+
 
3   The feraiseexcept function returns zero if the excepts argument is zero or if all
     the specified exceptions were successfully raised. Otherwise, it returns a nonzero value.
 
 

-
-
+
 

 
7.6.2.4 [The fesetexceptflag function]

-

-
-
-
1            #include <fenv.h>
+
+
1 Synopsis
+            #include <fenv.h>
              int fesetexceptflag(const fexcept_t *flagp,
                   int excepts);
     Description
 

-
-
+
 
2   The fesetexceptflag function attempts to set the floating-point status flags
     indicated by the argument excepts to the states stored in the object pointed to by
     flagp. The value of *flagp shall have been set by a previous call to
@@ -12358,44 +10784,28 @@ Forward references:         conditional inclusion (6.10.1), complex arithmetic
     point exceptions, but only sets the state of the flags.
     Returns
 

-
-
+
 
3   The fesetexceptflag function returns zero if the excepts argument is zero or if
     all the specified flags were successfully set to the appropriate state. Otherwise, it returns
     a nonzero value.
 

-
-
+
 

 
7.6.2.5 [The fetestexcept function]

-

-
-
-
1            #include <fenv.h>
+
+
1 Synopsis
+            #include <fenv.h>
              int fetestexcept(int excepts);
     Description
 

-
-
+
 
2   The fetestexcept function determines which of a specified subset of the floating-
     point exception flags are currently set. The excepts argument specifies the floating-
-    point status flags to be queried.217)
+    point status flags to be queried.[217]
     Returns
 

-
 
 
Footnote 217) This mechanism allows testing several floating-point exceptions with just one function call.
-

-
-
-
3   The fetestexcept function returns the value of the bitwise OR of the floating-point
-    exception macros corresponding to the currently set floating-point exceptions included in
-    excepts.
-

-
-
-
4   EXAMPLE       Call f if ``invalid'' is set, then g if ``overflow'' is set:
-
            #include <fenv.h>
            /* ... */
            {
@@ -12408,65 +10818,62 @@ Forward references:         conditional inclusion (6.10.1), complex arithmetic
                    if (set_excepts & FE_OVERFLOW) g();
                    /* ... */
            }
+

+
+
+
3   The fetestexcept function returns the value of the bitwise OR of the floating-point
+    exception macros corresponding to the currently set floating-point exceptions included in
+    excepts.
+

+
+
4   EXAMPLE       Call f if ``invalid'' is set, then g if ``overflow'' is set:
 
 

-
-
+
 

 
7.6.3 [Rounding]

-

-
-
+
 
1   The fegetround and fesetround functions provide control of rounding direction
     modes.
 

-
-
+
 

 
7.6.3.1 [The fegetround function]

-

-
-
-
1          #include <fenv.h>
+
+
1 Synopsis
+          #include <fenv.h>
            int fegetround(void);
     Description
 

-
-
+
 
2   The fegetround function gets the current rounding direction.
     Returns
 

-
-
+
 
3   The fegetround function returns the value of the rounding direction macro
     representing the current rounding direction or a negative value if there is no such
     rounding direction macro or the current rounding direction is not determinable.
 

-
-
+
 

 
7.6.3.2 [The fesetround function]

-

-
-
-
1          #include <fenv.h>
+
+
1 Synopsis
+          #include <fenv.h>
            int fesetround(int round);
     Description
 

-
-
+
 
2   The fesetround function establishes the rounding direction represented by its
     argument round. If the argument is not equal to the value of a rounding direction macro,
     the rounding direction is not changed.
     Returns
 

-
-
+
 
3   The fesetround function returns zero if and only if the requested rounding direction
     was established.
 

-
-
+
 
4   EXAMPLE Save, set, and restore the rounding direction. Report an error and abort if setting the
     rounding direction fails.
             #include <fenv.h>
@@ -12485,59 +10892,48 @@ Forward references:         conditional inclusion (6.10.1), complex arithmetic
             }
 
 

-
-
+
 

 
7.6.4 [Environment]

-

-
-
+
 
1   The functions in this section manage the floating-point environment -- status flags and
     control modes -- as one entity.
 

-
-
+
 

 
7.6.4.1 [The fegetenv function]

-

-
-
-
1           #include <fenv.h>
+
+
1 Synopsis
+           #include <fenv.h>
             int fegetenv(fenv_t *envp);
     Description
 

-
-
+
 
2   The fegetenv function attempts to store the current floating-point environment in the
     object pointed to by envp.
     Returns
 

-
-
+
 
3   The fegetenv function returns zero if the environment was successfully stored.
     Otherwise, it returns a nonzero value.
 

-
-
+
 

 
7.6.4.2 [The feholdexcept function]

-

-
-
-
1           #include <fenv.h>
+
+
1 Synopsis
+           #include <fenv.h>
             int feholdexcept(fenv_t *envp);
     Description
 

-
-
+
 
2   The feholdexcept function saves the current floating-point environment in the object
     pointed to by envp, clears the floating-point status flags, and then installs a non-stop
     (continue on floating-point exceptions) mode, if available, for all floating-point
-    exceptions.218)
+    exceptions.[218]
 
     Returns
 

-
 
 
Footnote 218) IEC 60559 systems have a default non-stop mode, and typically at least one other mode for trap
          handling or aborting; if the system provides only the non-stop mode then installing it is trivial. For
@@ -12545,23 +10941,20 @@ Forward references:         conditional inclusion (6.10.1), complex arithmetic
          function to write routines that hide spurious floating-point exceptions from their callers.
 

 
-
+
 
3   The feholdexcept function returns zero if and only if non-stop floating-point
     exception handling was successfully installed.
 

-
-
+
 

 
7.6.4.3 [The fesetenv function]

-

-
-
-
1           #include <fenv.h>
+
+
1 Synopsis
+           #include <fenv.h>
             int fesetenv(const fenv_t *envp);
     Description
 

-
-
+
 
2   The fesetenv function attempts to establish the floating-point environment represented
     by the object pointed to by envp. The argument envp shall point to an object set by a
     call to fegetenv or feholdexcept, or equal a floating-point environment macro.
@@ -12569,24 +10962,20 @@ Forward references:         conditional inclusion (6.10.1), complex arithmetic
     represented through its argument, and does not raise these floating-point exceptions.
     Returns
 

-
-
+
 
3   The fesetenv function returns zero if the environment was successfully established.
     Otherwise, it returns a nonzero value.
 

-
-
+
 

 
7.6.4.4 [The feupdateenv function]

-

-
-
-
1           #include <fenv.h>
+
+
1 Synopsis
+           #include <fenv.h>
             int feupdateenv(const fenv_t *envp);
     Description
 

-
-
+
 
2   The feupdateenv function attempts to save the currently raised floating-point
     exceptions in its automatic storage, install the floating-point environment represented by
     the object pointed to by envp, and then raise the saved floating-point exceptions. The
@@ -12594,14 +10983,12 @@ Forward references:         conditional inclusion (6.10.1), complex arithmetic
     or equal a floating-point environment macro.
     Returns
 

-
-
+
 
3   The feupdateenv function returns zero if all the actions were successfully carried out.
     Otherwise, it returns a nonzero value.
 
 

-
-
+
 
4   EXAMPLE     Hide spurious underflow floating-point exceptions:
             #include <fenv.h>
             double f(double x)
@@ -12620,106 +11007,88 @@ Forward references:         conditional inclusion (6.10.1), complex arithmetic
                   return result;
             }
 

-
-
+
 

-
7.7 [Characteristics of floating types ]

-

-
-
+
7.7 [Characteristics of floating types <float.h>]

+
 
1   The header <float.h> defines several macros that expand to various limits and
     parameters of the standard floating-point types.
 

-
-
+
 
2   The macros, their meanings, and the constraints (or restrictions) on their values are listed
-    in 5.2.4.2.2.
+    in 5.2.4.2.2.
 

-
-
+
 

-
7.8 [Format conversion of integer types ]

-

-
-
+
7.8 [Format conversion of integer types <inttypes.h>]

+
 
1   The header <inttypes.h> includes the header <stdint.h> and extends it with
     additional facilities provided by hosted implementations.
 

-
-
+
 
2   It declares functions for manipulating greatest-width integers and converting numeric
     character strings to greatest-width integers, and it declares the type
              imaxdiv_t
     which is a structure type that is the type of the value returned by the imaxdiv function.
     For each type declared in <stdint.h>, it defines corresponding macros for conversion
-    specifiers for use with the formatted input/output functions.219)
-    Forward references: integer types <stdint.h> (7.20), formatted input/output
-    functions (7.21.6), formatted wide character input/output functions (7.29.2).
+    specifiers for use with the formatted input/output functions.[219]
+    Forward references: integer types <stdint.h> (7.20), formatted input/output
+    functions (7.21.6), formatted wide character input/output functions (7.29.2).
 

-
 
-
Footnote 219) See ``future library directions'' (7.31.5).
+
Footnote 219) See ``future library directions'' (7.31.5).
 

 
-
+
 

 
7.8.1 [Macros for format specifiers]

-

-
-
+
 
1   Each of the following object-like macros expands to a character string literal containing a
     conversion specifier, possibly modified by a length modifier, suitable for use within the
     format argument of a formatted input/output function when converting the corresponding
     integer type. These macro names have the general form of PRI (character string literals
     for the fprintf and fwprintf family) or SCN (character string literals for the
-    fscanf and fwscanf family),220) followed by the conversion specifier, followed by a
-    name corresponding to a similar type name in 7.20.1. In these names, N represents the
-    width of the type as described in 7.20.1. For example, PRIdFAST32 can be used in a
+    fscanf and fwscanf family),[220] followed by the conversion specifier, followed by a
+    name corresponding to a similar type name in 7.20.1. In these names, N represents the
+    width of the type as described in 7.20.1. For example, PRIdFAST32 can be used in a
     format string to print the value of an integer of type int_fast32_t.
 

-
 
 
Footnote 220) Separate macros are given for use with fprintf and fscanf functions because, in the general case,
          different format specifiers may be required for fprintf and fscanf, even when the type is the
          same.
+           SCNdN           SCNdLEASTN               SCNdFASTN              SCNdMAX             SCNdPTR
+           SCNiN           SCNiLEASTN               SCNiFASTN              SCNiMAX             SCNiPTR
 

 
-
+
 
2   The fprintf macros for signed integers are:
            PRIdN             PRIdLEASTN                PRIdFASTN          PRIdMAX             PRIdPTR
            PRIiN             PRIiLEASTN                PRIiFASTN          PRIiMAX             PRIiPTR
 

-
-
+
 
3   The fprintf macros for unsigned integers are:
            PRIoN             PRIoLEASTN                PRIoFASTN          PRIoMAX             PRIoPTR
            PRIuN             PRIuLEASTN                PRIuFASTN          PRIuMAX             PRIuPTR
            PRIxN             PRIxLEASTN                PRIxFASTN          PRIxMAX             PRIxPTR
            PRIXN             PRIXLEASTN                PRIXFASTN          PRIXMAX             PRIXPTR
 

-
-
+
 
4   The fscanf macros for signed integers are:
-
-           SCNdN           SCNdLEASTN               SCNdFASTN              SCNdMAX             SCNdPTR
-           SCNiN           SCNiLEASTN               SCNiFASTN              SCNiMAX             SCNiPTR
 

-
-
+
 
5   The fscanf macros for unsigned integers are:
            SCNoN           SCNoLEASTN               SCNoFASTN              SCNoMAX             SCNoPTR
            SCNuN           SCNuLEASTN               SCNuFASTN              SCNuMAX             SCNuPTR
            SCNxN           SCNxLEASTN               SCNxFASTN              SCNxMAX             SCNxPTR
 

-
-
+
 
6   For each type that the implementation provides in <stdint.h>, the corresponding
     fprintf macros shall be defined and the corresponding fscanf macros shall be
     defined unless the implementation does not have a suitable fscanf length modifier for
     the type.
 

-
-
+
 
7   EXAMPLE
             #include <inttypes.h>
             #include <wchar.h>
@@ -12732,101 +11101,84 @@ Forward references:         conditional inclusion (6.10.1), complex arithmetic
             }
 
 

-
-
+
 

 
7.8.2 [Functions for greatest-width integer types]

-
 Functions for greatest-width integer types
-

-
-
+
 

 
7.8.2.1 [The imaxabs function]

-

-
-
-
1           #include <inttypes.h>
+
+
1 Synopsis
+           #include <inttypes.h>
             intmax_t imaxabs(intmax_t j);
     Description
 

-
-
+
 
2   The imaxabs function computes the absolute value of an integer j. If the result cannot
-    be represented, the behavior is undefined.221)
+    be represented, the behavior is undefined.[221]
     Returns
 

-
 
 
Footnote 221) The absolute value of the most negative number cannot be represented in two's complement.
 

 
-
+
 
3   The imaxabs function returns the absolute value.
 
 

-
-
+
 

 
7.8.2.2 [The imaxdiv function]

-

-
-
-
1           #include <inttypes.h>
+
+
1 Synopsis
+           #include <inttypes.h>
             imaxdiv_t imaxdiv(intmax_t numer, intmax_t denom);
     Description
 

-
-
+
 
2   The imaxdiv function computes numer / denom and numer % denom in a single
     operation.
     Returns
 

-
-
+
 
3   The imaxdiv function returns a structure of type imaxdiv_t comprising both the
     quotient and the remainder. The structure shall contain (in either order) the members
     quot (the quotient) and rem (the remainder), each of which has type intmax_t. If
     either part of the result cannot be represented, the behavior is undefined.
 

-
-
+
 

 
7.8.2.3 [The strtoimax and strtoumax functions]

-

-
-
-
1           #include <inttypes.h>
+
+
1 Synopsis
+           #include <inttypes.h>
             intmax_t strtoimax(const char * restrict nptr,
                  char ** restrict endptr, int base);
             uintmax_t strtoumax(const char * restrict nptr,
                  char ** restrict endptr, int base);
     Description
 

-
-
+
 
2   The strtoimax and strtoumax functions are equivalent to the strtol, strtoll,
     strtoul, and strtoull functions, except that the initial portion of the string is
     converted to intmax_t and uintmax_t representation, respectively.
     Returns
 

-
-
+
 
3   The strtoimax and strtoumax functions return the converted value, if any. If no
     conversion could be performed, zero is returned. If the correct value is outside the range
     of representable values, INTMAX_MAX, INTMAX_MIN, or UINTMAX_MAX is returned
     (according to the return type and sign of the value, if any), and the value of the macro
     ERANGE is stored in errno.
     Forward references: the strtol, strtoll, strtoul, and strtoull functions
-    (7.22.1.4).
+    (7.22.1.4).
 

-
-
+
 

 
7.8.2.4 [The wcstoimax and wcstoumax functions]

-

-
-
-
1          #include <stddef.h>           // for wchar_t
+
+
1 Synopsis
+          #include <stddef.h>           // for wchar_t
            #include <inttypes.h>
            intmax_t wcstoimax(const wchar_t * restrict nptr,
                 wchar_t ** restrict endptr, int base);
@@ -12834,30 +11186,25 @@ Forward references:         conditional inclusion (6.10.1), complex arithmetic
                 wchar_t ** restrict endptr, int base);
     Description
 

-
-
+
 
2   The wcstoimax and wcstoumax functions are equivalent to the wcstol, wcstoll,
     wcstoul, and wcstoull functions except that the initial portion of the wide string is
     converted to intmax_t and uintmax_t representation, respectively.
     Returns
 

-
-
+
 
3   The wcstoimax function returns the converted value, if any. If no conversion could be
     performed, zero is returned. If the correct value is outside the range of representable
     values, INTMAX_MAX, INTMAX_MIN, or UINTMAX_MAX is returned (according to the
     return type and sign of the value, if any), and the value of the macro ERANGE is stored in
     errno.
     Forward references: the wcstol, wcstoll, wcstoul, and wcstoull functions
-    (7.29.4.1.2).
+    (7.29.4.1.2).
 

-
-
+
 

-
7.9 [Alternative spellings ]

-

-
-
+
7.9 [Alternative spellings <iso646.h>]

+
 
1   The header <iso646.h> defines the following eleven macros (on the left) that expand
     to the corresponding tokens (on the right):
             and        &&
@@ -12872,37 +11219,29 @@ Forward references:         conditional inclusion (6.10.1), complex arithmetic
             xor        ^
             xor_eq     ^=
 

-
-
+
 

-
7.10 [Sizes of integer types ]

-

-
-
+
7.10 [Sizes of integer types <limits.h>]

+
 
1   The header <limits.h> defines several macros that expand to various limits and
     parameters of the standard integer types.
 

-
-
+
 
2   The macros, their meanings, and the constraints (or restrictions) on their values are listed
-    in 5.2.4.2.1.
+    in 5.2.4.2.1.
 

-
-
+
 

-
7.11 [Localization ]

-

-
-
+
7.11 [Localization <locale.h>]

+
 
1   The header <locale.h> declares two functions, one type, and defines several macros.
 

-
-
+
 
2   The type is
             struct lconv
     which contains members related to the formatting of numeric values. The structure shall
     contain at least the following members, in any order. The semantics of the members and
-    their normal ranges are explained in 7.11.2.1. In the "C" locale, the members shall have
+    their normal ranges are explained in 7.11.2.1. In the "C" locale, the members shall have
     the values specified in the comments.
             char   *decimal_point;                //   "."
             char   *thousands_sep;                //   ""
@@ -12929,9 +11268,8 @@ Forward references:         conditional inclusion (6.10.1), complex arithmetic
             char   int_p_sign_posn;               //   CHAR_MAX
             char   int_n_sign_posn;               //   CHAR_MAX
 

-
-
-
3   The macros defined are NULL (described in 7.19); and
+
+
3   The macros defined are NULL (described in 7.19); and
              LC_ALL
              LC_COLLATE
              LC_CTYPE
@@ -12939,130 +11277,111 @@ Forward references:         conditional inclusion (6.10.1), complex arithmetic
              LC_NUMERIC
              LC_TIME
     which expand to integer constant expressions with distinct values, suitable for use as the
-    first argument to the setlocale function.222) Additional macro definitions, beginning
-    with the characters LC_ and an uppercase letter,223) may also be specified by the
+    first argument to the setlocale function.[222] Additional macro definitions, beginning
+    with the characters LC_ and an uppercase letter,[223] may also be specified by the
     implementation.
 

-
 
 
Footnote 222) ISO/IEC 9945-2 specifies locale and charmap formats that may be used to specify locales for C.
 

 
 
-
Footnote 223) See ``future library directions'' (7.31.6).
+
Footnote 223) See ``future library directions'' (7.31.6).
 

 
-
+
 

 
7.11.1 [Locale control]

-
 Locale control
-

-
-
+
 

 
7.11.1.1 [The setlocale function]

-

-
-
-
1            #include <locale.h>
+
+
1 Synopsis
+            #include <locale.h>
              char *setlocale(int category, const char *locale);
     Description
 

-
-
+
 
2   The setlocale function selects the appropriate portion of the program's locale as
     specified by the category and locale arguments. The setlocale function may be
     used to change or query the program's entire current locale or portions thereof. The value
     LC_ALL for category names the program's entire locale; the other values for
     category name only a portion of the program's locale. LC_COLLATE affects the
     behavior of the strcoll and strxfrm functions. LC_CTYPE affects the behavior of
-    the character handling functions224) and the multibyte and wide character functions.
+    the character handling functions[224] and the multibyte and wide character functions.
     LC_MONETARY affects the monetary formatting information returned by the
     localeconv function. LC_NUMERIC affects the decimal-point character for the
     formatted input/output functions and the string conversion functions, as well as the
     nonmonetary formatting information returned by the localeconv function. LC_TIME
     affects the behavior of the strftime and wcsftime functions.
 

-
 
-
Footnote 224) The only functions in 7.4 whose behavior is not affected by the current locale are isdigit and
+
Footnote 224) The only functions in 7.4 whose behavior is not affected by the current locale are isdigit and
          isxdigit.
 

 
-
+
 
3   A value of "C" for locale specifies the minimal environment for C translation; a value
     of "" for locale specifies the locale-specific native environment. Other
     implementation-defined strings may be passed as the second argument to setlocale.
 
 

-
-
+
 
4   At program startup, the equivalent of
             setlocale(LC_ALL, "C");
     is executed.
 

-
-
+
 
5   A call to the setlocale function may introduce a data race with other calls to the
     setlocale function or with calls to functions that are affected by the current locale.
     The implementation shall behave as if no library function calls the setlocale function.
     Returns
 

-
-
+
 
6   If a pointer to a string is given for locale and the selection can be honored, the
     setlocale function returns a pointer to the string associated with the specified
     category for the new locale. If the selection cannot be honored, the setlocale
     function returns a null pointer and the program's locale is not changed.
 

-
-
+
 
7   A null pointer for locale causes the setlocale function to return a pointer to the
     string associated with the category for the program's current locale; the program's
-    locale is not changed.225)
+    locale is not changed.[225]
 

-
 
 
Footnote 225) The implementation shall arrange to encode in a string the various categories due to a heterogeneous
          locale when category has the value LC_ALL.
 

 
-
+
 
8   The pointer to string returned by the setlocale function is such that a subsequent call
     with that string value and its associated category will restore that part of the program's
     locale. The string pointed to shall not be modified by the program, but may be
     overwritten by a subsequent call to the setlocale function.
-    Forward references: formatted input/output functions (7.21.6), multibyte/wide
-    character conversion functions (7.22.7), multibyte/wide string conversion functions
-    (7.22.8), numeric conversion functions (7.22.1), the strcoll function (7.24.4.3), the
-    strftime function (7.27.3.5), the strxfrm function (7.24.4.5).
+    Forward references: formatted input/output functions (7.21.6), multibyte/wide
+    character conversion functions (7.22.7), multibyte/wide string conversion functions
+    (7.22.8), numeric conversion functions (7.22.1), the strcoll function (7.24.4.3), the
+    strftime function (7.27.3.5), the strxfrm function (7.24.4.5).
 

-
-
+
 

 
7.11.2 [Numeric formatting convention inquiry]

-
 Numeric formatting convention inquiry
-

-
-
+
 

 
7.11.2.1 [The localeconv function]

-

-
-
-
1           #include <locale.h>
+
+
1 Synopsis
+           #include <locale.h>
             struct lconv *localeconv(void);
     Description
 

-
-
+
 
2   The localeconv function sets the components of an object with type struct lconv
     with values appropriate for the formatting of numeric quantities (monetary and otherwise)
     according to the rules of the current locale.
 
 

-
-
+
 
3   The members of the structure with type char * are pointers to strings, any of which
     (except decimal_point) can point to "", to indicate that the value is not available in
     the current locale or is of zero length. Apart from grouping and mon_grouping, the
@@ -13148,8 +11467,7 @@ char int_p_sep_by_space
               Set to a value indicating the positioning of the negative_sign for a
               negative internationally formatted monetary quantity.
 

-
-
+
 
4   The elements of grouping and mon_grouping are interpreted according to the
     following:
     CHAR_MAX        No further grouping is to be performed.
@@ -13159,8 +11477,7 @@ char int_p_sep_by_space
                     The next element is examined to determine the size of the next group of
                     digits before the current group.
 

-
-
+
 
5   The values of p_sep_by_space, n_sep_by_space, int_p_sep_by_space,
     and int_n_sep_by_space are interpreted according to the following:
     0     No space separates the currency symbol and value.
@@ -13171,8 +11488,7 @@ char int_p_sep_by_space
     For int_p_sep_by_space and int_n_sep_by_space, the fourth character of
     int_curr_symbol is used instead of a space.
 

-
-
+
 
6   The values of p_sign_posn, n_sign_posn, int_p_sign_posn,                              and
     int_n_sign_posn are interpreted according to the following:
     0     Parentheses surround the quantity and currency symbol.
@@ -13181,22 +11497,19 @@ char int_p_sep_by_space
     3     The sign string immediately precedes the currency symbol.
     4     The sign string immediately succeeds the currency symbol.
 

-
-
+
 
7    The implementation shall behave as if no library function calls the localeconv
      function.
      Returns
 

-
-
+
 
8    The localeconv function returns a pointer to the filled-in object. The structure
      pointed to by the return value shall not be modified by the program, but may be
      overwritten by a subsequent call to the localeconv function. In addition, calls to the
      setlocale function with categories LC_ALL, LC_MONETARY, or LC_NUMERIC may
      overwrite the contents of the structure.
 

-
-
+
 
9    EXAMPLE 1 The following table illustrates rules which may well be used by four countries to format
      monetary quantities.
                                    Local format                                     International format
@@ -13208,8 +11521,7 @@ char int_p_sep_by_space
      Country3      1.234,56                -1.234,56                    NLG   1.234,56         NLG -1.234,56
      Country4     SFrs.1,234.56           SFrs.1,234.56C                CHF   1,234.56         CHF 1,234.56C
 

-
-
+
 
10   For these four countries, the respective values for the monetary members of the structure returned by
      localeconv could be:
                                        Country1              Country2              Country3            Country4
@@ -13236,8 +11548,7 @@ char int_p_sep_by_space
      int_p_sign_posn                   1                     1                    1                   1
      int_n_sign_posn                   4                     1                    4                   2
 

-
-
+
 
11   EXAMPLE 2 The following table illustrates how the cs_precedes, sep_by_space, and sign_posn members
      affect the formatted value.
                                                                    p_sep_by_space
@@ -13256,27 +11567,23 @@ char int_p_sep_by_space
                                           3         +$1.25             +$ 1.25             + $1.25
                                           4         $+1.25             $+ 1.25             $ +1.25
 

-
-
+
 

-
7.12 [Mathematics ]

-

-
-
+
7.12 [Mathematics <math.h>]

+
 
1   The header <math.h> declares two types and many mathematical functions and defines
     several macros. Most synopses specify a family of functions consisting of a principal
     function with one or more double parameters, a double return value, or both; and
     other functions with the same name but with f and l suffixes, which are corresponding
-    functions with float and long double parameters, return values, or both.226)
+    functions with float and long double parameters, return values, or both.[226]
     Integer arithmetic functions and conversion functions are discussed later.
 

-
 
 
Footnote 226) Particularly on systems with wide expression evaluation, a <math.h> function might pass arguments
          and return values in wider format than the synopsis prototype indicates.
 

 
-
+
 
2   The types
             float_t
             double_t
@@ -13285,51 +11592,42 @@ char int_p_sep_by_space
     float_t and double_t are float and double, respectively; if
     FLT_EVAL_METHOD equals 1, they are both double; if FLT_EVAL_METHOD equals
     2, they are both long double; and for other values of FLT_EVAL_METHOD, they are
-    otherwise implementation-defined.227)
+    otherwise implementation-defined.[227]
 

-
 
 
Footnote 227) The types float_t and double_t are intended to be the implementation's most efficient types at
          least as wide as float and double, respectively. For FLT_EVAL_METHOD equal 0, 1, or 2, the
          type float_t is the narrowest type used by the implementation to evaluate floating expressions.
 

 
-
+
 
3   The macro
             HUGE_VAL
     expands to a positive double constant expression, not necessarily representable as a
     float. The macros
             HUGE_VALF
             HUGE_VALL
-    are respectively float and long double analogs of HUGE_VAL.228)
+    are respectively float and long double analogs of HUGE_VAL.[228]
 

-
 
 
Footnote 228) HUGE_VAL, HUGE_VALF, and HUGE_VALL can be positive infinities in an implementation that
          supports infinities.
+    translation time.229)
 

 
-
+
 
4   The macro
             INFINITY
     expands to a constant expression of type float representing positive or unsigned
     infinity, if available; else to a positive constant of type float that overflows at
-
-    translation time.229)
 

-
-
-
Footnote 229) In this case, using INFINITY will violate the constraint in 6.4.4 and thus require a diagnostic.
-

-
-
+
 
5   The macro
              NAN
     is defined if and only if the implementation supports quiet NaNs for the float type. It
     expands to a constant expression of type float representing a quiet NaN.
 

-
-
+
 
6   The number classification macros
              FP_INFINITE
              FP_NAN
@@ -13341,26 +11639,24 @@ char int_p_sep_by_space
     point classifications, with macro definitions beginning with FP_ and an uppercase letter,
     may also be specified by the implementation.
 

-
-
+
 
7   The macro
              FP_FAST_FMA
     is optionally defined. If defined, it indicates that the fma function generally executes
-    about as fast as, or faster than, a multiply and an add of double operands.230) The
+    about as fast as, or faster than, a multiply and an add of double operands.[230] The
     macros
              FP_FAST_FMAF
              FP_FAST_FMAL
     are, respectively, float and long double analogs of FP_FAST_FMA. If defined,
     these macros expand to the integer constant 1.
 

-
 
 
Footnote 230) Typically, the FP_FAST_FMA macro is defined if and only if the fma function is implemented
          directly with a hardware multiply-add instruction. Software implementations are expected to be
          substantially slower.
 

 
-
+
 
8   The macros
              FP_ILOGB0
              FP_ILOGBNAN
@@ -13369,8 +11665,7 @@ char int_p_sep_by_space
     -INT_MAX. The value of FP_ILOGBNAN shall be either INT_MAX or INT_MIN.
 
 

-
-
+
 
9   The macros
               MATH_ERRNO
               MATH_ERREXCEPT
@@ -13386,55 +11681,47 @@ char int_p_sep_by_space
     shall define the macros FE_DIVBYZERO, FE_INVALID, and FE_OVERFLOW in
     <fenv.h>.
 

-
-
+
 

 
7.12.1 [Treatment of error conditions]

-

-
-
+
 
1   The behavior of each of the functions in <math.h> is specified for all representable
     values of its input arguments, except where stated otherwise. Each function shall execute
     as if it were a single operation without raising SIGFPE and without generating any of the
     floating-point exceptions ``invalid'', ``divide-by-zero'', or ``overflow'' except to reflect
     the result of the function.
 

-
-
+
 
2   For all functions, a domain error occurs if an input argument is outside the domain over
     which the mathematical function is defined. The description of each function lists any
     required domain errors; an implementation may define additional domain errors, provided
-    that such errors are consistent with the mathematical definition of the function.231) On a
+    that such errors are consistent with the mathematical definition of the function.[231] On a
     domain error, the function returns an implementation-defined value; if the integer
     expression math_errhandling & MATH_ERRNO is nonzero, the integer expression
     errno acquires the value EDOM; if the integer expression math_errhandling &
     MATH_ERREXCEPT is nonzero, the ``invalid'' floating-point exception is raised.
 

-
 
 
Footnote 231) In an implementation that supports infinities, this allows an infinity as an argument to be a domain
          error if the mathematical domain of the function does not include the infinity.
+    math_errhandling & MATH_ERRNO is nonzero, the integer expression errno
+    acquires the value ERANGE; if the integer expression math_errhandling &
+    MATH_ERREXCEPT is nonzero, the ``divide-by-zero'' floating-point exception is raised.
 

 
-
+
 
3   Similarly, a pole error (also known as a singularity or infinitary) occurs if the
     mathematical function has an exact infinite result as the finite input argument(s) are
     approached in the limit (for example, log(0.0)). The description of each function lists
     any required pole errors; an implementation may define additional pole errors, provided
     that such errors are consistent with the mathematical definition of the function. On a pole
     error, the function returns an implementation-defined value; if the integer expression
-
-    math_errhandling & MATH_ERRNO is nonzero, the integer expression errno
-    acquires the value ERANGE; if the integer expression math_errhandling &
-    MATH_ERREXCEPT is nonzero, the ``divide-by-zero'' floating-point exception is raised.
 

-
-
+
 
4   Likewise, a range error occurs if the mathematical result of the function cannot be
     represented in an object of the specified type, due to extreme magnitude.
 

-
-
+
 
5   A floating result overflows if the magnitude of the mathematical result is finite but so
     large that the mathematical result cannot be represented without extraordinary roundoff
     error in an object of the specified type. If a floating result overflows and default rounding
@@ -13445,11 +11732,10 @@ char int_p_sep_by_space
     math_errhandling & MATH_ERREXCEPT is nonzero, the ``overflow'' floating-
     point exception is raised.
 

-
-
+
 
6   The result underflows if the magnitude of the mathematical result is so small that the
     mathematical result cannot be represented, without extraordinary roundoff error, in an
-    object of the specified type.232) If the result underflows, the function returns an
+    object of the specified type.[232] If the result underflows, the function returns an
     implementation-defined value whose magnitude is no greater than the smallest
     normalized positive number in the specified type; if the integer expression
     math_errhandling & MATH_ERRNO is nonzero, whether errno acquires the
@@ -13457,38 +11743,34 @@ char int_p_sep_by_space
     math_errhandling & MATH_ERREXCEPT is nonzero, whether the ``underflow''
     floating-point exception is raised is implementation-defined.
 

-
 
 
Footnote 232) The term underflow here is intended to encompass both ``gradual underflow'' as in IEC 60559 and
          also ``flush-to-zero'' underflow.
 

 
-
+
 
7   If a domain, pole, or range error occurs and the integer expression
-    math_errhandling & MATH_ERRNO is zero,233) then errno shall either be set to
+    math_errhandling & MATH_ERRNO is zero,[233] then errno shall either be set to
     the value corresponding to the error or left unmodified. If no such error occurs, errno
     shall be left unmodified regardless of the setting of math_errhandling.
 
 

-
 
 
Footnote 233) Math errors are being indicated by the floating-point exception flags rather than by errno.
 

 
-
+
 

 
7.12.2 [The FP_CONTRACT pragma]

-

-
-
-
1            #include <math.h>
+
+
1 Synopsis
+            #include <math.h>
              #pragma STDC FP_CONTRACT on-off-switch
     Description
 

-
-
+
 
2   The FP_CONTRACT pragma can be used to allow (if the state is ``on'') or disallow (if the
-    state is ``off'') the implementation to contract expressions (6.5). Each pragma can occur
+    state is ``off'') the implementation to contract expressions (6.5). Each pragma can occur
     either outside external declarations or preceding all explicit declarations and statements
     inside a compound statement. When outside external declarations, the pragma takes
     effect from its occurrence until another FP_CONTRACT pragma is encountered, or until
@@ -13500,608 +11782,500 @@ char int_p_sep_by_space
     context, the behavior is undefined. The default state (``on'' or ``off'') for the pragma is
     implementation-defined.
 

-
-
+
 

 
7.12.3 [Classification macros]

-

-
-
+
 
1   In the synopses in this subclause, real-floating indicates that the argument shall be an
     expression of real floating type.
 

-
-
+
 

 
7.12.3.1 [The fpclassify macro]

-

-
-
-
1            #include <math.h>
+
+
1 Synopsis
+            #include <math.h>
              int fpclassify(real-floating x);
     Description
 

-
-
+
 
2   The fpclassify macro classifies its argument value as NaN, infinite, normal,
     subnormal, zero, or into another implementation-defined category. First, an argument
     represented in a format wider than its semantic type is converted to its semantic type.
-    Then classification is based on the type of the argument.234)
+    Then classification is based on the type of the argument.[234]
     Returns
 

-
 
 
Footnote 234) Since an expression can be evaluated with more range and precision than its type has, it is important to
          know the type that classification is based on. For example, a normal long double value might
          become subnormal when converted to double, and zero when converted to float.
 

 
-
+
 
3   The fpclassify macro returns the value of the number classification macro
     appropriate to the value of its argument.
 
 

-
-
+
 

 
7.12.3.2 [The isfinite macro]

-

-
-
-
1           #include <math.h>
+
+
1 Synopsis
+           #include <math.h>
             int isfinite(real-floating x);
     Description
 

-
-
+
 
2   The isfinite macro determines whether its argument has a finite value (zero,
     subnormal, or normal, and not infinite or NaN). First, an argument represented in a
     format wider than its semantic type is converted to its semantic type. Then determination
     is based on the type of the argument.
     Returns
 

-
-
+
 
3   The isfinite macro returns a nonzero value if and only if its argument has a finite
     value.
 

-
-
+
 

 
7.12.3.3 [The isinf macro]

-

-
-
-
1           #include <math.h>
+
+
1 Synopsis
+           #include <math.h>
             int isinf(real-floating x);
     Description
 

-
-
+
 
2   The isinf macro determines whether its argument value is an infinity (positive or
     negative). First, an argument represented in a format wider than its semantic type is
     converted to its semantic type. Then determination is based on the type of the argument.
     Returns
 

-
-
+
 
3   The isinf macro returns a nonzero value if and only if its argument has an infinite
     value.
 

-
-
+
 

 
7.12.3.4 [The isnan macro]

-

-
-
-
1           #include <math.h>
+
+
1 Synopsis
+           #include <math.h>
             int isnan(real-floating x);
     Description
 

-
-
+
 
2   The isnan macro determines whether its argument value is a NaN. First, an argument
     represented in a format wider than its semantic type is converted to its semantic type.
-    Then determination is based on the type of the argument.235)
-
-    Returns
+    Then determination is based on the type of the argument.[235]
 

-
 
 
Footnote 235) For the isnan macro, the type for determination does not matter unless the implementation supports
          NaNs in the evaluation type but not in the semantic type.
+    Returns
 

 
-
+
 
3   The isnan macro returns a nonzero value if and only if its argument has a NaN value.
 

-
-
+
 

 
7.12.3.5 [The isnormal macro]

-

-
-
-
1           #include <math.h>
+
+
1 Synopsis
+           #include <math.h>
             int isnormal(real-floating x);
     Description
 

-
-
+
 
2   The isnormal macro determines whether its argument value is normal (neither zero,
     subnormal, infinite, nor NaN). First, an argument represented in a format wider than its
     semantic type is converted to its semantic type. Then determination is based on the type
     of the argument.
     Returns
 

-
-
+
 
3   The isnormal macro returns a nonzero value if and only if its argument has a normal
     value.
 

-
-
+
 

 
7.12.3.6 [The signbit macro]

-

-
-
-
1           #include <math.h>
+
+
1 Synopsis
+           #include <math.h>
             int signbit(real-floating x);
     Description
 

-
-
-
2   The signbit macro determines whether the sign of its argument value is negative.236)
+
+
2   The signbit macro determines whether the sign of its argument value is negative.[236]
     Returns
 

-
 
 
Footnote 236) The signbit macro reports the sign of all values, including infinities, zeros, and NaNs. If zero is
          unsigned, it is treated as positive.
 

 
-
+
 
3   The signbit macro returns a nonzero value if and only if the sign of its argument value
     is negative.
 
 

-
-
+
 

 
7.12.4 [Trigonometric functions]

-
 Trigonometric functions
-

-
-
+
 

 
7.12.4.1 [The acos functions]

-

-
-
-
1          #include <math.h>
+
+
1 Synopsis
+          #include <math.h>
            double acos(double x);
            float acosf(float x);
            long double acosl(long double x);
     Description
 

-
-
+
 
2   The acos functions compute the principal value of the arc cosine of x. A domain error
     occurs for arguments not in the interval [-1, +1].
     Returns
 

-
-
+
 
3   The acos functions return arccos x in the interval [0,  ] radians.
 

-
-
+
 

 
7.12.4.2 [The asin functions]

-

-
-
-
1          #include <math.h>
+
+
1 Synopsis
+          #include <math.h>
            double asin(double x);
            float asinf(float x);
            long double asinl(long double x);
     Description
 

-
-
+
 
2   The asin functions compute the principal value of the arc sine of x. A domain error
     occurs for arguments not in the interval [-1, +1].
     Returns
 

-
-
+
 
3   The asin functions return arcsin x in the interval [- /2, + /2] radians.
 

-
-
+
 

 
7.12.4.3 [The atan functions]

-

-
-
-
1          #include <math.h>
+
+
1 Synopsis
+          #include <math.h>
            double atan(double x);
            float atanf(float x);
            long double atanl(long double x);
     Description
 

-
-
+
 
2   The atan functions compute the principal value of the arc tangent of x.
     Returns
 

-
-
+
 
3   The atan functions return arctan x in the interval [- /2, + /2] radians.
 

-
-
+
 

 
7.12.4.4 [The atan2 functions]

-

-
-
-
1           #include <math.h>
+
+
1 Synopsis
+           #include <math.h>
             double atan2(double y, double x);
             float atan2f(float y, float x);
             long double atan2l(long double y, long double x);
     Description
 

-
-
+
 
2   The atan2 functions compute the value of the arc tangent of y/x, using the signs of both
     arguments to determine the quadrant of the return value. A domain error may occur if
     both arguments are zero.
     Returns
 

-
-
+
 
3   The atan2 functions return arctan y/x in the interval [- , + ] radians.
 

-
-
+
 

 
7.12.4.5 [The cos functions]

-

-
-
-
1           #include <math.h>
+
+
1 Synopsis
+           #include <math.h>
             double cos(double x);
             float cosf(float x);
             long double cosl(long double x);
     Description
 

-
-
+
 
2   The cos functions compute the cosine of x (measured in radians).
     Returns
 

-
-
+
 
3   The cos functions return cos x.
 

-
-
+
 

 
7.12.4.6 [The sin functions]

-

-
-
-
1           #include <math.h>
+
+
1 Synopsis
+           #include <math.h>
             double sin(double x);
             float sinf(float x);
             long double sinl(long double x);
     Description
 

-
-
+
 
2   The sin functions compute the sine of x (measured in radians).
 
     Returns
 

-
-
+
 
3   The sin functions return sin x.
 

-
-
+
 

 
7.12.4.7 [The tan functions]

-

-
-
-
1          #include <math.h>
+
+
1 Synopsis
+          #include <math.h>
            double tan(double x);
            float tanf(float x);
            long double tanl(long double x);
     Description
 

-
-
+
 
2   The tan functions return the tangent of x (measured in radians).
     Returns
 

-
-
+
 
3   The tan functions return tan x.
 

-
-
+
 

 
7.12.5 [Hyperbolic functions]

-
 Hyperbolic functions
-

-
-
+
 

 
7.12.5.1 [The acosh functions]

-

-
-
-
1          #include <math.h>
+
+
1 Synopsis
+          #include <math.h>
            double acosh(double x);
            float acoshf(float x);
            long double acoshl(long double x);
     Description
 

-
-
+
 
2   The acosh functions compute the (nonnegative) arc hyperbolic cosine of x. A domain
     error occurs for arguments less than 1.
     Returns
 

-
-
+
 
3   The acosh functions return arcosh x in the interval [0, +].
 

-
-
+
 

 
7.12.5.2 [The asinh functions]

-

-
-
-
1          #include <math.h>
+
+
1 Synopsis
+          #include <math.h>
            double asinh(double x);
            float asinhf(float x);
            long double asinhl(long double x);
     Description
 

-
-
+
 
2   The asinh functions compute the arc hyperbolic sine of x.
     Returns
 

-
-
+
 
3   The asinh functions return arsinh x.
 

-
-
+
 

 
7.12.5.3 [The atanh functions]

-

-
-
-
1           #include <math.h>
+
+
1 Synopsis
+           #include <math.h>
             double atanh(double x);
             float atanhf(float x);
             long double atanhl(long double x);
     Description
 

-
-
+
 
2   The atanh functions compute the arc hyperbolic tangent of x. A domain error occurs
     for arguments not in the interval [-1, +1]. A pole error may occur if the argument equals
     -1 or +1.
     Returns
 

-
-
+
 
3   The atanh functions return artanh x.
 

-
-
+
 

 
7.12.5.4 [The cosh functions]

-

-
-
-
1           #include <math.h>
+
+
1 Synopsis
+           #include <math.h>
             double cosh(double x);
             float coshf(float x);
             long double coshl(long double x);
     Description
 

-
-
+
 
2   The cosh functions compute the hyperbolic cosine of x. A range error occurs if the
     magnitude of x is too large.
     Returns
 

-
-
+
 
3   The cosh functions return cosh x.
 

-
-
+
 

 
7.12.5.5 [The sinh functions]

-

-
-
-
1           #include <math.h>
+
+
1 Synopsis
+           #include <math.h>
             double sinh(double x);
             float sinhf(float x);
             long double sinhl(long double x);
     Description
 

-
-
+
 
2   The sinh functions compute the hyperbolic sine of x. A range error occurs if the
     magnitude of x is too large.
     Returns
 

-
-
+
 
3   The sinh functions return sinh x.
 

-
-
+
 

 
7.12.5.6 [The tanh functions]

-

-
-
-
1          #include <math.h>
+
+
1 Synopsis
+          #include <math.h>
            double tanh(double x);
            float tanhf(float x);
            long double tanhl(long double x);
     Description
 

-
-
+
 
2   The tanh functions compute the hyperbolic tangent of x.
     Returns
 

-
-
+
 
3   The tanh functions return tanh x.
 

-
-
+
 

 
7.12.6 [Exponential and logarithmic functions]

-
 Exponential and logarithmic functions
-

-
-
+
 

 
7.12.6.1 [The exp functions]

-

-
-
-
1          #include <math.h>
+
+
1 Synopsis
+          #include <math.h>
            double exp(double x);
            float expf(float x);
            long double expl(long double x);
     Description
 

-
-
+
 
2   The exp functions compute the base-e exponential of x. A range error occurs if the
     magnitude of x is too large.
     Returns
 

-
-
+
 
3   The exp functions return ex .
 

-
-
+
 

 
7.12.6.2 [The exp2 functions]

-

-
-
-
1          #include <math.h>
+
+
1 Synopsis
+          #include <math.h>
            double exp2(double x);
            float exp2f(float x);
            long double exp2l(long double x);
     Description
 

-
-
+
 
2   The exp2 functions compute the base-2 exponential of x. A range error occurs if the
     magnitude of x is too large.
 
     Returns
 

-
-
+
 
3   The exp2 functions return 2x .
 

-
-
+
 

 
7.12.6.3 [The expm1 functions]

-

-
-
-
1           #include <math.h>
+
+
1 Synopsis
+           #include <math.h>
             double expm1(double x);
             float expm1f(float x);
             long double expm1l(long double x);
     Description
 

-
-
+
 
2   The expm1 functions compute the base-e exponential of the argument, minus 1. A range
-    error occurs if x is too large.237)
+    error occurs if x is too large.[237]
     Returns
 

-
 
 
Footnote 237) For small magnitude x, expm1(x) is expected to be more accurate than exp(x) - 1.
 

 
-
+
 
3   The expm1 functions return ex - 1.
 

-
-
+
 

 
7.12.6.4 [The frexp functions]

-

-
-
-
1           #include <math.h>
+
+
1 Synopsis
+           #include <math.h>
             double frexp(double value, int *exp);
             float frexpf(float value, int *exp);
             long double frexpl(long double value, int *exp);
     Description
 

-
-
+
 
2   The frexp functions break a floating-point number into a normalized fraction and an
     integral power of 2. They store the integer in the int object pointed to by exp.
     Returns
 

-
-
+
 
3   If value is not a floating-point number or if the integral power of 2 is outside the range
     of int, the results are unspecified. Otherwise, the frexp functions return the value x,
-    such that x has a magnitude in the interval [1/2, 1) or zero, and value equals x × 2*exp .
+    such that x has a magnitude in the interval [1/2, [1] or zero, and value equals x \xD7 2*exp .
     If value is zero, both parts of the result are zero.
 
 

-
 
 
Footnote 1) This International Standard is designed to promote the portability of C programs among a variety of
          data-processing systems. It is intended for use by implementors and programmers.
 

 
-
+
 

 
7.12.6.5 [The ilogb functions]

-

-
-
-
1          #include <math.h>
+
+
1 Synopsis
+          #include <math.h>
            int ilogb(double x);
            int ilogbf(float x);
            int ilogbl(long double x);
     Description
 

-
-
+
 
2   The ilogb functions extract the exponent of x as a signed int value. If x is zero they
     compute the value FP_ILOGB0; if x is infinite they compute the value INT_MAX; if x is
     a NaN they compute the value FP_ILOGBNAN; otherwise, they are equivalent to calling
@@ -14110,191 +12284,160 @@ char int_p_sep_by_space
     the range of the return type, the numeric result is unspecified.
     Returns
 

-
-
+
 
3   The ilogb functions return the exponent of x as a signed int value.
-    Forward references: the logb functions (7.12.6.11).
+    Forward references: the logb functions (7.12.6.11).
 

-
-
+
 

 
7.12.6.6 [The ldexp functions]

-

-
-
-
1          #include <math.h>
+
+
1 Synopsis
+          #include <math.h>
            double ldexp(double x, int exp);
            float ldexpf(float x, int exp);
            long double ldexpl(long double x, int exp);
     Description
 

-
-
+
 
2   The ldexp functions multiply a floating-point number by an integral power of 2. A
     range error may occur.
     Returns
 

-
-
-
3   The ldexp functions return x × 2exp .
+
+
3   The ldexp functions return x \xD7 2exp .
 

-
-
+
 

 
7.12.6.7 [The log functions]

-

-
-
-
1          #include <math.h>
+
+
1 Synopsis
+          #include <math.h>
            double log(double x);
            float logf(float x);
            long double logl(long double x);
 
     Description
 

-
-
+
 
2   The log functions compute the base-e (natural) logarithm of x. A domain error occurs if
     the argument is negative. A pole error may occur if the argument is zero.
     Returns
 

-
-
+
 
3   The log functions return loge x.
 

-
-
+
 

 
7.12.6.8 [The log10 functions]

-

-
-
-
1           #include <math.h>
+
+
1 Synopsis
+           #include <math.h>
             double log10(double x);
             float log10f(float x);
             long double log10l(long double x);
     Description
 

-
-
+
 
2   The log10 functions compute the base-10 (common) logarithm of x. A domain error
     occurs if the argument is negative. A pole error may occur if the argument is zero.
     Returns
 

-
-
+
 
3   The log10 functions return log10 x.
 

-
-
+
 

 
7.12.6.9 [The log1p functions]

-

-
-
-
1           #include <math.h>
+
+
1 Synopsis
+           #include <math.h>
             double log1p(double x);
             float log1pf(float x);
             long double log1pl(long double x);
     Description
 

-
-
-
2   The log1p functions compute the base-e (natural) logarithm of 1 plus the argument.238)
+
+
2   The log1p functions compute the base-e (natural) logarithm of 1 plus the argument.[238]
     A domain error occurs if the argument is less than -1. A pole error may occur if the
     argument equals -1.
     Returns
 

-
 
 
Footnote 238) For small magnitude x, log1p(x) is expected to be more accurate than log(1 + x).
 

 
-
+
 
3   The log1p functions return loge (1 + x).
 
 

-
-
+
 

 
7.12.6.10 [The log2 functions]

-

-
-
-
1          #include <math.h>
+
+
1 Synopsis
+          #include <math.h>
            double log2(double x);
            float log2f(float x);
            long double log2l(long double x);
     Description
 

-
-
+
 
2   The log2 functions compute the base-2 logarithm of x. A domain error occurs if the
     argument is less than zero. A pole error may occur if the argument is zero.
     Returns
 

-
-
+
 
3   The log2 functions return log2 x.
 

-
-
+
 

 
7.12.6.11 [The logb functions]

-

-
-
-
1          #include <math.h>
+
+
1 Synopsis
+          #include <math.h>
            double logb(double x);
            float logbf(float x);
            long double logbl(long double x);
     Description
 

-
-
+
 
2   The logb functions extract the exponent of x, as a signed integer value in floating-point
     format. If x is subnormal it is treated as though it were normalized; thus, for positive
     finite x,
-          1  x × FLT_RADIX-logb(x) < FLT_RADIX
+          1  x \xD7 FLT_RADIX-logb(x) < FLT_RADIX
     A domain error or pole error may occur if the argument is zero.
     Returns
 

-
-
+
 
3   The logb functions return the signed exponent of x.
 

-
-
+
 

 
7.12.6.12 [The modf functions]

-

-
-
-
1          #include <math.h>
+
+
1 Synopsis
+          #include <math.h>
            double modf(double value, double *iptr);
            float modff(float value, float *iptr);
            long double modfl(long double value, long double *iptr);
     Description
 

-
-
+
 
2   The modf functions break the argument value into integral and fractional parts, each of
     which has the same type and sign as the argument. They store the integral part (in
     floating-point format) in the object pointed to by iptr.
     Returns
 

-
-
+
 
3   The modf functions return the signed fractional part of value.
 

-
-
+
 

 
7.12.6.13 [The scalbn and scalbln functions]

-

-
-
-
1           #include <math.h>
+
+
1 Synopsis
+           #include <math.h>
             double scalbn(double x, int n);
             float scalbnf(float x, int n);
             long double scalbnl(long double x, int n);
@@ -14303,167 +12446,134 @@ char int_p_sep_by_space
             long double scalblnl(long double x, long int n);
     Description
 

-
-
-
2   The scalbn and scalbln functions compute x × FLT_RADIXn efficiently, not
+
+
2   The scalbn and scalbln functions compute x \xD7 FLT_RADIXn efficiently, not
     normally by computing FLT_RADIXn explicitly. A range error may occur.
     Returns
 

-
-
-
3   The scalbn and scalbln functions return x × FLT_RADIXn .
+
+
3   The scalbn and scalbln functions return x \xD7 FLT_RADIXn .
 

-
-
+
 

 
7.12.7 [Power and absolute-value functions]

-
 Power and absolute-value functions
-

-
-
+
 

 
7.12.7.1 [The cbrt functions]

-

-
-
-
1           #include <math.h>
+
+
1 Synopsis
+           #include <math.h>
             double cbrt(double x);
             float cbrtf(float x);
             long double cbrtl(long double x);
     Description
 

-
-
+
 
2   The cbrt functions compute the real cube root of x.
     Returns
 

-
-
+
 
3   The cbrt functions return x1/3 .
 

-
-
+
 

 
7.12.7.2 [The fabs functions]

-

-
-
-
1          #include <math.h>
+
+
1 Synopsis
+          #include <math.h>
            double fabs(double x);
            float fabsf(float x);
            long double fabsl(long double x);
     Description
 

-
-
+
 
2   The fabs functions compute the absolute value of a floating-point number x.
     Returns
 

-
-
+
 
3   The fabs functions return | x |.
 

-
-
+
 

 
7.12.7.3 [The hypot functions]

-

-
-
-
1          #include <math.h>
+
+
1 Synopsis
+          #include <math.h>
            double hypot(double x, double y);
            float hypotf(float x, float y);
            long double hypotl(long double x, long double y);
     Description
 

-
-
+
 
2   The hypot functions compute the square root of the sum of the squares of x and y,
     without undue overflow or underflow. A range error may occur.
 

-
-
+
 
3   Returns
 

-
-
+
 
4   The hypot functions return  x2 + y 2 .
 

-
-
+
 

 
7.12.7.4 [The pow functions]

-

-
-
-
1          #include <math.h>
+
+
1 Synopsis
+          #include <math.h>
            double pow(double x, double y);
            float powf(float x, float y);
            long double powl(long double x, long double y);
     Description
 

-
-
+
 
2   The pow functions compute x raised to the power y. A domain error occurs if x is finite
     and negative and y is finite and not an integer value. A range error may occur. A domain
     error may occur if x is zero and y is zero. A domain error or pole error may occur if x is
     zero and y is less than zero.
     Returns
 

-
-
+
 
3   The pow functions return xy .
 

-
-
+
 

 
7.12.7.5 [The sqrt functions]

-

-
-
-
1           #include <math.h>
+
+
1 Synopsis
+           #include <math.h>
             double sqrt(double x);
             float sqrtf(float x);
             long double sqrtl(long double x);
     Description
 

-
-
+
 
2   The sqrt functions compute the nonnegative square root of x. A domain error occurs if
     the argument is less than zero.
     Returns
 

-
-
+
 
3   The sqrt functions return x.
-                              
+
 

-
-
+
 

 
7.12.8 [Error and gamma functions]

-
 Error and gamma functions
-

-
-
+
 

 
7.12.8.1 [The erf functions]

-

-
-
-
1           #include <math.h>
+
+
1 Synopsis
+           #include <math.h>
             double erf(double x);
             float erff(float x);
             long double erfl(long double x);
     Description
 

-
-
+
 
2   The erf functions compute the error function of x.
     Returns
 

-
-
+
 
3                                      2      x
                                                   e-t dt .
                                                      2
@@ -14471,188 +12581,155 @@ char int_p_sep_by_space
                                            0
 
 

-
-
+
 

 
7.12.8.2 [The erfc functions]

-

-
-
-
1           #include <math.h>
+
+
1 Synopsis
+           #include <math.h>
             double erfc(double x);
             float erfcf(float x);
             long double erfcl(long double x);
     Description
 

-
-
+
 
2   The erfc functions compute the complementary error function of x. A range error
     occurs if x is too large.
     Returns
 

-
-
-
3                                                       2      
+
+
3                                                       2
                                                                   e-t dt .
                                                                      2
     The erfc functions return erfc x = 1 - erf x =
                                                             x
 
 

-
-
+
 

 
7.12.8.3 [The lgamma functions]

-

-
-
-
1          #include <math.h>
+
+
1 Synopsis
+          #include <math.h>
            double lgamma(double x);
            float lgammaf(float x);
            long double lgammal(long double x);
     Description
 

-
-
+
 
2   The lgamma functions compute the natural logarithm of the absolute value of gamma of
     x. A range error occurs if x is too large. A pole error may occur if x is a negative integer
     or zero.
     Returns
 

-
-
+
 
3   The lgamma functions return loge | (x) |.
 

-
-
+
 

 
7.12.8.4 [The tgamma functions]

-

-
-
-
1          #include <math.h>
+
+
1 Synopsis
+          #include <math.h>
            double tgamma(double x);
            float tgammaf(float x);
            long double tgammal(long double x);
     Description
 

-
-
+
 
2   The tgamma functions compute the gamma function of x. A domain error or pole error
     may occur if x is a negative integer or zero. A range error occurs if the magnitude of x is
     too large and may occur if the magnitude of x is too small.
     Returns
 

-
-
+
 
3   The tgamma functions return (x).
 

-
-
+
 

 
7.12.9 [Nearest integer functions]

-
 Nearest integer functions
-

-
-
+
 

 
7.12.9.1 [The ceil functions]

-

-
-
-
1           #include <math.h>
+
+
1 Synopsis
+           #include <math.h>
             double ceil(double x);
             float ceilf(float x);
             long double ceill(long double x);
     Description
 

-
-
+
 
2   The ceil functions compute the smallest integer value not less than x.
     Returns
 

-
-
+
 
3   The ceil functions return x, expressed as a floating-point number.
 

-
-
+
 

 
7.12.9.2 [The floor functions]

-

-
-
-
1           #include <math.h>
+
+
1 Synopsis
+           #include <math.h>
             double floor(double x);
             float floorf(float x);
             long double floorl(long double x);
     Description
 

-
-
+
 
2   The floor functions compute the largest integer value not greater than x.
     Returns
 

-
-
+
 
3   The floor functions return x, expressed as a floating-point number.
 

-
-
+
 

 
7.12.9.3 [The nearbyint functions]

-

-
-
-
1           #include <math.h>
+
+
1 Synopsis
+           #include <math.h>
             double nearbyint(double x);
             float nearbyintf(float x);
             long double nearbyintl(long double x);
     Description
 

-
-
+
 
2   The nearbyint functions round their argument to an integer value in floating-point
     format, using the current rounding direction and without raising the ``inexact'' floating-
     point exception.
     Returns
 

-
-
+
 
3   The nearbyint functions return the rounded integer value.
 

-
-
+
 

 
7.12.9.4 [The rint functions]

-

-
-
-
1          #include <math.h>
+
+
1 Synopsis
+          #include <math.h>
            double rint(double x);
            float rintf(float x);
            long double rintl(long double x);
     Description
 

-
-
-
2   The rint functions differ from the nearbyint functions (7.12.9.3) only in that the
+
+
2   The rint functions differ from the nearbyint functions (7.12.9.3) only in that the
     rint functions may raise the ``inexact'' floating-point exception if the result differs in
     value from the argument.
     Returns
 

-
-
+
 
3   The rint functions return the rounded integer value.
 

-
-
+
 

 
7.12.9.5 [The lrint and llrint functions]

-

-
-
-
1          #include <math.h>
+
+
1 Synopsis
+          #include <math.h>
            long int lrint(double x);
            long int lrintf(float x);
            long int lrintl(long double x);
@@ -14661,50 +12738,42 @@ char int_p_sep_by_space
            long long int llrintl(long double x);
     Description
 

-
-
+
 
2   The lrint and llrint functions round their argument to the nearest integer value,
     rounding according to the current rounding direction. If the rounded value is outside the
     range of the return type, the numeric result is unspecified and a domain error or range
     error may occur.
     Returns
 

-
-
+
 
3   The lrint and llrint functions return the rounded integer value.
 

-
-
+
 

 
7.12.9.6 [The round functions]

-

-
-
-
1           #include <math.h>
+
+
1 Synopsis
+           #include <math.h>
             double round(double x);
             float roundf(float x);
             long double roundl(long double x);
     Description
 

-
-
+
 
2   The round functions round their argument to the nearest integer value in floating-point
     format, rounding halfway cases away from zero, regardless of the current rounding
     direction.
     Returns
 

-
-
+
 
3   The round functions return the rounded integer value.
 

-
-
+
 

 
7.12.9.7 [The lround and llround functions]

-

-
-
-
1           #include <math.h>
+
+
1 Synopsis
+           #include <math.h>
             long int lround(double x);
             long int lroundf(float x);
             long int lroundl(long double x);
@@ -14713,178 +12782,146 @@ char int_p_sep_by_space
             long long int llroundl(long double x);
     Description
 

-
-
+
 
2   The lround and llround functions round their argument to the nearest integer value,
     rounding halfway cases away from zero, regardless of the current rounding direction. If
     the rounded value is outside the range of the return type, the numeric result is unspecified
     and a domain error or range error may occur.
     Returns
 

-
-
+
 
3   The lround and llround functions return the rounded integer value.
 

-
-
+
 

 
7.12.9.8 [The trunc functions]

-

-
-
-
1           #include <math.h>
+
+
1 Synopsis
+           #include <math.h>
             double trunc(double x);
             float truncf(float x);
             long double truncl(long double x);
     Description
 

-
-
+
 
2   The trunc functions round their argument to the integer value, in floating format,
     nearest to but no larger in magnitude than the argument.
     Returns
 

-
-
+
 
3   The trunc functions return the truncated integer value.
 

-
-
+
 

 
7.12.10 [Remainder functions]

-
 Remainder functions
-

-
-
+
 

 
7.12.10.1 [The fmod functions]

-

-
-
-
1            #include <math.h>
+
+
1 Synopsis
+            #include <math.h>
              double fmod(double x, double y);
              float fmodf(float x, float y);
              long double fmodl(long double x, long double y);
     Description
 

-
-
+
 
2   The fmod functions compute the floating-point remainder of x/y.
     Returns
 

-
-
+
 
3   The fmod functions return the value x - ny, for some integer n such that, if y is nonzero,
     the result has the same sign as x and magnitude less than the magnitude of y. If y is zero,
     whether a domain error occurs or the fmod functions return zero is implementation-
     defined.
 

-
-
+
 

 
7.12.10.2 [The remainder functions]

-

-
-
-
1            #include <math.h>
+
+
1 Synopsis
+            #include <math.h>
              double remainder(double x, double y);
              float remainderf(float x, float y);
              long double remainderl(long double x, long double y);
     Description
 

-
-
-
2   The remainder functions compute the remainder x REM y required by IEC 60559.239)
-
-    Returns
+
+
2   The remainder functions compute the remainder x REM y required by IEC 60559.[239]
 

-
 
 
Footnote 239) ``When y  0, the remainder r = x REM y is defined regardless of the rounding mode by the
          mathematical relation r = x - ny , where n is the integer nearest the exact value of x / y ; whenever
          | n - x / y | = 1/2, then n is even. If r = 0, its sign shall be that of x .'' This definition is applicable for
          all implementations.
+    Returns
 

 
-
+
 
3   The remainder functions return x REM y. If y is zero, whether a domain error occurs
     or the functions return zero is implementation defined.
 

-
-
+
 

 
7.12.10.3 [The remquo functions]

-

-
-
-
1           #include <math.h>
+
+
1 Synopsis
+           #include <math.h>
             double remquo(double x, double y, int *quo);
             float remquof(float x, float y, int *quo);
             long double remquol(long double x, long double y,
                  int *quo);
     Description
 

-
-
+
 
2   The remquo functions compute the same remainder as the remainder functions. In
     the object pointed to by quo they store a value whose sign is the sign of x/y and whose
     magnitude is congruent modulo 2n to the magnitude of the integral quotient of x/y, where
     n is an implementation-defined integer greater than or equal to 3.
     Returns
 

-
-
+
 
3   The remquo functions return x REM y. If y is zero, the value stored in the object
     pointed to by quo is unspecified and whether a domain error occurs or the functions
     return zero is implementation defined.
 

-
-
+
 

 
7.12.11 [Manipulation functions]

-
 Manipulation functions
-

-
-
+
 

 
7.12.11.1 [The copysign functions]

-

-
-
-
1           #include <math.h>
+
+
1 Synopsis
+           #include <math.h>
             double copysign(double x, double y);
             float copysignf(float x, float y);
             long double copysignl(long double x, long double y);
     Description
 

-
-
+
 
2   The copysign functions produce a value with the magnitude of x and the sign of y.
     They produce a NaN (with the sign of y) if x is a NaN. On implementations that
     represent a signed zero but do not treat negative zero consistently in arithmetic
     operations, the copysign functions regard the sign of zero as positive.
     Returns
 

-
-
+
 
3   The copysign functions return a value with the magnitude of x and the sign of y.
 
 

-
-
+
 

 
7.12.11.2 [The nan functions]

-

-
-
-
1           #include <math.h>
+
+
1 Synopsis
+           #include <math.h>
             double nan(const char *tagp);
             float nanf(const char *tagp);
             long double nanl(const char *tagp);
     Description
 

-
-
+
 
2   The call nan("n-char-sequence") is equivalent to strtod("NAN(n-char-
     sequence)",     (char**)       NULL); the call nan("") is equivalent to
     strtod("NAN()", (char**) NULL). If tagp does not point to an n-char
@@ -14893,206 +12930,171 @@ char int_p_sep_by_space
     and strtold.
     Returns
 

-
-
+
 
3   The nan functions return a quiet NaN, if available, with content indicated through tagp.
     If the implementation does not support quiet NaNs, the functions return zero.
-    Forward references: the strtod, strtof, and strtold functions (7.22.1.3).
+    Forward references: the strtod, strtof, and strtold functions (7.22.1.3).
 

-
-
+
 

 
7.12.11.3 [The nextafter functions]

-

-
-
-
1           #include <math.h>
+
+
1 Synopsis
+           #include <math.h>
             double nextafter(double x, double y);
             float nextafterf(float x, float y);
             long double nextafterl(long double x, long double y);
     Description
 

-
-
+
 
2   The nextafter functions determine the next representable value, in the type of the
     function, after x in the direction of y, where x and y are first converted to the type of the
-    function.240) The nextafter functions return y if x equals y. A range error may occur
+    function.[240] The nextafter functions return y if x equals y. A range error may occur
     if the magnitude of x is the largest finite value representable in the type and the result is
     infinite or not representable in the type.
     Returns
 

-
 
 
Footnote 240) The argument values are converted to the type of the function, even by a macro implementation of the
          function.
 

 
-
+
 
3   The nextafter functions return the next representable value in the specified format
     after x in the direction of y.
 
 

-
-
+
 

 
7.12.11.4 [The nexttoward functions]

-

-
-
-
1           #include <math.h>
+
+
1 Synopsis
+           #include <math.h>
             double nexttoward(double x, long double y);
             float nexttowardf(float x, long double y);
             long double nexttowardl(long double x, long double y);
     Description
 

-
-
+
 
2   The nexttoward functions are equivalent to the nextafter functions except that the
     second parameter has type long double and the functions return y converted to the
-    type of the function if x equals y.241)
+    type of the function if x equals y.[241]
 

-
 
 
Footnote 241) The result of the nexttoward functions is determined in the type of the function, without loss of
          range or precision in a floating second argument.
+    Description
 

 
-
+
 

 
7.12.12 [Maximum, minimum, and positive difference functions]

-
 Maximum, minimum, and positive difference functions
-

-
-
+
 

 
7.12.12.1 [The fdim functions]

-

-
-
-
1           #include <math.h>
+
+
1 Synopsis
+           #include <math.h>
             double fdim(double x, double y);
             float fdimf(float x, float y);
             long double fdiml(long double x, long double y);
     Description
 

-
-
+
 
2   The fdim functions determine the positive difference between their arguments:
           x - y if x > y
-          
+
           +0      if x  y
     A range error may occur.
     Returns
 

-
-
+
 
3   The fdim functions return the positive difference value.
 

-
-
+
 

 
7.12.12.2 [The fmax functions]

-

-
-
-
1           #include <math.h>
+
+
1 Synopsis
+           #include <math.h>
             double fmax(double x, double y);
             float fmaxf(float x, float y);
             long double fmaxl(long double x, long double y);
-
-    Description
 

-
-
-
2   The fmax functions determine the maximum numeric value of their arguments.242)
+
+
2   The fmax functions determine the maximum numeric value of their arguments.[242]
     Returns
 

-
 
 
Footnote 242) NaN arguments are treated as missing data: if one argument is a NaN and the other numeric, then the
-         fmax functions choose the numeric value. See F.10.9.2.
+         fmax functions choose the numeric value. See F.10.9.2.
 

 
-
+
 
3   The fmax functions return the maximum numeric value of their arguments.
 

-
-
+
 

 
7.12.12.3 [The fmin functions]

-

-
-
-
1           #include <math.h>
+
+
1 Synopsis
+           #include <math.h>
             double fmin(double x, double y);
             float fminf(float x, float y);
             long double fminl(long double x, long double y);
     Description
 

-
-
-
2   The fmin functions determine the minimum numeric value of their arguments.243)
+
+
2   The fmin functions determine the minimum numeric value of their arguments.[243]
     Returns
 

-
 
 
Footnote 243) The fmin functions are analogous to the fmax functions in their treatment of NaNs.
 

 
-
+
 
3   The fmin functions return the minimum numeric value of their arguments.
 

-
-
+
 

 
7.12.13 [Floating multiply-add]

-
 Floating multiply-add
-

-
-
+
 

 
7.12.13.1 [The fma functions]

-

-
-
-
1           #include <math.h>
+
+
1 Synopsis
+           #include <math.h>
             double fma(double x, double y, double z);
             float fmaf(float x, float y, float z);
             long double fmal(long double x, long double y,
                  long double z);
     Description
 

-
-
-
2   The fma functions compute (x × y) + z, rounded as one ternary operation: they compute
+
+
2   The fma functions compute (x \xD7 y) + z, rounded as one ternary operation: they compute
     the value (as if) to infinite precision and round once to the result format, according to the
     current rounding mode. A range error may occur.
     Returns
 

-
-
-
3   The fma functions return (x × y) + z, rounded as one ternary operation.
+
+
3   The fma functions return (x \xD7 y) + z, rounded as one ternary operation.
 
 

-
-
+
 

 
7.12.14 [Comparison macros]

-

-
-
+
 
1   The relational and equality operators support the usual mathematical relationships
     between numeric values. For any ordered pair of numeric values exactly one of the
     relationships -- less, greater , and equal -- is true. Relational operators may raise the
     ``invalid'' floating-point exception when argument values are NaNs. For a NaN and a
-    numeric value, or for two NaNs, just the unordered relationship is true.244) The following
+    numeric value, or for two NaNs, just the unordered relationship is true.[244] The following
     subclauses provide macros that are quiet (non floating-point exception raising) versions
     of the relational operators, and other comparison macros that facilitate writing efficient
     code that accounts for NaNs without suffering the ``invalid'' floating-point exception. In
     the synopses in this subclause, real-floating indicates that the argument shall be an
-    expression of real floating type245) (both arguments need not have the same type).246)
+    expression of real floating type[245] (both arguments need not have the same type).[246]
 

-
 
 
Footnote 244) IEC 60559 requires that the built-in relational operators raise the ``invalid'' floating-point exception if
          the operands compare unordered, as an error indicator for programs written without consideration of
@@ -15107,113 +13109,94 @@ char int_p_sep_by_space
 
 
Footnote 246) Whether an argument represented in a format wider than its semantic type is converted to the semantic
          type is unspecified.
+    Description
 

 
-
+
 

 
7.12.14.1 [The isgreater macro]

-

-
-
-
1            #include <math.h>
+
+
1 Synopsis
+            #include <math.h>
              int isgreater(real-floating x, real-floating y);
     Description
 

-
-
+
 
2   The isgreater macro determines whether its first argument is greater than its second
     argument. The value of isgreater(x, y) is always equal to (x) > (y); however,
     unlike (x) > (y), isgreater(x, y) does not raise the ``invalid'' floating-point
     exception when x and y are unordered.
     Returns
 

-
-
+
 
3   The isgreater macro returns the value of (x) > (y).
 

-
-
+
 

 
7.12.14.2 [The isgreaterequal macro]

-

-
-
-
1            #include <math.h>
+
+
1 Synopsis
+            #include <math.h>
              int isgreaterequal(real-floating x, real-floating y);
-
-    Description
 

-
-
+
 
2   The isgreaterequal macro determines whether its first argument is greater than or
     equal to its second argument. The value of isgreaterequal(x, y) is always equal
     to (x) >= (y); however, unlike (x) >= (y), isgreaterequal(x, y) does
     not raise the ``invalid'' floating-point exception when x and y are unordered.
     Returns
 

-
-
+
 
3   The isgreaterequal macro returns the value of (x) >= (y).
 

-
-
+
 

 
7.12.14.3 [The isless macro]

-

-
-
-
1         #include <math.h>
+
+
1 Synopsis
+         #include <math.h>
           int isless(real-floating x, real-floating y);
     Description
 

-
-
+
 
2   The isless macro determines whether its first argument is less than its second
     argument. The value of isless(x, y) is always equal to (x) < (y); however,
     unlike (x) < (y), isless(x, y) does not raise the ``invalid'' floating-point
     exception when x and y are unordered.
     Returns
 

-
-
+
 
3   The isless macro returns the value of (x) < (y).
 

-
-
+
 

 
7.12.14.4 [The islessequal macro]

-

-
-
-
1         #include <math.h>
+
+
1 Synopsis
+         #include <math.h>
           int islessequal(real-floating x, real-floating y);
     Description
 

-
-
+
 
2   The islessequal macro determines whether its first argument is less than or equal to
     its second argument. The value of islessequal(x, y) is always equal to
     (x) <= (y); however, unlike (x) <= (y), islessequal(x, y) does not raise
     the ``invalid'' floating-point exception when x and y are unordered.
     Returns
 

-
-
+
 
3   The islessequal macro returns the value of (x) <= (y).
 

-
-
+
 

 
7.12.14.5 [The islessgreater macro]

-

-
-
-
1           #include <math.h>
+
+
1 Synopsis
+           #include <math.h>
             int islessgreater(real-floating x, real-floating y);
     Description
 

-
-
+
 
2   The islessgreater macro determines whether its first argument is less than or
     greater than its second argument. The islessgreater(x, y) macro is similar to
     (x) < (y) || (x) > (y); however, islessgreater(x, y) does not raise
@@ -15221,47 +13204,42 @@ char int_p_sep_by_space
     and y twice).
     Returns
 

-
-
+
 
3   The islessgreater macro returns the value of (x) < (y) || (x) > (y).
 

-
-
+
 

 
7.12.14.6 [The isunordered macro]

-

-
-
-
1           #include <math.h>
+
+
1 Synopsis
+           #include <math.h>
             int isunordered(real-floating x, real-floating y);
     Description
 

-
-
+
 
2   The isunordered macro determines whether its arguments are unordered.
     Returns
 

-
-
+
 
3   The isunordered macro returns 1 if its arguments are unordered and 0 otherwise.
 

-
-
+
 

-
7.13 [Nonlocal jumps ]

-

-
-
+
7.13 [Nonlocal jumps <setjmp.h>]

+
 
1   The header <setjmp.h> defines the macro setjmp, and declares one function and
-    one type, for bypassing the normal function call and return discipline.247)
+    one type, for bypassing the normal function call and return discipline.[247]
 

-
 
 
Footnote 247) These functions are useful for dealing with unusual conditions encountered in a low-level function of
          a program.
+        expression of a selection or iteration statement;
+    -- the operand of a unary ! operator with the resulting expression being the entire
+       controlling expression of a selection or iteration statement; or
+    -- the entire expression of an expression statement (possibly cast to void).
 

 
-
+
 
2   The type declared is
             jmp_buf
     which is an array type suitable for holding the information needed to restore a calling
@@ -15271,93 +13249,71 @@ char int_p_sep_by_space
     floating-point status flags, of open files, or of any other component of the abstract
     machine.
 

-
-
+
 
3   It is unspecified whether setjmp is a macro or an identifier declared with external
     linkage. If a macro definition is suppressed in order to access an actual function, or a
     program defines an external identifier with the name setjmp, the behavior is undefined.
 

-
-
+
 

 
7.13.1 [Save calling environment]

-
 Save calling environment
-

-
-
+
 

 
7.13.1.1 [The setjmp macro]

-

-
-
-
1           #include <setjmp.h>
+
+
1 Synopsis
+           #include <setjmp.h>
             int setjmp(jmp_buf env);
     Description
 

-
-
+
 
2   The setjmp macro saves its calling environment in its jmp_buf argument for later use
     by the longjmp function.
     Returns
 

-
-
+
 
3   If the return is from a direct invocation, the setjmp macro returns the value zero. If the
     return is from a call to the longjmp function, the setjmp macro returns a nonzero
     value.
     Environmental limits
 

-
-
+
 
4   An invocation of the setjmp macro shall appear only in one of the following contexts:
     -- the entire controlling expression of a selection or iteration statement;
     -- one operand of a relational or equality operator with the other operand an integer
        constant expression, with the resulting expression being the entire controlling
-
-        expression of a selection or iteration statement;
-    -- the operand of a unary ! operator with the resulting expression being the entire
-       controlling expression of a selection or iteration statement; or
-    -- the entire expression of an expression statement (possibly cast to void).
 

-
-
+
 
5   If the invocation appears in any other context, the behavior is undefined.
 

-
-
+
 

 
7.13.2 [Restore calling environment]

-
 Restore calling environment
-

-
-
+
 

 
7.13.2.1 [The longjmp function]

-

-
-
-
1            #include <setjmp.h>
+
+
1 Synopsis
+            #include <setjmp.h>
              _Noreturn void longjmp(jmp_buf env, int val);
     Description
 

-
-
+
 
2   The longjmp function restores the environment saved by the most recent invocation of
     the setjmp macro in the same invocation of the program with the corresponding
     jmp_buf argument. If there has been no such invocation, or if the invocation was from
     another thread of execution, or if the function containing the invocation of the setjmp
-    macro has terminated execution248) in the interim, or if the invocation of the setjmp
+    macro has terminated execution[248] in the interim, or if the invocation of the setjmp
     macro was within the scope of an identifier with variably modified type and execution has
     left that scope in the interim, the behavior is undefined.
 

-
 
 
Footnote 248) For example, by executing a return statement or because another longjmp call has caused a
          transfer to a setjmp invocation in a function earlier in the set of nested calls.
 

 
-
-
3   All accessible objects have values, and all other components of the abstract machine249)
+
+
3   All accessible objects have values, and all other components of the abstract machine[249]
     have state, as of the time the longjmp function was called, except that the values of
     objects of automatic storage duration that are local to the function containing the
     invocation of the corresponding setjmp macro that do not have volatile-qualified type
@@ -15365,22 +13321,8 @@ char int_p_sep_by_space
     indeterminate.
     Returns
 

-
 
 
Footnote 249) This includes, but is not limited to, the floating-point status flags and the state of open files.
-

-
-
-
4   After longjmp is completed, thread execution continues as if the corresponding
-    invocation of the setjmp macro had just returned the value specified by val. The
-    longjmp function cannot cause the setjmp macro to return the value 0; if val is 0,
-    the setjmp macro returns the value 1.
-

-
-
-
5   EXAMPLE The longjmp function that returns control back to the point of the setjmp invocation
-    might cause memory associated with a variable length array object to be squandered.
-
       #include <setjmp.h>
       jmp_buf buf;
       void g(int n);
@@ -15402,26 +13344,32 @@ char int_p_sep_by_space
             int b[n];             // b may remain allocated
             longjmp(buf, 2);      // might cause memory loss
       }
+

+
+
+
4   After longjmp is completed, thread execution continues as if the corresponding
+    invocation of the setjmp macro had just returned the value specified by val. The
+    longjmp function cannot cause the setjmp macro to return the value 0; if val is 0,
+    the setjmp macro returns the value 1.
 

-
-
+
+
5   EXAMPLE The longjmp function that returns control back to the point of the setjmp invocation
+    might cause memory associated with a variable length array object to be squandered.
+

+
 

-
7.14 [Signal handling ]

-

-
-
+
7.14 [Signal handling <signal.h>]

+
 
1   The header <signal.h> declares a type and two functions and defines several macros,
     for handling various signals (conditions that may be reported during program execution).
 

-
-
+
 
2   The type defined is
              sig_atomic_t
     which is the (possibly volatile-qualified) integer type of an object that can be accessed as
     an atomic entity, even in the presence of asynchronous interrupts.
 

-
-
+
 
3   The macros defined are
              SIG_DFL
              SIG_ERR
@@ -15439,56 +13387,48 @@ char int_p_sep_by_space
              SIGSEGV an invalid access to storage
              SIGTERM a termination request sent to the program
 

-
-
+
 
4   An implementation need not generate any of these signals, except as a result of explicit
     calls to the raise function. Additional signals and pointers to undeclarable functions,
     with macro definitions beginning, respectively, with the letters SIG and an uppercase
-    letter or with SIG_ and an uppercase letter,250) may also be specified by the
+    letter or with SIG_ and an uppercase letter,[250] may also be specified by the
     implementation. The complete set of signals, their semantics, and their default handling
     is implementation-defined; all signal numbers shall be positive.
 
 

-
 
-
Footnote 250) See ``future library directions'' (7.31.7). The names of the signal numbers reflect the following terms
+
Footnote 250) See ``future library directions'' (7.31.7). The names of the signal numbers reflect the following terms
          (respectively): abort, floating-point exception, illegal instruction, interrupt, segmentation violation,
          and termination.
 

 
-
+
 

 
7.14.1 [Specify signal handling]

-
 Specify signal handling
-

-
-
+
 

 
7.14.1.1 [The signal function]

-

-
-
-
1            #include <signal.h>
+
+
1 Synopsis
+            #include <signal.h>
              void (*signal(int sig, void (*func)(int)))(int);
     Description
 

-
-
+
 
2   The signal function chooses one of three ways in which receipt of the signal number
     sig is to be subsequently handled. If the value of func is SIG_DFL, default handling
     for that signal will occur. If the value of func is SIG_IGN, the signal will be ignored.
     Otherwise, func shall point to a function to be called when that signal occurs. An
     invocation of such a function because of a signal, or (recursively) of any further functions
-    called by that invocation (other than functions in the standard library),251) is called a
+    called by that invocation (other than functions in the standard library),[251] is called a
     signal handler .
 

-
 
 
Footnote 251) This includes functions called indirectly via standard library functions (e.g., a SIGABRT handler
          called via the abort function).
 

 
-
+
 
3   When a signal occurs and func points to a function, it is implementation-defined
     whether the equivalent of signal(sig, SIG_DFL); is executed or the
     implementation prevents some implementation-defined set of signals (at least including
@@ -15499,13 +13439,11 @@ char int_p_sep_by_space
     value corresponding to a computational exception, the behavior is undefined; otherwise
     the program will resume execution at the point it was interrupted.
 

-
-
+
 
4   If the signal occurs as the result of calling the abort or raise function, the signal
     handler shall not call the raise function.
 

-
-
+
 
5   If the signal occurs other than as the result of calling the abort or raise function, the
     behavior is undefined if the signal handler refers to any object with static or thread
     storage duration that is not a lock-free atomic object other than by assigning a value to an
@@ -15514,15 +13452,14 @@ char int_p_sep_by_space
     quick_exit function, or the signal function with the first argument equal to the
     signal number corresponding to the signal that caused the invocation of the handler.
     Furthermore, if such a call to the signal function results in a SIG_ERR return, the
-    value of errno is indeterminate.252)
+    value of errno is indeterminate.[252]
 
 

-
 
 
Footnote 252) If any signal is generated by an asynchronous signal handler, the behavior is undefined.
 

 
-
+
 
6   At program startup, the equivalent of
             signal(sig, SIG_IGN);
     may be executed for some signals selected in an implementation-defined manner; the
@@ -15530,93 +13467,74 @@ char int_p_sep_by_space
             signal(sig, SIG_DFL);
     is executed for all other signals defined by the implementation.
 

-
-
+
 
7   Use of this function in a multi-threaded program results in undefined behavior. The
     implementation shall behave as if no library function calls the signal function.
     Returns
 

-
-
+
 
8   If the request can be honored, the signal function returns the value of func for the
     most recent successful call to signal for the specified signal sig. Otherwise, a value of
     SIG_ERR is returned and a positive value is stored in errno.
-    Forward references: the abort function (7.22.4.1), the exit function (7.22.4.4), the
-    _Exit function (7.22.4.5), the quick_exit function (7.22.4.7).
+    Forward references: the abort function (7.22.4.1), the exit function (7.22.4.4), the
+    _Exit function (7.22.4.5), the quick_exit function (7.22.4.7).
 

-
-
+
 

 
7.14.2 [Send signal]

-
 Send signal
-

-
-
+
 

 
7.14.2.1 [The raise function]

-

-
-
-
1           #include <signal.h>
+
+
1 Synopsis
+           #include <signal.h>
             int raise(int sig);
     Description
 

-
-
-
2   The raise function carries out the actions described in 7.14.1.1 for the signal sig. If a
+
+
2   The raise function carries out the actions described in 7.14.1.1 for the signal sig. If a
     signal handler is called, the raise function shall not return until after the signal handler
     does.
     Returns
 

-
-
+
 
3   The raise function returns zero if successful, nonzero if unsuccessful.
 

-
-
+
 

-
7.15 [Alignment ]

-

-
-
+
7.15 [Alignment <stdalign.h>]

+
 
1   The header <stdalign.h> defines four macros.
 

-
-
+
 
2   The macro
            alignas
     expands to _Alignas; the macro
            alignof
     expands to _Alignof.
 

-
-
+
 
3   The remaining macros are suitable for use in #if preprocessing directives. They are
            _ _alignas_is_defined
     and
            _ _alignof_is_defined
     which both expand to the integer constant 1.
 

-
-
+
 

-
7.16 [Variable arguments ]

-

-
-
+
7.16 [Variable arguments <stdarg.h>]

+
 
1   The header <stdarg.h> declares a type and defines four macros, for advancing
     through a list of arguments whose number and types are not known to the called function
     when it is translated.
 

-
-
+
 
2   A function may be called with a variable number of arguments of varying types. As
-    described in 6.9.1, its parameter list contains one or more parameters. The rightmost
+    described in 6.9.1, its parameter list contains one or more parameters. The rightmost
     parameter plays a special role in the access mechanism, and will be designated parmN in
     this description.
 

-
-
+
 
3   The type declared is
             va_list
     which is a complete object type suitable for holding information needed by the macros
@@ -15625,45 +13543,11 @@ char int_p_sep_by_space
     subclause) having type va_list. The object ap may be passed as an argument to
     another function; if that function invokes the va_arg macro with parameter ap, the
     value of ap in the calling function is indeterminate and shall be passed to the va_end
-    macro prior to any further reference to ap.253)
+    macro prior to any further reference to ap.[253]
 

-
 
 
Footnote 253) It is permitted to create a pointer to a va_list and pass that pointer to another function, in which
          case the original function may make further use of the original list after the other function returns.
-

-
-
-

-
7.16.1 [Variable argument list access macros]

-

-
-
-
1   The va_start and va_arg macros described in this subclause shall be implemented
-    as macros, not functions. It is unspecified whether va_copy and va_end are macros or
-    identifiers declared with external linkage. If a macro definition is suppressed in order to
-    access an actual function, or a program defines an external identifier with the same name,
-    the behavior is undefined. Each invocation of the va_start and va_copy macros
-    shall be matched by a corresponding invocation of the va_end macro in the same
-    function.
-

-
-
-

-
7.16.1.1 [The va_arg macro]

-

-
-
-
1           #include <stdarg.h>
-            type va_arg(va_list ap, type);
-    Description
-

-
-
-
2   The va_arg macro expands to an expression that has the specified type and the value of
-    the next argument in the call. The parameter ap shall have been initialized by the
-    va_start or va_copy macro (without an intervening invocation of the va_end
-
     macro for the same ap). Each invocation of the va_arg macro modifies ap so that the
     values of successive arguments are returned in turn. The parameter type shall be a type
     name specified such that the type of a pointer to an object that has the specified type can
@@ -15675,26 +13559,49 @@ char int_p_sep_by_space
        type, and the value is representable in both types;
     -- one type is pointer to void and the other is a pointer to a character type.
     Returns
-

+

 
-
+
+

+
7.16.1 [Variable argument list access macros]

+
+
1   The va_start and va_arg macros described in this subclause shall be implemented
+    as macros, not functions. It is unspecified whether va_copy and va_end are macros or
+    identifiers declared with external linkage. If a macro definition is suppressed in order to
+    access an actual function, or a program defines an external identifier with the same name,
+    the behavior is undefined. Each invocation of the va_start and va_copy macros
+    shall be matched by a corresponding invocation of the va_end macro in the same
+    function.
+

+
+

+
7.16.1.1 [The va_arg macro]

+
+
1 Synopsis
+           #include <stdarg.h>
+            type va_arg(va_list ap, type);
+    Description
+

+
+
2   The va_arg macro expands to an expression that has the specified type and the value of
+    the next argument in the call. The parameter ap shall have been initialized by the
+    va_start or va_copy macro (without an intervening invocation of the va_end
+

+
 
3   The first invocation of the va_arg macro after that of the va_start macro returns the
     value of the argument after that specified by parmN . Successive invocations return the
     values of the remaining arguments in succession.
 

-
-
+
 

 
7.16.1.2 [The va_copy macro]

-

-
-
-
1          #include <stdarg.h>
+
+
1 Synopsis
+          #include <stdarg.h>
            void va_copy(va_list dest, va_list src);
     Description
 

-
-
+
 
2   The va_copy macro initializes dest as a copy of src, as if the va_start macro had
     been applied to dest followed by the same sequence of uses of the va_arg macro as
     had previously been used to reach the present state of src. Neither the va_copy nor
@@ -15702,23 +13609,19 @@ char int_p_sep_by_space
     invocation of the va_end macro for the same dest.
     Returns
 

-
-
+
 
3   The va_copy macro returns no value.
 

-
-
+
 

 
7.16.1.3 [The va_end macro]

-

-
-
-
1          #include <stdarg.h>
+
+
1 Synopsis
+          #include <stdarg.h>
            void va_end(va_list ap);
     Description
 

-
-
+
 
2   The va_end macro facilitates a normal return from the function whose variable
     argument list was referred to by the expansion of the va_start macro, or the function
     containing the expansion of the va_copy macro, that initialized the va_list ap. The
@@ -15729,33 +13632,27 @@ char int_p_sep_by_space
     return, the behavior is undefined.
     Returns
 

-
-
+
 
3   The va_end macro returns no value.
 

-
-
+
 

 
7.16.1.4 [The va_start macro]

-

-
-
-
1           #include <stdarg.h>
+
+
1 Synopsis
+           #include <stdarg.h>
             void va_start(va_list ap, parmN);
     Description
 

-
-
+
 
2   The va_start macro shall be invoked before any access to the unnamed arguments.
 

-
-
+
 
3   The va_start macro initializes ap for subsequent use by the va_arg and va_end
     macros. Neither the va_start nor va_copy macro shall be invoked to reinitialize ap
     without an intervening invocation of the va_end macro for the same ap.
 

-
-
+
 
4   The parameter parmN is the identifier of the rightmost parameter in the variable
     parameter list in the function definition (the one just before the , ...). If the parameter
     parmN is declared with the register storage class, with a function or array type, or
@@ -15763,12 +13660,10 @@ char int_p_sep_by_space
     argument promotions, the behavior is undefined.
     Returns
 

-
-
+
 
5   The va_start macro returns no value.
 

-
-
+
 
6   EXAMPLE 1 The function f1 gathers into an array a list of arguments that are pointers to strings (but not
     more than MAXARGS arguments), then passes the array as a single argument to function f2. The number of
     pointers is specified by the first argument to f1.
@@ -15791,8 +13686,7 @@ char int_p_sep_by_space
              void f1(int, ...);
 
 

-
-
+
 
7   EXAMPLE 2 The function f3 is similar, but saves the status of the variable argument list after the
     indicated number of arguments; after f2 has been called once with the whole list, the trailing part of the list
     is gathered again and passed to function f4.
@@ -15822,33 +13716,28 @@ char int_p_sep_by_space
                       f4(n_ptrs, array);
              }
 

-
-
+
 

-
7.17 [Atomics ]

-
 Atomics 
-

-
-
+
7.17 [Atomics <stdatomic.h>]

+
 

 
7.17.1 [Introduction]

-

-
-
+
 
1   The header <stdatomic.h> defines several macros and declares several types and
-    functions for performing atomic operations on data shared between threads.254)
+    functions for performing atomic operations on data shared between threads.[254]
 

-
 
-
Footnote 254) See ``future library directions'' (7.31.8).
+
Footnote 254) See ``future library directions'' (7.31.8).
+    -- The functions not ending in _explicit have the same semantics as the
+       corresponding _explicit function with memory_order_seq_cst for the
+       memory_order argument.
 

 
-
+
 
2   Implementations that define the macro _ _STDC_NO_ATOMICS_ _ need not provide
     this header nor support any of its facilities.
 

-
-
+
 
3   The macros defined are the atomic lock-free macros
              ATOMIC_BOOL_LOCK_FREE
              ATOMIC_CHAR_LOCK_FREE
@@ -15865,53 +13754,40 @@ char int_p_sep_by_space
              ATOMIC_FLAG_INIT
     which expands to an initializer for an object of type atomic_flag.
 

-
-
+
 
4   The types include
               memory_order
     which is an enumerated type whose enumerators identify memory ordering constraints;
               atomic_flag
-    which is a structure type representing a lock-free, primitive atomic flag; and several 
+    which is a structure type representing a lock-free, primitive atomic flag; and several
     atomic analogs of integer types.
 

-
-
+
 
5   In the following synopses:
     -- An A refers to one of the atomic types.
-    -- A C refers to its corresponding non-atomic type.                                        
+    -- A C refers to its corresponding non-atomic type.
     -- An M refers to the type of the other argument for arithmetic operations. For atomic
        integer types, M is C . For atomic pointer types, M is ptrdiff_t.
-
-    -- The functions not ending in _explicit have the same semantics as the
-       corresponding _explicit function with memory_order_seq_cst for the
-       memory_order argument.
 

-
-
+
 
6   NOTE Many operations are volatile-qualified. The ``volatile as device register'' semantics have not
     changed in the standard. This qualification means that volatility is preserved when applying these
     operations to volatile objects.
 
 

-
-
+
 

 
7.17.2 [Initialization]

-
 Initialization
-

-
-
+
 

 
7.17.2.1 [The ATOMIC_VAR_INIT macro]

-

-
-
-
1           #include <stdatomic.h>
+
+
1 Synopsis
+           #include <stdatomic.h>
             #define ATOMIC_VAR_INIT(C value)
     Description
 

-
-
+
 
2   The ATOMIC_VAR_INIT macro expands to a token sequence suitable for initializing an
     atomic object of a type that is initialization-compatible with value. An atomic object
     with automatic storage duration that is not explicitly initialized using
@@ -15919,62 +13795,51 @@ char int_p_sep_by_space
     initialization for objects with static or thread-local storage duration is guaranteed to
     produce a valid state.
 

-
-
+
 
3   Concurrent access to the variable being initialized, even via an atomic operation,
     constitutes a data race.
 

-
-
+
 
4   EXAMPLE
             atomic_int guide = ATOMIC_VAR_INIT(42);
 
 

-
-
+
 

 
7.17.2.2 [The atomic_init generic function]

-

-
-
-
1           #include <stdatomic.h>
+
+
1 Synopsis
+           #include <stdatomic.h>
             void atomic_init(volatile A *obj, C value);
     Description
 

-
-
+
 
2   The atomic_init generic function initializes the atomic object pointed to by obj to
     the value value, while also initializing any additional state that the implementation
     might need to carry for the atomic object.
 

-
-
+
 
3   Although this function initializes an atomic object, it does not avoid data races;
     concurrent access to the variable being initialized, even via an atomic operation,
     constitutes a data race.
     Returns
 

-
-
+
 
4   The atomic_init generic function returns no value.
 

-
-
+
 
5   EXAMPLE
               atomic_int guide;
               atomic_init(&guide, 42);
 
 

-
-
+
 

 
7.17.3 [Order and consistency]

-

-
-
+
 
1   The enumerated type memory_order specifies the detailed regular (non-atomic)
-    memory synchronization operations as defined in 5.1.2.4 and may provide for operation
-    ordering. Its enumeration constants are as follows:255)
+    memory synchronization operations as defined in 5.1.2.4 and may provide for operation
+    ordering. Its enumeration constants are as follows:[255]
              memory_order_relaxed
              memory_order_consume
              memory_order_acquire
@@ -15982,33 +13847,30 @@ char int_p_sep_by_space
              memory_order_acq_rel
              memory_order_seq_cst
 

-
 
-
Footnote 255) See ``future library directions'' (7.31.8).
+
Footnote 255) See ``future library directions'' (7.31.8).
+     -- if A does not exist, the result of some modification of M in the visible sequence of
+        side effects with respect to B that is not memory_order_seq_cst.
 

 
-
+
 
2   For memory_order_relaxed, no operation orders memory.
 

-
-
+
 
3   For       memory_order_release,       memory_order_acq_rel,             and
     memory_order_seq_cst, a store operation performs a release operation on the
     affected memory location.
 

-
-
+
 
4   For       memory_order_acquire,       memory_order_acq_rel,             and
     memory_order_seq_cst, a load operation performs an acquire operation on the
     affected memory location.
 

-
-
+
 
5   For memory_order_consume, a load operation performs a consume operation on the
     affected memory location.
 

-
-
+
 
6   There shall be a single total order S on all memory_order_seq_cst operations,
     consistent with the ``happens before'' order and modification orders for all affected
     locations, such that each memory_order_seq_cst operation B that loads a value
@@ -16017,75 +13879,56 @@ char int_p_sep_by_space
     -- if A exists, the result of some modification of M in the visible sequence of side
        effects with respect to B that is not memory_order_seq_cst and that does not
        happen before A, or
-
-     -- if A does not exist, the result of some modification of M in the visible sequence of
-        side effects with respect to B that is not memory_order_seq_cst.
 

-
-
+
 
7    NOTE 1 Although it is not explicitly required that S include lock operations, it can always be extended to
      an order that does include lock and unlock operations, since the ordering between those is already included
      in the ``happens before'' ordering.
 
 

-
-
+
 
8    NOTE 2 Atomic operations specifying memory_order_relaxed are relaxed only with respect to
      memory ordering. Implementations must still guarantee that any given atomic access to a particular atomic
      object be indivisible with respect to all other atomic accesses to that object.
 
 

-
-
+
 
9    For an atomic operation B that reads the value of an atomic object M , if there is a
      memory_order_seq_cst fence X sequenced before B, then B observes either the
      last memory_order_seq_cst modification of M preceding X in the total order S or
      a later modification of M in its modification order.
 

-
-
+
 
10   For atomic operations A and B on an atomic object M , where A modifies M and B takes
      its value, if there is a memory_order_seq_cst fence X such that A is sequenced
      before X and B follows X in S , then B observes either the effects of A or a later
      modification of M in its modification order.
 

-
-
+
 
11   For atomic operations A and B on an atomic object M , where A modifies M and B takes
      its value, if there are memory_order_seq_cst fences X and Y such that A is
      sequenced before X , Y is sequenced before B, and X precedes Y in S , then B observes
      either the effects of A or a later modification of M in its modification order.
 

-
-
+
 
12   Atomic read-modify-write operations shall always read the last value (in the modification
      order) stored before the write associated with the read-modify-write operation.
 

-
-
+
 
13   An atomic store shall only store a value that has been computed from constants and
      program input values by a finite sequence of program evaluations, such that each
      evaluation observes the values of variables as computed by the last prior assignment in
-     the sequence.256) The ordering of evaluations in this sequence shall be such that
+     the sequence.[256] The ordering of evaluations in this sequence shall be such that
      -- If an evaluation B observes a value computed by A in a different thread, then B does
         not happen before A.
      -- If an evaluation A is included in the sequence, then all evaluations that assign to the
         same variable and happen before A are also included.
 

-
 
 
Footnote 256) Among other implications, atomic variables shall not decay.
-

-
-
-
14   NOTE 3 The second requirement disallows ``out-of-thin-air'', or ``speculative'' stores of atomics when
-     relaxed atomics are used. Since unordered operations are involved, evaluations may appear in this
-     sequence out of thread order. For example, with x and y initially zero,
-
                // Thread 1:
                r1 = atomic_load_explicit(&y, memory_order_relaxed);
                atomic_store_explicit(&x, r1, memory_order_relaxed);
-
                // Thread 2:
                r2 = atomic_load_explicit(&x, memory_order_relaxed);
                atomic_store_explicit(&y, 42, memory_order_relaxed);
@@ -16098,18 +13941,21 @@ char int_p_sep_by_space
                // Thread 1:
                r1 = atomic_load_explicit(&y, memory_order_relaxed);
                atomic_store_explicit(&x, r1, memory_order_relaxed);
-
                // Thread 2:
                r2 = atomic_load_explicit(&x, memory_order_relaxed);
                atomic_store_explicit(&y, r2, memory_order_relaxed);
      is not allowed to produce r1 == 42 && r2 = 42, since there is no sequence of evaluations that results
      in the computation of 42. In the absence of ``relaxed'' operations and read-modify-write operations with
      weaker than memory_order_acq_rel ordering, the second requirement has no impact.
-
      Recommended practice
-

+

 
-
+
+
14   NOTE 3 The second requirement disallows ``out-of-thin-air'', or ``speculative'' stores of atomics when
+     relaxed atomics are used. Since unordered operations are involved, evaluations may appear in this
+     sequence out of thread order. For example, with x and y initially zero,
+

+
 
15   The requirements do not forbid r1 == 42 && r2 == 42 in the following example,
      with x and y initially zero:
              // Thread 1:
@@ -16123,79 +13969,65 @@ char int_p_sep_by_space
                   atomic_store_explicit(&x, 42, memory_order_relaxed);
      However, this is not useful behavior, and implementations should not allow it.
 

-
-
+
 
16   Implementations should make atomic stores visible to atomic loads within a reasonable
      amount of time.
 

-
-
+
 

 
7.17.3.1 [The kill_dependency macro]

-

-
-
-
1          #include <stdatomic.h>
+
+
1 Synopsis
+          #include <stdatomic.h>
            type kill_dependency(type y);
     Description
 

-
-
+
 
2   The kill_dependency macro terminates a dependency chain; the argument does not
     carry a dependency to the return value.
     Returns
 

-
-
+
 
3   The kill_dependency macro returns the value of y.
 

-
-
+
 

 
7.17.4 [Fences]

-

-
-
+
 
1   This subclause introduces synchronization primitives called fences. Fences can have
     acquire semantics, release semantics, or both. A fence with acquire semantics is called
     an acquire fence; a fence with release semantics is called a release fence.
 

-
-
+
 
2   A release fence A synchronizes with an acquire fence B if there exist atomic operations
     X and Y , both operating on some atomic object M , such that A is sequenced before X , X
     modifies M , Y is sequenced before B, and Y reads the value written by X or a value
     written by any side effect in the hypothetical release sequence X would head if it were a
     release operation.
 

-
-
+
 
3   A release fence A synchronizes with an atomic operation B that performs an acquire
     operation on an atomic object M if there exists an atomic operation X such that A is
     sequenced before X , X modifies M , and B reads the value written by X or a value written
     by any side effect in the hypothetical release sequence X would head if it were a release
     operation.
 

-
-
+
 
4   An atomic operation A that is a release operation on an atomic object M synchronizes
     with an acquire fence B if there exists some atomic operation X on M such that X is
     sequenced before B and reads the value written by A or a value written by any side effect
     in the release sequence headed by A.
 

-
-
+
 

 
7.17.4.1 [The atomic_thread_fence function]

-

-
-
-
1          #include <stdatomic.h>
+
+
1 Synopsis
+          #include <stdatomic.h>
            void atomic_thread_fence(memory_order order);
     Description
 

-
-
+
 
2   Depending on the value of order, this operation:
     -- has no effects, if order == memory_order_relaxed;
 
@@ -16208,97 +14040,86 @@ char int_p_sep_by_space
        memory_order_seq_cst.
     Returns
 

-
-
+
 
3   The atomic_thread_fence function returns no value.
 

-
-
+
 

 
7.17.4.2 [The atomic_signal_fence function]

-

-
-
-
1           #include <stdatomic.h>
+
+
1 Synopsis
+           #include <stdatomic.h>
             void atomic_signal_fence(memory_order order);
     Description
 

-
-
+
 
2   Equivalent to atomic_thread_fence(order), except that the resulting ordering
     constraints are established only between a thread and a signal handler executed in the
     same thread.
 

-
-
+
 
3   NOTE 1 The atomic_signal_fence function can be used to specify the order in which actions
     performed by the thread become visible to the signal handler.
 
 

-
-
+
 
4   NOTE 2 Compiler optimizations and reorderings of loads and stores are inhibited in the same way as with
     atomic_thread_fence, but the hardware fence instructions that atomic_thread_fence would
     have inserted are not emitted.
 
     Returns
 

-
-
+
 
5   The atomic_signal_fence function returns no value.
 

-
-
+
 

 
7.17.5 [Lock-free property]

-

-
-
+
 
1   The atomic lock-free macros indicate the lock-free property of integer and address atomic
     types. A value of 0 indicates that the type is never lock-free; a value of 1 indicates that
     the type is sometimes lock-free; a value of 2 indicates that the type is always lock-free.
 

-
-
+
 
2   NOTE Operations that are lock-free should also be address-free. That is, atomic operations on the same
     memory location via two different addresses will communicate atomically. The implementation should not
     depend on any per-process state. This restriction enables communication via memory mapped into a
     process more than once and memory shared between two processes.
 

-
-
+
 

 
7.17.5.1 [The atomic_is_lock_free generic function]

-

-
-
-
1            #include <stdatomic.h>
+
+
1 Synopsis
+            #include <stdatomic.h>
              _Bool atomic_is_lock_free(const volatile A *obj);
     Description
 

-
-
+
 
2   The atomic_is_lock_free generic function indicates whether or not the object
-    pointed to by obj is lock-free.                                              
+    pointed to by obj is lock-free.
     Returns
 

-
-
+
 
3   The atomic_is_lock_free generic function returns nonzero (true) if and only if the
     object's operations are lock-free. The result of a lock-free query on one object cannot be
     inferred from the result of a lock-free query on another object.
 

-
-
+
 

 
7.17.6 [Atomic integer types]

-

-
-
-
1   For each line in the following table,257) the atomic type name is declared as a type that
+
+
1   For each line in the following table,[257] the atomic type name is declared as a type that
     has the same representation and alignment requirements as the corresponding direct
-    type.258)
-
+    type.[258]
+

+
+
Footnote 257) See ``future library directions'' (7.31.8).
+

+
+
+
Footnote 258) The same representation and alignment requirements are meant to imply interchangeability as
+         arguments to functions, return values from functions, and members of unions.
                   Atomic type name                            Direct type
               atomic_bool                        _Atomic     _Bool
               atomic_char                        _Atomic     char
@@ -16337,115 +14158,89 @@ char int_p_sep_by_space
               atomic_ptrdiff_t                   _Atomic     ptrdiff_t
               atomic_intmax_t                    _Atomic     intmax_t
               atomic_uintmax_t                   _Atomic     uintmax_t
-

-
-
-
Footnote 257) See ``future library directions'' (7.31.8).
 

 
-
-
Footnote 258) The same representation and alignment requirements are meant to imply interchangeability as
-         arguments to functions, return values from functions, and members of unions.
-

-
-
-
2   The semantics of the operations on these types are defined in 7.17.7.                       
+
+
2   The semantics of the operations on these types are defined in 7.17.7.
 
 

-
-
+
 
3   NOTE The representation of atomic integer types need not have the same size as their corresponding
     regular types. They should have the same size whenever possible, as it eases effort required to port existing
     code.
 
 

-
-
+
 

 
7.17.7 [Operations on atomic types]

-

-
-
+
 
1   There are only a few kinds of operations on atomic types, though there are many
     instances of those kinds. This subclause specifies each general kind.
 

-
-
+
 

 
7.17.7.1 [The atomic_store generic functions]

-

-
-
-
1            #include <stdatomic.h>
+
+
1 Synopsis
+            #include <stdatomic.h>
              void atomic_store(volatile A *object, C desired);
              void atomic_store_explicit(volatile A *object,
                   C desired, memory_order order);
     Description
 

-
-
+
 
2   The      order      argument    shall    not    be    memory_order_acquire,
     memory_order_consume, nor memory_order_acq_rel. Atomically replace the
     value pointed to by object with the value of desired. Memory is affected according
     to the value of order.
     Returns
 

-
-
+
 
3   The atomic_store generic functions return no value.
 

-
-
+
 

 
7.17.7.2 [The atomic_load generic functions]

-

-
-
-
1            #include <stdatomic.h>
+
+
1 Synopsis
+            #include <stdatomic.h>
              C atomic_load(volatile A *object);
              C atomic_load_explicit(volatile A *object,
                   memory_order order);
     Description
 

-
-
+
 
2   The order argument shall not be memory_order_release nor
     memory_order_acq_rel. Memory is affected according to the value of order.
     Returns
     Atomically returns the value pointed to by object.
 

-
-
+
 

 
7.17.7.3 [The atomic_exchange generic functions]

-

-
-
-
1            #include <stdatomic.h>
+
+
1 Synopsis
+            #include <stdatomic.h>
              C atomic_exchange(volatile A *object, C desired);
              C atomic_exchange_explicit(volatile A *object,
                   C desired, memory_order order);
     Description
 

-
-
+
 
2   Atomically replace the value pointed to by object with desired. Memory is affected
     according to the value of order. These operations are read-modify-write operations
-    (5.1.2.4).
+    (5.1.2.4).
     Returns
 

-
-
+
 
3   Atomically returns the value pointed to by object immediately before the effects.
 

-
-
+
 

 
7.17.7.4 [The atomic_compare_exchange generic functions]

-

-
-
-
1            #include <stdatomic.h>
+
+
1 Synopsis
+            #include <stdatomic.h>
              _Bool atomic_compare_exchange_strong(volatile A *object,
                   C *expected, C desired);
              _Bool atomic_compare_exchange_strong_explicit(
@@ -16458,8 +14253,7 @@ char int_p_sep_by_space
                   memory_order success, memory_order failure);
     Description
 

-
-
+
 
2   The failure argument shall not be memory_order_release nor
     memory_order_acq_rel. The failure argument shall be no stronger than the
     success argument. Atomically, compares the value pointed to by object for equality
@@ -16467,10 +14261,9 @@ char int_p_sep_by_space
     desired, and if false, updates the value in expected with the value pointed to by
     object. Further, if the comparison is true, memory is affected according to the value of
     success, and if the comparison is false, memory is affected according to the value of
-    failure. These operations are atomic read-modify-write operations (5.1.2.4).
+    failure. These operations are atomic read-modify-write operations (5.1.2.4).
 

-
-
+
 
3   NOTE 1    For example, the effect of atomic_compare_exchange_strong is
              if (memcmp(object, expected, sizeof (*object)) == 0)
                    memcpy(object, &desired, sizeof (*object));
@@ -16478,20 +14271,17 @@ char int_p_sep_by_space
                    memcpy(expected, object, sizeof (*object));
 
 

-
-
+
 
4   A weak compare-and-exchange operation may fail spuriously. That is, even when the
     contents of memory referred to by expected and object are equal, it may return zero
     and store back to expected the same memory contents that were originally there.
 

-
-
+
 
5   NOTE 2 This spurious failure enables implementation of compare-and-exchange on a broader class of
     machines, e.g. load-locked store-conditional machines.
 
 

-
-
+
 
6   EXAMPLE         A consequence of spurious failure is that nearly all uses of weak compare-and-exchange will
     be in a loop.
              exp = atomic_load(&cur);
@@ -16504,19 +14294,15 @@ char int_p_sep_by_space
 
     Returns
 

-
-
+
 
7   The result of the comparison.
 

-
-
+
 

 
7.17.7.5 [The atomic_fetch and modify generic functions]

-

-
-
+
 
1   The following operations perform arithmetic and bitwise computations. All of these
-    operations are applicable to an object of any atomic integer type. None of these 
+    operations are applicable to an object of any atomic integer type. None of these
     operations is applicable to atomic_bool. The key, operator, and computation
     correspondence is:
      key            op          computation
@@ -16527,31 +14313,27 @@ char int_p_sep_by_space
      and            &       bitwise and
     Synopsis
 

-
-
+
 
2            #include <stdatomic.h>
              C atomic_fetch_key(volatile A *object, M operand);
              C atomic_fetch_key_explicit(volatile A *object,
                   M operand, memory_order order);
     Description
 

-
-
+
 
3   Atomically replaces the value pointed to by object with the result of the computation
     applied to the value pointed to by object and the given operand. Memory is affected
     according to the value of order. These operations are atomic read-modify-write
-    operations (5.1.2.4). For signed integer types, arithmetic is defined to use two's
+    operations (5.1.2.4). For signed integer types, arithmetic is defined to use two's
     complement representation with silent wrap-around on overflow; there are no undefined
     results. For address types, the result may be an undefined address, but the operations
     otherwise have no undefined behavior.
     Returns
 

-
-
+
 
4   Atomically, the value pointed to by object immediately before the effects.
 

-
-
+
 
5   NOTE The operation of the atomic_fetch and modify generic functions are nearly equivalent to the
     operation of the corresponding op= compound assignment operators. The only differences are that the
     compound assignment operators are not guaranteed to operate atomically, and the value yielded by a
@@ -16559,106 +14341,86 @@ char int_p_sep_by_space
     atomic_fetch and modify generic functions is the previous value of the atomic object.
 
 

-
-
+
 

 
7.17.8 [Atomic flag type and operations]

-

-
-
+
 
1   The atomic_flag type provides the classic test-and-set functionality. It has two
     states, set and clear.
 

-
-
+
 
2   Operations on an object of type atomic_flag shall be lock free.
 

-
-
+
 
3   NOTE Hence the operations should also be address-free. No other type requires lock-free operations, so
     the atomic_flag type is the minimum hardware-implemented type needed to conform to this
     International standard. The remaining types can be emulated with atomic_flag, though with less than
     ideal properties.
 
 

-
-
+
 
4   The macro ATOMIC_FLAG_INIT may be used to initialize an atomic_flag to the
     clear state. An atomic_flag that is not explicitly initialized with
     ATOMIC_FLAG_INIT is initially in an indeterminate state.
 

-
-
+
 
5   EXAMPLE
             atomic_flag guard = ATOMIC_FLAG_INIT;
 
 

-
-
+
 

 
7.17.8.1 [The atomic_flag_test_and_set functions]

-

-
-
-
1           #include <stdatomic.h>
+
+
1 Synopsis
+           #include <stdatomic.h>
             _Bool atomic_flag_test_and_set(
                  volatile atomic_flag *object);
             _Bool atomic_flag_test_and_set_explicit(
                  volatile atomic_flag *object, memory_order order);
     Description
 

-
-
+
 
2   Atomically sets the value pointed to by object to true. Memory is affected according
     to the value of order. These operations are atomic read-modify-write operations
-    (5.1.2.4).
+    (5.1.2.4).
     Returns
 

-
-
+
 
3   Atomically, the value of the object immediately before the effects.
 

-
-
+
 

 
7.17.8.2 [The atomic_flag_clear functions]

-

-
-
-
1          #include <stdatomic.h>
+
+
1 Synopsis
+          #include <stdatomic.h>
            void atomic_flag_clear(volatile atomic_flag *object);
            void atomic_flag_clear_explicit(
                 volatile atomic_flag *object, memory_order order);
     Description
 

-
-
+
 
2   The order argument shall not be memory_order_acquire nor
     memory_order_acq_rel. Atomically sets the value pointed to by object to false.
     Memory is affected according to the value of order.
     Returns
 

-
-
+
 
3   The atomic_flag_clear functions return no value.
 

-
-
+
 

-
7.18 [Boolean type and values ]

-

-
-
+
7.18 [Boolean type and values <stdbool.h>]

+
 
1   The header <stdbool.h> defines four macros.
 

-
-
+
 
2   The macro
              bool
     expands to _Bool.
 

-
-
+
 
3   The remaining three macros are suitable for use in #if preprocessing directives. They
     are
              true
@@ -16668,28 +14430,23 @@ char int_p_sep_by_space
              _ _bool_true_false_are_defined
     which expands to the integer constant 1.
 

-
-
-
4   Notwithstanding the provisions of 7.1.3, a program may undefine and perhaps then
-    redefine the macros bool, true, and false.259)
+
+
4   Notwithstanding the provisions of 7.1.3, a program may undefine and perhaps then
+    redefine the macros bool, true, and false.[259]
 
 

-
 
-
Footnote 259) See ``future library directions'' (7.31.9).
+
Footnote 259) See ``future library directions'' (7.31.9).
 

 
-
+
 

-
7.19 [Common definitions ]

-

-
-
+
7.19 [Common definitions <stddef.h>]

+
 
1   The header <stddef.h> defines the following macros and declares the following types.
     Some are also defined in other headers, as noted in their respective subclauses.
 

-
-
+
 
2   The types are
            ptrdiff_t
     which is the signed integer type of the result of subtracting two pointers;
@@ -16706,8 +14463,7 @@ char int_p_sep_by_space
     character      constant     if     an      implementation      does      not      define
     _ _STDC_MB_MIGHT_NEQ_WC_ _.
 

-
-
+
 
3   The macros are
            NULL
     which expands to an implementation-defined null pointer constant; and
@@ -16721,30 +14477,25 @@ char int_p_sep_by_space
     specified member is a bit-field, the behavior is undefined.)
     Recommended practice
 

-
-
+
 
4   The types used for size_t and ptrdiff_t should not have an integer conversion rank
     greater than that of signed long int unless the implementation supports objects
-    large enough to make this necessary.                                               
+    large enough to make this necessary.
 
 

-
-
+
 

-
7.20 [Integer types ]

-

-
-
+
7.20 [Integer types <stdint.h>]

+
 
1   The header <stdint.h> declares sets of integer types having specified widths, and
-    defines corresponding sets of macros.260) It also defines macros that specify limits of
+    defines corresponding sets of macros.[260] It also defines macros that specify limits of
     integer types corresponding to types defined in other standard headers.
 

-
 
-
Footnote 260) See ``future library directions'' (7.31.10).
+
Footnote 260) See ``future library directions'' (7.31.10).
 

 
-
+
 
2   Types are defined in the following categories:
     -- integer types having certain exact widths;
     -- integer types having at least certain specified widths;
@@ -16753,84 +14504,68 @@ char int_p_sep_by_space
     -- integer types having greatest width.
     (Some of these types may denote the same type.)
 

-
-
+
 
3   Corresponding macros specify limits of the declared types and construct suitable
     constants.
 

-
-
-
4   For each type described herein that the implementation provides,261) <stdint.h> shall
+
+
4   For each type described herein that the implementation provides,[261] <stdint.h> shall
     declare that typedef name and define the associated macros. Conversely, for each type
     described herein that the implementation does not provide, <stdint.h> shall not
     declare that typedef name nor shall it define the associated macros. An implementation
     shall provide those types described as ``required'', but need not provide any of the others
     (described as ``optional'').
 

-
 
 
Footnote 261) Some of these types may denote implementation-defined extended integer types.
 

 
-
+
 

 
7.20.1 [Integer types]

-

-
-
+
 
1   When typedef names differing only in the absence or presence of the initial u are defined,
-    they shall denote corresponding signed and unsigned types as described in 6.2.5; an
+    they shall denote corresponding signed and unsigned types as described in 6.2.5; an
     implementation providing one of these corresponding types shall also provide the other.
 

-
-
+
 
2   In the following descriptions, the symbol N represents an unsigned decimal integer with
     no leading zeros (e.g., 8 or 24, but not 04 or 048).
 
 

-
-
+
 

 
7.20.1.1 [Exact-width integer types]

-

-
-
+
 
1   The typedef name intN_t designates a signed integer type with width N , no padding
     bits, and a two's complement representation. Thus, int8_t denotes such a signed
     integer type with a width of exactly 8 bits.
 

-
-
+
 
2   The typedef name uintN_t designates an unsigned integer type with width N and no
     padding bits. Thus, uint24_t denotes such an unsigned integer type with a width of
     exactly 24 bits.
 

-
-
+
 
3   These types are optional. However, if an implementation provides integer types with
     widths of 8, 16, 32, or 64 bits, no padding bits, and (for the signed types) that have a
     two's complement representation, it shall define the corresponding typedef names.
 

-
-
+
 

 
7.20.1.2 [Minimum-width integer types]

-

-
-
+
 
1   The typedef name int_leastN_t designates a signed integer type with a width of at
     least N , such that no signed integer type with lesser size has at least the specified width.
     Thus, int_least32_t denotes a signed integer type with a width of at least 32 bits.
 

-
-
+
 
2   The typedef name uint_leastN_t designates an unsigned integer type with a width
     of at least N , such that no unsigned integer type with lesser size has at least the specified
     width. Thus, uint_least16_t denotes an unsigned integer type with a width of at
     least 16 bits.
 

-
-
+
 
3   The following types are required:
              int_least8_t                                      uint_least8_t
              int_least16_t                                     uint_least16_t
@@ -16838,31 +14573,26 @@ char int_p_sep_by_space
              int_least64_t                                     uint_least64_t
     All other types of this form are optional.
 

-
-
+
 

 
7.20.1.3 [Fastest minimum-width integer types]

-

-
-
-
1   Each of the following types designates an integer type that is usually fastest262) to operate
+
+
1   Each of the following types designates an integer type that is usually fastest[262] to operate
     with among all integer types that have at least the specified width.
 

-
 
 
Footnote 262) The designated type is not guaranteed to be fastest for all purposes; if the implementation has no clear
          grounds for choosing one type over another, it will simply pick some integer type satisfying the
          signedness and width requirements.
 

 
-
+
 
2   The typedef name int_fastN_t designates the fastest signed integer type with a width
     of at least N . The typedef name uint_fastN_t designates the fastest unsigned integer
     type with a width of at least N .
 
 

-
-
+
 
3   The following types are required:
             int_fast8_t                                    uint_fast8_t
             int_fast16_t                                   uint_fast16_t
@@ -16870,13 +14600,10 @@ char int_p_sep_by_space
             int_fast64_t                                   uint_fast64_t
     All other types of this form are optional.
 

-
-
+
 

 
7.20.1.4 [Integer types capable of holding object pointers]

-

-
-
+
 
1   The following type designates a signed integer type with the property that any valid
     pointer to void can be converted to this type, then converted back to pointer to void,
     and the result will compare equal to the original pointer:
@@ -16887,13 +14614,10 @@ char int_p_sep_by_space
             uintptr_t
     These types are optional.
 

-
-
+
 

 
7.20.1.5 [Greatest-width integer types]

-

-
-
+
 
1   The following type designates a signed integer type capable of representing any value of
     any signed integer type:
             intmax_t
@@ -16902,18 +14626,14 @@ char int_p_sep_by_space
             uintmax_t
     These types are required.
 

-
-
+
 

 
7.20.2 [Limits of specified-width integer types]

-

-
-
+
 
1   The following object-like macros specify the minimum and maximum limits of the types
-    declared in <stdint.h>. Each macro name corresponds to a similar type name in 7.20.1.
+    declared in <stdint.h>. Each macro name corresponds to a similar type name in 7.20.1.
 

-
-
+
 
2   Each instance of any defined macro shall be replaced by a constant expression suitable
     for use in #if preprocessing directives, and this expression shall have the same type as
     would an expression that is an object of the corresponding type converted according to
@@ -16922,13 +14642,10 @@ char int_p_sep_by_space
     except where stated to be exactly the given value.
 
 

-
-
+
 

 
7.20.2.1 [Limits of exact-width integer types]

-

-
-
+
 
1   -- minimum values of exact-width signed integer types
           INTN_MIN                                   exactly -(2 N -1 )
     -- maximum values of exact-width signed integer types
@@ -16936,13 +14653,10 @@ char int_p_sep_by_space
     -- maximum values of exact-width unsigned integer types
        UINTN_MAX                                     exactly 2 N - 1
 

-
-
+
 

 
7.20.2.2 [Limits of minimum-width integer types]

-

-
-
+
 
1   -- minimum values of minimum-width signed integer types
           INT_LEASTN_MIN                                     -(2 N -1 - 1)
     -- maximum values of minimum-width signed integer types
@@ -16950,13 +14664,10 @@ char int_p_sep_by_space
     -- maximum values of minimum-width unsigned integer types
        UINT_LEASTN_MAX                                       2N - 1
 

-
-
+
 

 
7.20.2.3 [Limits of fastest minimum-width integer types]

-

-
-
+
 
1   -- minimum values of fastest minimum-width signed integer types
           INT_FASTN_MIN                                      -(2 N -1 - 1)
     -- maximum values of fastest minimum-width signed integer types
@@ -16964,13 +14675,10 @@ char int_p_sep_by_space
     -- maximum values of fastest minimum-width unsigned integer types
        UINT_FASTN_MAX                                        2N - 1
 

-
-
+
 

 
7.20.2.4 [Limits of integer types capable of holding object pointers]

-

-
-
+
 
1   -- minimum value of pointer-holding signed integer type
           INTPTR_MIN                                         -(215 - 1)
     -- maximum value of pointer-holding signed integer type
@@ -16979,13 +14687,10 @@ char int_p_sep_by_space
        UINTPTR_MAX                                           216 - 1
 
 

-
-
+
 

 
7.20.2.5 [Limits of greatest-width integer types]

-

-
-
+
 
1   -- minimum value of greatest-width signed integer type
         INTMAX_MIN                                                    -(263 - 1)
     -- maximum value of greatest-width signed integer type
@@ -16993,25 +14698,21 @@ char int_p_sep_by_space
     -- maximum value of greatest-width unsigned integer type
         UINTMAX_MAX                                                   264 - 1
 

-
-
+
 

 
7.20.3 [Limits of other integer types]

-

-
-
+
 
1   The following object-like macros specify the minimum and maximum limits of integer
     types corresponding to types defined in other standard headers.
 

-
-
+
 
2   Each instance of these macros shall be replaced by a constant expression suitable for use
     in #if preprocessing directives, and this expression shall have the same type as would an
     expression that is an object of the corresponding type converted according to the integer
     promotions. Its implementation-defined value shall be equal to or greater in magnitude
     (absolute value) than the corresponding value given below, with the same sign. An
     implementation shall define only the macros corresponding to those typedef names it
-    actually provides.263)
+    actually provides.[263]
     -- limits of ptrdiff_t
         PTRDIFF_MIN                                                 -65535
         PTRDIFF_MAX                                                 +65535
@@ -17024,71 +14725,59 @@ char int_p_sep_by_space
         WCHAR_MIN                                                   see below
         WCHAR_MAX                                                   see below
     -- limits of wint_t
-
-        WINT_MIN                                              see below
-        WINT_MAX                                              see below
 

-
 
 
Footnote 263) A freestanding implementation need not provide all of these types.
+        WINT_MIN                                              see below
+        WINT_MAX                                              see below
 

 
-
-
3   If sig_atomic_t (see 7.14) is defined as a signed integer type, the value of
+
+
3   If sig_atomic_t (see 7.14) is defined as a signed integer type, the value of
     SIG_ATOMIC_MIN shall be no greater than -127 and the value of SIG_ATOMIC_MAX
     shall be no less than 127; otherwise, sig_atomic_t is defined as an unsigned integer
     type, and the value of SIG_ATOMIC_MIN shall be 0 and the value of
     SIG_ATOMIC_MAX shall be no less than 255.
 

-
-
-
4   If wchar_t (see 7.19) is defined as a signed integer type, the value of WCHAR_MIN
+
+
4   If wchar_t (see 7.19) is defined as a signed integer type, the value of WCHAR_MIN
     shall be no greater than -127 and the value of WCHAR_MAX shall be no less than 127;
     otherwise, wchar_t is defined as an unsigned integer type, and the value of
-    WCHAR_MIN shall be 0 and the value of WCHAR_MAX shall be no less than 255.264)
+    WCHAR_MIN shall be 0 and the value of WCHAR_MAX shall be no less than 255.[264]
 

-
 
 
Footnote 264) The values WCHAR_MIN and WCHAR_MAX do not necessarily correspond to members of the extended
          character set.
 

 
-
-
5   If wint_t (see 7.29) is defined as a signed integer type, the value of WINT_MIN shall
+
+
5   If wint_t (see 7.29) is defined as a signed integer type, the value of WINT_MIN shall
     be no greater than -32767 and the value of WINT_MAX shall be no less than 32767;
     otherwise, wint_t is defined as an unsigned integer type, and the value of WINT_MIN
     shall be 0 and the value of WINT_MAX shall be no less than 65535.
 

-
-
+
 

 
7.20.4 [Macros for integer constants]

-

-
-
+
 
1   The following function-like macros expand to integer constants suitable for initializing
     objects that have integer types corresponding to types defined in <stdint.h>. Each
-    macro name corresponds to a similar type name in 7.20.1.2 or 7.20.1.5.
+    macro name corresponds to a similar type name in 7.20.1.2 or 7.20.1.5.
 

-
-
+
 
2   The argument in any instance of these macros shall be an unsuffixed integer constant (as
-    defined in 6.4.4.1) with a value that does not exceed the limits for the corresponding type.
+    defined in 6.4.4.1) with a value that does not exceed the limits for the corresponding type.
 

-
-
+
 
3   Each invocation of one of these macros shall expand to an integer constant expression
     suitable for use in #if preprocessing directives. The type of the expression shall have
     the same type as would an expression of the corresponding type converted according to
     the integer promotions. The value of the expression shall be that of the argument.
 

-
-
+
 

 
7.20.4.1 [Macros for minimum-width integer constants]

-

-
-
+
 
1   The macro INTN_C(value) shall expand to an integer constant expression
     corresponding to the type int_leastN_t. The macro UINTN_C(value) shall expand
     to an integer constant expression corresponding to the type uint_leastN_t. For
@@ -17096,13 +14785,10 @@ char int_p_sep_by_space
     then UINT64_C(0x123) might expand to the integer constant 0x123ULL.
 
 

-
-
+
 

 
7.20.4.2 [Macros for greatest-width integer constants]

-

-
-
+
 
1   The following macro expands to an integer constant expression having the value specified
     by its argument and the type intmax_t:
             INTMAX_C(value)
@@ -17110,25 +14796,18 @@ char int_p_sep_by_space
     by its argument and the type uintmax_t:
             UINTMAX_C(value)
 

-
-
+
 

-
7.21 [Input/output ]

-
 Input/output 
-

-
-
+
7.21 [Input/output <stdio.h>]

+
 

 
7.21.1 [Introduction]

-

-
-
+
 
1   The header <stdio.h> defines several macros, and declares three types and many
     functions for performing input and output.
 

-
-
-
2   The types declared are size_t (described in 7.19);
+
+
2   The types declared are size_t (described in 7.19);
            FILE
     which is an object type capable of recording all the information needed to control a
     stream, including its file position indicator, a pointer to its associated buffer (if any), an
@@ -17138,9 +14817,8 @@ char int_p_sep_by_space
     which is a complete object type other than an array type capable of recording all the
     information needed to specify uniquely every position within a file.
 

-
-
-
3   The macros are NULL (described in 7.19);
+
+
3   The macros are NULL (described in 7.19);
            _IOFBF
            _IOLBF
            _IONBF
@@ -17160,7 +14838,7 @@ char int_p_sep_by_space
     which expands to an integer constant expression that is the size needed for an array of
     char large enough to hold the longest file name string that the implementation
 
-    guarantees can be opened;265)
+    guarantees can be opened;[265]
              L_tmpnam
     which expands to an integer constant expression that is the size needed for an array of
     char large enough to hold a temporary file name string generated by the tmpnam
@@ -17179,62 +14857,59 @@ char int_p_sep_by_space
     which are expressions of type ``pointer to FILE'' that point to the FILE objects
     associated, respectively, with the standard error, input, and output streams.
 

-
 
 
Footnote 265) If the implementation imposes no practical limit on the length of file name strings, the value of
          FILENAME_MAX should instead be the recommended size of an array intended to hold a file name
          string. Of course, file name string contents are subject to other system-specific constraints; therefore
          all possible strings of length FILENAME_MAX cannot be expected to be opened successfully.
-

-
-
-
4   The header <wchar.h> declares a number of functions useful for wide character input
-    and output. The wide character input/output functions described in that subclause
-    provide operations analogous to most of those described here, except that the
-    fundamental units internal to the program are wide characters. The external
-    representation (in the file) is a sequence of ``generalized'' multibyte characters, as
-    described further in 7.21.3.
-

-
-
-
5   The input/output functions are given the following collective terms:
-    -- The wide character input functions -- those functions described in 7.29 that perform
-       input into wide characters and wide strings: fgetwc, fgetws, getwc, getwchar,
-       fwscanf, wscanf, vfwscanf, and vwscanf.
-    -- The wide character output functions -- those functions described in 7.29 that perform
-       output from wide characters and wide strings: fputwc, fputws, putwc,
-       putwchar, fwprintf, wprintf, vfwprintf, and vwprintf.
-
     -- The wide character input/output functions -- the union of the ungetwc function, the
        wide character input functions, and the wide character output functions.
     -- The byte input/output functions -- those functions described in this subclause that
        perform input/output: fgetc, fgets, fprintf, fputc, fputs, fread,
        fscanf, fwrite, getc, getchar, printf, putc, putchar, puts, scanf,
        ungetc, vfprintf, vfscanf, vprintf, and vscanf.
-    Forward references: files (7.21.3), the fseek function (7.21.9.2), streams (7.21.2), the
-    tmpnam function (7.21.4.4), <wchar.h> (7.29).
-

+    Forward references: files (7.21.3), the fseek function (7.21.9.2), streams (7.21.2), the
+    tmpnam function (7.21.4.4), <wchar.h> (7.29).
+

 
-
+
+
4   The header <wchar.h> declares a number of functions useful for wide character input
+    and output. The wide character input/output functions described in that subclause
+    provide operations analogous to most of those described here, except that the
+    fundamental units internal to the program are wide characters. The external
+    representation (in the file) is a sequence of ``generalized'' multibyte characters, as
+    described further in 7.21.3.
+

+
+
5   The input/output functions are given the following collective terms:
+    -- The wide character input functions -- those functions described in 7.29 that perform
+       input into wide characters and wide strings: fgetwc, fgetws, getwc, getwchar,
+       fwscanf, wscanf, vfwscanf, and vwscanf.
+    -- The wide character output functions -- those functions described in 7.29 that perform
+       output from wide characters and wide strings: fputwc, fputws, putwc,
+       putwchar, fwprintf, wprintf, vfwprintf, and vwprintf.
+

+
 

 
7.21.2 [Streams]

-

-
-
+
 
1   Input and output, whether to or from physical devices such as terminals and tape drives,
     or whether to or from files supported on structured storage devices, are mapped into
     logical data streams, whose properties are more uniform than their various inputs and
     outputs. Two forms of mapping are supported, for text streams and for binary
-    streams.266)
+    streams.[266]
 

-
 
 
Footnote 266) An implementation need not distinguish between text streams and binary streams. In such an
          implementation, there need be no new-line characters in a text stream nor any limit to the length of a
          line.
+    stream becomes a wide-oriented stream . Similarly, once a byte input/output function has
+    been applied to a stream without orientation, the stream becomes a byte-oriented stream .
+    Only a call to the freopen function or the fwide function can otherwise alter the
+    orientation of a stream. (A successful call to freopen removes any orientation.)267)
 

 
-
+
 
2   A text stream is an ordered sequence of characters composed into lines, each line
     consisting of zero or more characters plus a terminating new-line character. Whether the
     last line requires a terminating new-line character is implementation-defined. Characters
@@ -17248,31 +14923,19 @@ char int_p_sep_by_space
     Whether space characters that are written out immediately before a new-line character
     appear when read in is implementation-defined.
 

-
-
+
 
3   A binary stream is an ordered sequence of characters that can transparently record
     internal data. Data read in from a binary stream shall compare equal to the data that were
     earlier written out to that stream, under the same implementation. Such a stream may,
     however, have an implementation-defined number of null characters appended to the end
     of the stream.
 

-
-
+
 
4   Each stream has an orientation. After a stream is associated with an external file, but
     before any operations are performed on it, the stream is without orientation. Once a wide
     character input/output function has been applied to a stream without orientation, the
-
-    stream becomes a wide-oriented stream . Similarly, once a byte input/output function has
-    been applied to a stream without orientation, the stream becomes a byte-oriented stream .
-    Only a call to the freopen function or the fwide function can otherwise alter the
-    orientation of a stream. (A successful call to freopen removes any orientation.)267)
 

-
-
-
Footnote 267) The three predefined streams stdin, stdout, and stderr are unoriented at program startup.
-

-
-
+
 
5   Byte input/output functions shall not be applied to a wide-oriented stream and wide
     character input/output functions shall not be applied to a byte-oriented stream. The
     remaining stream operations do not affect, and are not affected by, a stream's orientation,
@@ -17284,45 +14947,38 @@ char int_p_sep_by_space
        function can overwrite a partial multibyte character; any file contents beyond the
        byte(s) written are henceforth indeterminate.
 

-
-
+
 
6   Each wide-oriented stream has an associated mbstate_t object that stores the current
     parse state of the stream. A successful call to fgetpos stores a representation of the
     value of this mbstate_t object as part of the value of the fpos_t object. A later
     successful call to fsetpos using the same stored fpos_t value restores the value of
     the associated mbstate_t object as well as the position within the controlled stream.
 

-
-
+
 
7   Each stream has an associated lock that is used to prevent data races when multiple
     threads of execution access a stream, and to restrict the interleaving of stream operations
     performed by multiple threads. Only one thread may hold this lock at a time. The lock is
     reentrant: a single thread may hold the lock multiple times at a given time.
 

-
-
+
 
8   All functions that read, write, position, or query the position of a stream lock the stream
     before accessing it. They release the lock associated with the stream when the access is
     complete.
     Environmental limits
 

-
-
+
 
9   An implementation shall support text files with lines containing at least 254 characters,
     including the terminating new-line character. The value of the macro BUFSIZ shall be at
     least 256.
-    Forward references: the freopen function (7.21.5.4), the fwide function (7.29.3.5),
-    mbstate_t (7.30.1), the fgetpos function (7.21.9.1), the fsetpos function
-    (7.21.9.3).
+    Forward references: the freopen function (7.21.5.4), the fwide function (7.29.3.5),
+    mbstate_t (7.30.1), the fgetpos function (7.21.9.1), the fsetpos function
+    (7.21.9.3).
 
 

-
-
+
 

 
7.21.3 [Files]

-

-
-
+
 
1   A stream is associated with an external file (which may be a physical device) by opening
     a file, which may involve creating a new file. Creating an existing file causes its former
     contents to be discarded, if necessary. If a file can support positioning requests (such as a
@@ -17333,14 +14989,12 @@ char int_p_sep_by_space
     position indicator is maintained by subsequent reads, writes, and positioning requests, to
     facilitate an orderly progression through the file.
 

-
-
-
2   Binary files are not truncated, except as defined in 7.21.5.3. Whether a write on a text
+
+
2   Binary files are not truncated, except as defined in 7.21.5.3. Whether a write on a text
     stream causes the associated file to be truncated beyond that point is implementation-
     defined.
 

-
-
+
 
3   When a stream is unbuffered , characters are intended to appear from the source or at the
     destination as soon as possible. Otherwise characters may be accumulated and
     transmitted to or from the host environment as a block. When a stream is fully buffered ,
@@ -17353,8 +15007,7 @@ char int_p_sep_by_space
     characters from the host environment. Support for these characteristics is
     implementation-defined, and may be affected via the setbuf and setvbuf functions.
 

-
-
+
 
4   A file may be disassociated from a controlling stream by closing the file. Output streams
     are flushed (any unwritten buffer contents are transmitted to the host environment) before
     the stream is disassociated from the file. The value of a pointer to a FILE object is
@@ -17362,8 +15015,7 @@ char int_p_sep_by_space
     Whether a file of zero length (on which no characters have been written by an output
     stream) actually exists is implementation-defined.
 

-
-
+
 
5   The file may be subsequently reopened, by the same or another program execution, and
     its contents reclaimed or modified (if it can be repositioned at its start). If the main
     function returns to its original caller, or if the exit function is called, all open files are
@@ -17371,14 +15023,12 @@ char int_p_sep_by_space
     program termination, such as calling the abort function, need not close all files
     properly.
 

-
-
+
 
6   The address of the FILE object used to control a stream may be significant; a copy of a
     FILE object need not serve in place of the original.
 
 

-
-
+
 
7    At program startup, three text streams are predefined and need not be opened explicitly
      -- standard input (for reading conventional input), standard output (for writing
      conventional output), and standard error (for writing diagnostic output). As initially
@@ -17386,205 +15036,173 @@ char int_p_sep_by_space
      output streams are fully buffered if and only if the stream can be determined not to refer
      to an interactive device.
 

-
-
+
 
8    Functions that open additional (nontemporary) files require a file name, which is a string.
      The rules for composing valid file names are implementation-defined. Whether the same
      file can be simultaneously open multiple times is also implementation-defined.
 

-
-
+
 
9    Although both text and binary wide-oriented streams are conceptually sequences of wide
      characters, the external file associated with a wide-oriented stream is a sequence of
      multibyte characters, generalized as follows:
      -- Multibyte encodings within files may contain embedded null bytes (unlike multibyte
         encodings valid for use internal to the program).
-     -- A file need not begin nor end in the initial shift state.268)
+     -- A file need not begin nor end in the initial shift state.[268]
 

-
 
 
Footnote 268) Setting the file position indicator to end-of-file, as with fseek(file, 0, SEEK_END), has
           undefined behavior for a binary stream (because of possible trailing null characters) or for any stream
           with state-dependent encoding that does not assuredly end in the initial shift state.
+     multibyte character. The wide character input/output functions and the byte input/output
+     functions store the value of the macro EILSEQ in errno if and only if an encoding error
+     occurs.
+     Environmental limits
 

 
-
+
 
10   Moreover, the encodings used for multibyte characters may differ among files. Both the
      nature and choice of such encodings are implementation-defined.
 

-
-
+
 
11   The wide character input functions read multibyte characters from the stream and convert
      them to wide characters as if they were read by successive calls to the fgetwc function.
      Each conversion occurs as if by a call to the mbrtowc function, with the conversion state
      described by the stream's own mbstate_t object. The byte input functions read
      characters from the stream as if by successive calls to the fgetc function.
 

-
-
+
 
12   The wide character output functions convert wide characters to multibyte characters and
      write them to the stream as if they were written by successive calls to the fputwc
      function. Each conversion occurs as if by a call to the wcrtomb function, with the
      conversion state described by the stream's own mbstate_t object. The byte output
      functions write characters to the stream as if by successive calls to the fputc function.
 

-
-
+
 
13   In some cases, some of the byte input/output functions also perform conversions between
      multibyte characters and wide characters. These conversions also occur as if by calls to
      the mbrtowc and wcrtomb functions.
 

-
-
+
 
14   An encoding error occurs if the character sequence presented to the underlying
      mbrtowc function does not form a valid (generalized) multibyte character, or if the code
      value passed to the underlying wcrtomb does not correspond to a valid (generalized)
-
-     multibyte character. The wide character input/output functions and the byte input/output
-     functions store the value of the macro EILSEQ in errno if and only if an encoding error
-     occurs.
-     Environmental limits
 

-
-
+
 
15   The value of FOPEN_MAX shall be at least eight, including the three standard text
      streams.
-     Forward references: the exit function (7.22.4.4), the fgetc function (7.21.7.1), the
-     fopen function (7.21.5.3), the fputc function (7.21.7.3), the setbuf function
-     (7.21.5.5), the setvbuf function (7.21.5.6), the fgetwc function (7.29.3.1), the
-     fputwc function (7.29.3.3), conversion state (7.29.6), the mbrtowc function
-     (7.29.6.3.2), the wcrtomb function (7.29.6.3.3).
+     Forward references: the exit function (7.22.4.4), the fgetc function (7.21.7.1), the
+     fopen function (7.21.5.3), the fputc function (7.21.7.3), the setbuf function
+     (7.21.5.5), the setvbuf function (7.21.5.6), the fgetwc function (7.29.3.1), the
+     fputwc function (7.29.3.3), conversion state (7.29.6), the mbrtowc function
+     (7.29.6.3.2), the wcrtomb function (7.29.6.3.3).
 

-
-
+
 

 
7.21.4 [Operations on files]

-
 Operations on files
-

-
-
+
 

 
7.21.4.1 [The remove function]

-

-
-
-
1           #include <stdio.h>
+
+
1 Synopsis
+           #include <stdio.h>
             int remove(const char *filename);
      Description
 

-
-
+
 
2    The remove function causes the file whose name is the string pointed to by filename
      to be no longer accessible by that name. A subsequent attempt to open that file using that
      name will fail, unless it is created anew. If the file is open, the behavior of the remove
      function is implementation-defined.
      Returns
 

-
-
+
 
3    The remove function returns zero if the operation succeeds, nonzero if it fails.
 

-
-
+
 

 
7.21.4.2 [The rename function]

-

-
-
-
1           #include <stdio.h>
+
+
1 Synopsis
+           #include <stdio.h>
             int rename(const char *old, const char *new);
      Description
 

-
-
+
 
2    The rename function causes the file whose name is the string pointed to by old to be
      henceforth known by the name given by the string pointed to by new. The file named
      old is no longer accessible by that name. If a file named by the string pointed to by new
      exists prior to the call to the rename function, the behavior is implementation-defined.
     Returns
 

-
-
-
3   The rename function returns zero if the operation succeeds, nonzero if it fails,269) in
+
+
3   The rename function returns zero if the operation succeeds, nonzero if it fails,[269] in
     which case if the file existed previously it is still known by its original name.
 

-
 
 
Footnote 269) Among the reasons the implementation may cause the rename function to fail are that the file is open
          or that it is necessary to copy its contents to effectuate its renaming.
 

 
-
+
 

 
7.21.4.3 [The tmpfile function]

-

-
-
-
1           #include <stdio.h>
+
+
1 Synopsis
+           #include <stdio.h>
             FILE *tmpfile(void);
     Description
 

-
-
+
 
2   The tmpfile function creates a temporary binary file that is different from any other
     existing file and that will automatically be removed when it is closed or at program
     termination. If the program terminates abnormally, whether an open temporary file is
     removed is implementation-defined. The file is opened for update with "wb+" mode.
     Recommended practice
 

-
-
+
 
3   It should be possible to open at least TMP_MAX temporary files during the lifetime of the
     program (this limit may be shared with tmpnam) and there should be no limit on the
     number simultaneously open other than this limit and any limit on the number of open
     files (FOPEN_MAX).
     Returns
 

-
-
+
 
4   The tmpfile function returns a pointer to the stream of the file that it created. If the file
     cannot be created, the tmpfile function returns a null pointer.
-    Forward references: the fopen function (7.21.5.3).
+    Forward references: the fopen function (7.21.5.3).
 

-
-
+
 

 
7.21.4.4 [The tmpnam function]

-

-
-
-
1           #include <stdio.h>
+
+
1 Synopsis
+           #include <stdio.h>
             char *tmpnam(char *s);
     Description
 

-
-
+
 
2   The tmpnam function generates a string that is a valid file name and that is not the same
-    as the name of an existing file.270) The function is potentially capable of generating at
-
-    least TMP_MAX different strings, but any or all of them may already be in use by existing
-    files and thus not be suitable return values.
+    as the name of an existing file.[270] The function is potentially capable of generating at
 

-
 
 
Footnote 270) Files created using strings generated by the tmpnam function are temporary only in the sense that
          their names should not collide with those generated by conventional naming rules for the
          implementation. It is still necessary to use the remove function to remove such files when their use
          is ended, and before program termination.
+    least TMP_MAX different strings, but any or all of them may already be in use by existing
+    files and thus not be suitable return values.
 

 
-
+
 
3   The tmpnam function generates a different string each time it is called.
 

-
-
+
 
4   Calls to the tmpnam function with a null pointer argument may introduce data races with
     each other. The implementation shall behave as if no library function calls the tmpnam
     function.
     Returns
 

-
-
+
 
5   If no suitable string can be generated, the tmpnam function returns a null pointer.
     Otherwise, if the argument is a null pointer, the tmpnam function leaves its result in an
     internal static object and returns a pointer to that object (subsequent calls to the tmpnam
@@ -17593,29 +15211,22 @@ char int_p_sep_by_space
     in that array and returns the argument as its value.
     Environmental limits
 

-
-
+
 
6   The value of the macro TMP_MAX shall be at least 25.
 

-
-
+
 

 
7.21.5 [File access functions]

-
 File access functions
-

-
-
+
 

 
7.21.5.1 [The fclose function]

-

-
-
-
1          #include <stdio.h>
+
+
1 Synopsis
+          #include <stdio.h>
            int fclose(FILE *stream);
     Description
 

-
-
+
 
2   A successful call to the fclose function causes the stream pointed to by stream to be
     flushed and the associated file to be closed. Any unwritten buffered data for the stream
     are delivered to the host environment to be written to the file; any unread buffered data
@@ -17624,69 +15235,63 @@ char int_p_sep_by_space
     (and deallocated if it was automatically allocated).
     Returns
 

-
-
+
 
3   The fclose function returns zero if the stream was successfully closed, or EOF if any
     errors were detected.
 

-
-
+
 

 
7.21.5.2 [The fflush function]

-

-
-
-
1           #include <stdio.h>
+
+
1 Synopsis
+           #include <stdio.h>
             int fflush(FILE *stream);
     Description
 

-
-
+
 
2   If stream points to an output stream or an update stream in which the most recent
     operation was not input, the fflush function causes any unwritten data for that stream
     to be delivered to the host environment to be written to the file; otherwise, the behavior is
     undefined.
 

-
-
+
 
3   If stream is a null pointer, the fflush function performs this flushing action on all
     streams for which the behavior is defined above.
     Returns
 

-
-
+
 
4   The fflush function sets the error indicator for the stream and returns EOF if a write
     error occurs, otherwise it returns zero.
-    Forward references: the fopen function (7.21.5.3).
+    Forward references: the fopen function (7.21.5.3).
 

-
-
+
 

 
7.21.5.3 [The fopen function]

-

-
-
-
1           #include <stdio.h>
+
+
1 Synopsis
+           #include <stdio.h>
             FILE *fopen(const char * restrict filename,
                  const char * restrict mode);
     Description
 

-
-
+
 
2   The fopen function opens the file whose name is the string pointed to by filename,
     and associates a stream with it.
 

-
-
+
 
3   The argument mode points to a string. If the string is one of the following, the file is
-    open in the indicated mode. Otherwise, the behavior is undefined.271)
+    open in the indicated mode. Otherwise, the behavior is undefined.[271]
     r                     open text file for reading
     w                     truncate to zero length or create text file for writing
     wx                    create text file for writing
     a                     append; open or create text file for writing at end-of-file
     rb                    open binary file for reading
     wb                    truncate to zero length or create binary file for writing
-
+

+
+
Footnote 271) If the string begins with one of the above sequences, the implementation might choose to ignore the
+         remaining characters, or it might use them to select different kinds of a file (some of which might not
+         conform to the properties in 7.21.2).
     wbx               create binary file for writing
     ab                append; open or create binary file for writing at end-of-file
     r+                open text file for update (reading and writing)
@@ -17697,27 +15302,19 @@ char int_p_sep_by_space
     w+b or wb+        truncate to zero length or create binary file for update
     w+bx or wb+x      create binary file for update
     a+b or ab+        append; open or create binary file for update, writing at end-of-file
-

-
-
-
Footnote 271) If the string begins with one of the above sequences, the implementation might choose to ignore the
-         remaining characters, or it might use them to select different kinds of a file (some of which might not
-         conform to the properties in 7.21.2).
 

 
-
+
 
4   Opening a file with read mode ('r' as the first character in the mode argument) fails if
     the file does not exist or cannot be read.
 

-
-
+
 
5   Opening a file with exclusive mode ('x' as the last character in the mode argument)
     fails if the file already exists or cannot be created. Otherwise, the file is created with
     exclusive (also known as non-shared) access to the extent that the underlying system
     supports exclusive access.
 

-
-
+
 
6   Opening a file with append mode ('a' as the first character in the mode argument)
     causes all subsequent writes to the file to be forced to the then current end-of-file,
     regardless of intervening calls to the fseek function. In some implementations, opening
@@ -17725,8 +15322,7 @@ char int_p_sep_by_space
     mode argument values) may initially position the file position indicator for the stream
     beyond the last data written, because of null character padding.
 

-
-
+
 
7   When a file is opened with update mode ('+' as the second or third character in the
     above list of mode argument values), both input and output may be performed on the
     associated stream. However, output shall not be directly followed by input without an
@@ -17736,154 +15332,131 @@ char int_p_sep_by_space
     of-file. Opening (or creating) a text file with update mode may instead open (or create) a
     binary stream in some implementations.
 

-
-
+
 
8   When opened, a stream is fully buffered if and only if it can be determined not to refer to
     an interactive device. The error and end-of-file indicators for the stream are cleared.
     Returns
 

-
-
+
 
9   The fopen function returns a pointer to the object controlling the stream. If the open
     operation fails, fopen returns a null pointer.
-    Forward references: file positioning functions (7.21.9).
+    Forward references: file positioning functions (7.21.9).
 
 

-
-
+
 

 
7.21.5.4 [The freopen function]

-

-
-
-
1           #include <stdio.h>
+
+
1 Synopsis
+           #include <stdio.h>
             FILE *freopen(const char * restrict filename,
                  const char * restrict mode,
                  FILE * restrict stream);
     Description
 

-
-
+
 
2   The freopen function opens the file whose name is the string pointed to by filename
     and associates the stream pointed to by stream with it. The mode argument is used just
-    as in the fopen function.272)
+    as in the fopen function.[272]
 

-
 
 
Footnote 272) The primary use of the freopen function is to change the file associated with a standard text stream
          (stderr, stdin, or stdout), as those identifiers need not be modifiable lvalues to which the value
          returned by the fopen function may be assigned.
+    Returns
 

 
-
+
 
3   If filename is a null pointer, the freopen function attempts to change the mode of
     the stream to that specified by mode, as if the name of the file currently associated with
     the stream had been used. It is implementation-defined which changes of mode are
     permitted (if any), and under what circumstances.
 

-
-
+
 
4   The freopen function first attempts to close any file that is associated with the specified
     stream. Failure to close the file is ignored. The error and end-of-file indicators for the
     stream are cleared.
     Returns
 

-
-
+
 
5   The freopen function returns a null pointer if the open operation fails. Otherwise,
     freopen returns the value of stream.
 

-
-
+
 

 
7.21.5.5 [The setbuf function]

-

-
-
-
1           #include <stdio.h>
+
+
1 Synopsis
+           #include <stdio.h>
             void setbuf(FILE * restrict stream,
                  char * restrict buf);
     Description
 

-
-
+
 
2   Except that it returns no value, the setbuf function is equivalent to the setvbuf
     function invoked with the values _IOFBF for mode and BUFSIZ for size, or (if buf
     is a null pointer), with the value _IONBF for mode.
-
-    Returns
 

-
-
+
 
3   The setbuf function returns no value.
-    Forward references: the setvbuf function (7.21.5.6).
+    Forward references: the setvbuf function (7.21.5.6).
 

-
-
+
 

 
7.21.5.6 [The setvbuf function]

-

-
-
-
1           #include <stdio.h>
+
+
1 Synopsis
+           #include <stdio.h>
             int setvbuf(FILE * restrict stream,
                  char * restrict buf,
                  int mode, size_t size);
     Description
 

-
-
+
 
2   The setvbuf function may be used only after the stream pointed to by stream has
     been associated with an open file and before any other operation (other than an
     unsuccessful call to setvbuf) is performed on the stream. The argument mode
     determines how stream will be buffered, as follows: _IOFBF causes input/output to be
     fully buffered; _IOLBF causes input/output to be line buffered; _IONBF causes
     input/output to be unbuffered. If buf is not a null pointer, the array it points to may be
-    used instead of a buffer allocated by the setvbuf function273) and the argument size
+    used instead of a buffer allocated by the setvbuf function[273] and the argument size
     specifies the size of the array; otherwise, size may determine the size of a buffer
     allocated by the setvbuf function. The contents of the array at any time are
     indeterminate.
     Returns
 

-
 
 
Footnote 273) The buffer has to have a lifetime at least as great as the open stream, so the stream should be closed
          before a buffer that has automatic storage duration is deallocated upon block exit.
 

 
-
+
 
3   The setvbuf function returns zero on success, or nonzero if an invalid value is given
     for mode or if the request cannot be honored.
 
 

-
-
+
 

 
7.21.6 [Formatted input/output functions]

-

-
-
+
 
1   The formatted input/output functions shall behave as if there is a sequence point after the
-    actions associated with each specifier.274)
+    actions associated with each specifier.[274]
 

-
 
 
Footnote 274) The fprintf functions perform writes to memory for the %n specifier.
 

 
-
+
 

 
7.21.6.1 [The fprintf function]

-

-
-
-
1            #include <stdio.h>
+
+
1 Synopsis
+            #include <stdio.h>
              int fprintf(FILE * restrict stream,
                   const char * restrict format, ...);
     Description
 

-
-
+
 
2   The fprintf function writes output to the stream pointed to by stream, under control
     of the string pointed to by format that specifies how subsequent arguments are
     converted for output. If there are insufficient arguments for the format, the behavior is
@@ -17891,8 +15464,7 @@ char int_p_sep_by_space
     evaluated (as always) but are otherwise ignored. The fprintf function returns when
     the end of the format string is encountered.
 

-
-
+
 
3   The format shall be a multibyte character sequence, beginning and ending in its initial
     shift state. The format is composed of zero or more directives: ordinary multibyte
     characters (not %), which are copied unchanged to the output stream; and conversion
@@ -17900,8 +15472,7 @@ char int_p_sep_by_space
     converting them, if applicable, according to the corresponding conversion specifier, and
     then writing the result to the output stream.
 

-
-
+
 
4   Each conversion specification is introduced by the character %. After the %, the following
     appear in sequence:
     -- Zero or more flags (in any order) that modify the meaning of the conversion
@@ -17909,25 +15480,23 @@ char int_p_sep_by_space
     -- An optional minimum field width. If the converted value has fewer characters than the
        field width, it is padded with spaces (by default) on the left (or right, if the left
        adjustment flag, described later, has been given) to the field width. The field width
-       takes the form of an asterisk * (described later) or a nonnegative decimal integer.275)
+       takes the form of an asterisk * (described later) or a nonnegative decimal integer.[275]
     -- An optional precision that gives the minimum number of digits to appear for the d, i,
        o, u, x, and X conversions, the number of digits to appear after the decimal-point
        character for a, A, e, E, f, and F conversions, the maximum number of significant
        digits for the g and G conversions, or the maximum number of bytes to be written for
-
+

+
+
Footnote 275) Note that 0 is taken as a flag, not as the beginning of a field width.
         s conversions. The precision takes the form of a period (.) followed either by an
         asterisk * (described later) or by an optional decimal integer; if only the period is
         specified, the precision is taken as zero. If a precision appears with any other
         conversion specifier, the behavior is undefined.
     -- An optional length modifier that specifies the size of the argument.
     -- A conversion specifier character that specifies the type of conversion to be applied.
-

-
-
-
Footnote 275) Note that 0 is taken as a flag, not as the beginning of a field width.
 

 
-
+
 
5   As noted above, a field width, or precision, or both, may be indicated by an asterisk. In
     this case, an int argument supplies the field width or precision. The arguments
     specifying field width, or precision, or both, shall appear (in that order) before the
@@ -17935,14 +15504,13 @@ char int_p_sep_by_space
     followed by a positive field width. A negative precision argument is taken as if the
     precision were omitted.
 

-
-
+
 
6   The flag characters and their meanings are:
     -        The result of the conversion is left-justified within the field. (It is right-justified if
              this flag is not specified.)
     +        The result of a signed conversion always begins with a plus or minus sign. (It
              begins with a sign only when a negative value is converted if this flag is not
-             specified.)276)
+             specified.)[276]
     space If the first character of a signed conversion is not a sign, or if a signed conversion
           results in no characters, a space is prefixed to the result. If the space and + flags
           both appear, the space flag is ignored.
@@ -17959,17 +15527,15 @@ char int_p_sep_by_space
              (following any indication of sign or base) are used to pad to the field width rather
              than performing space padding, except when converting an infinity or NaN. If the
              0 and - flags both appear, the 0 flag is ignored. For d, i, o, u, x, and X
-
-              conversions, if a precision is specified, the 0 flag is ignored. For other
-              conversions, the behavior is undefined.
 

-
 
 
Footnote 276) The results of all floating conversions of a negative zero, and of negative values that round to zero,
          include a minus sign.
+              conversions, if a precision is specified, the 0 flag is ignored. For other
+              conversions, the behavior is undefined.
 

 
-
+
 
7   The length modifiers and their meanings are:
     hh            Specifies that a following d, i, o, u, x, or X conversion specifier applies to a
                   signed char or unsigned char argument (the argument will have
@@ -18010,8 +15576,7 @@ char int_p_sep_by_space
     If a length modifier appears with any conversion specifier other than as specified above,
     the behavior is undefined.
 

-
-
+
 
8   The conversion specifiers and their meanings are:
     d,i           The int argument is converted to signed decimal in the style [-]dddd. The
                   precision specifies the minimum number of digits to appear; if the value
@@ -18038,12 +15603,15 @@ char int_p_sep_by_space
                   [-]nan or [-]nan(n-char-sequence) -- which style, and the meaning of
                   any n-char-sequence, is implementation-defined. The F conversion specifier
                   produces INF, INFINITY, or NAN instead of inf, infinity, or nan,
-                  respectively.277)
+                  respectively.[277]
     e,E           A double argument representing a floating-point number is converted in the
-                  style [-]d.ddd e±dd, where there is one digit (which is nonzero if the
+                  style [-]d.ddd e\xB1dd, where there is one digit (which is nonzero if the
                   argument is nonzero) before the decimal-point character and the number of
                   digits after it is equal to the precision; if the precision is missing, it is taken as
-
+

+
+
Footnote 277) When applied to infinite and NaN values, the -, +, and space flag characters have their usual meaning;
+         the # and 0 flag characters have no effect.
                   6; if the precision is zero and the # flag is not specified, no decimal-point
                   character appears. The value is rounded to the appropriate number of digits.
                   The E conversion specifier produces a number with E instead of e
@@ -18066,147 +15634,67 @@ char int_p_sep_by_space
                   A double argument representing an infinity or NaN is converted in the style
                   of an f or F conversion specifier.
     a,A           A double argument representing a floating-point number is converted in the
-                  style [-]0xh.hhhh p±d, where there is one hexadecimal digit (which is
+                  style [-]0xh.hhhh p\xB1d, where there is one hexadecimal digit (which is
                   nonzero if the argument is a normalized floating-point number and is
                   otherwise unspecified) before the decimal-point character278) and the number
                   of hexadecimal digits after it is equal to the precision; if the precision is
                   missing and FLT_RADIX is a power of 2, then the precision is sufficient for
                   an exact representation of the value; if the precision is missing and
                   FLT_RADIX is not a power of 2, then the precision is sufficient to
-
-                  distinguish279) values of type double, except that trailing zeros may be
-                  omitted; if the precision is zero and the # flag is not specified, no decimal-
-                  point character appears. The letters abcdef are used for a conversion and
-                  the letters ABCDEF for A conversion. The A conversion specifier produces a
-                  number with X and P instead of x and p. The exponent always contains at
-                  least one digit, and only as many more digits as necessary to represent the
-                  decimal exponent of 2. If the value is zero, the exponent is zero.
-                  A double argument representing an infinity or NaN is converted in the style
-                  of an f or F conversion specifier.
-    c             If no l length modifier is present, the int argument is converted to an
-                  unsigned char, and the resulting character is written.
-                  If an l length modifier is present, the wint_t argument is converted as if by
-                  an ls conversion specification with no precision and an argument that points
-                  to the initial element of a two-element array of wchar_t, the first element
-                  containing the wint_t argument to the lc conversion specification and the
-                  second a null wide character.
-    s             If no l length modifier is present, the argument shall be a pointer to the initial
-                  element of an array of character type.280) Characters from the array are
-                  written up to (but not including) the terminating null character. If the
-                  precision is specified, no more than that many bytes are written. If the
-                  precision is not specified or is greater than the size of the array, the array shall
-                  contain a null character.
-                  If an l length modifier is present, the argument shall be a pointer to the initial
-                  element of an array of wchar_t type. Wide characters from the array are
-                  converted to multibyte characters (each as if by a call to the wcrtomb
-                  function, with the conversion state described by an mbstate_t object
-                  initialized to zero before the first wide character is converted) up to and
-                  including a terminating null wide character. The resulting multibyte
-                  characters are written up to (but not including) the terminating null character
-                  (byte). If no precision is specified, the array shall contain a null wide
-                  character. If a precision is specified, no more than that many bytes are
-                  written (including shift sequences, if any), and the array shall contain a null
-                  wide character if, to equal the multibyte character sequence length given by
-
-                    the precision, the function would need to access a wide character one past the
-                    end of the array. In no case is a partial multibyte character written.281)
-     p              The argument shall be a pointer to void. The value of the pointer is
-                    converted to a sequence of printing characters, in an implementation-defined
-                    manner.
-     n              The argument shall be a pointer to signed integer into which is written the
-                    number of characters written to the output stream so far by this call to
-                    fprintf. No argument is converted, but one is consumed. If the conversion
-                    specification includes any flags, a field width, or a precision, the behavior is
-                    undefined.
-     %              A % character is written. No argument is converted. The complete
-                    conversion specification shall be %%.
-

-
-
-
Footnote 277) When applied to infinite and NaN values, the -, +, and space flag characters have their usual meaning;
-         the # and 0 flag characters have no effect.
 

 
-
-
Footnote 278) Binary implementations can choose the hexadecimal digit to the left of the decimal-point character so
-         that subsequent digits align to nibble (4-bit) boundaries.
-

-
-
-
Footnote 279) The precision p is sufficient to distinguish values of the source type if 16 p-1 > b n where b is
-         FLT_RADIX and n is the number of base-b digits in the significand of the source type. A smaller p
-         might suffice depending on the implementation's scheme for determining the digit to the left of the
-         decimal-point character.
-

-
-
-
Footnote 280) No special provisions are made for multibyte characters.
-

-
-
-
Footnote 281) Redundant shift sequences may result if multibyte characters have a state-dependent encoding.
-

-
-
-
9    If a conversion specification is invalid, the behavior is undefined.282) If any argument is
+
+
9    If a conversion specification is invalid, the behavior is undefined.[282] If any argument is
      not the correct type for the corresponding conversion specification, the behavior is
      undefined.
 

-
 
-
Footnote 282) See ``future library directions'' (7.31.11).
+
Footnote 282) See ``future library directions'' (7.31.11).
 

 
-
+
 
10   In no case does a nonexistent or small field width cause truncation of a field; if the result
      of a conversion is wider than the field width, the field is expanded to contain the
      conversion result.
 

-
-
+
 
11   For a and A conversions, if FLT_RADIX is a power of 2, the value is correctly rounded
      to a hexadecimal floating number with the given precision.
      Recommended practice
 

-
-
+
 
12   For a and A conversions, if FLT_RADIX is not a power of 2 and the result is not exactly
      representable in the given precision, the result should be one of the two adjacent numbers
      in hexadecimal floating style with the given precision, with the extra stipulation that the
      error should have a correct sign for the current rounding direction.
 

-
-
+
 
13   For e, E, f, F, g, and G conversions, if the number of significant decimal digits is at most
-     DECIMAL_DIG, then the result should be correctly rounded.283) If the number of
+     DECIMAL_DIG, then the result should be correctly rounded.[283] If the number of
      significant decimal digits is more than DECIMAL_DIG but the source value is exactly
      representable with DECIMAL_DIG digits, then the result should be an exact
      representation with trailing zeros. Otherwise, the source value is bounded by two
      adjacent decimal strings L < U , both having DECIMAL_DIG significant digits; the value
-
-     of the resultant decimal string D should satisfy L  D  U , with the extra stipulation that
-     the error should have a correct sign for the current rounding direction.
-     Returns
 

-
 
 
Footnote 283) For binary-to-decimal conversion, the result format's values are the numbers representable with the
           given format specifier. The number of significant digits is determined by the format specifier, and in
           the case of fixed-point conversion by the source value as well.
+     of the resultant decimal string D should satisfy L  D  U , with the extra stipulation that
+     the error should have a correct sign for the current rounding direction.
+     Returns
 

 
-
+
 
14   The fprintf function returns the number of characters transmitted, or a negative value
      if an output or encoding error occurred.
      Environmental limits
 

-
-
+
 
15   The number of characters that can be produced by any single conversion shall be at least
      4095.
 

-
-
+
 
16   EXAMPLE 1         To print a date and time in the form ``Sunday, July 3, 10:02'' followed by  to five decimal
      places:
               #include <math.h>
@@ -18219,14 +15707,12 @@ char int_p_sep_by_space
               fprintf(stdout, "pi = %.5f\n", 4 * atan(1.0));
 
 

-
-
+
 
17   EXAMPLE 2 In this example, multibyte characters do not have a state-dependent encoding, and the
      members of the extended character set that consist of more than one byte each consist of exactly two bytes,
      the first of which is denoted here by a and the second by an uppercase letter.
 

-
-
+
 
18   Given the following wide string with length seven,
               static wchar_t wstr[] = L" X Yabc Z W";
      the seven calls
@@ -18246,23 +15732,20 @@ char int_p_sep_by_space
               |      abc Z W|
               |            Z|
 
-     Forward references: conversion state (7.29.6), the wcrtomb function (7.29.6.3.3).
+     Forward references: conversion state (7.29.6), the wcrtomb function (7.29.6.3.3).
 
 

-
-
+
 

 
7.21.6.2 [The fscanf function]

-

-
-
-
1           #include <stdio.h>
+
+
1 Synopsis
+           #include <stdio.h>
             int fscanf(FILE * restrict stream,
                  const char * restrict format, ...);
     Description
 

-
-
+
 
2   The fscanf function reads input from the stream pointed to by stream, under control
     of the string pointed to by format that specifies the admissible input sequences and how
     they are to be converted for assignment, using subsequent arguments as pointers to the
@@ -18270,8 +15753,7 @@ char int_p_sep_by_space
     the behavior is undefined. If the format is exhausted while arguments remain, the excess
     arguments are evaluated (as always) but are otherwise ignored.
 

-
-
+
 
3   The format shall be a multibyte character sequence, beginning and ending in its initial
     shift state. The format is composed of zero or more directives: one or more white-space
     characters, an ordinary multibyte character (neither % nor a white-space character), or a
@@ -18283,60 +15765,65 @@ char int_p_sep_by_space
     -- An optional length modifier that specifies the size of the receiving object.
     -- A conversion specifier character that specifies the type of conversion to be applied.
 

-
-
+
 
4   The fscanf function executes each directive of the format in turn. When all directives
     have been executed, or if a directive fails (as detailed below), the function returns.
     Failures are described as input failures (due to the occurrence of an encoding error or the
     unavailability of input characters), or matching failures (due to inappropriate input).
 

-
-
+
 
5   A directive composed of white-space character(s) is executed by reading input up to the
     first non-white-space character (which remains unread), or until no more characters can
     be read. The directive never fails.
 

-
-
+
 
6   A directive that is an ordinary multibyte character is executed by reading the next
     characters of the stream. If any of those characters differ from the ones composing the
     directive, the directive fails and the differing and subsequent characters remain unread.
     Similarly, if end-of-file, an encoding error, or a read error prevents a character from being
     read, the directive fails.
 

-
-
+
 
7   A directive that is a conversion specification defines a set of matching input sequences, as
     described below for each specifier. A conversion specification is executed in the
 
      following steps:
 

-
-
+
 
8    Input white-space characters (as specified by the isspace function) are skipped, unless
-     the specification includes a [, c, or n specifier.284)
+     the specification includes a [, c, or n specifier.[284]
 

-
 
 
Footnote 284) These white-space characters are not counted against a specified field width.
 

 
-
+
 
9    An input item is read from the stream, unless the specification includes an n specifier. An
      input item is defined as the longest sequence of input characters which does not exceed
-     any specified field width and which is, or is a prefix of, a matching input sequence.285)
+     any specified field width and which is, or is a prefix of, a matching input sequence.[285]
      The first character, if any, after the input item remains unread. If the length of the input
      item is zero, the execution of the directive fails; this condition is a matching failure unless
      end-of-file, an encoding error, or a read error prevented input from the stream, in which
      case it is an input failure.
 

-
 
 
Footnote 285) fscanf pushes back at most one input character onto the input stream. Therefore, some sequences
           that are acceptable to strtod, strtol, etc., are unacceptable to fscanf.
+     j            Specifies that a following d, i, o, u, x, X, or n conversion specifier applies
+                  to an argument with type pointer to intmax_t or uintmax_t.
+     z            Specifies that a following d, i, o, u, x, X, or n conversion specifier applies
+                  to an argument with type pointer to size_t or the corresponding signed
+                  integer type.
+     t            Specifies that a following d, i, o, u, x, X, or n conversion specifier applies
+                  to an argument with type pointer to ptrdiff_t or the corresponding
+                  unsigned integer type.
+     L            Specifies that a following a, A, e, E, f, F, g, or G conversion specifier
+                  applies to an argument with type pointer to long double.
+     If a length modifier appears with any conversion specifier other than as specified above,
+     the behavior is undefined.
 

 
-
+
 
10   Except in the case of a % specifier, the input item (or, in the case of a %n directive, the
      count of input characters) is converted to a type appropriate to the conversion specifier. If
      the input item is not a matching sequence, the execution of the directive fails: this
@@ -18346,8 +15833,7 @@ char int_p_sep_by_space
      does not have an appropriate type, or if the result of the conversion cannot be represented
      in the object, the behavior is undefined.
 

-
-
+
 
11   The length modifiers and their meanings are:
      hh             Specifies that a following d, i, o, u, x, X, or n conversion specifier applies
                     to an argument with type pointer to signed char or unsigned char.
@@ -18362,22 +15848,8 @@ char int_p_sep_by_space
      ll (ell-ell) Specifies that a following d, i, o, u, x, X, or n conversion specifier applies
                   to an argument with type pointer to long long int or unsigned
                   long long int.
-
-     j            Specifies that a following d, i, o, u, x, X, or n conversion specifier applies
-                  to an argument with type pointer to intmax_t or uintmax_t.
-     z            Specifies that a following d, i, o, u, x, X, or n conversion specifier applies
-                  to an argument with type pointer to size_t or the corresponding signed
-                  integer type.
-     t            Specifies that a following d, i, o, u, x, X, or n conversion specifier applies
-                  to an argument with type pointer to ptrdiff_t or the corresponding
-                  unsigned integer type.
-     L            Specifies that a following a, A, e, E, f, F, g, or G conversion specifier
-                  applies to an argument with type pointer to long double.
-     If a length modifier appears with any conversion specifier other than as specified above,
-     the behavior is undefined.
 

-
-
+
 
12   The conversion specifiers and their meanings are:
      d           Matches an optionally signed decimal integer, whose format is the same as
                  expected for the subject sequence of the strtol function with the value 10
@@ -18403,7 +15875,7 @@ char int_p_sep_by_space
              format is the same as expected for the subject sequence of the strtod
              function. The corresponding argument shall be a pointer to floating.
     c             Matches a sequence of characters of exactly the number specified by the field
-                  width (1 if no field width is present in the directive).286)
+                  width (1 if no field width is present in the directive).[286]
                   If no l length modifier is present, the corresponding argument shall be a
                   pointer to the initial element of a character array large enough to accept the
                   sequence. No null character is added.
@@ -18415,7 +15887,7 @@ char int_p_sep_by_space
                   corresponding argument shall be a pointer to the initial element of an array of
                   wchar_t large enough to accept the resulting sequence of wide characters.
                   No null wide character is added.
-    s             Matches a sequence of non-white-space characters.286)
+    s             Matches a sequence of non-white-space characters.[286]
                   If no l length modifier is present, the corresponding argument shall be a
                   pointer to the initial element of a character array large enough to accept the
                   sequence and a terminating null character, which will be added automatically.
@@ -18428,7 +15900,7 @@ char int_p_sep_by_space
                   to accept the sequence and the terminating null wide character, which will be
                   added automatically.
     [             Matches a nonempty sequence of characters from a set of expected characters
-                  (the scanset ).286)
+                  (the scanset ).[286]
                   If no l length modifier is present, the corresponding argument shall be a
                   pointer to the initial element of a character array large enough to accept the
                   sequence and a terminating null character, which will be added automatically.
@@ -18436,7 +15908,11 @@ char int_p_sep_by_space
                   characters that begins in the initial shift state. Each multibyte character is
                   converted to a wide character as if by a call to the mbrtowc function, with
                   the conversion state described by an mbstate_t object initialized to zero
-
+

+
+
Footnote 286) No special provisions are made for multibyte characters in the matching rules used by the c, s, and [
+         conversion specifiers -- the extent of the input field is determined on a byte-by-byte basis. The
+         resulting field is nevertheless a sequence of multibyte characters that begins in the initial shift state.
                     before the first multibyte character is converted. The corresponding argument
                     shall be a pointer to the initial element of an array of wchar_t large enough
                     to accept the sequence and the terminating null wide character, which will be
@@ -18469,55 +15945,109 @@ char int_p_sep_by_space
                     suppressing character or a field width, the behavior is undefined.
      %              Matches a single % character; no conversion or assignment occurs. The
                     complete conversion specification shall be %%.
+

+
+
+
Footnote 286) No special provisions are made for multibyte characters in the matching rules used by the c, s, and [
+         conversion specifiers -- the extent of the input field is determined on a byte-by-byte basis. The
+         resulting field is nevertheless a sequence of multibyte characters that begins in the initial shift state.
+                    before the first multibyte character is converted. The corresponding argument
+                    shall be a pointer to the initial element of an array of wchar_t large enough
+                    to accept the sequence and the terminating null wide character, which will be
+                    added automatically.
+                    The conversion specifier includes all subsequent characters in the format
+                    string, up to and including the matching right bracket (]). The characters
+                    between the brackets (the scanlist ) compose the scanset, unless the character
+                    after the left bracket is a circumflex (^), in which case the scanset contains all
+                    characters that do not appear in the scanlist between the circumflex and the
+                    right bracket. If the conversion specifier begins with [] or [^], the right
+                    bracket character is in the scanlist and the next following right bracket
+                    character is the matching right bracket that ends the specification; otherwise
+                    the first following right bracket character is the one that ends the
+                    specification. If a - character is in the scanlist and is not the first, nor the
+                    second where the first character is a ^, nor the last character, the behavior is
+                    implementation-defined.
+     p              Matches an implementation-defined set of sequences, which should be the
+                    same as the set of sequences that may be produced by the %p conversion of
+                    the fprintf function. The corresponding argument shall be a pointer to a
+                    pointer to void. The input item is converted to a pointer value in an
+                    implementation-defined manner. If the input item is a value converted earlier
+                    during the same program execution, the pointer that results shall compare
+                    equal to that value; otherwise the behavior of the %p conversion is undefined.
+     n              No input is consumed. The corresponding argument shall be a pointer to
+                    signed integer into which is to be written the number of characters read from
+                    the input stream so far by this call to the fscanf function. Execution of a
+                    %n directive does not increment the assignment count returned at the
+                    completion of execution of the fscanf function. No argument is converted,
+                    but one is consumed. If the conversion specification includes an assignment-
+                    suppressing character or a field width, the behavior is undefined.
+     %              Matches a single % character; no conversion or assignment occurs. The
+                    complete conversion specification shall be %%.
+

+
+
+
Footnote 286) No special provisions are made for multibyte characters in the matching rules used by the c, s, and [
+         conversion specifiers -- the extent of the input field is determined on a byte-by-byte basis. The
+         resulting field is nevertheless a sequence of multibyte characters that begins in the initial shift state.
+                    before the first multibyte character is converted. The corresponding argument
+                    shall be a pointer to the initial element of an array of wchar_t large enough
+                    to accept the sequence and the terminating null wide character, which will be
+                    added automatically.
+                    The conversion specifier includes all subsequent characters in the format
+                    string, up to and including the matching right bracket (]). The characters
+                    between the brackets (the scanlist ) compose the scanset, unless the character
+                    after the left bracket is a circumflex (^), in which case the scanset contains all
+                    characters that do not appear in the scanlist between the circumflex and the
+                    right bracket. If the conversion specifier begins with [] or [^], the right
+                    bracket character is in the scanlist and the next following right bracket
+                    character is the matching right bracket that ends the specification; otherwise
+                    the first following right bracket character is the one that ends the
+                    specification. If a - character is in the scanlist and is not the first, nor the
+                    second where the first character is a ^, nor the last character, the behavior is
+                    implementation-defined.
+     p              Matches an implementation-defined set of sequences, which should be the
+                    same as the set of sequences that may be produced by the %p conversion of
+                    the fprintf function. The corresponding argument shall be a pointer to a
+                    pointer to void. The input item is converted to a pointer value in an
+                    implementation-defined manner. If the input item is a value converted earlier
+                    during the same program execution, the pointer that results shall compare
+                    equal to that value; otherwise the behavior of the %p conversion is undefined.
+     n              No input is consumed. The corresponding argument shall be a pointer to
+                    signed integer into which is to be written the number of characters read from
+                    the input stream so far by this call to the fscanf function. Execution of a
+                    %n directive does not increment the assignment count returned at the
+                    completion of execution of the fscanf function. No argument is converted,
+                    but one is consumed. If the conversion specification includes an assignment-
+                    suppressing character or a field width, the behavior is undefined.
+     %              Matches a single % character; no conversion or assignment occurs. The
+                    complete conversion specification shall be %%.
+

+
+
+
13   If a conversion specification is invalid, the behavior is undefined.[287]
 

-
-
-
Footnote 286) No special provisions are made for multibyte characters in the matching rules used by the c, s, and [
-         conversion specifiers -- the extent of the input field is determined on a byte-by-byte basis. The
-         resulting field is nevertheless a sequence of multibyte characters that begins in the initial shift state.
-

-
-
-
Footnote 286) No special provisions are made for multibyte characters in the matching rules used by the c, s, and [
-         conversion specifiers -- the extent of the input field is determined on a byte-by-byte basis. The
-         resulting field is nevertheless a sequence of multibyte characters that begins in the initial shift state.
-

-
-
-
Footnote 286) No special provisions are made for multibyte characters in the matching rules used by the c, s, and [
-         conversion specifiers -- the extent of the input field is determined on a byte-by-byte basis. The
-         resulting field is nevertheless a sequence of multibyte characters that begins in the initial shift state.
-

-
-
-
13   If a conversion specification is invalid, the behavior is undefined.287)
-

-
 
-
Footnote 287) See ``future library directions'' (7.31.11).
+
Footnote 287) See ``future library directions'' (7.31.11).
 

 
-
+
 
14   The conversion specifiers A, E, F, G, and X are also valid and behave the same as,
      respectively, a, e, f, g, and x.
 
 

-
-
+
 
15   Trailing white space (including new-line characters) is left unread unless matched by a
      directive. The success of literal matches and suppressed assignments is not directly
      determinable other than via the %n directive.
      Returns
 

-
-
+
 
16   The fscanf function returns the value of the macro EOF if an input failure occurs
      before the first conversion (if any) has completed. Otherwise, the function returns the
      number of input items assigned, which can be fewer than provided for, or even zero, in
      the event of an early matching failure.
 

-
-
+
 
17   EXAMPLE 1        The call:
               #include <stdio.h>
               /* ... */
@@ -18529,8 +16059,7 @@ char int_p_sep_by_space
      thompson\0.
 
 

-
-
+
 
18   EXAMPLE 2        The call:
               #include <stdio.h>
               /* ... */
@@ -18542,8 +16071,7 @@ char int_p_sep_by_space
      sequence 56\0. The next character read from the input stream will be a.
 
 

-
-
+
 
19   EXAMPLE 3        To accept repeatedly from stdin a quantity, a unit of measure, and an item name:
               #include <stdio.h>
               /* ... */
@@ -18553,8 +16081,7 @@ char int_p_sep_by_space
                       fscanf(stdin,"%*[^\n]");
               } while (!feof(stdin) && !ferror(stdin));
 

-
-
+
 
20   If the stdin stream contains the following lines:
               2 quarts of oil
               -12.8degrees Celsius
@@ -18575,8 +16102,7 @@ char int_p_sep_by_space
                count     =   EOF;
 
 

-
-
+
 
21   EXAMPLE 4         In:
                #include <stdio.h>
                /* ... */
@@ -18586,8 +16112,7 @@ char int_p_sep_by_space
      of 3 is also assigned to n2. The value of d2 is not affected. The value 1 is assigned to i.
 
 

-
-
+
 
22   EXAMPLE 5         The call:
                #include <stdio.h>
                /* ... */
@@ -18597,16 +16122,14 @@ char int_p_sep_by_space
      the % and d conversion specifiers.
 
 

-
-
+
 
23   EXAMPLE 6 In these examples, multibyte characters do have a state-dependent encoding, and the
      members of the extended character set that consist of more than one byte each consist of exactly two bytes,
      the first of which is denoted here by a and the second by an uppercase letter, but are only recognized as
      such when in the alternate shift state. The shift sequences are denoted by  and , in which the first causes
      entry into the alternate shift state.
 

-
-
+
 
24   After the call:
                #include <stdio.h>
                /* ... */
@@ -18617,8 +16140,7 @@ char int_p_sep_by_space
      str will contain  X Y\0 assuming that none of the bytes of the shift sequences (or of the multibyte
      characters, in the more general case) appears to be a single-byte white-space character.
 

-
-
+
 
25   In contrast, after the call:
              #include <stdio.h>
              #include <stddef.h>
@@ -18628,8 +16150,7 @@ char int_p_sep_by_space
      with the same input line, wstr will contain the two wide characters that correspond to X and Y and a
      terminating null wide character.
 

-
-
+
 
26   However, the call:
              #include <stdio.h>
              #include <stddef.h>
@@ -18639,8 +16160,7 @@ char int_p_sep_by_space
      with the same input line will return zero due to a matching failure against the  sequence in the format
      string.
 

-
-
+
 
27   Assuming that the first byte of the multibyte character X is the same as the first byte of the multibyte
      character Y, after the call:
              #include <stdio.h>
@@ -18651,70 +16171,59 @@ char int_p_sep_by_space
      with the same input line, zero will again be returned, but stdin will be left with a partially consumed
      multibyte character.
 
-     Forward references: the strtod, strtof, and strtold functions (7.22.1.3), the
-     strtol, strtoll, strtoul, and strtoull functions (7.22.1.4), conversion state
-     (7.29.6), the wcrtomb function (7.29.6.3.3).
+     Forward references: the strtod, strtof, and strtold functions (7.22.1.3), the
+     strtol, strtoll, strtoul, and strtoull functions (7.22.1.4), conversion state
+     (7.29.6), the wcrtomb function (7.29.6.3.3).
 

-
-
+
 

 
7.21.6.3 [The printf function]

-

-
-
-
1            #include <stdio.h>
+
+
1 Synopsis
+            #include <stdio.h>
              int printf(const char * restrict format, ...);
      Description
 

-
-
+
 
2    The printf function is equivalent to fprintf with the argument stdout interposed
      before the arguments to printf.
      Returns
 

-
-
+
 
3    The printf function returns the number of characters transmitted, or a negative value if
      an output or encoding error occurred.
 

-
-
+
 

 
7.21.6.4 [The scanf function]

-

-
-
-
1           #include <stdio.h>
+
+
1 Synopsis
+           #include <stdio.h>
             int scanf(const char * restrict format, ...);
     Description
 

-
-
+
 
2   The scanf function is equivalent to fscanf with the argument stdin interposed
     before the arguments to scanf.
     Returns
 

-
-
+
 
3   The scanf function returns the value of the macro EOF if an input failure occurs before
     the first conversion (if any) has completed. Otherwise, the scanf function returns the
     number of input items assigned, which can be fewer than provided for, or even zero, in
     the event of an early matching failure.
 

-
-
+
 

 
7.21.6.5 [The snprintf function]

-

-
-
-
1           #include <stdio.h>
+
+
1 Synopsis
+           #include <stdio.h>
             int snprintf(char * restrict s, size_t n,
                  const char * restrict format, ...);
     Description
 

-
-
+
 
2   The snprintf function is equivalent to fprintf, except that the output is written into
     an array (specified by argument s) rather than to a stream. If n is zero, nothing is written,
     and s may be a null pointer. Otherwise, output characters beyond the n-1st are
@@ -18723,100 +16232,86 @@ char int_p_sep_by_space
     that overlap, the behavior is undefined.
     Returns
 

-
-
+
 
3   The snprintf function returns the number of characters that would have been written
     had n been sufficiently large, not counting the terminating null character, or a negative
     value if an encoding error occurred. Thus, the null-terminated output has been
     completely written if and only if the returned value is nonnegative and less than n.
 

-
-
+
 

 
7.21.6.6 [The sprintf function]

-

-
-
-
1           #include <stdio.h>
+
+
1 Synopsis
+           #include <stdio.h>
             int sprintf(char * restrict s,
                  const char * restrict format, ...);
     Description
 

-
-
+
 
2   The sprintf function is equivalent to fprintf, except that the output is written into
     an array (specified by the argument s) rather than to a stream. A null character is written
     at the end of the characters written; it is not counted as part of the returned value. If
     copying takes place between objects that overlap, the behavior is undefined.
     Returns
 

-
-
+
 
3   The sprintf function returns the number of characters written in the array, not
     counting the terminating null character, or a negative value if an encoding error occurred.
 

-
-
+
 

 
7.21.6.7 [The sscanf function]

-

-
-
-
1          #include <stdio.h>
+
+
1 Synopsis
+          #include <stdio.h>
            int sscanf(const char * restrict s,
                 const char * restrict format, ...);
     Description
 

-
-
+
 
2   The sscanf function is equivalent to fscanf, except that input is obtained from a
     string (specified by the argument s) rather than from a stream. Reaching the end of the
     string is equivalent to encountering end-of-file for the fscanf function. If copying
     takes place between objects that overlap, the behavior is undefined.
     Returns
 

-
-
+
 
3   The sscanf function returns the value of the macro EOF if an input failure occurs
     before the first conversion (if any) has completed. Otherwise, the sscanf function
     returns the number of input items assigned, which can be fewer than provided for, or even
     zero, in the event of an early matching failure.
 

-
-
+
 

 
7.21.6.8 [The vfprintf function]

-

-
-
-
1          #include <stdarg.h>
+
+
1 Synopsis
+          #include <stdarg.h>
            #include <stdio.h>
            int vfprintf(FILE * restrict stream,
                 const char * restrict format,
                 va_list arg);
     Description
 

-
-
+
 
2   The vfprintf function is equivalent to fprintf, with the variable argument list
     replaced by arg, which shall have been initialized by the va_start macro (and
     possibly subsequent va_arg calls). The vfprintf function does not invoke the
 
-    va_end macro.288)
+    va_end macro.[288]
     Returns
 

-
 
 
Footnote 288) As the functions vfprintf, vfscanf, vprintf, vscanf, vsnprintf, vsprintf, and
          vsscanf invoke the va_arg macro, the value of arg after the return is indeterminate.
 

 
-
+
 
3   The vfprintf function returns the number of characters transmitted, or a negative
     value if an output or encoding error occurred.
 

-
-
+
 
4   EXAMPLE       The following shows the use of the vfprintf function in a general error-reporting routine.
             #include <stdarg.h>
             #include <stdio.h>
@@ -18832,285 +16327,247 @@ char int_p_sep_by_space
             }
 
 

-
-
+
 

 
7.21.6.9 [The vfscanf function]

-

-
-
-
1           #include <stdarg.h>
+
+
1 Synopsis
+           #include <stdarg.h>
             #include <stdio.h>
             int vfscanf(FILE * restrict stream,
                  const char * restrict format,
                  va_list arg);
     Description
 

-
-
+
 
2   The vfscanf function is equivalent to fscanf, with the variable argument list
     replaced by arg, which shall have been initialized by the va_start macro (and
     possibly subsequent va_arg calls). The vfscanf function does not invoke the
-    va_end macro.288)
+    va_end macro.[288]
     Returns
 

-
 
 
Footnote 288) As the functions vfprintf, vfscanf, vprintf, vscanf, vsnprintf, vsprintf, and
          vsscanf invoke the va_arg macro, the value of arg after the return is indeterminate.
 

 
-
+
 
3   The vfscanf function returns the value of the macro EOF if an input failure occurs
     before the first conversion (if any) has completed. Otherwise, the vfscanf function
     returns the number of input items assigned, which can be fewer than provided for, or even
     zero, in the event of an early matching failure.
 
 

-
-
+
 

 
7.21.6.10 [The vprintf function]

-

-
-
-
1          #include <stdarg.h>
+
+
1 Synopsis
+          #include <stdarg.h>
            #include <stdio.h>
            int vprintf(const char * restrict format,
                 va_list arg);
     Description
 

-
-
+
 
2   The vprintf function is equivalent to printf, with the variable argument list
     replaced by arg, which shall have been initialized by the va_start macro (and
     possibly subsequent va_arg calls). The vprintf function does not invoke the
-    va_end macro.288)
+    va_end macro.[288]
     Returns
 

-
 
 
Footnote 288) As the functions vfprintf, vfscanf, vprintf, vscanf, vsnprintf, vsprintf, and
          vsscanf invoke the va_arg macro, the value of arg after the return is indeterminate.
 

 
-
+
 
3   The vprintf function returns the number of characters transmitted, or a negative value
     if an output or encoding error occurred.
 

-
-
+
 

 
7.21.6.11 [The vscanf function]

-

-
-
-
1          #include <stdarg.h>
+
+
1 Synopsis
+          #include <stdarg.h>
            #include <stdio.h>
            int vscanf(const char * restrict format,
                 va_list arg);
     Description
 

-
-
+
 
2   The vscanf function is equivalent to scanf, with the variable argument list replaced
     by arg, which shall have been initialized by the va_start macro (and possibly
     subsequent va_arg calls). The vscanf function does not invoke the va_end
-    macro.288)
+    macro.[288]
     Returns
 

-
 
 
Footnote 288) As the functions vfprintf, vfscanf, vprintf, vscanf, vsnprintf, vsprintf, and
          vsscanf invoke the va_arg macro, the value of arg after the return is indeterminate.
 

 
-
+
 
3   The vscanf function returns the value of the macro EOF if an input failure occurs
     before the first conversion (if any) has completed. Otherwise, the vscanf function
     returns the number of input items assigned, which can be fewer than provided for, or even
     zero, in the event of an early matching failure.
 

-
-
+
 

 
7.21.6.12 [The vsnprintf function]

-

-
-
-
1           #include <stdarg.h>
+
+
1 Synopsis
+           #include <stdarg.h>
             #include <stdio.h>
             int vsnprintf(char * restrict s, size_t n,
                  const char * restrict format,
                  va_list arg);
     Description
 

-
-
+
 
2   The vsnprintf function is equivalent to snprintf, with the variable argument list
     replaced by arg, which shall have been initialized by the va_start macro (and
     possibly subsequent va_arg calls). The vsnprintf function does not invoke the
-    va_end macro.288) If copying takes place between objects that overlap, the behavior is
+    va_end macro.[288] If copying takes place between objects that overlap, the behavior is
     undefined.
     Returns
 

-
 
 
Footnote 288) As the functions vfprintf, vfscanf, vprintf, vscanf, vsnprintf, vsprintf, and
          vsscanf invoke the va_arg macro, the value of arg after the return is indeterminate.
 

 
-
+
 
3   The vsnprintf function returns the number of characters that would have been written
     had n been sufficiently large, not counting the terminating null character, or a negative
     value if an encoding error occurred. Thus, the null-terminated output has been
     completely written if and only if the returned value is nonnegative and less than n.
 

-
-
+
 

 
7.21.6.13 [The vsprintf function]

-

-
-
-
1           #include <stdarg.h>
+
+
1 Synopsis
+           #include <stdarg.h>
             #include <stdio.h>
             int vsprintf(char * restrict s,
                  const char * restrict format,
                  va_list arg);
     Description
 

-
-
+
 
2   The vsprintf function is equivalent to sprintf, with the variable argument list
     replaced by arg, which shall have been initialized by the va_start macro (and
     possibly subsequent va_arg calls). The vsprintf function does not invoke the
-    va_end macro.288) If copying takes place between objects that overlap, the behavior is
+    va_end macro.[288] If copying takes place between objects that overlap, the behavior is
     undefined.
     Returns
 

-
 
 
Footnote 288) As the functions vfprintf, vfscanf, vprintf, vscanf, vsnprintf, vsprintf, and
          vsscanf invoke the va_arg macro, the value of arg after the return is indeterminate.
 

 
-
+
 
3   The vsprintf function returns the number of characters written in the array, not
     counting the terminating null character, or a negative value if an encoding error occurred.
 

-
-
+
 

 
7.21.6.14 [The vsscanf function]

-

-
-
-
1           #include <stdarg.h>
+
+
1 Synopsis
+           #include <stdarg.h>
             #include <stdio.h>
             int vsscanf(const char * restrict s,
                  const char * restrict format,
                  va_list arg);
     Description
 

-
-
+
 
2   The vsscanf function is equivalent to sscanf, with the variable argument list
     replaced by arg, which shall have been initialized by the va_start macro (and
     possibly subsequent va_arg calls). The vsscanf function does not invoke the
-    va_end macro.288)
+    va_end macro.[288]
     Returns
 

-
 
 
Footnote 288) As the functions vfprintf, vfscanf, vprintf, vscanf, vsnprintf, vsprintf, and
          vsscanf invoke the va_arg macro, the value of arg after the return is indeterminate.
 

 
-
+
 
3   The vsscanf function returns the value of the macro EOF if an input failure occurs
     before the first conversion (if any) has completed. Otherwise, the vsscanf function
     returns the number of input items assigned, which can be fewer than provided for, or even
     zero, in the event of an early matching failure.
 

-
-
+
 

 
7.21.7 [Character input/output functions]

-
 Character input/output functions
-

-
-
+
 

 
7.21.7.1 [The fgetc function]

-

-
-
-
1           #include <stdio.h>
+
+
1 Synopsis
+           #include <stdio.h>
             int fgetc(FILE *stream);
     Description
 

-
-
+
 
2   If the end-of-file indicator for the input stream pointed to by stream is not set and a
     next character is present, the fgetc function obtains that character as an unsigned
     char converted to an int and advances the associated file position indicator for the
     stream (if defined).
     Returns
 

-
-
+
 
3   If the end-of-file indicator for the stream is set, or if the stream is at end-of-file, the end-
     of-file indicator for the stream is set and the fgetc function returns EOF. Otherwise, the
     fgetc function returns the next character from the input stream pointed to by stream.
     If a read error occurs, the error indicator for the stream is set and the fgetc function
-    returns EOF.289)
+    returns EOF.[289]
 
 

-
 
 
Footnote 289) An end-of-file and a read error can be distinguished by use of the feof and ferror functions.
 

 
-
+
 

 
7.21.7.2 [The fgets function]

-

-
-
-
1           #include <stdio.h>
+
+
1 Synopsis
+           #include <stdio.h>
             char *fgets(char * restrict s, int n,
                  FILE * restrict stream);
     Description
 

-
-
+
 
2   The fgets function reads at most one less than the number of characters specified by n
     from the stream pointed to by stream into the array pointed to by s. No additional
     characters are read after a new-line character (which is retained) or after end-of-file. A
     null character is written immediately after the last character read into the array.
     Returns
 

-
-
+
 
3   The fgets function returns s if successful. If end-of-file is encountered and no
     characters have been read into the array, the contents of the array remain unchanged and a
     null pointer is returned. If a read error occurs during the operation, the array contents are
     indeterminate and a null pointer is returned.
 

-
-
+
 

 
7.21.7.3 [The fputc function]

-

-
-
-
1           #include <stdio.h>
+
+
1 Synopsis
+           #include <stdio.h>
             int fputc(int c, FILE *stream);
     Description
 

-
-
+
 
2   The fputc function writes the character specified by c (converted to an unsigned
     char) to the output stream pointed to by stream, at the position indicated by the
     associated file position indicator for the stream (if defined), and advances the indicator
@@ -19118,163 +16575,135 @@ char int_p_sep_by_space
     with append mode, the character is appended to the output stream.
     Returns
 

-
-
+
 
3   The fputc function returns the character written. If a write error occurs, the error
     indicator for the stream is set and fputc returns EOF.
 

-
-
+
 

 
7.21.7.4 [The fputs function]

-

-
-
-
1           #include <stdio.h>
+
+
1 Synopsis
+           #include <stdio.h>
             int fputs(const char * restrict s,
                  FILE * restrict stream);
 
     Description
 

-
-
+
 
2   The fputs function writes the string pointed to by s to the stream pointed to by
     stream. The terminating null character is not written.
     Returns
 

-
-
+
 
3   The fputs function returns EOF if a write error occurs; otherwise it returns a
     nonnegative value.
 

-
-
+
 

 
7.21.7.5 [The getc function]

-

-
-
-
1          #include <stdio.h>
+
+
1 Synopsis
+          #include <stdio.h>
            int getc(FILE *stream);
     Description
 

-
-
+
 
2   The getc function is equivalent to fgetc, except that if it is implemented as a macro, it
     may evaluate stream more than once, so the argument should never be an expression
     with side effects.
     Returns
 

-
-
+
 
3   The getc function returns the next character from the input stream pointed to by
     stream. If the stream is at end-of-file, the end-of-file indicator for the stream is set and
     getc returns EOF. If a read error occurs, the error indicator for the stream is set and
     getc returns EOF.
 

-
-
+
 

 
7.21.7.6 [The getchar function]

-

-
-
-
1          #include <stdio.h>
+
+
1 Synopsis
+          #include <stdio.h>
            int getchar(void);
     Description
 

-
-
+
 
2   The getchar function is equivalent to getc with the argument stdin.
     Returns
 

-
-
+
 
3   The getchar function returns the next character from the input stream pointed to by
     stdin. If the stream is at end-of-file, the end-of-file indicator for the stream is set and
     getchar returns EOF. If a read error occurs, the error indicator for the stream is set and
     getchar returns EOF.
 

-
-
+
 

 
7.21.7.7 [The putc function]

-

-
-
-
1           #include <stdio.h>
+
+
1 Synopsis
+           #include <stdio.h>
             int putc(int c, FILE *stream);
     Description
 

-
-
+
 
2   The putc function is equivalent to fputc, except that if it is implemented as a macro, it
     may evaluate stream more than once, so that argument should never be an expression
     with side effects.
     Returns
 

-
-
+
 
3   The putc function returns the character written. If a write error occurs, the error
     indicator for the stream is set and putc returns EOF.
 

-
-
+
 

 
7.21.7.8 [The putchar function]

-

-
-
-
1           #include <stdio.h>
+
+
1 Synopsis
+           #include <stdio.h>
             int putchar(int c);
     Description
 

-
-
+
 
2   The putchar function is equivalent to putc with the second argument stdout.
     Returns
 

-
-
+
 
3   The putchar function returns the character written. If a write error occurs, the error
     indicator for the stream is set and putchar returns EOF.
 

-
-
+
 

 
7.21.7.9 [The puts function]

-

-
-
-
1           #include <stdio.h>
+
+
1 Synopsis
+           #include <stdio.h>
             int puts(const char *s);
     Description
 

-
-
+
 
2   The puts function writes the string pointed to by s to the stream pointed to by stdout,
     and appends a new-line character to the output. The terminating null character is not
     written.
     Returns
 

-
-
+
 
3   The puts function returns EOF if a write error occurs; otherwise it returns a nonnegative
     value.
 

-
-
+
 

 
7.21.7.10 [The ungetc function]

-

-
-
-
1            #include <stdio.h>
+
+
1 Synopsis
+            #include <stdio.h>
              int ungetc(int c, FILE *stream);
     Description
 

-
-
+
 
2   The ungetc function pushes the character specified by c (converted to an unsigned
     char) back onto the input stream pointed to by stream. Pushed-back characters will be
     returned by subsequent reads on that stream in the reverse order of their pushing. A
@@ -19282,19 +16711,16 @@ char int_p_sep_by_space
     function (fseek, fsetpos, or rewind) discards any pushed-back characters for the
     stream. The external storage corresponding to the stream is unchanged.
 

-
-
+
 
3   One character of pushback is guaranteed. If the ungetc function is called too many
     times on the same stream without an intervening read or file positioning operation on that
     stream, the operation may fail.
 

-
-
+
 
4   If the value of c equals that of the macro EOF, the operation fails and the input stream is
     unchanged.
 

-
-
+
 
5   A successful call to the ungetc function clears the end-of-file indicator for the stream.
     The value of the file position indicator for the stream after reading or discarding all
     pushed-back characters shall be the same as it was before the characters were pushed
@@ -19302,41 +16728,34 @@ char int_p_sep_by_space
     ungetc function is unspecified until all pushed-back characters are read or discarded.
     For a binary stream, its file position indicator is decremented by each successful call to
     the ungetc function; if its value was zero before a call, it is indeterminate after the
-    call.290)
+    call.[290]
     Returns
 

-
 
-
Footnote 290) See ``future library directions'' (7.31.11).
+
Footnote 290) See ``future library directions'' (7.31.11).
 

 
-
+
 
6   The ungetc function returns the character pushed back after conversion, or EOF if the
     operation fails.
-    Forward references: file positioning functions (7.21.9).
+    Forward references: file positioning functions (7.21.9).
 
 

-
-
+
 

 
7.21.8 [Direct input/output functions]

-
 Direct input/output functions
-

-
-
+
 

 
7.21.8.1 [The fread function]

-

-
-
-
1           #include <stdio.h>
+
+
1 Synopsis
+           #include <stdio.h>
             size_t fread(void * restrict ptr,
                  size_t size, size_t nmemb,
                  FILE * restrict stream);
     Description
 

-
-
+
 
2   The fread function reads, into the array pointed to by ptr, up to nmemb elements
     whose size is specified by size, from the stream pointed to by stream. For each
     object, size calls are made to the fgetc function and the results stored, in the order
@@ -19346,28 +16765,24 @@ char int_p_sep_by_space
     indeterminate. If a partial element is read, its value is indeterminate.
     Returns
 

-
-
+
 
3   The fread function returns the number of elements successfully read, which may be
     less than nmemb if a read error or end-of-file is encountered. If size or nmemb is zero,
     fread returns zero and the contents of the array and the state of the stream remain
     unchanged.
 

-
-
+
 

 
7.21.8.2 [The fwrite function]

-

-
-
-
1           #include <stdio.h>
+
+
1 Synopsis
+           #include <stdio.h>
             size_t fwrite(const void * restrict ptr,
                  size_t size, size_t nmemb,
                  FILE * restrict stream);
     Description
 

-
-
+
 
2   The fwrite function writes, from the array pointed to by ptr, up to nmemb elements
     whose size is specified by size, to the stream pointed to by stream. For each object,
     size calls are made to the fputc function, taking the values (in order) from an array of
@@ -19377,133 +16792,110 @@ char int_p_sep_by_space
     indeterminate.
     Returns
 

-
-
+
 
3   The fwrite function returns the number of elements successfully written, which will be
     less than nmemb only if a write error is encountered. If size or nmemb is zero,
     fwrite returns zero and the state of the stream remains unchanged.
 

-
-
+
 

 
7.21.9 [File positioning functions]

-
 File positioning functions
-

-
-
+
 

 
7.21.9.1 [The fgetpos function]

-

-
-
-
1          #include <stdio.h>
+
+
1 Synopsis
+          #include <stdio.h>
            int fgetpos(FILE * restrict stream,
                 fpos_t * restrict pos);
     Description
 

-
-
+
 
2   The fgetpos function stores the current values of the parse state (if any) and file
     position indicator for the stream pointed to by stream in the object pointed to by pos.
     The values stored contain unspecified information usable by the fsetpos function for
     repositioning the stream to its position at the time of the call to the fgetpos function.
     Returns
 

-
-
+
 
3   If successful, the fgetpos function returns zero; on failure, the fgetpos function
     returns nonzero and stores an implementation-defined positive value in errno.
-    Forward references: the fsetpos function (7.21.9.3).
+    Forward references: the fsetpos function (7.21.9.3).
 

-
-
+
 

 
7.21.9.2 [The fseek function]

-

-
-
-
1          #include <stdio.h>
+
+
1 Synopsis
+          #include <stdio.h>
            int fseek(FILE *stream, long int offset, int whence);
     Description
 

-
-
+
 
2   The fseek function sets the file position indicator for the stream pointed to by stream.
     If a read or write error occurs, the error indicator for the stream is set and fseek fails.
 

-
-
+
 
3   For a binary stream, the new position, measured in characters from the beginning of the
     file, is obtained by adding offset to the position specified by whence. The specified
     position is the beginning of the file if whence is SEEK_SET, the current value of the file
     position indicator if SEEK_CUR, or end-of-file if SEEK_END. A binary stream need not
     meaningfully support fseek calls with a whence value of SEEK_END.
 

-
-
+
 
4   For a text stream, either offset shall be zero, or offset shall be a value returned by
     an earlier successful call to the ftell function on a stream associated with the same file
     and whence shall be SEEK_SET.
 
 

-
-
+
 
5   After determining the new position, a successful call to the fseek function undoes any
     effects of the ungetc function on the stream, clears the end-of-file indicator for the
     stream, and then establishes the new position. After a successful fseek call, the next
     operation on an update stream may be either input or output.
     Returns
 

-
-
+
 
6   The fseek function returns nonzero only for a request that cannot be satisfied.
-    Forward references: the ftell function (7.21.9.4).
+    Forward references: the ftell function (7.21.9.4).
 

-
-
+
 

 
7.21.9.3 [The fsetpos function]

-

-
-
-
1           #include <stdio.h>
+
+
1 Synopsis
+           #include <stdio.h>
             int fsetpos(FILE *stream, const fpos_t *pos);
     Description
 

-
-
+
 
2   The fsetpos function sets the mbstate_t object (if any) and file position indicator
     for the stream pointed to by stream according to the value of the object pointed to by
     pos, which shall be a value obtained from an earlier successful call to the fgetpos
     function on a stream associated with the same file. If a read or write error occurs, the
     error indicator for the stream is set and fsetpos fails.
 

-
-
+
 
3   A successful call to the fsetpos function undoes any effects of the ungetc function
     on the stream, clears the end-of-file indicator for the stream, and then establishes the new
     parse state and position. After a successful fsetpos call, the next operation on an
     update stream may be either input or output.
     Returns
 

-
-
+
 
4   If successful, the fsetpos function returns zero; on failure, the fsetpos function
     returns nonzero and stores an implementation-defined positive value in errno.
 

-
-
+
 

 
7.21.9.4 [The ftell function]

-

-
-
-
1           #include <stdio.h>
+
+
1 Synopsis
+           #include <stdio.h>
             long int ftell(FILE *stream);
     Description
 

-
-
+
 
2   The ftell function obtains the current value of the file position indicator for the stream
     pointed to by stream. For a binary stream, the value is the number of characters from
     the beginning of the file. For a text stream, its file position indicator contains unspecified
@@ -19514,117 +16906,94 @@ char int_p_sep_by_space
     or read.
     Returns
 

-
-
+
 
3   If successful, the ftell function returns the current value of the file position indicator
     for the stream. On failure, the ftell function returns -1L and stores an
     implementation-defined positive value in errno.
 

-
-
+
 

 
7.21.9.5 [The rewind function]

-

-
-
-
1          #include <stdio.h>
+
+
1 Synopsis
+          #include <stdio.h>
            void rewind(FILE *stream);
     Description
 

-
-
+
 
2   The rewind function sets the file position indicator for the stream pointed to by
     stream to the beginning of the file. It is equivalent to
            (void)fseek(stream, 0L, SEEK_SET)
     except that the error indicator for the stream is also cleared.
     Returns
 

-
-
+
 
3   The rewind function returns no value.
 

-
-
+
 

 
7.21.10 [Error-handling functions]

-
 Error-handling functions
-

-
-
+
 

 
7.21.10.1 [The clearerr function]

-

-
-
-
1          #include <stdio.h>
+
+
1 Synopsis
+          #include <stdio.h>
            void clearerr(FILE *stream);
     Description
 

-
-
+
 
2   The clearerr function clears the end-of-file and error indicators for the stream pointed
     to by stream.
     Returns
 

-
-
+
 
3   The clearerr function returns no value.
 

-
-
+
 

 
7.21.10.2 [The feof function]

-

-
-
-
1           #include <stdio.h>
+
+
1 Synopsis
+           #include <stdio.h>
             int feof(FILE *stream);
     Description
 

-
-
+
 
2   The feof function tests the end-of-file indicator for the stream pointed to by stream.
     Returns
 

-
-
+
 
3   The feof function returns nonzero if and only if the end-of-file indicator is set for
     stream.
 

-
-
+
 

 
7.21.10.3 [The ferror function]

-

-
-
-
1           #include <stdio.h>
+
+
1 Synopsis
+           #include <stdio.h>
             int ferror(FILE *stream);
     Description
 

-
-
+
 
2   The ferror function tests the error indicator for the stream pointed to by stream.
     Returns
 

-
-
+
 
3   The ferror function returns nonzero if and only if the error indicator is set for
     stream.
 

-
-
+
 

 
7.21.10.4 [The perror function]

-

-
-
-
1           #include <stdio.h>
+
+
1 Synopsis
+           #include <stdio.h>
             void perror(const char *s);
     Description
 

-
-
+
 
2   The perror function maps the error number in the integer expression errno to an
     error message. It writes a sequence of characters to the standard error stream thus: first
     (if s is not a null pointer and the character pointed to by s is not the null character), the
@@ -19633,28 +17002,23 @@ char int_p_sep_by_space
     strings are the same as those returned by the strerror function with argument errno.
     Returns
 

-
-
+
 
3   The perror function returns no value.
-    Forward references: the strerror function (7.24.6.2).
+    Forward references: the strerror function (7.24.6.2).
 

-
-
+
 

-
7.22 [General utilities ]

-

-
-
+
7.22 [General utilities <stdlib.h>]

+
 
1   The header <stdlib.h> declares five types and several functions of general utility, and
-    defines several macros.291)
+    defines several macros.[291]
 

-
 
-
Footnote 291) See ``future library directions'' (7.31.12).
+
Footnote 291) See ``future library directions'' (7.31.12).
 

 
-
-
2   The types declared are size_t and wchar_t (both described in 7.19),
+
+
2   The types declared are size_t and wchar_t (both described in 7.19),
              div_t
     which is a structure type that is the type of the value returned by the div function,
              ldiv_t
@@ -19662,9 +17026,8 @@ char int_p_sep_by_space
              lldiv_t
     which is a structure type that is the type of the value returned by the lldiv function.
 

-
-
-
3   The macros defined are NULL (described in 7.19);
+
+
3   The macros defined are NULL (described in 7.19);
              EXIT_FAILURE
     and
              EXIT_SUCCESS
@@ -19680,55 +17043,45 @@ char int_p_sep_by_space
     current locale (category LC_CTYPE), which is never greater than MB_LEN_MAX.
 
 

-
-
+
 

 
7.22.1 [Numeric conversion functions]

-

-
-
+
 
1   The functions atof, atoi, atol, and atoll need not affect the value of the integer
     expression errno on an error. If the value of the result cannot be represented, the
     behavior is undefined.
 

-
-
+
 

 
7.22.1.1 [The atof function]

-

-
-
-
1           #include <stdlib.h>
+
+
1 Synopsis
+           #include <stdlib.h>
             double atof(const char *nptr);
     Description
 

-
-
+
 
2   The atof function converts the initial portion of the string pointed to by nptr to
     double representation. Except for the behavior on error, it is equivalent to
             strtod(nptr, (char **)NULL)
     Returns
 

-
-
+
 
3   The atof function returns the converted value.
-    Forward references: the strtod, strtof, and strtold functions (7.22.1.3).
+    Forward references: the strtod, strtof, and strtold functions (7.22.1.3).
 

-
-
+
 

 
7.22.1.2 [The atoi, atol, and atoll functions]

-

-
-
-
1           #include <stdlib.h>
+
+
1 Synopsis
+           #include <stdlib.h>
             int atoi(const char *nptr);
             long int atol(const char *nptr);
             long long int atoll(const char *nptr);
     Description
 

-
-
+
 
2   The atoi, atol, and atoll functions convert the initial portion of the string pointed
     to by nptr to int, long int, and long long int representation, respectively.
     Except for the behavior on error, they are equivalent to
@@ -19737,21 +17090,18 @@ char int_p_sep_by_space
             atoll: strtoll(nptr, (char **)NULL, 10)
     Returns
 

-
-
+
 
3   The atoi, atol, and atoll functions return the converted value.
     Forward references: the strtol, strtoll, strtoul, and strtoull functions
-    (7.22.1.4).
+    (7.22.1.4).
 
 

-
-
+
 

 
7.22.1.3 [The strtod, strtof, and strtold functions]

-

-
-
-
1          #include <stdlib.h>
+
+
1 Synopsis
+          #include <stdlib.h>
            double strtod(const char * restrict nptr,
                 char ** restrict endptr);
            float strtof(const char * restrict nptr,
@@ -19760,8 +17110,7 @@ char int_p_sep_by_space
                 char ** restrict endptr);
     Description
 

-
-
+
 
2   The strtod, strtof, and strtold functions convert the initial portion of the string
     pointed to by nptr to double, float, and long double representation,
     respectively. First, they decompose the input string into three parts: an initial, possibly
@@ -19771,14 +17120,13 @@ char int_p_sep_by_space
     character of the input string. Then, they attempt to convert the subject sequence to a
     floating-point number, and return the result.
 

-
-
+
 
3   The expected form of the subject sequence is an optional plus or minus sign, then one of
     the following:
     -- a nonempty sequence of decimal digits optionally containing a decimal-point
-       character, then an optional exponent part as defined in 6.4.4.2;
+       character, then an optional exponent part as defined in 6.4.4.2;
     -- a 0x or 0X, then a nonempty sequence of hexadecimal digits optionally containing a
-       decimal-point character, then an optional binary exponent part as defined in 6.4.4.2;
+       decimal-point character, then an optional binary exponent part as defined in 6.4.4.2;
     -- INF or INFINITY, ignoring case
     -- NAN or NAN(n-char-sequenceopt), ignoring case in the NAN part, where:
                n-char-sequence:
@@ -19790,28 +17138,26 @@ char int_p_sep_by_space
     starting with the first non-white-space character, that is of the expected form. The subject
     sequence contains no characters if the input string is not of the expected form.
 

-
-
+
 
4   If the subject sequence has the expected form for a floating-point number, the sequence of
     characters starting with the first digit or the decimal-point character (whichever occurs
-    first) is interpreted as a floating constant according to the rules of 6.4.4.2, except that the
+    first) is interpreted as a floating constant according to the rules of 6.4.4.2, except that the
     decimal-point character is used in place of a period, and that if neither an exponent part
     nor a decimal-point character appears in a decimal floating point number, or if a binary
     exponent part does not appear in a hexadecimal floating point number, an exponent part
     of the appropriate type with value zero is assumed to follow the last digit in the string. If
-    the subject sequence begins with a minus sign, the sequence is interpreted as negated.292)
+    the subject sequence begins with a minus sign, the sequence is interpreted as negated.[292]
     A character sequence INF or INFINITY is interpreted as an infinity, if representable in
     the return type, else like a floating constant that is too large for the range of the return
     type. A character sequence NAN or NAN(n-char-sequenceopt) is interpreted as a quiet
     NaN, if supported in the return type, else like a subject sequence part that does not have
-    the expected form; the meaning of the n-char sequence is implementation-defined.293) A
+    the expected form; the meaning of the n-char sequence is implementation-defined.[293] A
     pointer to the final string is stored in the object pointed to by endptr, provided that
     endptr is not a null pointer.
 

-
 
 
Footnote 292) It is unspecified whether a minus-signed sequence is converted to a negative number directly or by
-         negating the value resulting from converting the corresponding unsigned sequence (see F.5); the two
+         negating the value resulting from converting the corresponding unsigned sequence (see F.5); the two
          methods may yield different results if rounding is toward positive or negative infinity. In either case,
          the functions honor the sign of zero if floating-point arithmetic supports signed zeros.
 

@@ -19819,34 +17165,33 @@ char int_p_sep_by_space
 
 
Footnote 293) An implementation may use the n-char sequence to determine extra information to be represented in
          the NaN's significand.
+     stipulation that the error with respect to D should have a correct sign for the current
+     rounding direction.294)
+     Returns
 

 
-
+
 
5   If the subject sequence has the hexadecimal form and FLT_RADIX is a power of 2, the
     value resulting from the conversion is correctly rounded.
 

-
-
+
 
6   In other than the "C" locale, additional locale-specific subject sequence forms may be
     accepted.
 

-
-
+
 
7   If the subject sequence is empty or does not have the expected form, no conversion is
     performed; the value of nptr is stored in the object pointed to by endptr, provided
     that endptr is not a null pointer.
     Recommended practice
 

-
-
+
 
8   If the subject sequence has the hexadecimal form, FLT_RADIX is not a power of 2, and
     the result is not exactly representable, the result should be one of the two numbers in the
     appropriate internal format that are adjacent to the hexadecimal floating source value,
     with the extra stipulation that the error should have a correct sign for the current rounding
     direction.
 

-
-
+
 
9   If the subject sequence has the decimal form and at most DECIMAL_DIG (defined in
     <float.h>) significant digits, the result should be correctly rounded. If the subject
     sequence D has the decimal form and more than DECIMAL_DIG significant digits,
@@ -19854,34 +17199,22 @@ char int_p_sep_by_space
     DECIMAL_DIG significant digits, such that the values of L , D, and U satisfy L  D  U .
     The result should be one of the (equal or adjacent) values that would be obtained by
     correctly rounding L and U according to the current rounding direction, with the extra
-
-     stipulation that the error with respect to D should have a correct sign for the current
-     rounding direction.294)
-     Returns
 

-
-
-
Footnote 294) DECIMAL_DIG, defined in <float.h>, should be sufficiently large that L and U will usually round
-          to the same internal floating value, but if not will round to adjacent values.
-

-
-
+
 
10   The functions return the converted value, if any. If no conversion could be performed,
-     zero is returned. If the correct value overflows and default rounding is in effect (7.12.1),
+     zero is returned. If the correct value overflows and default rounding is in effect (7.12.1),
      plus or minus HUGE_VAL, HUGE_VALF, or HUGE_VALL is returned (according to the
      return type and sign of the value), and the value of the macro ERANGE is stored in
-     errno. If the result underflows (7.12.1), the functions return a value whose magnitude is
+     errno. If the result underflows (7.12.1), the functions return a value whose magnitude is
      no greater than the smallest normalized positive number in the return type; whether
      errno acquires the value ERANGE is implementation-defined.
 

-
-
+
 

 
7.22.1.4 [The strtol, strtoll, strtoul, and strtoull functions]

-

-
-
-
1            #include <stdlib.h>
+
+
1 Synopsis
+            #include <stdlib.h>
              long int strtol(
                   const char * restrict nptr,
                   char ** restrict endptr,
@@ -19900,23 +17233,16 @@ char int_p_sep_by_space
                   int base);
      Description
 

-
-
+
 
2    The strtol, strtoll, strtoul, and strtoull functions convert the initial
      portion of the string pointed to by nptr to long int, long long int, unsigned
      long int, and unsigned long long int representation, respectively. First,
      they decompose the input string into three parts: an initial, possibly empty, sequence of
      white-space characters (as specified by the isspace function), a subject sequence
-
-    resembling an integer represented in some radix determined by the value of base, and a
-    final string of one or more unrecognized characters, including the terminating null
-    character of the input string. Then, they attempt to convert the subject sequence to an
-    integer, and return the result.
 

-
-
+
 
3   If the value of base is zero, the expected form of the subject sequence is that of an
-    integer constant as described in 6.4.4.1, optionally preceded by a plus or minus sign, but
+    integer constant as described in 6.4.4.1, optionally preceded by a plus or minus sign, but
     not including an integer suffix. If the value of base is between 2 and 36 (inclusive), the
     expected form of the subject sequence is a sequence of letters and digits representing an
     integer with the radix specified by base, optionally preceded by a plus or minus sign,
@@ -19925,121 +17251,100 @@ char int_p_sep_by_space
     than that of base are permitted. If the value of base is 16, the characters 0x or 0X may
     optionally precede the sequence of letters and digits, following the sign if present.
 

-
-
+
 
4   The subject sequence is defined as the longest initial subsequence of the input string,
     starting with the first non-white-space character, that is of the expected form. The subject
     sequence contains no characters if the input string is empty or consists entirely of white
     space, or if the first non-white-space character is other than a sign or a permissible letter
     or digit.
 

-
-
+
 
5   If the subject sequence has the expected form and the value of base is zero, the sequence
     of characters starting with the first digit is interpreted as an integer constant according to
-    the rules of 6.4.4.1. If the subject sequence has the expected form and the value of base
+    the rules of 6.4.4.1. If the subject sequence has the expected form and the value of base
     is between 2 and 36, it is used as the base for conversion, ascribing to each letter its value
     as given above. If the subject sequence begins with a minus sign, the value resulting from
     the conversion is negated (in the return type). A pointer to the final string is stored in the
     object pointed to by endptr, provided that endptr is not a null pointer.
 

-
-
+
 
6   In other than the "C" locale, additional locale-specific subject sequence forms may be
     accepted.
 

-
-
+
 
7   If the subject sequence is empty or does not have the expected form, no conversion is
     performed; the value of nptr is stored in the object pointed to by endptr, provided
     that endptr is not a null pointer.
     Returns
 

-
-
+
 
8   The strtol, strtoll, strtoul, and strtoull functions return the converted
     value, if any. If no conversion could be performed, zero is returned. If the correct value
     is outside the range of representable values, LONG_MIN, LONG_MAX, LLONG_MIN,
     LLONG_MAX, ULONG_MAX, or ULLONG_MAX is returned (according to the return type
     and sign of the value, if any), and the value of the macro ERANGE is stored in errno.
 

-
-
+
 

 
7.22.2 [Pseudo-random sequence generation functions]

-
 Pseudo-random sequence generation functions
-

-
-
+
 

 
7.22.2.1 [The rand function]

-

-
-
-
1           #include <stdlib.h>
+
+
1 Synopsis
+           #include <stdlib.h>
             int rand(void);
     Description
 

-
-
+
 
2   The rand function computes a sequence of pseudo-random integers in the range 0 to
-    RAND_MAX.295)
+    RAND_MAX.[295]
 

-
 
 
Footnote 295) There are no guarantees as to the quality of the random sequence produced and some implementations
          are known to produce sequences with distressingly non-random low-order bits. Applications with
          particular requirements should use a generator that is known to be sufficient for their needs.
+    Returns
 

 
-
+
 
3   The rand function is not required to avoid data races with other calls to pseudo-random
     sequence generation functions. The implementation shall behave as if no library function
     calls the rand function.
     Returns
 

-
-
+
 
4   The rand function returns a pseudo-random integer.
     Environmental limits
 

-
-
+
 
5   The value of the RAND_MAX macro shall be at least 32767.
 

-
-
+
 

 
7.22.2.2 [The srand function]

-

-
-
-
1           #include <stdlib.h>
+
+
1 Synopsis
+           #include <stdlib.h>
             void srand(unsigned int seed);
     Description
 

-
-
+
 
2   The srand function uses the argument as a seed for a new sequence of pseudo-random
     numbers to be returned by subsequent calls to rand. If srand is then called with the
     same seed value, the sequence of pseudo-random numbers shall be repeated. If rand is
     called before any calls to srand have been made, the same sequence shall be generated
     as when srand is first called with a seed value of 1.
 

-
-
+
 
3   The srand function is not required to avoid data races with other calls to pseudo-
     random sequence generation functions. The implementation shall behave as if no library
     function calls the srand function.
-
-    Returns
 

-
-
+
 
4   The srand function returns no value.
 

-
-
+
 
5   EXAMPLE     The following functions define a portable implementation of rand and srand.
             static unsigned long int next = 1;
             int rand(void)   // RAND_MAX assumed to be 32767
@@ -20053,13 +17358,10 @@ char int_p_sep_by_space
             }
 
 

-
-
+
 

 
7.22.3 [Memory management functions]

-

-
-
+
 
1   The order and contiguity of storage allocated by successive calls to the
     aligned_alloc, calloc, malloc, and realloc functions is unspecified. The
     pointer returned if the allocation succeeds is suitably aligned so that it may be assigned to
@@ -20073,8 +17375,7 @@ char int_p_sep_by_space
     is returned, or the behavior is as if the size were some nonzero value, except that the
     returned pointer shall not be used to access an object.
 

-
-
+
 
2   For purposes of determining the existence of a data race, memory allocation functions
     behave as though they accessed only memory locations accessible through their
     arguments and not other static duration storage. These functions may, however, visibly
@@ -20083,70 +17384,59 @@ char int_p_sep_by_space
     or part of the region p. This synchronization occurs after any access of p by the
     deallocating function, and before any such access by the allocating function.
 

-
-
+
 

 
7.22.3.1 [The aligned_alloc function]

-

-
-
-
1           #include <stdlib.h>
+
+
1 Synopsis
+           #include <stdlib.h>
             void *aligned_alloc(size_t alignment, size_t size);
 
     Description
 

-
-
+
 
2   The aligned_alloc function allocates space for an object whose alignment is
     specified by alignment, whose size is specified by size, and whose value is
     indeterminate. The value of alignment shall be a valid alignment supported by the
     implementation and the value of size shall be an integral multiple of alignment.
     Returns
 

-
-
+
 
3   The aligned_alloc function returns either a null pointer or a pointer to the allocated
     space.
 

-
-
+
 

 
7.22.3.2 [The calloc function]

-

-
-
-
1           #include <stdlib.h>
+
+
1 Synopsis
+           #include <stdlib.h>
             void *calloc(size_t nmemb, size_t size);
     Description
 

-
-
+
 
2   The calloc function allocates space for an array of nmemb objects, each of whose size
-    is size. The space is initialized to all bits zero.296)
+    is size. The space is initialized to all bits zero.[296]
     Returns
 

-
 
 
Footnote 296) Note that this need not be the same as the representation of floating-point zero or a null pointer
          constant.
 

 
-
+
 
3   The calloc function returns either a null pointer or a pointer to the allocated space.
 

-
-
+
 

 
7.22.3.3 [The free function]

-

-
-
-
1           #include <stdlib.h>
+
+
1 Synopsis
+           #include <stdlib.h>
             void free(void *ptr);
     Description
 

-
-
+
 
2   The free function causes the space pointed to by ptr to be deallocated, that is, made
     available for further allocation. If ptr is a null pointer, no action occurs. Otherwise, if
     the argument does not match a pointer earlier returned by a memory management
@@ -20154,53 +17444,44 @@ char int_p_sep_by_space
     behavior is undefined.
     Returns
 

-
-
+
 
3   The free function returns no value.
 
 

-
-
+
 

 
7.22.3.4 [The malloc function]

-

-
-
-
1           #include <stdlib.h>
+
+
1 Synopsis
+           #include <stdlib.h>
             void *malloc(size_t size);
     Description
 

-
-
+
 
2   The malloc function allocates space for an object whose size is specified by size and
     whose value is indeterminate.
     Returns
 

-
-
+
 
3   The malloc function returns either a null pointer or a pointer to the allocated space.
 

-
-
+
 

 
7.22.3.5 [The realloc function]

-

-
-
-
1           #include <stdlib.h>
+
+
1 Synopsis
+           #include <stdlib.h>
             void *realloc(void *ptr, size_t size);
     Description
 

-
-
+
 
2   The realloc function deallocates the old object pointed to by ptr and returns a
     pointer to a new object that has the size specified by size. The contents of the new
     object shall be the same as that of the old object prior to deallocation, up to the lesser of
     the new and old sizes. Any bytes in the new object beyond the size of the old object have
     indeterminate values.
 

-
-
+
 
3   If ptr is a null pointer, the realloc function behaves like the malloc function for the
     specified size. Otherwise, if ptr does not match a pointer earlier returned by a memory
     management function, or if the space has been deallocated by a call to the free or
@@ -20208,31 +17489,24 @@ char int_p_sep_by_space
     allocated, the old object is not deallocated and its value is unchanged.
     Returns
 

-
-
+
 
4   The realloc function returns a pointer to the new object (which may have the same
     value as a pointer to the old object), or a null pointer if the new object could not be
     allocated.
 

-
-
+
 

 
7.22.4 [Communication with the environment]

-
 Communication with the environment
-

-
-
+
 

 
7.22.4.1 [The abort function]

-

-
-
-
1          #include <stdlib.h>
+
+
1 Synopsis
+          #include <stdlib.h>
            _Noreturn void abort(void);
     Description
 

-
-
+
 
2   The abort function causes abnormal program termination to occur, unless the signal
     SIGABRT is being caught and the signal handler does not return. Whether open streams
     with unwritten buffered data are flushed, open streams are closed, or temporary files are
@@ -20241,119 +17515,102 @@ char int_p_sep_by_space
     call raise(SIGABRT).
     Returns
 

-
-
+
 
3   The abort function does not return to its caller.
 

-
-
+
 

 
7.22.4.2 [The atexit function]

-

-
-
-
1          #include <stdlib.h>
+
+
1 Synopsis
+          #include <stdlib.h>
            int atexit(void (*func)(void));
     Description
 

-
-
+
 
2   The atexit function registers the function pointed to by func, to be called without
-    arguments at normal program termination.297) It is unspecified whether a call to the
+    arguments at normal program termination.[297] It is unspecified whether a call to the
     atexit function that does not happen before the exit function is called will succeed.
     Environmental limits
 

-
 
 
Footnote 297) The atexit function registrations are distinct from the at_quick_exit registrations, so
          applications may need to call both registration functions with the same argument.
 

 
-
+
 
3   The implementation shall support the registration of at least 32 functions.
     Returns
 

-
-
+
 
4   The atexit function returns zero if the registration succeeds, nonzero if it fails.
-    Forward references: the at_quick_exit function (7.22.4.3), the exit function
-    (7.22.4.4).
+    Forward references: the at_quick_exit function (7.22.4.3), the exit function
+    (7.22.4.4).
 
 

-
-
+
 

 
7.22.4.3 [The at_quick_exit function]

-

-
-
-
1           #include <stdlib.h>
+
+
1 Synopsis
+           #include <stdlib.h>
             int at_quick_exit(void (*func)(void));
     Description
 

-
-
+
 
2   The at_quick_exit function registers the function pointed to by func, to be called
-    without arguments should quick_exit be called.298) It is unspecified whether a call to
+    without arguments should quick_exit be called.[298] It is unspecified whether a call to
     the at_quick_exit function that does not happen before the quick_exit function
     is called will succeed.
     Environmental limits
 

-
 
 
Footnote 298) The at_quick_exit function registrations are distinct from the atexit registrations, so
          applications may need to call both registration functions with the same argument.
 

 
-
+
 
3   The implementation shall support the registration of at least 32 functions.
     Returns
 

-
-
+
 
4   The at_quick_exit function returns zero if the registration succeeds, nonzero if it
     fails.
-    Forward references: the quick_exit function (7.22.4.7).
+    Forward references: the quick_exit function (7.22.4.7).
 

-
-
+
 

 
7.22.4.4 [The exit function]

-

-
-
-
1           #include <stdlib.h>
+
+
1 Synopsis
+           #include <stdlib.h>
             _Noreturn void exit(int status);
     Description
 

-
-
+
 
2   The exit function causes normal program termination to occur. No functions registered
     by the at_quick_exit function are called. If a program calls the exit function
     more than once, or calls the quick_exit function in addition to the exit function, the
     behavior is undefined.
 

-
-
+
 
3   First, all functions registered by the atexit function are called, in the reverse order of
-    their registration,299) except that a function is called after any previously registered
+    their registration,[299] except that a function is called after any previously registered
     functions that had already been called at the time it was registered. If, during the call to
     any such function, a call to the longjmp function is made that would terminate the call
     to the registered function, the behavior is undefined.
 
 

-
 
 
Footnote 299) Each function is called as many times as it was registered, and in the correct order with respect to
          other registered functions.
 

 
-
+
 
4   Next, all open streams with unwritten buffered data are flushed, all open streams are
     closed, and all files created by the tmpfile function are removed.
 

-
-
+
 
5   Finally, control is returned to the host environment. If the value of status is zero or
     EXIT_SUCCESS, an implementation-defined form of the status successful termination is
     returned. If the value of status is EXIT_FAILURE, an implementation-defined form
@@ -20361,163 +17618,137 @@ char int_p_sep_by_space
     implementation-defined.
     Returns
 

-
-
+
 
6   The exit function cannot return to its caller.
 

-
-
+
 

 
7.22.4.5 [The _Exit function]

-

-
-
-
1           #include <stdlib.h>
+
+
1 Synopsis
+           #include <stdlib.h>
             _Noreturn void _Exit(int status);
     Description
 

-
-
+
 
2   The _Exit function causes normal program termination to occur and control to be
     returned to the host environment. No functions registered by the atexit function, the
     at_quick_exit function, or signal handlers registered by the signal function are
     called. The status returned to the host environment is determined in the same way as for
-    the exit function (7.22.4.4). Whether open streams with unwritten buffered data are
+    the exit function (7.22.4.4). Whether open streams with unwritten buffered data are
     flushed, open streams are closed, or temporary files are removed is implementation-
     defined.
     Returns
 

-
-
+
 
3   The _Exit function cannot return to its caller.
 

-
-
+
 

 
7.22.4.6 [The getenv function]

-

-
-
-
1           #include <stdlib.h>
+
+
1 Synopsis
+           #include <stdlib.h>
             char *getenv(const char *name);
     Description
 

-
-
+
 
2   The getenv function searches an environment list , provided by the host environment,
     for a string that matches the string pointed to by name. The set of environment names
     and the method for altering the environment list are implementation-defined. The
     getenv function need not avoid data races with other threads of execution that modify
-    the environment list.300)
+    the environment list.[300]
 
 

-
 
 
Footnote 300) Many implementations provide non-standard functions that modify the environment list.
 

 
-
+
 
3   The implementation shall behave as if no library function calls the getenv function.
     Returns
 

-
-
+
 
4   The getenv function returns a pointer to a string associated with the matched list
     member. The string pointed to shall not be modified by the program, but may be
     overwritten by a subsequent call to the getenv function. If the specified name cannot
     be found, a null pointer is returned.
 

-
-
+
 

 
7.22.4.7 [The quick_exit function]

-

-
-
-
1           #include <stdlib.h>
+
+
1 Synopsis
+           #include <stdlib.h>
             _Noreturn void quick_exit(int status);
     Description
 

-
-
+
 
2   The quick_exit function causes normal program termination to occur. No functions
     registered by the atexit function or signal handlers registered by the signal function
     are called. If a program calls the quick_exit function more than once, or calls the
     exit function in addition to the quick_exit function, the behavior is undefined. If a
     signal is raised while the quick_exit function is executing, the behavior is undefined.
 

-
-
+
 
3   The quick_exit function first calls all functions registered by the at_quick_exit
-    function, in the reverse order of their registration,301) except that a function is called after
+    function, in the reverse order of their registration,[301] except that a function is called after
     any previously registered functions that had already been called at the time it was
     registered. If, during the call to any such function, a call to the longjmp function is
     made that would terminate the call to the registered function, the behavior is undefined.
 

-
 
 
Footnote 301) Each function is called as many times as it was registered, and in the correct order with respect to
          other registered functions.
-

-
-
-
4   Then control is returned to the host environment by means of the function call
-    _Exit(status).
-    Returns
-

-
-
-
5   The quick_exit function cannot return to its caller.
-

-
-
-

-
7.22.4.8 [The system function]

-

-
-
-
1           #include <stdlib.h>
-            int system(const char *string);
-    Description
-

-
-
-
2   If string is a null pointer, the system function determines whether the host
-    environment has a command processor . If string is not a null pointer, the system
-
     function passes the string pointed to by string to that command processor to be
     executed in a manner which the implementation shall document; this might then cause the
     program calling system to behave in a non-conforming manner or to terminate.
     Returns
-

+

 
-
+
+
4   Then control is returned to the host environment by means of the function call
+    _Exit(status).
+    Returns
+

+
+
5   The quick_exit function cannot return to its caller.
+

+
+

+
7.22.4.8 [The system function]

+
+
1 Synopsis
+           #include <stdlib.h>
+            int system(const char *string);
+    Description
+

+
+
2   If string is a null pointer, the system function determines whether the host
+    environment has a command processor . If string is not a null pointer, the system
+

+
 
3   If the argument is a null pointer, the system function returns nonzero only if a
     command processor is available. If the argument is not a null pointer, and the system
     function does return, it returns an implementation-defined value.
 

-
-
+
 

 
7.22.5 [Searching and sorting utilities]

-

-
-
+
 
1   These utilities make use of a comparison function to search or sort arrays of unspecified
     type. Where an argument declared as size_t nmemb specifies the length of the array
     for a function, nmemb can have the value zero on a call to that function; the comparison
     function is not called, a search finds no matching element, and sorting performs no
     rearrangement. Pointer arguments on such a call shall still have valid values, as described
-    in 7.1.4.
+    in 7.1.4.
 

-
-
+
 
2   The implementation shall ensure that the second argument of the comparison function
     (when called from bsearch), or both arguments (when called from qsort), are
-    pointers to elements of the array.302) The first argument when called from bsearch
+    pointers to elements of the array.[302] The first argument when called from bsearch
     shall equal key.
 

-
 
 
Footnote 302) That is, if the value passed is p, then the following expressions are always nonzero:
                   ((char *)p - (char *)base) % size == 0
@@ -20525,83 +17756,72 @@ char int_p_sep_by_space
                   (char *)p < (char *)base + nmemb * size
 

 
-
+
 
3   The comparison function shall not alter the contents of the array. The implementation
     may reorder elements of the array between calls to the comparison function, but shall not
     alter the contents of any individual element.
 

-
-
+
 
4   When the same objects (consisting of size bytes, irrespective of their current positions
     in the array) are passed more than once to the comparison function, the results shall be
     consistent with one another. That is, for qsort they shall define a total ordering on the
     array, and for bsearch the same object shall always compare the same way with the
     key.
 

-
-
+
 
5   A sequence point occurs immediately before and immediately after each call to the
     comparison function, and also between any call to the comparison function and any
     movement of the objects passed as arguments to that call.
 

-
-
+
 

 
7.22.5.1 [The bsearch function]

-

-
-
-
1            #include <stdlib.h>
+
+
1 Synopsis
+            #include <stdlib.h>
              void *bsearch(const void *key, const void *base,
                   size_t nmemb, size_t size,
                   int (*compar)(const void *, const void *));
     Description
 

-
-
+
 
2   The bsearch function searches an array of nmemb objects, the initial element of which
     is pointed to by base, for an element that matches the object pointed to by key. The
     size of each element of the array is specified by size.
 

-
-
+
 
3   The comparison function pointed to by compar is called with two arguments that point
     to the key object and to an array element, in that order. The function shall return an
     integer less than, equal to, or greater than zero if the key object is considered,
     respectively, to be less than, to match, or to be greater than the array element. The array
     shall consist of: all the elements that compare less than, all the elements that compare
-    equal to, and all the elements that compare greater than the key object, in that order.303)
+    equal to, and all the elements that compare greater than the key object, in that order.[303]
     Returns
 

-
 
 
Footnote 303) In practice, the entire array is sorted according to the comparison function.
 

 
-
+
 
4   The bsearch function returns a pointer to a matching element of the array, or a null
     pointer if no match is found. If two elements compare as equal, which element is
     matched is unspecified.
 

-
-
+
 

 
7.22.5.2 [The qsort function]

-

-
-
-
1            #include <stdlib.h>
+
+
1 Synopsis
+            #include <stdlib.h>
              void qsort(void *base, size_t nmemb, size_t size,
                   int (*compar)(const void *, const void *));
     Description
 

-
-
+
 
2   The qsort function sorts an array of nmemb objects, the initial element of which is
     pointed to by base. The size of each object is specified by size.
 

-
-
+
 
3   The contents of the array are sorted into ascending order according to a comparison
     function pointed to by compar, which is called with two arguments that point to the
     objects being compared. The function shall return an integer less than, equal to, or
@@ -20609,69 +17829,56 @@ char int_p_sep_by_space
     or greater than the second.
 
 

-
-
+
 
4   If two elements compare as equal, their order in the resulting sorted array is unspecified.
     Returns
 

-
-
+
 
5   The qsort function returns no value.
 

-
-
+
 

 
7.22.6 [Integer arithmetic functions]

-
 Integer arithmetic functions
-

-
-
+
 

 
7.22.6.1 [The abs, labs and llabs functions]

-

-
-
-
1           #include <stdlib.h>
+
+
1 Synopsis
+           #include <stdlib.h>
             int abs(int j);
             long int labs(long int j);
             long long int llabs(long long int j);
     Description
 

-
-
+
 
2   The abs, labs, and llabs functions compute the absolute value of an integer j. If the
-    result cannot be represented, the behavior is undefined.304)
+    result cannot be represented, the behavior is undefined.[304]
     Returns
 

-
 
 
Footnote 304) The absolute value of the most negative number cannot be represented in two's complement.
 

 
-
+
 
3   The abs, labs, and llabs, functions return the absolute value.
 

-
-
+
 

 
7.22.6.2 [The div, ldiv, and lldiv functions]

-

-
-
-
1           #include <stdlib.h>
+
+
1 Synopsis
+           #include <stdlib.h>
             div_t div(int numer, int denom);
             ldiv_t ldiv(long int numer, long int denom);
             lldiv_t lldiv(long long int numer, long long int denom);
     Description
 

-
-
+
 
2   The div, ldiv, and lldiv, functions compute numer / denom and numer %
     denom in a single operation.
     Returns
 

-
-
+
 
3   The div, ldiv, and lldiv functions return a structure of type div_t, ldiv_t, and
     lldiv_t, respectively, comprising both the quotient and the remainder. The structures
     shall contain (in either order) the members quot (the quotient) and rem (the remainder),
@@ -20679,77 +17886,66 @@ char int_p_sep_by_space
     the result cannot be represented, the behavior is undefined.
 
 

-
-
+
 

 
7.22.7 [Multibyte/wide character conversion functions]

-

-
-
+
 
1   The behavior of the multibyte character functions is affected by the LC_CTYPE category
     of the current locale. For a state-dependent encoding, each function is placed into its
     initial conversion state at program startup and can be returned to that state by a call for
     which its character pointer argument, s, is a null pointer. Subsequent calls with s as
     other than a null pointer cause the internal conversion state of the function to be altered as
     necessary. A call with s as a null pointer causes these functions to return a nonzero value
-    if encodings have state dependency, and zero otherwise.305) Changing the LC_CTYPE
+    if encodings have state dependency, and zero otherwise.[305] Changing the LC_CTYPE
     category causes the conversion state of these functions to be indeterminate.
 

-
 
 
Footnote 305) If the locale employs special bytes to change the shift state, these bytes do not produce separate wide
          character codes, but are grouped with an adjacent multibyte character.
 

 
-
+
 

 
7.22.7.1 [The mblen function]

-

-
-
-
1           #include <stdlib.h>
+
+
1 Synopsis
+           #include <stdlib.h>
             int mblen(const char *s, size_t n);
     Description
 

-
-
+
 
2   If s is not a null pointer, the mblen function determines the number of bytes contained
     in the multibyte character pointed to by s. Except that the conversion state of the
     mbtowc function is not affected, it is equivalent to
             mbtowc((wchar_t *)0, (const char *)0, 0);
             mbtowc((wchar_t *)0, s, n);
 

-
-
+
 
3   The implementation shall behave as if no library function calls the mblen function.
     Returns
 

-
-
+
 
4   If s is a null pointer, the mblen function returns a nonzero or zero value, if multibyte
     character encodings, respectively, do or do not have state-dependent encodings. If s is
     not a null pointer, the mblen function either returns 0 (if s points to the null character),
     or returns the number of bytes that are contained in the multibyte character (if the next n
     or fewer bytes form a valid multibyte character), or returns -1 (if they do not form a valid
     multibyte character).
-    Forward references: the mbtowc function (7.22.7.2).
+    Forward references: the mbtowc function (7.22.7.2).
 
 

-
-
+
 

 
7.22.7.2 [The mbtowc function]

-

-
-
-
1          #include <stdlib.h>
+
+
1 Synopsis
+          #include <stdlib.h>
            int mbtowc(wchar_t * restrict pwc,
                 const char * restrict s,
                 size_t n);
     Description
 

-
-
+
 
2   If s is not a null pointer, the mbtowc function inspects at most n bytes beginning with
     the byte pointed to by s to determine the number of bytes needed to complete the next
     multibyte character (including any shift sequences). If the function determines that the
@@ -20758,13 +17954,11 @@ char int_p_sep_by_space
     the object pointed to by pwc. If the corresponding wide character is the null wide
     character, the function is left in the initial conversion state.
 

-
-
+
 
3   The implementation shall behave as if no library function calls the mbtowc function.
     Returns
 

-
-
+
 
4   If s is a null pointer, the mbtowc function returns a nonzero or zero value, if multibyte
     character encodings, respectively, do or do not have state-dependent encodings. If s is
     not a null pointer, the mbtowc function either returns 0 (if s points to the null character),
@@ -20772,24 +17966,20 @@ char int_p_sep_by_space
     the next n or fewer bytes form a valid multibyte character), or returns -1 (if they do not
     form a valid multibyte character).
 

-
-
+
 
5   In no case will the value returned be greater than n or the value of the MB_CUR_MAX
     macro.
 

-
-
+
 

 
7.22.7.3 [The wctomb function]

-

-
-
-
1          #include <stdlib.h>
+
+
1 Synopsis
+          #include <stdlib.h>
            int wctomb(char *s, wchar_t wc);
     Description
 

-
-
+
 
2   The wctomb function determines the number of bytes needed to represent the multibyte
     character corresponding to the wide character given by wc (including any shift
     sequences), and stores the multibyte character representation in the array whose first
@@ -20799,48 +17989,39 @@ char int_p_sep_by_space
     conversion state.
 
 

-
-
+
 
3   The implementation shall behave as if no library function calls the wctomb function.
     Returns
 

-
-
+
 
4   If s is a null pointer, the wctomb function returns a nonzero or zero value, if multibyte
     character encodings, respectively, do or do not have state-dependent encodings. If s is
     not a null pointer, the wctomb function returns -1 if the value of wc does not correspond
     to a valid multibyte character, or returns the number of bytes that are contained in the
     multibyte character corresponding to the value of wc.
 

-
-
+
 
5   In no case will the value returned be greater than the value of the MB_CUR_MAX macro.
 

-
-
+
 

 
7.22.8 [Multibyte/wide string conversion functions]

-

-
-
+
 
1   The behavior of the multibyte string functions is affected by the LC_CTYPE category of
     the current locale.
 

-
-
+
 

 
7.22.8.1 [The mbstowcs function]

-

-
-
-
1            #include <stdlib.h>
+
+
1 Synopsis
+            #include <stdlib.h>
              size_t mbstowcs(wchar_t * restrict pwcs,
                   const char * restrict s,
                   size_t n);
     Description
 

-
-
+
 
2   The mbstowcs function converts a sequence of multibyte characters that begins in the
     initial shift state from the array pointed to by s into a sequence of corresponding wide
     characters and stores not more than n wide characters into the array pointed to by pwcs.
@@ -20849,38 +18030,33 @@ char int_p_sep_by_space
     a call to the mbtowc function, except that the conversion state of the mbtowc function is
     not affected.
 

-
-
+
 
3   No more than n elements will be modified in the array pointed to by pwcs. If copying
     takes place between objects that overlap, the behavior is undefined.
     Returns
 

-
-
+
 
4   If an invalid multibyte character is encountered, the mbstowcs function returns
     (size_t)(-1). Otherwise, the mbstowcs function returns the number of array
-    elements modified, not including a terminating null wide character, if any.306)
+    elements modified, not including a terminating null wide character, if any.[306]
 
 

-
 
 
Footnote 306) The array will not be null-terminated if the value returned is n.
 

 
-
+
 

 
7.22.8.2 [The wcstombs function]

-

-
-
-
1          #include <stdlib.h>
+
+
1 Synopsis
+          #include <stdlib.h>
            size_t wcstombs(char * restrict s,
                 const wchar_t * restrict pwcs,
                 size_t n);
     Description
 

-
-
+
 
2   The wcstombs function converts a sequence of wide characters from the array pointed
     to by pwcs into a sequence of corresponding multibyte characters that begins in the
     initial shift state, and stores these multibyte characters into the array pointed to by s,
@@ -20888,118 +18064,95 @@ char int_p_sep_by_space
     character is stored. Each wide character is converted as if by a call to the wctomb
     function, except that the conversion state of the wctomb function is not affected.
 

-
-
+
 
3   No more than n bytes will be modified in the array pointed to by s. If copying takes place
     between objects that overlap, the behavior is undefined.
     Returns
 

-
-
+
 
4   If a wide character is encountered that does not correspond to a valid multibyte character,
     the wcstombs function returns (size_t)(-1). Otherwise, the wcstombs function
     returns the number of bytes modified, not including a terminating null character, if
-    any.306)
+    any.[306]
 

-
 
 
Footnote 306) The array will not be null-terminated if the value returned is n.
 

 
-
+
 

-
7.23 [_Noreturn ]

-

-
-
+
7.23 [_Noreturn <stdnoreturn.h>]

+
 
1   The header <stdnoreturn.h> defines the macro
             noreturn
     which expands to _Noreturn.
 

-
-
+
 

-
7.24 [String handling ]

-
 String handling 
-

-
-
+
7.24 [String handling <string.h>]

+
 

 
7.24.1 [String function conventions]

-

-
-
+
 
1   The header <string.h> declares one type and several functions, and defines one
     macro useful for manipulating arrays of character type and other objects treated as arrays
-    of character type.307) The type is size_t and the macro is NULL (both described in
-     7.19). Various methods are used for determining the lengths of the arrays, but in all cases
+    of character type.[307] The type is size_t and the macro is NULL (both described in
+     7.19). Various methods are used for determining the lengths of the arrays, but in all cases
     a char * or void * argument points to the initial (lowest addressed) character of the
     array. If an array is accessed beyond the end of an object, the behavior is undefined.
 

-
 
-
Footnote 307) See ``future library directions'' (7.31.13).
+
Footnote 307) See ``future library directions'' (7.31.13).
 

 
-
+
 
2   Where an argument declared as size_t n specifies the length of the array for a
     function, n can have the value zero on a call to that function. Unless explicitly stated
     otherwise in the description of a particular function in this subclause, pointer arguments
-    on such a call shall still have valid values, as described in 7.1.4. On such a call, a
+    on such a call shall still have valid values, as described in 7.1.4. On such a call, a
     function that locates a character finds no occurrence, a function that compares two
     character sequences returns zero, and a function that copies characters copies zero
     characters.
 

-
-
+
 
3   For all functions in this subclause, each character shall be interpreted as if it had the type
     unsigned char (and therefore every possible object representation is valid and has a
     different value).
 

-
-
+
 

 
7.24.2 [Copying functions]

-
 Copying functions
-

-
-
+
 

 
7.24.2.1 [The memcpy function]

-

-
-
-
1            #include <string.h>
+
+
1 Synopsis
+            #include <string.h>
              void *memcpy(void * restrict s1,
                   const void * restrict s2,
                   size_t n);
     Description
 

-
-
+
 
2   The memcpy function copies n characters from the object pointed to by s2 into the
     object pointed to by s1. If copying takes place between objects that overlap, the behavior
     is undefined.
     Returns
 

-
-
+
 
3   The memcpy function returns the value of s1.
 
 

-
-
+
 

 
7.24.2.2 [The memmove function]

-

-
-
-
1           #include <string.h>
+
+
1 Synopsis
+           #include <string.h>
             void *memmove(void *s1, const void *s2, size_t n);
     Description
 

-
-
+
 
2   The memmove function copies n characters from the object pointed to by s2 into the
     object pointed to by s1. Copying takes place as if the n characters from the object
     pointed to by s2 are first copied into a temporary array of n characters that does not
@@ -21007,258 +18160,213 @@ char int_p_sep_by_space
     temporary array are copied into the object pointed to by s1.
     Returns
 

-
-
+
 
3   The memmove function returns the value of s1.
 

-
-
+
 

 
7.24.2.3 [The strcpy function]

-

-
-
-
1           #include <string.h>
+
+
1 Synopsis
+           #include <string.h>
             char *strcpy(char * restrict s1,
                  const char * restrict s2);
     Description
 

-
-
+
 
2   The strcpy function copies the string pointed to by s2 (including the terminating null
     character) into the array pointed to by s1. If copying takes place between objects that
     overlap, the behavior is undefined.
     Returns
 

-
-
+
 
3   The strcpy function returns the value of s1.
 

-
-
+
 

 
7.24.2.4 [The strncpy function]

-

-
-
-
1           #include <string.h>
+
+
1 Synopsis
+           #include <string.h>
             char *strncpy(char * restrict s1,
                  const char * restrict s2,
                  size_t n);
     Description
 

-
-
+
 
2   The strncpy function copies not more than n characters (characters that follow a null
     character are not copied) from the array pointed to by s2 to the array pointed to by
-    s1.308) If copying takes place between objects that overlap, the behavior is undefined.
+    s1.[308] If copying takes place between objects that overlap, the behavior is undefined.
 

-
 
 
Footnote 308) Thus, if there is no null character in the first n characters of the array pointed to by s2, the result will
          not be null-terminated.
 

 
-
+
 
3   If the array pointed to by s2 is a string that is shorter than n characters, null characters
     are appended to the copy in the array pointed to by s1, until n characters in all have been
     written.
     Returns
 

-
-
+
 
4   The strncpy function returns the value of s1.
 

-
-
+
 

 
7.24.3 [Concatenation functions]

-
 Concatenation functions
-

-
-
+
 

 
7.24.3.1 [The strcat function]

-

-
-
-
1            #include <string.h>
+
+
1 Synopsis
+            #include <string.h>
              char *strcat(char * restrict s1,
                   const char * restrict s2);
     Description
 

-
-
+
 
2   The strcat function appends a copy of the string pointed to by s2 (including the
     terminating null character) to the end of the string pointed to by s1. The initial character
     of s2 overwrites the null character at the end of s1. If copying takes place between
     objects that overlap, the behavior is undefined.
     Returns
 

-
-
+
 
3   The strcat function returns the value of s1.
 

-
-
+
 

 
7.24.3.2 [The strncat function]

-

-
-
-
1            #include <string.h>
+
+
1 Synopsis
+            #include <string.h>
              char *strncat(char * restrict s1,
                   const char * restrict s2,
                   size_t n);
     Description
 

-
-
+
 
2   The strncat function appends not more than n characters (a null character and
     characters that follow it are not appended) from the array pointed to by s2 to the end of
     the string pointed to by s1. The initial character of s2 overwrites the null character at the
-    end of s1. A terminating null character is always appended to the result.309) If copying
-
-    takes place between objects that overlap, the behavior is undefined.
-    Returns
+    end of s1. A terminating null character is always appended to the result.[309] If copying
 

-
 
 
Footnote 309) Thus, the maximum number of characters that can end up in the array pointed to by s1 is
          strlen(s1)+n+1.
+    takes place between objects that overlap, the behavior is undefined.
+    Returns
 

 
-
+
 
3   The strncat function returns the value of s1.
-    Forward references: the strlen function (7.24.6.3).
+    Forward references: the strlen function (7.24.6.3).
 

-
-
+
 

 
7.24.4 [Comparison functions]

-

-
-
+
 
1   The sign of a nonzero value returned by the comparison functions memcmp, strcmp,
     and strncmp is determined by the sign of the difference between the values of the first
     pair of characters (both interpreted as unsigned char) that differ in the objects being
     compared.
 

-
-
+
 

 
7.24.4.1 [The memcmp function]

-

-
-
-
1           #include <string.h>
+
+
1 Synopsis
+           #include <string.h>
             int memcmp(const void *s1, const void *s2, size_t n);
     Description
 

-
-
+
 
2   The memcmp function compares the first n characters of the object pointed to by s1 to
-    the first n characters of the object pointed to by s2.310)
+    the first n characters of the object pointed to by s2.[310]
     Returns
 

-
 
 
Footnote 310) The contents of ``holes'' used as padding for purposes of alignment within structure objects are
          indeterminate. Strings shorter than their allocated space and unions may also cause problems in
          comparison.
+    pointed to by s2.
 

 
-
+
 
3   The memcmp function returns an integer greater than, equal to, or less than zero,
     accordingly as the object pointed to by s1 is greater than, equal to, or less than the object
     pointed to by s2.
 

-
-
+
 

 
7.24.4.2 [The strcmp function]

-

-
-
-
1           #include <string.h>
+
+
1 Synopsis
+           #include <string.h>
             int strcmp(const char *s1, const char *s2);
     Description
 

-
-
+
 
2   The strcmp function compares the string pointed to by s1 to the string pointed to by
     s2.
     Returns
 

-
-
+
 
3   The strcmp function returns an integer greater than, equal to, or less than zero,
     accordingly as the string pointed to by s1 is greater than, equal to, or less than the string
-
-    pointed to by s2.
 

-
-
+
 

 
7.24.4.3 [The strcoll function]

-

-
-
-
1          #include <string.h>
+
+
1 Synopsis
+          #include <string.h>
            int strcoll(const char *s1, const char *s2);
     Description
 

-
-
+
 
2   The strcoll function compares the string pointed to by s1 to the string pointed to by
     s2, both interpreted as appropriate to the LC_COLLATE category of the current locale.
     Returns
 

-
-
+
 
3   The strcoll function returns an integer greater than, equal to, or less than zero,
     accordingly as the string pointed to by s1 is greater than, equal to, or less than the string
     pointed to by s2 when both are interpreted as appropriate to the current locale.
 

-
-
+
 

 
7.24.4.4 [The strncmp function]

-

-
-
-
1          #include <string.h>
+
+
1 Synopsis
+          #include <string.h>
            int strncmp(const char *s1, const char *s2, size_t n);
     Description
 

-
-
+
 
2   The strncmp function compares not more than n characters (characters that follow a
     null character are not compared) from the array pointed to by s1 to the array pointed to
     by s2.
     Returns
 

-
-
+
 
3   The strncmp function returns an integer greater than, equal to, or less than zero,
     accordingly as the possibly null-terminated array pointed to by s1 is greater than, equal
     to, or less than the possibly null-terminated array pointed to by s2.
 

-
-
+
 

 
7.24.4.5 [The strxfrm function]

-

-
-
-
1          #include <string.h>
+
+
1 Synopsis
+          #include <string.h>
            size_t strxfrm(char * restrict s1,
                 const char * restrict s2,
                 size_t n);
     Description
 

-
-
+
 
2   The strxfrm function transforms the string pointed to by s2 and places the resulting
     string into the array pointed to by s1. The transformation is such that if the strcmp
     function is applied to two transformed strings, it returns a value greater than, equal to, or
@@ -21270,213 +18378,175 @@ char int_p_sep_by_space
     undefined.
     Returns
 

-
-
+
 
3   The strxfrm function returns the length of the transformed string (not including the
     terminating null character). If the value returned is n or more, the contents of the array
     pointed to by s1 are indeterminate.
 

-
-
+
 
4   EXAMPLE The value of the following expression is the size of the array needed to hold the
     transformation of the string pointed to by s.
             1 + strxfrm(NULL, s, 0)
 
 

-
-
+
 

 
7.24.5 [Search functions]

-
 Search functions
-

-
-
+
 

 
7.24.5.1 [The memchr function]

-

-
-
-
1           #include <string.h>
+
+
1 Synopsis
+           #include <string.h>
             void *memchr(const void *s, int c, size_t n);
     Description
 

-
-
+
 
2   The memchr function locates the first occurrence of c (converted to an unsigned
     char) in the initial n characters (each interpreted as unsigned char) of the object
     pointed to by s. The implementation shall behave as if it reads the characters sequentially
     and stops as soon as a matching character is found.
     Returns
 

-
-
+
 
3   The memchr function returns a pointer to the located character, or a null pointer if the
     character does not occur in the object.
 

-
-
+
 

 
7.24.5.2 [The strchr function]

-

-
-
-
1           #include <string.h>
+
+
1 Synopsis
+           #include <string.h>
             char *strchr(const char *s, int c);
     Description
 

-
-
+
 
2   The strchr function locates the first occurrence of c (converted to a char) in the
     string pointed to by s. The terminating null character is considered to be part of the
     string.
 
     Returns
 

-
-
+
 
3   The strchr function returns a pointer to the located character, or a null pointer if the
     character does not occur in the string.
 

-
-
+
 

 
7.24.5.3 [The strcspn function]

-

-
-
-
1          #include <string.h>
+
+
1 Synopsis
+          #include <string.h>
            size_t strcspn(const char *s1, const char *s2);
     Description
 

-
-
+
 
2   The strcspn function computes the length of the maximum initial segment of the string
     pointed to by s1 which consists entirely of characters not from the string pointed to by
     s2.
     Returns
 

-
-
+
 
3   The strcspn function returns the length of the segment.
 

-
-
+
 

 
7.24.5.4 [The strpbrk function]

-

-
-
-
1          #include <string.h>
+
+
1 Synopsis
+          #include <string.h>
            char *strpbrk(const char *s1, const char *s2);
     Description
 

-
-
+
 
2   The strpbrk function locates the first occurrence in the string pointed to by s1 of any
     character from the string pointed to by s2.
     Returns
 

-
-
+
 
3   The strpbrk function returns a pointer to the character, or a null pointer if no character
     from s2 occurs in s1.
 

-
-
+
 

 
7.24.5.5 [The strrchr function]

-

-
-
-
1          #include <string.h>
+
+
1 Synopsis
+          #include <string.h>
            char *strrchr(const char *s, int c);
     Description
 

-
-
+
 
2   The strrchr function locates the last occurrence of c (converted to a char) in the
     string pointed to by s. The terminating null character is considered to be part of the
     string.
     Returns
 

-
-
+
 
3   The strrchr function returns a pointer to the character, or a null pointer if c does not
     occur in the string.
 

-
-
+
 

 
7.24.5.6 [The strspn function]

-

-
-
-
1           #include <string.h>
+
+
1 Synopsis
+           #include <string.h>
             size_t strspn(const char *s1, const char *s2);
     Description
 

-
-
+
 
2   The strspn function computes the length of the maximum initial segment of the string
     pointed to by s1 which consists entirely of characters from the string pointed to by s2.
     Returns
 

-
-
+
 
3   The strspn function returns the length of the segment.
 

-
-
+
 

 
7.24.5.7 [The strstr function]

-

-
-
-
1           #include <string.h>
+
+
1 Synopsis
+           #include <string.h>
             char *strstr(const char *s1, const char *s2);
     Description
 

-
-
+
 
2   The strstr function locates the first occurrence in the string pointed to by s1 of the
     sequence of characters (excluding the terminating null character) in the string pointed to
     by s2.
     Returns
 

-
-
+
 
3   The strstr function returns a pointer to the located string, or a null pointer if the string
     is not found. If s2 points to a string with zero length, the function returns s1.
 

-
-
+
 

 
7.24.5.8 [The strtok function]

-

-
-
-
1           #include <string.h>
+
+
1 Synopsis
+           #include <string.h>
             char *strtok(char * restrict s1,
                  const char * restrict s2);
     Description
 

-
-
+
 
2   A sequence of calls to the strtok function breaks the string pointed to by s1 into a
     sequence of tokens, each of which is delimited by a character from the string pointed to
     by s2. The first call in the sequence has a non-null first argument; subsequent calls in the
     sequence have a null first argument. The separator string pointed to by s2 may be
     different from call to call.
 

-
-
+
 
3   The first call in the sequence searches the string pointed to by s1 for the first character
     that is not contained in the current separator string pointed to by s2. If no such character
     is found, then there are no tokens in the string pointed to by s1 and the strtok function
     returns a null pointer. If such a character is found, it is the start of the first token.
 

-
-
+
 
4   The strtok function then searches from there for a character that is contained in the
     current separator string. If no such character is found, the current token extends to the
     end of the string pointed to by s1, and subsequent searches for a token will return a null
@@ -21484,29 +18554,25 @@ char int_p_sep_by_space
     terminates the current token. The strtok function saves a pointer to the following
     character, from which the next search for a token will start.
 

-
-
+
 
5   Each subsequent call, with a null pointer as the value of the first argument, starts
     searching from the saved pointer and behaves as described above.
 

-
-
+
 
6   The strtok function is not required to avoid data races with other calls to the strtok
-    function.311) The implementation shall behave as if no library function calls the strtok
+    function.[311] The implementation shall behave as if no library function calls the strtok
     function.
     Returns
 

-
 
 
Footnote 311) The strtok_s function can be used instead to avoid data races.
 

 
-
+
 
7   The strtok function returns a pointer to the first character of a token, or a null pointer
     if there is no token.
 

-
-
+
 
8   EXAMPLE
             #include <string.h>
             static char str[] = "?a???b,,,#c";
@@ -21516,114 +18582,93 @@ char int_p_sep_by_space
             t   =   strtok(NULL, "#,");       //   t   points to the token "c"
             t   =   strtok(NULL, "?");        //   t   is a null pointer
 
-    Forward references: The strtok_s function (K.3.7.3.1).
+    Forward references: The strtok_s function (K.3.7.3.1).
 
 

-
-
+
 

 
7.24.6 [Miscellaneous functions]

-
 Miscellaneous functions
-

-
-
+
 

 
7.24.6.1 [The memset function]

-

-
-
-
1           #include <string.h>
+
+
1 Synopsis
+           #include <string.h>
             void *memset(void *s, int c, size_t n);
     Description
 

-
-
+
 
2   The memset function copies the value of c (converted to an unsigned char) into
     each of the first n characters of the object pointed to by s.
     Returns
 

-
-
+
 
3   The memset function returns the value of s.
 

-
-
+
 

 
7.24.6.2 [The strerror function]

-

-
-
-
1           #include <string.h>
+
+
1 Synopsis
+           #include <string.h>
             char *strerror(int errnum);
     Description
 

-
-
+
 
2   The strerror function maps the number in errnum to a message string. Typically,
     the values for errnum come from errno, but strerror shall map any value of type
     int to a message.
 

-
-
+
 
3   The strerror function is not required to avoid data races with other calls to the
-    strerror function.312) The implementation shall behave as if no library function calls
+    strerror function.[312] The implementation shall behave as if no library function calls
     the strerror function.
     Returns
 

-
 
 
Footnote 312) The strerror_s function can be used instead to avoid data races.
 

 
-
+
 
4   The strerror function returns a pointer to the string, the contents of which are locale-
     specific. The array pointed to shall not be modified by the program, but may be
     overwritten by a subsequent call to the strerror function.
-    Forward references: The strerror_s function (K.3.7.4.2).
+    Forward references: The strerror_s function (K.3.7.4.2).
 
 

-
-
+
 

 
7.24.6.3 [The strlen function]

-

-
-
-
1          #include <string.h>
+
+
1 Synopsis
+          #include <string.h>
            size_t strlen(const char *s);
     Description
 

-
-
+
 
2   The strlen function computes the length of the string pointed to by s.
     Returns
 

-
-
+
 
3   The strlen function returns the number of characters that precede the terminating null
     character.
 

-
-
+
 

-
7.25 [Type-generic math ]

-

-
-
+
7.25 [Type-generic math <tgmath.h>]

+
 
1   The header <tgmath.h> includes the headers <math.h> and <complex.h> and
     defines several type-generic macros.
 

-
-
+
 
2   Of the <math.h> and <complex.h> functions without an f (float) or l (long
     double) suffix, several have one or more parameters whose corresponding real type is
     double. For each such function, except modf, there is a corresponding type-generic
-    macro.313) The parameters whose corresponding real type is double in the function
+    macro.[313] The parameters whose corresponding real type is double in the function
     synopsis are generic parameters. Use of the macro invokes a function whose
     corresponding real type and type domain are determined by the arguments for the generic
-    parameters.314)
+    parameters.[314]
 

-
 
 
Footnote 313) Like other function-like macros in Standard libraries, each type-generic macro can be suppressed to
          make available the corresponding ordinary function.
@@ -21632,24 +18677,6 @@ char int_p_sep_by_space
 
 
Footnote 314) If the type of the argument is not compatible with the type of the parameter for the selected function,
          the behavior is undefined.
-

-
-
-
3   Use of the macro invokes a function whose generic parameters have the corresponding
-    real type determined as follows:
-    -- First, if any argument for generic parameters has type long double, the type
-       determined is long double.
-    -- Otherwise, if any argument for generic parameters has type double or is of integer
-       type, the type determined is double.
-    -- Otherwise, the type determined is float.
-

-
-
-
4   For each unsuffixed function in <math.h> for which there is a function in
-    <complex.h> with the same name except for a c prefix, the corresponding type-
-    generic macro (for both functions) has the same name as the function in <math.h>. The
-    corresponding type-generic macro for fabs and cabs is fabs.
-
             <math.h>          <complex.h>              type-generic
              function            function                 macro
              acos               cacos                    acos
@@ -21671,9 +18698,24 @@ char int_p_sep_by_space
              fabs               cabs                     fabs
     If at least one argument for a generic parameter is complex, then use of the macro invokes
     a complex function; otherwise, use of the macro invokes a real function.
-

+

 
-
+
+
3   Use of the macro invokes a function whose generic parameters have the corresponding
+    real type determined as follows:
+    -- First, if any argument for generic parameters has type long double, the type
+       determined is long double.
+    -- Otherwise, if any argument for generic parameters has type double or is of integer
+       type, the type determined is double.
+    -- Otherwise, the type determined is float.
+

+
+
4   For each unsuffixed function in <math.h> for which there is a function in
+    <complex.h> with the same name except for a c prefix, the corresponding type-
+    generic macro (for both functions) has the same name as the function in <math.h>. The
+    corresponding type-generic macro for fabs and cabs is fabs.
+

+
 
5   For each unsuffixed function in <math.h> without a c-prefixed counterpart in
     <complex.h> (except modf), the corresponding type-generic macro has the same
     name as the function. These type-generic macros are:
@@ -21690,8 +18732,7 @@ char int_p_sep_by_space
     If all arguments for generic parameters are real, then use of the macro invokes a real
     function; otherwise, use of the macro results in undefined behavior.
 

-
-
+
 
6   For each unsuffixed function in <complex.h> that is not a c-prefixed counterpart to a
     function in <math.h>, the corresponding type-generic macro has the same name as the
     function. These type-generic macros are:
@@ -21699,8 +18740,7 @@ char int_p_sep_by_space
             cimag                   cproj
     Use of the macro with any real or complex argument invokes a complex function.
 

-
-
+
 
7   EXAMPLE       With the declarations
             #include <tgmath.h>
             int n;
@@ -21734,34 +18774,31 @@ char int_p_sep_by_space
                 carg(dc)                            carg(dc), the function
                 cproj(ldc)                          cprojl(ldc)
 

-
-
+
 

-
7.26 [Threads ]

-
 Threads 
-

-
-
+
7.26 [Threads <threads.h>]

+
 

 
7.26.1 [Introduction]

-

-
-
+
 
1   The header <threads.h> includes the header <time.h>, defines macros, and
     declares types, enumeration constants, and functions that support multiple threads of
-    execution.315)
+    execution.[315]
 

-
 
-
Footnote 315) See ``future library directions'' (7.31.15).
+
Footnote 315) See ``future library directions'' (7.31.15).
+            thrd_start_t
+    which is the function pointer type int (*)(void*) that is passed to thrd_create
+    to create a new thread; and
+              once_flag
+    which is a complete object type that holds a flag for use by call_once.
 

 
-
+
 
2   Implementations that define the macro _ _STDC_NO_THREADS_ _ need not provide
     this header nor support any of its facilities.
 

-
-
+
 
3   The macros are
              thread_local
     which expands to _Thread_local;
@@ -21772,8 +18809,7 @@ char int_p_sep_by_space
     which expands to an integer constant expression representing the maximum number of
     times that destructors will be called when a thread terminates.
 

-
-
+
 
4   The types are
              cnd_t
     which is a complete object type that holds an identifier for a condition variable;
@@ -21787,15 +18823,8 @@ char int_p_sep_by_space
              tss_dtor_t
     which is the function pointer type void (*)(void*), used for a destructor for a
     thread-specific storage pointer;
-
-            thrd_start_t
-    which is the function pointer type int (*)(void*) that is passed to thrd_create
-    to create a new thread; and
-              once_flag
-    which is a complete object type that holds a flag for use by call_once.
 

-
-
+
 
5   The enumeration constants are
             mtx_plain
     which is passed to mtx_init to create a mutex object that supports neither timeout nor
@@ -21817,154 +18846,125 @@ char int_p_sep_by_space
             thrd_nomem
     which is returned by a function to indicate that the requested operation failed because it
     was unable to allocate memory.
-    Forward references: date and time (7.27).
+    Forward references: date and time (7.27).
 

-
-
+
 

 
7.26.2 [Initialization functions]

-
 Initialization functions
-

-
-
+
 

 
7.26.2.1 [The call_once function]

-

-
-
-
1          #include <threads.h>
+
+
1 Synopsis
+          #include <threads.h>
            void call_once(once_flag *flag, void (*func)(void));
     Description
 

-
-
+
 
2   The call_once function uses the once_flag pointed to by flag to ensure that
     func is called exactly once, the first time the call_once function is called with that
     value of flag. Completion of an effective call to the call_once function synchronizes
     with all subsequent calls to the call_once function with the same value of flag.
     Returns
 

-
-
+
 
3   The call_once function returns no value.
 

-
-
+
 

 
7.26.3 [Condition variable functions]

-
 Condition variable functions
-

-
-
+
 

 
7.26.3.1 [The cnd_broadcast function]

-

-
-
-
1          #include <threads.h>
+
+
1 Synopsis
+          #include <threads.h>
            int cnd_broadcast(cnd_t *cond);
     Description
 

-
-
+
 
2   The cnd_broadcast function unblocks all of the threads that are blocked on the
     condition variable pointed to by cond at the time of the call. If no threads are blocked
     on the condition variable pointed to by cond at the time of the call, the function does
     nothing.
     Returns
 

-
-
+
 
3   The cnd_broadcast function returns thrd_success on success, or thrd_error
     if the request could not be honored.
 

-
-
+
 

 
7.26.3.2 [The cnd_destroy function]

-

-
-
-
1          #include <threads.h>
+
+
1 Synopsis
+          #include <threads.h>
            void cnd_destroy(cnd_t *cond);
     Description
 

-
-
+
 
2   The cnd_destroy function releases all resources used by the condition variable
     pointed to by cond. The cnd_destroy function requires that no threads be blocked
     waiting for the condition variable pointed to by cond.
 
     Returns
 

-
-
+
 
3   The cnd_destroy function returns no value.
 

-
-
+
 

 
7.26.3.3 [The cnd_init function]

-

-
-
-
1           #include <threads.h>
+
+
1 Synopsis
+           #include <threads.h>
             int cnd_init(cnd_t *cond);
     Description
 

-
-
+
 
2   The cnd_init function creates a condition variable. If it succeeds it sets the variable
     pointed to by cond to a value that uniquely identifies the newly created condition
     variable. A thread that calls cnd_wait on a newly created condition variable will
     block.
     Returns
 

-
-
+
 
3   The cnd_init function returns thrd_success on success, or thrd_nomem if no
     memory could be allocated for the newly created condition, or thrd_error if the
     request could not be honored.
 

-
-
+
 

 
7.26.3.4 [The cnd_signal function]

-

-
-
-
1           #include <threads.h>
+
+
1 Synopsis
+           #include <threads.h>
             int cnd_signal(cnd_t *cond);
     Description
 

-
-
+
 
2   The cnd_signal function unblocks one of the threads that are blocked on the
     condition variable pointed to by cond at the time of the call. If no threads are blocked
     on the condition variable at the time of the call, the function does nothing and return
     success.
     Returns
 

-
-
+
 
3   The cnd_signal function returns thrd_success on success or thrd_error if
     the request could not be honored.
 

-
-
+
 

 
7.26.3.5 [The cnd_timedwait function]

-

-
-
-
1           #include <threads.h>
+
+
1 Synopsis
+           #include <threads.h>
             int cnd_timedwait(cnd_t *restrict cond,
                  mtx_t *restrict mtx,
                  const struct timespec *restrict ts);
     Description
 

-
-
+
 
2   The cnd_timedwait function atomically unlocks the mutex pointed to by mtx and
     endeavors to block until the condition variable pointed to by cond is signaled by a call to
     cnd_signal or to cnd_broadcast, or until after the TIME_UTC-based calendar
@@ -21973,25 +18973,21 @@ char int_p_sep_by_space
     mutex pointed to by mtx be locked by the calling thread.
     Returns
 

-
-
+
 
3   The cnd_timedwait function returns thrd_success upon success, or
     thrd_timedout if the time specified in the call was reached without acquiring the
     requested resource, or thrd_error if the request could not be honored.
 

-
-
+
 

 
7.26.3.6 [The cnd_wait function]

-

-
-
-
1          #include <threads.h>
+
+
1 Synopsis
+          #include <threads.h>
            int cnd_wait(cnd_t *cond, mtx_t *mtx);
     Description
 

-
-
+
 
2   The cnd_wait function atomically unlocks the mutex pointed to by mtx and endeavors
     to block until the condition variable pointed to by cond is signaled by a call to
     cnd_signal or to cnd_broadcast. When the calling thread becomes unblocked it
@@ -21999,185 +18995,150 @@ char int_p_sep_by_space
     that the mutex pointed to by mtx be locked by the calling thread.
     Returns
 

-
-
+
 
3   The cnd_wait function returns thrd_success on success or thrd_error if the
     request could not be honored.
 

-
-
+
 

 
7.26.4 [Mutex functions]

-
 Mutex functions
-

-
-
+
 

 
7.26.4.1 [The mtx_destroy function]

-

-
-
-
1          #include <threads.h>
+
+
1 Synopsis
+          #include <threads.h>
            void mtx_destroy(mtx_t *mtx);
     Description
 

-
-
+
 
2   The mtx_destroy function releases any resources used by the mutex pointed to by
     mtx. No threads can be blocked waiting for the mutex pointed to by mtx.
     Returns
 

-
-
+
 
3   The mtx_destroy function returns no value.
 
 

-
-
+
 

 
7.26.4.2 [The mtx_init function]

-

-
-
-
1           #include <threads.h>
+
+
1 Synopsis
+           #include <threads.h>
             int mtx_init(mtx_t *mtx, int type);
     Description
 

-
-
+
 
2   The mtx_init function creates a mutex object with properties indicated by type,
     which must have one of the six values:
     mtx_plain for a simple non-recursive mutex,
-    mtx_timed for a non-recursive mutex that supports timeout,                      
+    mtx_timed for a non-recursive mutex that supports timeout,
     mtx_plain | mtx_recursive for a simple recursive mutex, or
     mtx_timed | mtx_recursive for a recursive mutex that supports timeout.
 

-
-
+
 
3   If the mtx_init function succeeds, it sets the mutex pointed to by mtx to a value that
     uniquely identifies the newly created mutex.
     Returns
 

-
-
+
 
4   The mtx_init function returns thrd_success on success, or thrd_error if the
     request could not be honored.
 

-
-
+
 

 
7.26.4.3 [The mtx_lock function]

-

-
-
-
1           #include <threads.h>
+
+
1 Synopsis
+           #include <threads.h>
             int mtx_lock(mtx_t *mtx);
     Description
 

-
-
+
 
2   The mtx_lock function blocks until it locks the mutex pointed to by mtx. If the mutex
     is non-recursive, it shall not be locked by the calling thread. Prior calls to mtx_unlock
     on the same mutex shall synchronize with this operation.
     Returns
 

-
-
-
3   The mtx_lock function returns thrd_success on success, or thrd_error if the 
+
+
3   The mtx_lock function returns thrd_success on success, or thrd_error if the
     request could not be honored.
 

-
-
+
 

 
7.26.4.4 [The mtx_timedlock function]

-

-
-
-
1           #include <threads.h>
+
+
1 Synopsis
+           #include <threads.h>
             int mtx_timedlock(mtx_t *restrict mtx,
                  const struct timespec *restrict ts);
     Description
 

-
-
+
 
2   The mtx_timedlock function endeavors to block until it locks the mutex pointed to by
     mtx or until after the TIME_UTC-based calendar time pointed to by ts. The specified
     mutex shall support timeout. If the operation succeeds, prior calls to mtx_unlock on
     the same mutex shall synchronize with this operation.
     Returns
 

-
-
+
 
3   The mtx_timedlock function returns thrd_success on success, or
     thrd_timedout if the time specified was reached without acquiring the requested
     resource, or thrd_error if the request could not be honored.
 

-
-
+
 

 
7.26.4.5 [The mtx_trylock function]

-

-
-
-
1          #include <threads.h>
+
+
1 Synopsis
+          #include <threads.h>
            int mtx_trylock(mtx_t *mtx);
     Description
 

-
-
-
2   The mtx_trylock function endeavors to lock the mutex pointed to by mtx. If the 
+
+
2   The mtx_trylock function endeavors to lock the mutex pointed to by mtx. If the
     mutex is already locked, the function returns without blocking. If the operation succeeds,
     prior calls to mtx_unlock on the same mutex shall synchronize with this operation.
     Returns
 

-
-
+
 
3   The mtx_trylock function returns thrd_success on success, or thrd_busy if
     the resource requested is already in use, or thrd_error if the request could not be
     honored.
 

-
-
+
 

 
7.26.4.6 [The mtx_unlock function]

-

-
-
-
1          #include <threads.h>
+
+
1 Synopsis
+          #include <threads.h>
            int mtx_unlock(mtx_t *mtx);
     Description
 

-
-
+
 
2   The mtx_unlock function unlocks the mutex pointed to by mtx. The mutex pointed to
     by mtx shall be locked by the calling thread.
     Returns
 

-
-
+
 
3   The mtx_unlock function returns thrd_success on success or thrd_error if
     the request could not be honored.
 

-
-
+
 

 
7.26.5 [Thread functions]

-
 Thread functions
-

-
-
+
 

 
7.26.5.1 [The thrd_create function]

-

-
-
-
1           #include <threads.h>
+
+
1 Synopsis
+           #include <threads.h>
             int thrd_create(thrd_t *thr, thrd_start_t func,
                  void *arg);
     Description
 

-
-
+
 
2   The thrd_create function creates a new thread executing func(arg). If the
     thrd_create function succeeds, it sets the object pointed to by thr to the identifier of
     the newly created thread. (A thread's identifier may be reused for a different thread once
@@ -22186,117 +19147,96 @@ char int_p_sep_by_space
     execution of the new thread.
     Returns
 

-
-
+
 
3   The thrd_create function returns thrd_success on success, or thrd_nomem if
     no memory could be allocated for the thread requested, or thrd_error if the request
     could not be honored.
 

-
-
+
 

 
7.26.5.2 [The thrd_current function]

-

-
-
-
1           #include <threads.h>
+
+
1 Synopsis
+           #include <threads.h>
             thrd_t thrd_current(void);
     Description
 

-
-
+
 
2   The thrd_current function identifies the thread that called it.
     Returns
 

-
-
+
 
3   The thrd_current function returns the identifier of the thread that called it.
 

-
-
+
 

 
7.26.5.3 [The thrd_detach function]

-

-
-
-
1           #include <threads.h>
+
+
1 Synopsis
+           #include <threads.h>
             int thrd_detach(thrd_t thr);
     Description
 

-
-
+
 
2   The thrd_detach function tells the operating system to dispose of any resources
     allocated to the thread identified by thr when that thread terminates. The thread
     identified by thr shall not have been previously detached or joined with another thread.
     Returns
 

-
-
+
 
3   The thrd_detach function returns thrd_success on success or thrd_error if
     the request could not be honored.
 

-
-
+
 

 
7.26.5.4 [The thrd_equal function]

-

-
-
-
1          #include <threads.h>
+
+
1 Synopsis
+          #include <threads.h>
            int thrd_equal(thrd_t thr0, thrd_t thr1);
     Description
 

-
-
+
 
2   The thrd_equal function will determine whether the thread identified by thr0 refers
     to the thread identified by thr1.
     Returns
 

-
-
+
 
3   The thrd_equal function returns zero if the thread thr0 and the thread thr1 refer to
     different threads. Otherwise the thrd_equal function returns a nonzero value.
 

-
-
+
 

 
7.26.5.5 [The thrd_exit function]

-

-
-
-
1          #include <threads.h>
+
+
1 Synopsis
+          #include <threads.h>
            _Noreturn void thrd_exit(int res);
     Description
 

-
-
+
 
2   The thrd_exit function terminates execution of the calling thread and sets its result
     code to res.
 

-
-
+
 
3   The program shall terminate normally after the last thread has been terminated. The
     behavior shall be as if the program called the exit function with the status
     EXIT_SUCCESS at thread termination time.
     Returns
 

-
-
+
 
4   The thrd_exit function returns no value.
 

-
-
+
 

 
7.26.5.6 [The thrd_join function]

-

-
-
-
1          #include <threads.h>
+
+
1 Synopsis
+          #include <threads.h>
            int thrd_join(thrd_t thr, int *res);
     Description
 

-
-
+
 
2   The thrd_join function joins the thread identified by thr with the current thread by
     blocking until the other thread has terminated. If the parameter res is not a null pointer,
     it stores the thread's result code in the integer pointed to by res. The termination of the
@@ -22305,25 +19245,21 @@ char int_p_sep_by_space
     identified by thr shall not have been previously detached or joined with another thread.
     Returns
 

-
-
+
 
3   The thrd_join function returns thrd_success on success or thrd_error if the
     request could not be honored.
 

-
-
+
 

 
7.26.5.7 [The thrd_sleep function]

-

-
-
-
1           #include <threads.h>
+
+
1 Synopsis
+           #include <threads.h>
             int thrd_sleep(const struct timespec *duration,
                  struct timespec *remaining);
     Description
 

-
-
+
 
2   The thrd_sleep function suspends execution of the calling thread until either the
     interval specified by duration has elapsed or a signal which is not being ignored is
     received. If interrupted by a signal and the remaining argument is not null, the
@@ -22331,149 +19267,118 @@ char int_p_sep_by_space
     in the interval it points to. The duration and remaining arguments may point to the
     same object.
 

-
-
+
 
3   The suspension time may be longer than requested because the interval is rounded up to
     an integer multiple of the sleep resolution or because of the scheduling of other activity
     by the system. But, except for the case of being interrupted by a signal, the suspension
     time shall not be less than that specified, as measured by the system clock TIME_UTC.
     Returns
 

-
-
+
 
4   The thrd_sleep function returns zero if the requested time has elapsed, -1 if it has
     been interrupted by a signal, or a negative value if it fails.
 

-
-
+
 

 
7.26.5.8 [The thrd_yield function]

-

-
-
-
1           #include <threads.h>
+
+
1 Synopsis
+           #include <threads.h>
             void thrd_yield(void);
     Description
 

-
-
+
 
2   The thrd_yield function endeavors to permit other threads to run, even if the current
     thread would ordinarily continue to run.
     Returns
 

-
-
+
 
3   The thrd_yield function returns no value.
 
 

-
-
+
 

 
7.26.6 [Thread-specific storage functions]

-
 Thread-specific storage functions
-

-
-
+
 

 
7.26.6.1 [The tss_create function]

-

-
-
-
1          #include <threads.h>
+
+
1 Synopsis
+          #include <threads.h>
            int tss_create(tss_t *key, tss_dtor_t dtor);
     Description
 

-
-
+
 
2   The tss_create function creates a thread-specific storage pointer with destructor
     dtor, which may be null.
     Returns
 

-
-
+
 
3   If the tss_create function is successful, it sets the thread-specific storage pointed to
     by key to a value that uniquely identifies the newly created pointer and returns
     thrd_success; otherwise, thrd_error is returned and the thread-specific storage
     pointed to by key is set to an undefined value.
 

-
-
+
 

 
7.26.6.2 [The tss_delete function]

-

-
-
-
1          #include <threads.h>
+
+
1 Synopsis
+          #include <threads.h>
            void tss_delete(tss_t key);
     Description
 

-
-
+
 
2   The tss_delete function releases any resources used by the thread-specific storage
     identified by key.
     Returns
 

-
-
+
 
3   The tss_delete function returns no value.
 

-
-
+
 

 
7.26.6.3 [The tss_get function]

-

-
-
-
1          #include <threads.h>
+
+
1 Synopsis
+          #include <threads.h>
            void *tss_get(tss_t key);
     Description
 

-
-
+
 
2   The tss_get function returns the value for the current thread held in the thread-specific
     storage identified by key.
     Returns
 

-
-
+
 
3   The tss_get function returns the value for the current thread if successful, or zero if
     unsuccessful.
 

-
-
+
 

 
7.26.6.4 [The tss_set function]

-

-
-
-
1           #include <threads.h>
+
+
1 Synopsis
+           #include <threads.h>
             int tss_set(tss_t key, void *val);
     Description
 

-
-
+
 
2   The tss_set function sets the value for the current thread held in the thread-specific
     storage identified by key to val.
     Returns
 

-
-
+
 
3   The tss_set function returns thrd_success on success or thrd_error if the
-    request could not be honored.                                             
+    request could not be honored.
 

-
-
+
 

-
7.27 [Date and time ]

-
 Date and time 
-

-
-
+
7.27 [Date and time <time.h>]

+
 

 
7.27.1 [Components of time]

-

-
-
+
 
1   The header <time.h> defines two macros, and declares several types and functions for
     manipulating time. Many functions deal with a calendar time that represents the current
     date (according to the Gregorian calendar) and time. Some functions deal with local
@@ -22481,24 +19386,22 @@ char int_p_sep_by_space
     Saving Time, which is a temporary change in the algorithm for determining local time.
     The local time zone and Daylight Saving Time are implementation-defined.
 

-
-
-
2   The macros defined are NULL (described in 7.19);                                                            
+
+
2   The macros defined are NULL (described in 7.19);
             CLOCKS_PER_SEC
     which expands to an expression with type clock_t (described below) that is the
     number per second of the value returned by the clock function; and
             TIME_UTC
     which expands to an integer constant greater than 0 that designates the UTC time
-    base.316)
+    base.[316]
 

-
 
 
Footnote 316) Implementations may define additional time bases, but are only required to support a real time clock
          based on UTC.
 

 
-
-
3   The types declared are size_t (described in 7.19);
+
+
3   The types declared are size_t (described in 7.19);
             clock_t
     and
             time_t
@@ -22509,12 +19412,14 @@ char int_p_sep_by_space
             struct tm
     which holds the components of a calendar time, called the broken-down time.
 

-
-
+
 
4   The range and precision of times representable in clock_t and time_t are
     implementation-defined. The timespec structure shall contain at least the following
-    members, in any order.317)
-
+    members, in any order.[317]
+

+
+
Footnote 317) The tv_sec member is a linear count of seconds and may not have the normal semantics of a
+         time_t. The semantics of the members and their normal ranges are expressed in the comments.
             time_t tv_sec; // whole seconds --  0
             long   tv_nsec; // nanoseconds -- [0, 999999999]
     The tm structure shall contain at least the following members, in any order. The
@@ -22530,114 +19435,80 @@ char int_p_sep_by_space
             int    tm_isdst;         //   Daylight Saving Time flag
     The value of tm_isdst is positive if Daylight Saving Time is in effect, zero if Daylight
     Saving Time is not in effect, and negative if the information is not available.
-

-
-
-
Footnote 317) The tv_sec member is a linear count of seconds and may not have the normal semantics of a
-         time_t. The semantics of the members and their normal ranges are expressed in the comments.
 

 
-
-
Footnote 318) The range [0, 60] for tm_sec allows for a positive leap second.
-

-
-
+
 

 
7.27.2 [Time manipulation functions]

-
 Time manipulation functions
-

-
-
+
 

 
7.27.2.1 [The clock function]

-

-
-
-
1           #include <time.h>
+
+
1 Synopsis
+           #include <time.h>
             clock_t clock(void);
     Description
 

-
-
+
 
2   The clock function determines the processor time used.
     Returns
 

-
-
+
 
3   The clock function returns the implementation's best approximation to the processor
     time used by the program since the beginning of an implementation-defined era related
     only to the program invocation. To determine the time in seconds, the value returned by
     the clock function should be divided by the value of the macro CLOCKS_PER_SEC. If
     the processor time used is not available or its value cannot be represented, the function
-    returns the value (clock_t)(-1).319)
+    returns the value (clock_t)(-1).[319]
 
 

-
 
 
Footnote 319) In order to measure the time spent in a program, the clock function should be called at the start of
          the program and its return value subtracted from the value returned by subsequent calls.
 

 
-
+
 

 
7.27.2.2 [The difftime function]

-

-
-
-
1           #include <time.h>
+
+
1 Synopsis
+           #include <time.h>
             double difftime(time_t time1, time_t time0);
     Description
 

-
-
+
 
2   The difftime function computes the difference between two calendar times: time1 -
     time0.
     Returns
 

-
-
+
 
3   The difftime function returns the difference expressed in seconds as a double.
 

-
-
+
 

 
7.27.2.3 [The mktime function]

-

-
-
-
1           #include <time.h>
+
+
1 Synopsis
+           #include <time.h>
             time_t mktime(struct tm *timeptr);
     Description
 

-
-
+
 
2   The mktime function converts the broken-down time, expressed as local time, in the
     structure pointed to by timeptr into a calendar time value with the same encoding as
     that of the values returned by the time function. The original values of the tm_wday
     and tm_yday components of the structure are ignored, and the original values of the
-    other components are not restricted to the ranges indicated above.320) On successful
+    other components are not restricted to the ranges indicated above.[320] On successful
     completion, the values of the tm_wday and tm_yday components of the structure are
     set appropriately, and the other components are set to represent the specified calendar
     time, but with their values forced to the ranges indicated above; the final value of
     tm_mday is not set until tm_mon and tm_year are determined.
     Returns
 

-
 
 
Footnote 320) Thus, a positive or zero value for tm_isdst causes the mktime function to presume initially that
          Daylight Saving Time, respectively, is or is not in effect for the specified time. A negative value
          causes it to attempt to determine whether Daylight Saving Time is in effect for the specified time.
-

-
-
-
3   The mktime function returns the specified calendar time encoded as a value of type
-    time_t. If the calendar time cannot be represented, the function returns the value
-    (time_t)(-1).
-

-
-
-
4   EXAMPLE       What day of the week is July 4, 2001?
-
             #include <stdio.h>
             #include <time.h>
             static const char *const wday[] = {
@@ -22656,98 +19527,100 @@ char int_p_sep_by_space
             if (mktime(&time_str) == (time_t)(-1))
                   time_str.tm_wday = 7;
             printf("%s\n", wday[time_str.tm_wday]);
+

+
+
+
3   The mktime function returns the specified calendar time encoded as a value of type
+    time_t. If the calendar time cannot be represented, the function returns the value
+    (time_t)(-1).
+

+
+
4   EXAMPLE       What day of the week is July 4, 2001?
 
 

-
-
+
 

 
7.27.2.4 [The time function]

-

-
-
-
1           #include <time.h>
+
+
1 Synopsis
+           #include <time.h>
             time_t time(time_t *timer);
     Description
 

-
-
+
 
2   The time function determines the current calendar time. The encoding of the value is
     unspecified.
     Returns
 

-
-
+
 
3   The time function returns the implementation's best approximation to the current
     calendar time. The value (time_t)(-1) is returned if the calendar time is not
     available. If timer is not a null pointer, the return value is also assigned to the object it
     points to.
 

-
-
+
 

 
7.27.2.5 [The timespec_get function]

-

-
-
-
1           #include <time.h>
+
+
1 Synopsis
+           #include <time.h>
             int timespec_get(struct timespec *ts, int base);
     Description
 

-
-
+
 
2   The timespec_get function sets the interval pointed to by ts to hold the current
     calendar time based on the specified time base.
 

-
-
+
 
3   If base is TIME_UTC, the tv_sec member is set to the number of seconds since an
     implementation defined epoch, truncated to a whole value and the tv_nsec member is
     set to the integral number of nanoseconds, rounded to the resolution of the system
-    clock.321)
+    clock.[321]
     Returns
 

-
 
 
Footnote 321) Although a struct timespec object describes times with nanosecond resolution, the available
          resolution is system dependent and may even be greater than 1 second.
 

 
-
+
 
4   If the timespec_get function is successful it returns the nonzero value base;
     otherwise, it returns zero.
 

-
-
+
 

 
7.27.3 [Time conversion functions]

-

-
-
+
 
1   Except for the strftime function, these functions each return a pointer to one of two
     types of static objects: a broken-down time structure or an array of char. Execution of
     any of the functions that return a pointer to one of these object types may overwrite the
     information in any object of the same type pointed to by the value returned from any
     previous call to any of them and the functions are not required to avoid data races with
-    each other.322) The implementation shall behave as if no other library functions call these
+    each other.[322] The implementation shall behave as if no other library functions call these
     functions.
 

-
 
-
Footnote 322) Alternative time conversion functions that do avoid data races are specified in K.3.8.2.
+
Footnote 322) Alternative time conversion functions that do avoid data races are specified in K.3.8.2.
+            sprintf(result, "%.3s %.3s%3d %.2d:%.2d:%.2d %d\n",
+                 wday_name[timeptr->tm_wday],
+                 mon_name[timeptr->tm_mon],
+                 timeptr->tm_mday, timeptr->tm_hour,
+                 timeptr->tm_min, timeptr->tm_sec,
+                 1900 + timeptr->tm_year);
+            return result;
+    }
 

 
-
+
 

 
7.27.3.1 [The asctime function]

-

-
-
-
1            #include <time.h>
+
+
1 Synopsis
+            #include <time.h>
              char *asctime(const struct tm *timeptr);
     Description
 

-
-
+
 
2   The asctime function converts the broken-down time in the structure pointed to by
     timeptr into a string in the form
              Sun Sep 16 01:03:52 1973\n\0
@@ -22762,117 +19635,90 @@ char int_p_sep_by_space
               "Jul", "Aug", "Sep", "Oct", "Nov", "Dec"
          };
          static char result[26];
-
-            sprintf(result, "%.3s %.3s%3d %.2d:%.2d:%.2d %d\n",
-                 wday_name[timeptr->tm_wday],
-                 mon_name[timeptr->tm_mon],
-                 timeptr->tm_mday, timeptr->tm_hour,
-                 timeptr->tm_min, timeptr->tm_sec,
-                 1900 + timeptr->tm_year);
-            return result;
-    }
 

-
-
+
 
3   If any of the members of the broken-down time contain values that are outside their
-    normal ranges,323) the behavior of the asctime function is undefined. Likewise, if the
+    normal ranges,[323] the behavior of the asctime function is undefined. Likewise, if the
     calculated year exceeds four digits or is less than the year 1000, the behavior is
     undefined.
     Returns
 

-
 
-
Footnote 323) See 7.27.1.
+
Footnote 323) See 7.27.1.
+    Description
 

 
-
+
 
4   The asctime function returns a pointer to the string.
 

-
-
+
 

 
7.27.3.2 [The ctime function]

-

-
-
-
1           #include <time.h>
+
+
1 Synopsis
+           #include <time.h>
             char *ctime(const time_t *timer);
     Description
 

-
-
+
 
2   The ctime function converts the calendar time pointed to by timer to local time in the
     form of a string. It is equivalent to
             asctime(localtime(timer))
     Returns
 

-
-
+
 
3   The ctime function returns the pointer returned by the asctime function with that
     broken-down time as argument.
-    Forward references: the localtime function (7.27.3.4).
+    Forward references: the localtime function (7.27.3.4).
 

-
-
+
 

 
7.27.3.3 [The gmtime function]

-

-
-
-
1           #include <time.h>
+
+
1 Synopsis
+           #include <time.h>
             struct tm *gmtime(const time_t *timer);
-
-    Description
 

-
-
+
 
2   The gmtime function converts the calendar time pointed to by timer into a broken-
     down time, expressed as UTC.
     Returns
 

-
-
+
 
3   The gmtime function returns a pointer to the broken-down time, or a null pointer if the
     specified time cannot be converted to UTC.
 

-
-
+
 

 
7.27.3.4 [The localtime function]

-

-
-
-
1          #include <time.h>
+
+
1 Synopsis
+          #include <time.h>
            struct tm *localtime(const time_t *timer);
     Description
 

-
-
+
 
2   The localtime function converts the calendar time pointed to by timer into a
     broken-down time, expressed as local time.
     Returns
 

-
-
+
 
3   The localtime function returns a pointer to the broken-down time, or a null pointer if
     the specified time cannot be converted to local time.
 

-
-
+
 

 
7.27.3.5 [The strftime function]

-

-
-
-
1          #include <time.h>
+
+
1 Synopsis
+          #include <time.h>
            size_t strftime(char * restrict s,
                 size_t maxsize,
                 const char * restrict format,
                 const struct tm * restrict timeptr);
     Description
 

-
-
+
 
2   The strftime function places characters into the array pointed to by s as controlled by
     the string pointed to by format. The format shall be a multibyte character sequence,
     beginning and ending in its initial shift state. The format string consists of zero or
@@ -22883,8 +19729,7 @@ char int_p_sep_by_space
     unchanged into the array. If copying takes place between objects that overlap, the
     behavior is undefined. No more than maxsize characters are placed into the array.
 

-
-
+
 
3   Each conversion specifier is replaced by appropriate characters as described in the
     following list. The appropriate characters are determined using the LC_TIME category
 
@@ -22896,7 +19741,7 @@ the specified values is outside the normal range, the characters stored are unsp
 %b   is replaced by the locale's abbreviated month name. [tm_mon]
 %B   is replaced by the locale's full month name. [tm_mon]
 %c   is replaced by the locale's appropriate date and time representation. [all specified
-     in 7.27.1]
+     in 7.27.1]
 %C   is replaced by the year divided by 100 and truncated to an integer, as a decimal
      number (00-99). [tm_year]
 %d   is replaced by the day of the month as a decimal number (01-31). [tm_mday]
@@ -22926,7 +19771,7 @@ the specified values is outside the normal range, the characters stored are unsp
      tm_sec]
 %u   is replaced by the ISO 8601 weekday as a decimal number (1-7), where Monday
      is 1. [tm_wday]
-%U   is replaced by the week number of the year (the first Sunday as the first day of week 1) 
+%U   is replaced by the week number of the year (the first Sunday as the first day of week 1)
      as a decimal number (00-53). [tm_year, tm_wday, tm_yday]
 %V   is replaced by the ISO 8601 week number (see below) as a decimal number
           (01-53). [tm_year, tm_wday, tm_yday]
@@ -22934,8 +19779,8 @@ the specified values is outside the normal range, the characters stored are unsp
           [tm_wday]
     %W    is replaced by the week number of the year (the first Monday as the first day of
           week 1) as a decimal number (00-53). [tm_year, tm_wday, tm_yday]
-    %x    is replaced by the locale's appropriate date representation. [all specified in 7.27.1]
-    %X    is replaced by the locale's appropriate time representation. [all specified in 7.27.1]
+    %x    is replaced by the locale's appropriate date representation. [all specified in 7.27.1]
+    %X    is replaced by the locale's appropriate time representation. [all specified in 7.27.1]
     %y    is replaced by the last 2 digits of the year as a decimal number (00-99).
           [tm_year]
     %Y    is replaced by the year as a decimal number (e.g., 1997). [tm_year]
@@ -22946,8 +19791,7 @@ the specified values is outside the normal range, the characters stored are unsp
           time zone is determinable. [tm_isdst]
     %%    is replaced by %.
 

-
-
+
 
4   Some conversion specifiers can be modified by the inclusion of an E or O modifier
     character to indicate an alternative format or specification. If the alternative format or
     specification does not exist for the current locale, the modifier is ignored.
@@ -22984,8 +19828,7 @@ the specified values is outside the normal range, the characters stored are unsp
     %Oy is replaced by the last 2 digits of the year, using the locale's alternative numeric
         symbols.
 

-
-
+
 
5   %g, %G, and %V give values according to the ISO 8601 week-based year. In this system,
     weeks begin on a Monday and week 1 of the year is the week that includes January 4th,
     which is also the week that includes the first Thursday of the year, and is also the first
@@ -22996,12 +19839,10 @@ the specified values is outside the normal range, the characters stored are unsp
     the following year. Thus, for Tuesday 30th December 1997, %G is replaced by 1998 and
     %V is replaced by 01.
 

-
-
+
 
6   If a conversion specifier is not one of the above, the behavior is undefined.
 

-
-
+
 
7   In the "C" locale, the E and O modifiers are ignored and the replacement strings for the
     following specifiers are:
     %a    the first three characters of %A.
@@ -23016,41 +19857,33 @@ the specified values is outside the normal range, the characters stored are unsp
     %Z    implementation-defined.
     Returns
 

-
-
+
 
8   If the total number of resulting characters including the terminating null character is not
     more than maxsize, the strftime function returns the number of characters placed
     into the array pointed to by s not including the terminating null character. Otherwise,
     zero is returned and the contents of the array are indeterminate.
 
 

-
-
+
 

-
7.28 [Unicode utilities ]

-

-
-
+
7.28 [Unicode utilities <uchar.h>]

+
 
1   The header <uchar.h> declares types and functions for manipulating Unicode
     characters.
 

-
-
-
2   The types declared are mbstate_t (described in 7.30.1) and size_t (described in 7.19);
+
+
2   The types declared are mbstate_t (described in 7.30.1) and size_t (described in 7.19);
            char16_t
     which is an unsigned integer type used for 16-bit characters and is the same type as
-    uint_least16_t (described in 7.20.1.2); and
+    uint_least16_t (described in 7.20.1.2); and
            char32_t
     which is an unsigned integer type used for 32-bit characters and is the same type as
-    uint_least32_t (also described in 7.20.1.2).
+    uint_least32_t (also described in 7.20.1.2).
 

-
-
+
 

 
7.28.1 [Restartable multibyte/wide character conversion functions]

-

-
-
+
 
1   These functions have a parameter, ps, of type pointer to mbstate_t that points to an
     object that can completely describe the current conversion state of the associated
     multibyte character sequence, which the functions alter as necessary. If ps is a null
@@ -23059,27 +19892,23 @@ the specified values is outside the normal range, the characters stored are unsp
     to avoid data races with other calls to the same function in this case. The implementation
     behaves as if no library function calls these functions with a null pointer for ps.
 

-
-
+
 

 
7.28.1.1 [The mbrtoc16 function]

-

-
-
-
1          #include <uchar.h>
+
+
1 Synopsis
+          #include <uchar.h>
            size_t mbrtoc16(char16_t * restrict pc16,
                 const char * restrict s, size_t n,
                 mbstate_t * restrict ps);
     Description
 

-
-
+
 
2   If s is a null pointer, the mbrtoc16 function is equivalent to the call:
                    mbrtoc16(NULL, "", 1, ps)
     In this case, the values of the parameters pc16 and n are ignored.
 

-
-
+
 
3   If s is not a null pointer, the mbrtoc16 function inspects at most n bytes beginning with
     the byte pointed to by s to determine the number of bytes needed to complete the next
     multibyte character (including any shift sequences). If the function determines that the
@@ -23091,8 +19920,7 @@ the specified values is outside the normal range, the characters stored are unsp
     character, the resulting state described is the initial conversion state.
     Returns
 

-
-
+
 
4   The mbrtoc16 function returns the first of the following that applies (given the current
     conversion state):
     0                     if the next n or fewer bytes complete the multibyte character that
@@ -23104,74 +19932,64 @@ the specified values is outside the normal range, the characters stored are unsp
                  bytes from the input have been consumed by this call).
     (size_t)(-2) if the next n bytes contribute to an incomplete (but potentially valid)
                  multibyte character, and all n bytes have been processed (no value is
-                 stored).324)
+                 stored).[324]
     (size_t)(-1) if an encoding error occurs, in which case the next n or fewer bytes
                  do not contribute to a complete and valid multibyte character (no
                  value is stored); the value of the macro EILSEQ is stored in errno,
                  and the conversion state is unspecified.
 

-
 
 
Footnote 324) When n has at least the value of the MB_CUR_MAX macro, this case can only occur if s points at a
          sequence of redundant shift sequences (for implementations with state-dependent encodings).
-

-
-
-

-
7.28.1.2 [The c16rtomb function]

-

-
-
-
1           #include <uchar.h>
-            size_t c16rtomb(char * restrict s, char16_t c16,
-                 mbstate_t * restrict ps);
-    Description
-

-
-
-
2   If s is a null pointer, the c16rtomb function is equivalent to the call
-                    c16rtomb(buf, L'\0', ps)
-    where buf is an internal buffer.
-

-
-
-
3   If s is not a null pointer, the c16rtomb function determines the number of bytes needed
-    to represent the multibyte character that corresponds to the wide character given by c16
-    (including any shift sequences), and stores the multibyte character representation in the
-
     array whose first element is pointed to by s. At most MB_CUR_MAX bytes are stored. If
     c16 is a null wide character, a null byte is stored, preceded by any shift sequence needed
     to restore the initial shift state; the resulting state described is the initial conversion state.
     Returns
-

+

 
-
+
+

+
7.28.1.2 [The c16rtomb function]

+
+
1 Synopsis
+           #include <uchar.h>
+            size_t c16rtomb(char * restrict s, char16_t c16,
+                 mbstate_t * restrict ps);
+    Description
+

+
+
2   If s is a null pointer, the c16rtomb function is equivalent to the call
+                    c16rtomb(buf, L'\0', ps)
+    where buf is an internal buffer.
+

+
+
3   If s is not a null pointer, the c16rtomb function determines the number of bytes needed
+    to represent the multibyte character that corresponds to the wide character given by c16
+    (including any shift sequences), and stores the multibyte character representation in the
+

+
 
4   The c16rtomb function returns the number of bytes stored in the array object (including
     any shift sequences). When c16 is not a valid wide character, an encoding error occurs:
     the function stores the value of the macro EILSEQ in errno and returns
     (size_t)(-1); the conversion state is unspecified.
 

-
-
+
 

 
7.28.1.3 [The mbrtoc32 function]

-

-
-
-
1           #include <uchar.h>
+
+
1 Synopsis
+           #include <uchar.h>
             size_t mbrtoc32(char32_t * restrict pc32,
                  const char * restrict s, size_t n,
                  mbstate_t * restrict ps);
     Description
 

-
-
+
 
2   If s is a null pointer, the mbrtoc32 function is equivalent to the call:
                     mbrtoc32(NULL, "", 1, ps)
     In this case, the values of the parameters pc32 and n are ignored.
 

-
-
+
 
3   If s is not a null pointer, the mbrtoc32 function inspects at most n bytes beginning with
     the byte pointed to by s to determine the number of bytes needed to complete the next
     multibyte character (including any shift sequences). If the function determines that the
@@ -23183,8 +20001,7 @@ the specified values is outside the normal range, the characters stored are unsp
     character, the resulting state described is the initial conversion state.
     Returns
 

-
-
+
 
4   The mbrtoc32 function returns the first of the following that applies (given the current
     conversion state):
     0                    if the next n or fewer bytes complete the multibyte character that
@@ -23196,37 +20013,33 @@ the specified values is outside the normal range, the characters stored are unsp
                  bytes from the input have been consumed by this call).
     (size_t)(-2) if the next n bytes contribute to an incomplete (but potentially valid)
                  multibyte character, and all n bytes have been processed (no value is
-                 stored).325)
+                 stored).[325]
     (size_t)(-1) if an encoding error occurs, in which case the next n or fewer bytes
                  do not contribute to a complete and valid multibyte character (no
                  value is stored); the value of the macro EILSEQ is stored in errno,
                  and the conversion state is unspecified.
 

-
 
 
Footnote 325) When n has at least the value of the MB_CUR_MAX macro, this case can only occur if s points at a
          sequence of redundant shift sequences (for implementations with state-dependent encodings).
 

 
-
+
 

 
7.28.1.4 [The c32rtomb function]

-

-
-
-
1           #include <uchar.h>
+
+
1 Synopsis
+           #include <uchar.h>
             size_t c32rtomb(char * restrict s, char32_t c32,
                  mbstate_t * restrict ps);
     Description
 

-
-
+
 
2   If s is a null pointer, the c32rtomb function is equivalent to the call
                     c32rtomb(buf, L'\0', ps)
     where buf is an internal buffer.
 

-
-
+
 
3   If s is not a null pointer, the c32rtomb function determines the number of bytes needed
     to represent the multibyte character that corresponds to the wide character given by c32
     (including any shift sequences), and stores the multibyte character representation in the
@@ -23235,37 +20048,29 @@ the specified values is outside the normal range, the characters stored are unsp
     to restore the initial shift state; the resulting state described is the initial conversion state.
     Returns
 

-
-
+
 
4   The c32rtomb function returns the number of bytes stored in the array object (including
     any shift sequences). When c32 is not a valid wide character, an encoding error occurs:
     the function stores the value of the macro EILSEQ in errno and returns
     (size_t)(-1); the conversion state is unspecified.
 
 

-
-
+
 

-
7.29 [Extended multibyte and wide character utilities ]

-
 Extended multibyte and wide character utilities 
-

-
-
+
7.29 [Extended multibyte and wide character utilities <wchar.h>]

+
 

 
7.29.1 [Introduction]

-

-
-
+
 
1   The header <wchar.h> defines four macros, and declares four data types, one tag, and
-    many functions.326)
+    many functions.[326]
 

-
 
-
Footnote 326) See ``future library directions'' (7.31.16).
+
Footnote 326) See ``future library directions'' (7.31.16).
 

 
-
-
2   The types declared are wchar_t and size_t (both described in 7.19);
+
+
2   The types declared are wchar_t and size_t (both described in 7.19);
              mbstate_t
     which is a complete object type other than an array type that can hold the conversion state
     information necessary to convert between sequences of multibyte characters and wide
@@ -23274,85 +20079,74 @@ the specified values is outside the normal range, the characters stored are unsp
     which is an integer type unchanged by default argument promotions that can hold any
     value corresponding to members of the extended character set, as well as at least one
     value that does not correspond to any member of the extended character set (see WEOF
-    below);327) and
+    below);[327] and
              struct tm
-    which is declared as an incomplete structure type (the contents are described in 7.27.1).
+    which is declared as an incomplete structure type (the contents are described in 7.27.1).
 

-
 
 
Footnote 327) wchar_t and wint_t can be the same integer type.
 

 
-
-
3   The macros defined are NULL (described in 7.19); WCHAR_MIN and WCHAR_MAX
-    (described in 7.20.3); and
+
+
3   The macros defined are NULL (described in 7.19); WCHAR_MIN and WCHAR_MAX
+    (described in 7.20.3); and
              WEOF
     which expands to a constant expression of type wint_t whose value does not
-    correspond to any member of the extended character set.328) It is accepted (and returned)
+    correspond to any member of the extended character set.[328] It is accepted (and returned)
     by several functions in this subclause to indicate end-of-file, that is, no more input from a
     stream. It is also used as a wide character value that does not correspond to any member
     of the extended character set.
 

-
 
 
Footnote 328) The value of the macro WEOF may differ from that of EOF and need not be negative.
+    -- Functions for wide string date and time conversion; and
+    -- Functions that provide extended capabilities for conversion between multibyte and
+       wide character sequences.
 

 
-
+
 
4   The functions declared are grouped as follows:
     -- Functions that perform input and output of wide characters, or multibyte characters,
        or both;
     -- Functions that provide wide string numeric conversion;
     -- Functions that perform general wide string manipulation;
-
-    -- Functions for wide string date and time conversion; and
-    -- Functions that provide extended capabilities for conversion between multibyte and
-       wide character sequences.
 

-
-
+
 
5   Arguments to the functions in this subclause may point to arrays containing wchar_t
     values that do not correspond to members of the extended character set. Such values
     shall be processed according to the specified semantics, except that it is unspecified
     whether an encoding error occurs if such a value appears in the format string for a
-    function in 7.29.2 or 7.29.5 and the specified semantics do not require that value to be
+    function in 7.29.2 or 7.29.5 and the specified semantics do not require that value to be
     processed by wcrtomb.
 

-
-
+
 
6   Unless explicitly stated otherwise, if the execution of a function described in this
     subclause causes copying to take place between objects that overlap, the behavior is
     undefined.
 

-
-
+
 

 
7.29.2 [Formatted wide character input/output functions]

-

-
-
+
 
1   The formatted wide character input/output functions shall behave as if there is a sequence
-    point after the actions associated with each specifier.329)
+    point after the actions associated with each specifier.[329]
 

-
 
 
Footnote 329) The fwprintf functions perform writes to memory for the %n specifier.
 

 
-
+
 

 
7.29.2.1 [The fwprintf function]

-

-
-
-
1           #include <stdio.h>
+
+
1 Synopsis
+           #include <stdio.h>
             #include <wchar.h>
             int fwprintf(FILE * restrict stream,
                  const wchar_t * restrict format, ...);
     Description
 

-
-
+
 
2   The fwprintf function writes output to the stream pointed to by stream, under
     control of the wide string pointed to by format that specifies how subsequent arguments
     are converted for output. If there are insufficient arguments for the format, the behavior
@@ -23360,8 +20154,7 @@ the specified values is outside the normal range, the characters stored are unsp
     are evaluated (as always) but are otherwise ignored. The fwprintf function returns
     when the end of the format string is encountered.
 

-
-
+
 
3   The format is composed of zero or more directives: ordinary wide characters (not %),
     which are copied unchanged to the output stream; and conversion specifications, each of
     which results in fetching zero or more subsequent arguments, converting them, if
@@ -23369,8 +20162,7 @@ the specified values is outside the normal range, the characters stored are unsp
     result to the output stream.
 
 

-
-
+
 
4   Each conversion specification is introduced by the wide character %. After the %, the
     following appear in sequence:
     -- Zero or more flags (in any order) that modify the meaning of the conversion
@@ -23379,7 +20171,7 @@ the specified values is outside the normal range, the characters stored are unsp
        than the field width, it is padded with spaces (by default) on the left (or right, if the
        left adjustment flag, described later, has been given) to the field width. The field
        width takes the form of an asterisk * (described later) or a nonnegative decimal
-       integer.330)
+       integer.[330]
     -- An optional precision that gives the minimum number of digits to appear for the d, i,
        o, u, x, and X conversions, the number of digits to appear after the decimal-point
        wide character for a, A, e, E, f, and F conversions, the maximum number of
@@ -23392,27 +20184,8 @@ the specified values is outside the normal range, the characters stored are unsp
     -- A conversion specifier wide character that specifies the type of conversion to be
        applied.
 

-
 
 
Footnote 330) Note that 0 is taken as a flag, not as the beginning of a field width.
-

-
-
-
5   As noted above, a field width, or precision, or both, may be indicated by an asterisk. In
-    this case, an int argument supplies the field width or precision. The arguments
-    specifying field width, or precision, or both, shall appear (in that order) before the
-    argument (if any) to be converted. A negative field width argument is taken as a - flag
-    followed by a positive field width. A negative precision argument is taken as if the
-    precision were omitted.
-

-
-
-
6   The flag wide characters and their meanings are:
-    -        The result of the conversion is left-justified within the field. (It is right-justified if
-             this flag is not specified.)
-    +        The result of a signed conversion always begins with a plus or minus sign. (It
-             begins with a sign only when a negative value is converted if this flag is not
-
               specified.)331)
     space If the first wide character of a signed conversion is not a sign, or if a signed
           conversion results in no wide characters, a space is prefixed to the result. If the
@@ -23432,14 +20205,24 @@ the specified values is outside the normal range, the characters stored are unsp
               0 and - flags both appear, the 0 flag is ignored. For d, i, o, u, x, and X
               conversions, if a precision is specified, the 0 flag is ignored. For other
               conversions, the behavior is undefined.
-

-
-
-
Footnote 331) The results of all floating conversions of a negative zero, and of negative values that round to zero,
-         include a minus sign.
 

 
-
+
+
5   As noted above, a field width, or precision, or both, may be indicated by an asterisk. In
+    this case, an int argument supplies the field width or precision. The arguments
+    specifying field width, or precision, or both, shall appear (in that order) before the
+    argument (if any) to be converted. A negative field width argument is taken as a - flag
+    followed by a positive field width. A negative precision argument is taken as if the
+    precision were omitted.
+

+
+
6   The flag wide characters and their meanings are:
+    -        The result of the conversion is left-justified within the field. (It is right-justified if
+             this flag is not specified.)
+    +        The result of a signed conversion always begins with a plus or minus sign. (It
+             begins with a sign only when a negative value is converted if this flag is not
+

+
 
7   The length modifiers and their meanings are:
     hh             Specifies that a following d, i, o, u, x, or X conversion specifier applies to a
                    signed char or unsigned char argument (the argument will have
@@ -23456,33 +20239,8 @@ the specified values is outside the normal range, the characters stored are unsp
     l (ell)        Specifies that a following d, i, o, u, x, or X conversion specifier applies to a
                    long int or unsigned long int argument; that a following n
                    conversion specifier applies to a pointer to a long int argument; that a
-
-                 following c conversion specifier applies to a wint_t argument; that a
-                 following s conversion specifier applies to a pointer to a wchar_t
-                 argument; or has no effect on a following a, A, e, E, f, F, g, or G conversion
-                 specifier.
-    ll (ell-ell) Specifies that a following d, i, o, u, x, or X conversion specifier applies to a
-                 long long int or unsigned long long int argument; or that a
-                 following n conversion specifier applies to a pointer to a long long int
-                 argument.
-    j            Specifies that a following d, i, o, u, x, or X conversion specifier applies to
-                 an intmax_t or uintmax_t argument; or that a following n conversion
-                 specifier applies to a pointer to an intmax_t argument.
-    z            Specifies that a following d, i, o, u, x, or X conversion specifier applies to a
-                 size_t or the corresponding signed integer type argument; or that a
-                 following n conversion specifier applies to a pointer to a signed integer type
-                 corresponding to size_t argument.
-    t            Specifies that a following d, i, o, u, x, or X conversion specifier applies to a
-                 ptrdiff_t or the corresponding unsigned integer type argument; or that a
-                 following n conversion specifier applies to a pointer to a ptrdiff_t
-                 argument.
-    L            Specifies that a following a, A, e, E, f, F, g, or G conversion specifier
-                 applies to a long double argument.
-        If a length modifier appears with any conversion specifier other than as specified above,
-        the behavior is undefined.
 

-
-
+
 
8   The conversion specifiers and their meanings are:
     d,i         The int argument is converted to signed decimal in the style [-]dddd. The
                 precision specifies the minimum number of digits to appear; if the value
@@ -23510,9 +20268,9 @@ the specified values is outside the normal range, the characters stored are unsp
                  [-]nan or [-]nan(n-wchar-sequence) -- which style, and the meaning of
                  any n-wchar-sequence, is implementation-defined. The F conversion
                  specifier produces INF, INFINITY, or NAN instead of inf, infinity, or
-                 nan, respectively.332)
+                 nan, respectively.[332]
     e,E          A double argument representing a floating-point number is converted in the
-                 style [-]d.ddd e±dd, where there is one digit (which is nonzero if the
+                 style [-]d.ddd e\xB1dd, where there is one digit (which is nonzero if the
                  argument is nonzero) before the decimal-point wide character and the number
                  of digits after it is equal to the precision; if the precision is missing, it is taken
                  as 6; if the precision is zero and the # flag is not specified, no decimal-point
@@ -23532,13 +20290,16 @@ the specified values is outside the normal range, the characters stored are unsp
                     P - ( X + 1).
                  -- otherwise, the conversion is with style e (or E) and precision P - 1.
                  Finally, unless the # flag is used, any trailing zeros are removed from the
-
+

+
+
Footnote 332) When applied to infinite and NaN values, the -, +, and space flag wide characters have their usual
+         meaning; the # and 0 flag wide characters have no effect.
                  fractional portion of the result and the decimal-point wide character is
                  removed if there is no fractional portion remaining.
                  A double argument representing an infinity or NaN is converted in the style
                  of an f or F conversion specifier.
     a,A          A double argument representing a floating-point number is converted in the
-                 style [-]0xh.hhhh p±d, where there is one hexadecimal digit (which is
+                 style [-]0xh.hhhh p\xB1d, where there is one hexadecimal digit (which is
                  nonzero if the argument is a normalized floating-point number and is
                  otherwise unspecified) before the decimal-point wide character333) and the
                  number of hexadecimal digits after it is equal to the precision; if the precision
@@ -23565,79 +20326,15 @@ the specified values is outside the normal range, the characters stored are unsp
                  if by repeated calls to the mbrtowc function, with the conversion state
                  described by an mbstate_t object initialized to zero before the first
                  multibyte character is converted, and written up to (but not including) the
-
-                    terminating null wide character. If the precision is specified, no more than
-                    that many wide characters are written. If the precision is not specified or is
-                    greater than the size of the converted array, the converted array shall contain a
-                    null wide character.
-                    If an l length modifier is present, the argument shall be a pointer to the initial
-                    element of an array of wchar_t type. Wide characters from the array are
-                    written up to (but not including) a terminating null wide character. If the
-                    precision is specified, no more than that many wide characters are written. If
-                    the precision is not specified or is greater than the size of the array, the array
-                    shall contain a null wide character.
-     p              The argument shall be a pointer to void. The value of the pointer is
-                    converted to a sequence of printing wide characters, in an implementation-
-                    defined manner.
-     n              The argument shall be a pointer to signed integer into which is written the
-                    number of wide characters written to the output stream so far by this call to
-                    fwprintf. No argument is converted, but one is consumed. If the
-                    conversion specification includes any flags, a field width, or a precision, the
-                    behavior is undefined.
-     %              A % wide character is written. No argument is converted. The complete
-                    conversion specification shall be %%.
-

-
-
-
Footnote 332) When applied to infinite and NaN values, the -, +, and space flag wide characters have their usual
-         meaning; the # and 0 flag wide characters have no effect.
 

 
-
-
Footnote 333) Binary implementations can choose the hexadecimal digit to the left of the decimal-point wide
-         character so that subsequent digits align to nibble (4-bit) boundaries.
-

-
-
-
Footnote 334) The precision p is sufficient to distinguish values of the source type if 16 p-1 > b n where b is
-         FLT_RADIX and n is the number of base-b digits in the significand of the source type. A smaller p
-         might suffice depending on the implementation's scheme for determining the digit to the left of the
-         decimal-point wide character.
-

-
-
-
9    If a conversion specification is invalid, the behavior is undefined.335) If any argument is
+
+
9    If a conversion specification is invalid, the behavior is undefined.[335] If any argument is
      not the correct type for the corresponding conversion specification, the behavior is
      undefined.
 

-
 
-
Footnote 335) See ``future library directions'' (7.31.16).
-

-
-
-
10   In no case does a nonexistent or small field width cause truncation of a field; if the result
-     of a conversion is wider than the field width, the field is expanded to contain the
-     conversion result.
-

-
-
-
11   For a and A conversions, if FLT_RADIX is a power of 2, the value is correctly rounded
-     to a hexadecimal floating number with the given precision.
-     Recommended practice
-

-
-
-
12   For a and A conversions, if FLT_RADIX is not a power of 2 and the result is not exactly
-     representable in the given precision, the result should be one of the two adjacent numbers
-     in hexadecimal floating style with the given precision, with the extra stipulation that the
-     error should have a correct sign for the current rounding direction.
-

-
-
-
13   For e, E, f, F, g, and G conversions, if the number of significant decimal digits is at most
-     DECIMAL_DIG, then the result should be correctly rounded.336) If the number of
-
+
Footnote 335) See ``future library directions'' (7.31.16).
      significant decimal digits is more than DECIMAL_DIG but the source value is exactly
      representable with DECIMAL_DIG digits, then the result should be an exact
      representation with trailing zeros. Otherwise, the source value is bounded by two
@@ -23645,26 +20342,48 @@ the specified values is outside the normal range, the characters stored are unsp
      of the resultant decimal string D should satisfy L  D  U , with the extra stipulation that
      the error should have a correct sign for the current rounding direction.
      Returns
-

+

 
+
+
10   In no case does a nonexistent or small field width cause truncation of a field; if the result
+     of a conversion is wider than the field width, the field is expanded to contain the
+     conversion result.
+

+
+
11   For a and A conversions, if FLT_RADIX is a power of 2, the value is correctly rounded
+     to a hexadecimal floating number with the given precision.
+     Recommended practice
+

+
+
12   For a and A conversions, if FLT_RADIX is not a power of 2 and the result is not exactly
+     representable in the given precision, the result should be one of the two adjacent numbers
+     in hexadecimal floating style with the given precision, with the extra stipulation that the
+     error should have a correct sign for the current rounding direction.
+

+
+
13   For e, E, f, F, g, and G conversions, if the number of significant decimal digits is at most
+     DECIMAL_DIG, then the result should be correctly rounded.[336] If the number of
+

 
 
Footnote 336) For binary-to-decimal conversion, the result format's values are the numbers representable with the
           given format specifier. The number of significant digits is determined by the format specifier, and in
           the case of fixed-point conversion by the source value as well.
+    as pointers to the objects to receive the converted input. If there are insufficient
+    arguments for the format, the behavior is undefined. If the format is exhausted while
+    arguments remain, the excess arguments are evaluated (as always) but are otherwise
+    ignored.
 

 
-
+
 
14   The fwprintf function returns the number of wide characters transmitted, or a negative
      value if an output or encoding error occurred.
      Environmental limits
 

-
-
+
 
15   The number of wide characters that can be produced by any single conversion shall be at
      least 4095.
 

-
-
+
 
16   EXAMPLE       To print a date and time in the form ``Sunday, July 3, 10:02'' followed by  to five decimal
      places:
              #include <math.h>
@@ -23677,35 +20396,26 @@ the specified values is outside the normal range, the characters stored are unsp
                      weekday, month, day, hour, min);
              fwprintf(stdout, L"pi = %.5f\n", 4 * atan(1.0));
 
-     Forward references:           the btowc function (7.29.6.1.1), the mbrtowc function
-     (7.29.6.3.2).
+     Forward references:           the btowc function (7.29.6.1.1), the mbrtowc function
+     (7.29.6.3.2).
 

-
-
+
 

 
7.29.2.2 [The fwscanf function]

-

-
-
-
1            #include <stdio.h>
+
+
1 Synopsis
+            #include <stdio.h>
              #include <wchar.h>
              int fwscanf(FILE * restrict stream,
                   const wchar_t * restrict format, ...);
      Description
 

-
-
+
 
2    The fwscanf function reads input from the stream pointed to by stream, under
      control of the wide string pointed to by format that specifies the admissible input
      sequences and how they are to be converted for assignment, using subsequent arguments
-
-    as pointers to the objects to receive the converted input. If there are insufficient
-    arguments for the format, the behavior is undefined. If the format is exhausted while
-    arguments remain, the excess arguments are evaluated (as always) but are otherwise
-    ignored.
 

-
-
+
 
3   The format is composed of zero or more directives: one or more white-space wide
     characters, an ordinary wide character (neither % nor a white-space wide character), or a
     conversion specification. Each conversion specification is introduced by the wide
@@ -23717,60 +20427,47 @@ the specified values is outside the normal range, the characters stored are unsp
     -- A conversion specifier wide character that specifies the type of conversion to be
        applied.
 

-
-
+
 
4   The fwscanf function executes each directive of the format in turn. When all directives
     have been executed, or if a directive fails (as detailed below), the function returns.
     Failures are described as input failures (due to the occurrence of an encoding error or the
     unavailability of input characters), or matching failures (due to inappropriate input).
 

-
-
+
 
5   A directive composed of white-space wide character(s) is executed by reading input up to
     the first non-white-space wide character (which remains unread), or until no more wide
     characters can be read. The directive never fails.
 

-
-
+
 
6   A directive that is an ordinary wide character is executed by reading the next wide
     character of the stream. If that wide character differs from the directive, the directive
     fails and the differing and subsequent wide characters remain unread. Similarly, if end-
     of-file, an encoding error, or a read error prevents a wide character from being read, the
     directive fails.
 

-
-
+
 
7   A directive that is a conversion specification defines a set of matching input sequences, as
     described below for each specifier. A conversion specification is executed in the
     following steps:
 

-
-
+
 
8   Input white-space wide characters (as specified by the iswspace function) are skipped,
-    unless the specification includes a [, c, or n specifier.337)
+    unless the specification includes a [, c, or n specifier.[337]
 

-
 
 
Footnote 337) These white-space wide characters are not counted against a specified field width.
-

-
-
-
9   An input item is read from the stream, unless the specification includes an n specifier. An
-    input item is defined as the longest sequence of input wide characters which does not
-    exceed any specified field width and which is, or is a prefix of, a matching input
-
      sequence.338) The first wide character, if any, after the input item remains unread. If the
      length of the input item is zero, the execution of the directive fails; this condition is a
      matching failure unless end-of-file, an encoding error, or a read error prevented input
      from the stream, in which case it is an input failure.
-

-
-
-
Footnote 338) fwscanf pushes back at most one input wide character onto the input stream. Therefore, some
-          sequences that are acceptable to wcstod, wcstol, etc., are unacceptable to fwscanf.
 

 
-
+
+
9   An input item is read from the stream, unless the specification includes an n specifier. An
+    input item is defined as the longest sequence of input wide characters which does not
+    exceed any specified field width and which is, or is a prefix of, a matching input
+

+
 
10   Except in the case of a % specifier, the input item (or, in the case of a %n directive, the
      count of input wide characters) is converted to a type appropriate to the conversion
      specifier. If the input item is not a matching sequence, the execution of the directive fails:
@@ -23780,8 +20477,7 @@ the specified values is outside the normal range, the characters stored are unsp
      object does not have an appropriate type, or if the result of the conversion cannot be
      represented in the object, the behavior is undefined.
 

-
-
+
 
11   The length modifiers and their meanings are:
      hh           Specifies that a following d, i, o, u, x, X, or n conversion specifier applies
                   to an argument with type pointer to signed char or unsigned char.
@@ -23804,14 +20500,8 @@ the specified values is outside the normal range, the characters stored are unsp
      t            Specifies that a following d, i, o, u, x, X, or n conversion specifier applies
                   to an argument with type pointer to ptrdiff_t or the corresponding
                   unsigned integer type.
-
-     L            Specifies that a following a, A, e, E, f, F, g, or G conversion specifier
-                  applies to an argument with type pointer to long double.
-     If a length modifier appears with any conversion specifier other than as specified above,
-     the behavior is undefined.
 

-
-
+
 
12   The conversion specifiers and their meanings are:
      d           Matches an optionally signed decimal integer, whose format is the same as
                  expected for the subject sequence of the wcstol function with the value 10
@@ -23861,7 +20551,7 @@ the specified values is outside the normal range, the characters stored are unsp
              automatically.
     [        Matches a nonempty sequence of wide characters from a set of expected
              characters (the scanset ).
-             
+
              If no l length modifier is present, characters from the input field are
              converted as if by repeated calls to the wcrtomb function, with the
              conversion state described by an mbstate_t object initialized to zero
@@ -23869,7 +20559,7 @@ the specified values is outside the normal range, the characters stored are unsp
              shall be a pointer to the initial element of a character array large enough to
              accept the sequence and a terminating null character, which will be added
              automatically.
-             
+
              If an l length modifier is present, the corresponding argument shall be a
              pointer to the initial element of an array of wchar_t large enough to accept
              the sequence and the terminating null wide character, which will be added
@@ -23905,35 +20595,34 @@ the specified values is outside the normal range, the characters stored are unsp
      %              Matches a single % wide character; no conversion or assignment occurs. The
                     complete conversion specification shall be %%.
 

-
-
-
13   If a conversion specification is invalid, the behavior is undefined.339)
+
+
13   If a conversion specification is invalid, the behavior is undefined.[339]
 

-
 
-
Footnote 339) See ``future library directions'' (7.31.16).
+
Footnote 339) See ``future library directions'' (7.31.16).
+     with the input line:
+              25 54.32E-1 thompson
+     will assign to n the value 3, to i the value 25, to x the value 5.432, and to name the sequence
+     thompson\0.
 

 
-
+
 
14   The conversion specifiers A, E, F, G, and X are also valid and behave the same as,
      respectively, a, e, f, g, and x.
 

-
-
+
 
15   Trailing white space (including new-line wide characters) is left unread unless matched
      by a directive. The success of literal matches and suppressed assignments is not directly
      determinable other than via the %n directive.
      Returns
 

-
-
+
 
16   The fwscanf function returns the value of the macro EOF if an input failure occurs
      before the first conversion (if any) has completed. Otherwise, the function returns the
      number of input items assigned, which can be fewer than provided for, or even zero, in
      the event of an early matching failure.
 

-
-
+
 
17   EXAMPLE 1       The call:
               #include <stdio.h>
               #include <wchar.h>
@@ -23941,14 +20630,8 @@ the specified values is outside the normal range, the characters stored are unsp
               int n, i; float x; wchar_t name[50];
               n = fwscanf(stdin, L"%d%f%ls", &i, &x, name);
 
-     with the input line:
-              25 54.32E-1 thompson
-     will assign to n the value 3, to i the value 25, to x the value 5.432, and to name the sequence
-     thompson\0.
-
 

-
-
+
 
18   EXAMPLE 2        The call:
               #include <stdio.h>
               #include <wchar.h>
@@ -23960,72 +20643,62 @@ the specified values is outside the normal range, the characters stored are unsp
      will assign to i the value 56 and to x the value 789.0, will skip past 0123, and will assign to y the value
      56.0. The next wide character read from the input stream will be a.
 
-     Forward references: the wcstod, wcstof, and wcstold functions (7.29.4.1.1), the
-     wcstol, wcstoll, wcstoul, and wcstoull functions (7.29.4.1.2), the wcrtomb
-     function (7.29.6.3.3).
+     Forward references: the wcstod, wcstof, and wcstold functions (7.29.4.1.1), the
+     wcstol, wcstoll, wcstoul, and wcstoull functions (7.29.4.1.2), the wcrtomb
+     function (7.29.6.3.3).
 

-
-
+
 

 
7.29.2.3 [The swprintf function]

-

-
-
-
1             #include <wchar.h>
+
+
1 Synopsis
+             #include <wchar.h>
               int swprintf(wchar_t * restrict s,
                    size_t n,
                    const wchar_t * restrict format, ...);
      Description
 

-
-
+
 
2    The swprintf function is equivalent to fwprintf, except that the argument s
      specifies an array of wide characters into which the generated output is to be written,
      rather than written to a stream. No more than n wide characters are written, including a
      terminating null wide character, which is always added (unless n is zero).
      Returns
 

-
-
+
 
3    The swprintf function returns the number of wide characters written in the array, not
      counting the terminating null wide character, or a negative value if an encoding error
      occurred or if n or more wide characters were requested to be written.
 

-
-
+
 

 
7.29.2.4 [The swscanf function]

-

-
-
-
1           #include <wchar.h>
+
+
1 Synopsis
+           #include <wchar.h>
             int swscanf(const wchar_t * restrict s,
                  const wchar_t * restrict format, ...);
     Description
 

-
-
+
 
2   The swscanf function is equivalent to fwscanf, except that the argument s specifies a
     wide string from which the input is to be obtained, rather than from a stream. Reaching
     the end of the wide string is equivalent to encountering end-of-file for the fwscanf
     function.
     Returns
 

-
-
+
 
3   The swscanf function returns the value of the macro EOF if an input failure occurs
     before the first conversion (if any) has completed. Otherwise, the swscanf function
     returns the number of input items assigned, which can be fewer than provided for, or even
     zero, in the event of an early matching failure.
 

-
-
+
 

 
7.29.2.5 [The vfwprintf function]

-

-
-
-
1           #include <stdarg.h>
+
+
1 Synopsis
+           #include <stdarg.h>
             #include <stdio.h>
             #include <wchar.h>
             int vfwprintf(FILE * restrict stream,
@@ -24033,27 +20706,24 @@ the specified values is outside the normal range, the characters stored are unsp
                  va_list arg);
     Description
 

-
-
+
 
2   The vfwprintf function is equivalent to fwprintf, with the variable argument list
     replaced by arg, which shall have been initialized by the va_start macro (and
     possibly subsequent va_arg calls). The vfwprintf function does not invoke the
-    va_end macro.340)
+    va_end macro.[340]
     Returns
 

-
 
 
Footnote 340) As the functions vfwprintf, vswprintf, vfwscanf, vwprintf, vwscanf, and vswscanf
          invoke the va_arg macro, the value of arg after the return is indeterminate.
 

 
-
+
 
3   The vfwprintf function returns the number of wide characters transmitted, or a
     negative value if an output or encoding error occurred.
 
 

-
-
+
 
4   EXAMPLE       The following shows the use of the vfwprintf function in a general error-reporting
     routine.
            #include <stdarg.h>
@@ -24071,14 +20741,12 @@ the specified values is outside the normal range, the characters stored are unsp
            }
 
 

-
-
+
 

 
7.29.2.6 [The vfwscanf function]

-

-
-
-
1          #include <stdarg.h>
+
+
1 Synopsis
+          #include <stdarg.h>
            #include <stdio.h>
            #include <wchar.h>
            int vfwscanf(FILE * restrict stream,
@@ -24086,34 +20754,30 @@ the specified values is outside the normal range, the characters stored are unsp
                 va_list arg);
     Description
 

-
-
+
 
2   The vfwscanf function is equivalent to fwscanf, with the variable argument list
     replaced by arg, which shall have been initialized by the va_start macro (and
     possibly subsequent va_arg calls). The vfwscanf function does not invoke the
-    va_end macro.340)
+    va_end macro.[340]
     Returns
 

-
 
 
Footnote 340) As the functions vfwprintf, vswprintf, vfwscanf, vwprintf, vwscanf, and vswscanf
          invoke the va_arg macro, the value of arg after the return is indeterminate.
 

 
-
+
 
3   The vfwscanf function returns the value of the macro EOF if an input failure occurs
     before the first conversion (if any) has completed. Otherwise, the vfwscanf function
     returns the number of input items assigned, which can be fewer than provided for, or even
     zero, in the event of an early matching failure.
 

-
-
+
 

 
7.29.2.7 [The vswprintf function]

-

-
-
-
1           #include <stdarg.h>
+
+
1 Synopsis
+           #include <stdarg.h>
             #include <wchar.h>
             int vswprintf(wchar_t * restrict s,
                  size_t n,
@@ -24121,224 +20785,195 @@ the specified values is outside the normal range, the characters stored are unsp
                  va_list arg);
     Description
 

-
-
+
 
2   The vswprintf function is equivalent to swprintf, with the variable argument list
     replaced by arg, which shall have been initialized by the va_start macro (and
     possibly subsequent va_arg calls). The vswprintf function does not invoke the
-    va_end macro.340)
+    va_end macro.[340]
     Returns
 

-
 
 
Footnote 340) As the functions vfwprintf, vswprintf, vfwscanf, vwprintf, vwscanf, and vswscanf
          invoke the va_arg macro, the value of arg after the return is indeterminate.
 

 
-
+
 
3   The vswprintf function returns the number of wide characters written in the array, not
     counting the terminating null wide character, or a negative value if an encoding error
     occurred or if n or more wide characters were requested to be generated.
 

-
-
+
 

 
7.29.2.8 [The vswscanf function]

-

-
-
-
1           #include <stdarg.h>
+
+
1 Synopsis
+           #include <stdarg.h>
             #include <wchar.h>
             int vswscanf(const wchar_t * restrict s,
                  const wchar_t * restrict format,
                  va_list arg);
     Description
 

-
-
+
 
2   The vswscanf function is equivalent to swscanf, with the variable argument list
     replaced by arg, which shall have been initialized by the va_start macro (and
     possibly subsequent va_arg calls). The vswscanf function does not invoke the
-    va_end macro.340)
+    va_end macro.[340]
     Returns
 

-
 
 
Footnote 340) As the functions vfwprintf, vswprintf, vfwscanf, vwprintf, vwscanf, and vswscanf
          invoke the va_arg macro, the value of arg after the return is indeterminate.
 

 
-
+
 
3   The vswscanf function returns the value of the macro EOF if an input failure occurs
     before the first conversion (if any) has completed. Otherwise, the vswscanf function
     returns the number of input items assigned, which can be fewer than provided for, or even
     zero, in the event of an early matching failure.
 

-
-
+
 

 
7.29.2.9 [The vwprintf function]

-

-
-
-
1          #include <stdarg.h>
+
+
1 Synopsis
+          #include <stdarg.h>
            #include <wchar.h>
            int vwprintf(const wchar_t * restrict format,
                 va_list arg);
     Description
 

-
-
+
 
2   The vwprintf function is equivalent to wprintf, with the variable argument list
     replaced by arg, which shall have been initialized by the va_start macro (and
     possibly subsequent va_arg calls). The vwprintf function does not invoke the
-    va_end macro.340)
+    va_end macro.[340]
     Returns
 

-
 
 
Footnote 340) As the functions vfwprintf, vswprintf, vfwscanf, vwprintf, vwscanf, and vswscanf
          invoke the va_arg macro, the value of arg after the return is indeterminate.
 

 
-
+
 
3   The vwprintf function returns the number of wide characters transmitted, or a negative
     value if an output or encoding error occurred.
 

-
-
+
 

 
7.29.2.10 [The vwscanf function]

-

-
-
-
1          #include <stdarg.h>
+
+
1 Synopsis
+          #include <stdarg.h>
            #include <wchar.h>
            int vwscanf(const wchar_t * restrict format,
                 va_list arg);
     Description
 

-
-
+
 
2   The vwscanf function is equivalent to wscanf, with the variable argument list
     replaced by arg, which shall have been initialized by the va_start macro (and
     possibly subsequent va_arg calls). The vwscanf function does not invoke the
-    va_end macro.340)
+    va_end macro.[340]
     Returns
 

-
 
 
Footnote 340) As the functions vfwprintf, vswprintf, vfwscanf, vwprintf, vwscanf, and vswscanf
          invoke the va_arg macro, the value of arg after the return is indeterminate.
 

 
-
+
 
3   The vwscanf function returns the value of the macro EOF if an input failure occurs
     before the first conversion (if any) has completed. Otherwise, the vwscanf function
     returns the number of input items assigned, which can be fewer than provided for, or even
     zero, in the event of an early matching failure.
 

-
-
+
 

 
7.29.2.11 [The wprintf function]

-

-
-
-
1           #include <wchar.h>
+
+
1 Synopsis
+           #include <wchar.h>
             int wprintf(const wchar_t * restrict format, ...);
     Description
 

-
-
+
 
2   The wprintf function is equivalent to fwprintf with the argument stdout
     interposed before the arguments to wprintf.
     Returns
 

-
-
+
 
3   The wprintf function returns the number of wide characters transmitted, or a negative
     value if an output or encoding error occurred.
 

-
-
+
 

 
7.29.2.12 [The wscanf function]

-

-
-
-
1           #include <wchar.h>
+
+
1 Synopsis
+           #include <wchar.h>
             int wscanf(const wchar_t * restrict format, ...);
     Description
 

-
-
+
 
2   The wscanf function is equivalent to fwscanf with the argument stdin interposed
     before the arguments to wscanf.
     Returns
 

-
-
+
 
3   The wscanf function returns the value of the macro EOF if an input failure occurs
     before the first conversion (if any) has completed. Otherwise, the wscanf function
     returns the number of input items assigned, which can be fewer than provided for, or even
     zero, in the event of an early matching failure.
 

-
-
+
 

 
7.29.3 [Wide character input/output functions]

-
 Wide character input/output functions
-

-
-
+
 

 
7.29.3.1 [The fgetwc function]

-

-
-
-
1           #include <stdio.h>
+
+
1 Synopsis
+           #include <stdio.h>
             #include <wchar.h>
             wint_t fgetwc(FILE *stream);
     Description
 

-
-
+
 
2   If the end-of-file indicator for the input stream pointed to by stream is not set and a
     next wide character is present, the fgetwc function obtains that wide character as a
     wchar_t converted to a wint_t and advances the associated file position indicator for
     the stream (if defined).
     Returns
 

-
-
+
 
3   If the end-of-file indicator for the stream is set, or if the stream is at end-of-file, the end-
     of-file indicator for the stream is set and the fgetwc function returns WEOF. Otherwise,
     the fgetwc function returns the next wide character from the input stream pointed to by
     stream. If a read error occurs, the error indicator for the stream is set and the fgetwc
     function returns WEOF. If an encoding error occurs (including too few bytes), the value of
-    the macro EILSEQ is stored in errno and the fgetwc function returns WEOF.341)
+    the macro EILSEQ is stored in errno and the fgetwc function returns WEOF.[341]
 

-
 
 
Footnote 341) An end-of-file and a read error can be distinguished by use of the feof and ferror functions.
          Also, errno will be set to EILSEQ by input/output functions only if an encoding error occurs.
+    support positioning requests, or if the stream was opened with append mode, the
+    character is appended to the output stream.
+    Returns
 

 
-
+
 

 
7.29.3.2 [The fgetws function]

-

-
-
-
1           #include <stdio.h>
+
+
1 Synopsis
+           #include <stdio.h>
             #include <wchar.h>
             wchar_t *fgetws(wchar_t * restrict s,
                  int n, FILE * restrict stream);
     Description
 

-
-
+
 
2   The fgetws function reads at most one less than the number of wide characters
     specified by n from the stream pointed to by stream into the array pointed to by s. No
     additional wide characters are read after a new-line wide character (which is retained) or
@@ -24346,199 +20981,163 @@ the specified values is outside the normal range, the characters stored are unsp
     character read into the array.
     Returns
 

-
-
+
 
3   The fgetws function returns s if successful. If end-of-file is encountered and no
     characters have been read into the array, the contents of the array remain unchanged and a
     null pointer is returned. If a read or encoding error occurs during the operation, the array
     contents are indeterminate and a null pointer is returned.
 

-
-
+
 

 
7.29.3.3 [The fputwc function]

-

-
-
-
1           #include <stdio.h>
+
+
1 Synopsis
+           #include <stdio.h>
             #include <wchar.h>
             wint_t fputwc(wchar_t c, FILE *stream);
     Description
 

-
-
+
 
2   The fputwc function writes the wide character specified by c to the output stream
     pointed to by stream, at the position indicated by the associated file position indicator
     for the stream (if defined), and advances the indicator appropriately. If the file cannot
-
-    support positioning requests, or if the stream was opened with append mode, the
-    character is appended to the output stream.
-    Returns
 

-
-
+
 
3   The fputwc function returns the wide character written. If a write error occurs, the
     error indicator for the stream is set and fputwc returns WEOF. If an encoding error
     occurs, the value of the macro EILSEQ is stored in errno and fputwc returns WEOF.
 

-
-
+
 

 
7.29.3.4 [The fputws function]

-

-
-
-
1           #include <stdio.h>
+
+
1 Synopsis
+           #include <stdio.h>
             #include <wchar.h>
             int fputws(const wchar_t * restrict s,
                  FILE * restrict stream);
     Description
 

-
-
+
 
2   The fputws function writes the wide string pointed to by s to the stream pointed to by
     stream. The terminating null wide character is not written.
     Returns
 

-
-
+
 
3   The fputws function returns EOF if a write or encoding error occurs; otherwise, it
     returns a nonnegative value.
 

-
-
+
 

 
7.29.3.5 [The fwide function]

-

-
-
-
1           #include <stdio.h>
+
+
1 Synopsis
+           #include <stdio.h>
             #include <wchar.h>
             int fwide(FILE *stream, int mode);
     Description
 

-
-
+
 
2   The fwide function determines the orientation of the stream pointed to by stream. If
     mode is greater than zero, the function first attempts to make the stream wide oriented. If
-    mode is less than zero, the function first attempts to make the stream byte oriented.342)
+    mode is less than zero, the function first attempts to make the stream byte oriented.[342]
     Otherwise, mode is zero and the function does not alter the orientation of the stream.
     Returns
 

-
 
 
Footnote 342) If the orientation of the stream has already been determined, fwide does not change it.
 

 
-
+
 
3   The fwide function returns a value greater than zero if, after the call, the stream has
     wide orientation, a value less than zero if the stream has byte orientation, or zero if the
     stream has no orientation.
 
 

-
-
+
 

 
7.29.3.6 [The getwc function]

-

-
-
-
1          #include <stdio.h>
+
+
1 Synopsis
+          #include <stdio.h>
            #include <wchar.h>
            wint_t getwc(FILE *stream);
     Description
 

-
-
+
 
2   The getwc function is equivalent to fgetwc, except that if it is implemented as a
     macro, it may evaluate stream more than once, so the argument should never be an
     expression with side effects.
     Returns
 

-
-
+
 
3   The getwc function returns the next wide character from the input stream pointed to by
     stream, or WEOF.
 

-
-
+
 

 
7.29.3.7 [The getwchar function]

-

-
-
-
1          #include <wchar.h>
+
+
1 Synopsis
+          #include <wchar.h>
            wint_t getwchar(void);
     Description
 

-
-
+
 
2   The getwchar function is equivalent to getwc with the argument stdin.
     Returns
 

-
-
+
 
3   The getwchar function returns the next wide character from the input stream pointed to
     by stdin, or WEOF.
 

-
-
+
 

 
7.29.3.8 [The putwc function]

-

-
-
-
1          #include <stdio.h>
+
+
1 Synopsis
+          #include <stdio.h>
            #include <wchar.h>
            wint_t putwc(wchar_t c, FILE *stream);
     Description
 

-
-
+
 
2   The putwc function is equivalent to fputwc, except that if it is implemented as a
     macro, it may evaluate stream more than once, so that argument should never be an
     expression with side effects.
     Returns
 

-
-
+
 
3   The putwc function returns the wide character written, or WEOF.
 
 

-
-
+
 

 
7.29.3.9 [The putwchar function]

-

-
-
-
1           #include <wchar.h>
+
+
1 Synopsis
+           #include <wchar.h>
             wint_t putwchar(wchar_t c);
     Description
 

-
-
+
 
2   The putwchar function is equivalent to putwc with the second argument stdout.
     Returns
 

-
-
+
 
3   The putwchar function returns the character written, or WEOF.
 

-
-
+
 

 
7.29.3.10 [The ungetwc function]

-

-
-
-
1           #include <stdio.h>
+
+
1 Synopsis
+           #include <stdio.h>
             #include <wchar.h>
             wint_t ungetwc(wint_t c, FILE *stream);
     Description
 

-
-
+
 
2   The ungetwc function pushes the wide character specified by c back onto the input
     stream pointed to by stream. Pushed-back wide characters will be returned by
     subsequent reads on that stream in the reverse order of their pushing. A successful
@@ -24546,21 +21145,18 @@ the specified values is outside the normal range, the characters stored are unsp
     (fseek, fsetpos, or rewind) discards any pushed-back wide characters for the
     stream. The external storage corresponding to the stream is unchanged.
 

-
-
+
 
3   One wide character of pushback is guaranteed, even if the call to the ungetwc function
     follows just after a call to a formatted wide character input function fwscanf,
     vfwscanf, vwscanf, or wscanf. If the ungetwc function is called too many times
     on the same stream without an intervening read or file positioning operation on that
     stream, the operation may fail.
 

-
-
+
 
4   If the value of c equals that of the macro WEOF, the operation fails and the input stream is
     unchanged.
 

-
-
+
 
5   A successful call to the ungetwc function clears the end-of-file indicator for the stream.
     The value of the file position indicator for the stream after reading or discarding all
     pushed-back wide characters is the same as it was before the wide characters were pushed
@@ -24569,47 +21165,37 @@ the specified values is outside the normal range, the characters stored are unsp
     read or discarded.
     Returns
 

-
-
+
 
6   The ungetwc function returns the wide character pushed back, or WEOF if the operation
     fails.
 

-
-
+
 

 
7.29.4 [General wide string utilities]

-

-
-
+
 
1   The header <wchar.h> declares a number of functions useful for wide string
     manipulation. Various methods are used for determining the lengths of the arrays, but in
     all cases a wchar_t * argument points to the initial (lowest addressed) element of the
     array. If an array is accessed beyond the end of an object, the behavior is undefined.
 

-
-
+
 
2   Where an argument declared as size_t n determines the length of the array for a
     function, n can have the value zero on a call to that function. Unless explicitly stated
     otherwise in the description of a particular function in this subclause, pointer arguments
-    on such a call shall still have valid values, as described in 7.1.4. On such a call, a
+    on such a call shall still have valid values, as described in 7.1.4. On such a call, a
     function that locates a wide character finds no occurrence, a function that compares two
     wide character sequences returns zero, and a function that copies wide characters copies
     zero wide characters.
 

-
-
+
 

 
7.29.4.1 [Wide string numeric conversion functions]

-
 Wide string numeric conversion functions
-

-
-
+
 

 
7.29.4.1.1 [The wcstod, wcstof, and wcstold functions]

-

-
-
-
1          #include <wchar.h>
+
+
1 Synopsis
+          #include <wchar.h>
            double wcstod(const wchar_t * restrict nptr,
                 wchar_t ** restrict endptr);
            float wcstof(const wchar_t * restrict nptr,
@@ -24618,8 +21204,7 @@ the specified values is outside the normal range, the characters stored are unsp
                 wchar_t ** restrict endptr);
     Description
 

-
-
+
 
2   The wcstod, wcstof, and wcstold functions convert the initial portion of the wide
     string pointed to by nptr to double, float, and long double representation,
     respectively. First, they decompose the input string into three parts: an initial, possibly
@@ -24629,16 +21214,15 @@ the specified values is outside the normal range, the characters stored are unsp
     including the terminating null wide character of the input wide string. Then, they attempt
     to convert the subject sequence to a floating-point number, and return the result.
 

-
-
+
 
3   The expected form of the subject sequence is an optional plus or minus sign, then one of
     the following:
     -- a nonempty sequence of decimal digits optionally containing a decimal-point wide
        character, then an optional exponent part as defined for the corresponding single-byte
-       characters in 6.4.4.2;
+       characters in 6.4.4.2;
     -- a 0x or 0X, then a nonempty sequence of hexadecimal digits optionally containing a
        decimal-point wide character, then an optional binary exponent part as defined in
-       6.4.4.2;
+       6.4.4.2;
     -- INF or INFINITY, or any other wide string equivalent except for case
     -- NAN or NAN(n-wchar-sequenceopt), or any other wide string equivalent except for
        case in the NAN part, where:
@@ -24652,30 +21236,25 @@ the specified values is outside the normal range, the characters stored are unsp
     The subject sequence contains no wide characters if the input wide string is not of the
     expected form.
 

-
-
+
 
4   If the subject sequence has the expected form for a floating-point number, the sequence of
     wide characters starting with the first digit or the decimal-point wide character
     (whichever occurs first) is interpreted as a floating constant according to the rules of
-     6.4.4.2, except that the decimal-point wide character is used in place of a period, and that
+     6.4.4.2, except that the decimal-point wide character is used in place of a period, and that
     if neither an exponent part nor a decimal-point wide character appears in a decimal
     floating point number, or if a binary exponent part does not appear in a hexadecimal
     floating point number, an exponent part of the appropriate type with value zero is
     assumed to follow the last digit in the string. If the subject sequence begins with a minus
-    sign, the sequence is interpreted as negated.343) A wide character sequence INF or
+    sign, the sequence is interpreted as negated.[343] A wide character sequence INF or
     INFINITY is interpreted as an infinity, if representable in the return type, else like a
     floating constant that is too large for the range of the return type. A wide character
     sequence NAN or NAN(n-wchar-sequenceopt) is interpreted as a quiet NaN, if supported
     in the return type, else like a subject sequence part that does not have the expected form;
-    the meaning of the n-wchar sequence is implementation-defined.344) A pointer to the
-
-     final wide string is stored in the object pointed to by endptr, provided that endptr is
-     not a null pointer.
+    the meaning of the n-wchar sequence is implementation-defined.[344] A pointer to the
 

-
 
 
Footnote 343) It is unspecified whether a minus-signed sequence is converted to a negative number directly or by
-         negating the value resulting from converting the corresponding unsigned sequence (see F.5); the two
+         negating the value resulting from converting the corresponding unsigned sequence (see F.5); the two
          methods may yield different results if rounding is toward positive or negative infinity. In either case,
          the functions honor the sign of zero if floating-point arithmetic supports signed zeros.
 

@@ -24683,34 +21262,32 @@ the specified values is outside the normal range, the characters stored are unsp
 
 
Footnote 344) An implementation may use the n-wchar sequence to determine extra information to be represented in
          the NaN's significand.
+     final wide string is stored in the object pointed to by endptr, provided that endptr is
+     not a null pointer.
 

 
-
+
 
5    If the subject sequence has the hexadecimal form and FLT_RADIX is a power of 2, the
      value resulting from the conversion is correctly rounded.
 

-
-
+
 
6    In other than the "C" locale, additional locale-specific subject sequence forms may be
      accepted.
 

-
-
+
 
7    If the subject sequence is empty or does not have the expected form, no conversion is
      performed; the value of nptr is stored in the object pointed to by endptr, provided
      that endptr is not a null pointer.
      Recommended practice
 

-
-
+
 
8    If the subject sequence has the hexadecimal form, FLT_RADIX is not a power of 2, and
      the result is not exactly representable, the result should be one of the two numbers in the
      appropriate internal format that are adjacent to the hexadecimal floating source value,
      with the extra stipulation that the error should have a correct sign for the current rounding
      direction.
 

-
-
+
 
9    If the subject sequence has the decimal form and at most DECIMAL_DIG (defined in
      <float.h>) significant digits, the result should be correctly rounded. If the subject
      sequence D has the decimal form and more than DECIMAL_DIG significant digits,
@@ -24719,33 +21296,30 @@ the specified values is outside the normal range, the characters stored are unsp
      The result should be one of the (equal or adjacent) values that would be obtained by
      correctly rounding L and U according to the current rounding direction, with the extra
      stipulation that the error with respect to D should have a correct sign for the current
-     rounding direction.345)
+     rounding direction.[345]
      Returns
 

-
 
 
Footnote 345) DECIMAL_DIG, defined in <float.h>, should be sufficiently large that L and U will usually round
           to the same internal floating value, but if not will round to adjacent values.
 

 
-
+
 
10   The functions return the converted value, if any. If no conversion could be performed,
-     zero is returned. If the correct value overflows and default rounding is in effect (7.12.1),
+     zero is returned. If the correct value overflows and default rounding is in effect (7.12.1),
      plus or minus HUGE_VAL, HUGE_VALF, or HUGE_VALL is returned (according to the
      return type and sign of the value), and the value of the macro ERANGE is stored in
-     errno. If the result underflows (7.12.1), the functions return a value whose magnitude is
+     errno. If the result underflows (7.12.1), the functions return a value whose magnitude is
      no greater than the smallest normalized positive number in the return type; whether
      errno acquires the value ERANGE is implementation-defined.
 
 

-
-
+
 

 
7.29.4.1.2 [The wcstol, wcstoll, wcstoul, and wcstoull functions]

-

-
-
-
1           #include <wchar.h>
+
+
1 Synopsis
+           #include <wchar.h>
             long int wcstol(
                  const wchar_t * restrict nptr,
                  wchar_t ** restrict endptr,
@@ -24764,8 +21338,7 @@ the specified values is outside the normal range, the characters stored are unsp
                  int base);
     Description
 

-
-
+
 
2   The wcstol, wcstoll, wcstoul, and wcstoull functions convert the initial
     portion of the wide string pointed to by nptr to long int, long long int,
     unsigned long int, and unsigned long long int representation,
@@ -24776,10 +21349,9 @@ the specified values is outside the normal range, the characters stored are unsp
     characters, including the terminating null wide character of the input wide string. Then,
     they attempt to convert the subject sequence to an integer, and return the result.
 

-
-
+
 
3   If the value of base is zero, the expected form of the subject sequence is that of an
-    integer constant as described for the corresponding single-byte characters in 6.4.4.1,
+    integer constant as described for the corresponding single-byte characters in 6.4.4.1,
     optionally preceded by a plus or minus sign, but not including an integer suffix. If the
     value of base is between 2 and 36 (inclusive), the expected form of the subject sequence
     is a sequence of letters and digits representing an integer with the radix specified by
@@ -24790,146 +21362,122 @@ the specified values is outside the normal range, the characters stored are unsp
     of letters and digits, following the sign if present.
 
 

-
-
+
 
4   The subject sequence is defined as the longest initial subsequence of the input wide
     string, starting with the first non-white-space wide character, that is of the expected form.
     The subject sequence contains no wide characters if the input wide string is empty or
     consists entirely of white space, or if the first non-white-space wide character is other
     than a sign or a permissible letter or digit.
 

-
-
+
 
5   If the subject sequence has the expected form and the value of base is zero, the sequence
     of wide characters starting with the first digit is interpreted as an integer constant
-    according to the rules of 6.4.4.1. If the subject sequence has the expected form and the
+    according to the rules of 6.4.4.1. If the subject sequence has the expected form and the
     value of base is between 2 and 36, it is used as the base for conversion, ascribing to each
     letter its value as given above. If the subject sequence begins with a minus sign, the value
     resulting from the conversion is negated (in the return type). A pointer to the final wide
     string is stored in the object pointed to by endptr, provided that endptr is not a null
     pointer.
 

-
-
+
 
6   In other than the "C" locale, additional locale-specific subject sequence forms may be
     accepted.
 

-
-
+
 
7   If the subject sequence is empty or does not have the expected form, no conversion is
     performed; the value of nptr is stored in the object pointed to by endptr, provided
     that endptr is not a null pointer.
     Returns
 

-
-
+
 
8   The wcstol, wcstoll, wcstoul, and wcstoull functions return the converted
     value, if any. If no conversion could be performed, zero is returned. If the correct value
     is outside the range of representable values, LONG_MIN, LONG_MAX, LLONG_MIN,
     LLONG_MAX, ULONG_MAX, or ULLONG_MAX is returned (according to the return type
     sign of the value, if any), and the value of the macro ERANGE is stored in errno.
 

-
-
+
 

 
7.29.4.2 [Wide string copying functions]

-
 Wide string copying functions
-

-
-
+
 

 
7.29.4.2.1 [The wcscpy function]

-

-
-
-
1          #include <wchar.h>
+
+
1 Synopsis
+          #include <wchar.h>
            wchar_t *wcscpy(wchar_t * restrict s1,
                 const wchar_t * restrict s2);
     Description
 

-
-
+
 
2   The wcscpy function copies the wide string pointed to by s2 (including the terminating
     null wide character) into the array pointed to by s1.
     Returns
 

-
-
+
 
3   The wcscpy function returns the value of s1.
 

-
-
+
 

 
7.29.4.2.2 [The wcsncpy function]

-

-
-
-
1            #include <wchar.h>
+
+
1 Synopsis
+            #include <wchar.h>
              wchar_t *wcsncpy(wchar_t * restrict s1,
                   const wchar_t * restrict s2,
                   size_t n);
     Description
 

-
-
+
 
2   The wcsncpy function copies not more than n wide characters (those that follow a null
     wide character are not copied) from the array pointed to by s2 to the array pointed to by
-    s1.346)
+    s1.[346]
 

-
 
 
Footnote 346) Thus, if there is no null wide character in the first n wide characters of the array pointed to by s2, the
          result will not be null-terminated.
 

 
-
+
 
3   If the array pointed to by s2 is a wide string that is shorter than n wide characters, null
     wide characters are appended to the copy in the array pointed to by s1, until n wide
     characters in all have been written.
     Returns
 

-
-
+
 
4   The wcsncpy function returns the value of s1.
 

-
-
+
 

 
7.29.4.2.3 [The wmemcpy function]

-

-
-
-
1            #include <wchar.h>
+
+
1 Synopsis
+            #include <wchar.h>
              wchar_t *wmemcpy(wchar_t * restrict s1,
                   const wchar_t * restrict s2,
                   size_t n);
     Description
 

-
-
+
 
2   The wmemcpy function copies n wide characters from the object pointed to by s2 to the
     object pointed to by s1.
     Returns
 

-
-
+
 
3   The wmemcpy function returns the value of s1.
 
 

-
-
+
 

 
7.29.4.2.4 [The wmemmove function]

-

-
-
-
1          #include <wchar.h>
+
+
1 Synopsis
+          #include <wchar.h>
            wchar_t *wmemmove(wchar_t *s1, const wchar_t *s2,
                 size_t n);
     Description
 

-
-
+
 
2   The wmemmove function copies n wide characters from the object pointed to by s2 to
     the object pointed to by s1. Copying takes place as if the n wide characters from the
     object pointed to by s2 are first copied into a temporary array of n wide characters that
@@ -24937,171 +21485,140 @@ the specified values is outside the normal range, the characters stored are unsp
     the temporary array are copied into the object pointed to by s1.
     Returns
 

-
-
+
 
3   The wmemmove function returns the value of s1.
 

-
-
+
 

 
7.29.4.3 [Wide string concatenation functions]

-
 Wide string concatenation functions
-

-
-
+
 

 
7.29.4.3.1 [The wcscat function]

-

-
-
-
1          #include <wchar.h>
+
+
1 Synopsis
+          #include <wchar.h>
            wchar_t *wcscat(wchar_t * restrict s1,
                 const wchar_t * restrict s2);
     Description
 

-
-
+
 
2   The wcscat function appends a copy of the wide string pointed to by s2 (including the
     terminating null wide character) to the end of the wide string pointed to by s1. The initial
     wide character of s2 overwrites the null wide character at the end of s1.
     Returns
 

-
-
+
 
3   The wcscat function returns the value of s1.
 

-
-
+
 

 
7.29.4.3.2 [The wcsncat function]

-

-
-
-
1          #include <wchar.h>
+
+
1 Synopsis
+          #include <wchar.h>
            wchar_t *wcsncat(wchar_t * restrict s1,
                 const wchar_t * restrict s2,
                 size_t n);
     Description
 

-
-
+
 
2   The wcsncat function appends not more than n wide characters (a null wide character
     and those that follow it are not appended) from the array pointed to by s2 to the end of
 
     the wide string pointed to by s1. The initial wide character of s2 overwrites the null
     wide character at the end of s1. A terminating null wide character is always appended to
-    the result.347)
+    the result.[347]
     Returns
 

-
 
 
Footnote 347) Thus, the maximum number of wide characters that can end up in the array pointed to by s1 is
          wcslen(s1)+n+1.
+    wide string pointed to by s2 when both are interpreted as appropriate to the current
+    locale.
 

 
-
+
 
3   The wcsncat function returns the value of s1.
 

-
-
+
 

 
7.29.4.4 [Wide string comparison functions]

-

-
-
+
 
1   Unless explicitly stated otherwise, the functions described in this subclause order two
     wide characters the same way as two integers of the underlying integer type designated
     by wchar_t.
 

-
-
+
 

 
7.29.4.4.1 [The wcscmp function]

-

-
-
-
1           #include <wchar.h>
+
+
1 Synopsis
+           #include <wchar.h>
             int wcscmp(const wchar_t *s1, const wchar_t *s2);
     Description
 

-
-
+
 
2   The wcscmp function compares the wide string pointed to by s1 to the wide string
     pointed to by s2.
     Returns
 

-
-
+
 
3   The wcscmp function returns an integer greater than, equal to, or less than zero,
     accordingly as the wide string pointed to by s1 is greater than, equal to, or less than the
     wide string pointed to by s2.
 

-
-
+
 

 
7.29.4.4.2 [The wcscoll function]

-

-
-
-
1           #include <wchar.h>
+
+
1 Synopsis
+           #include <wchar.h>
             int wcscoll(const wchar_t *s1, const wchar_t *s2);
     Description
 

-
-
+
 
2   The wcscoll function compares the wide string pointed to by s1 to the wide string
     pointed to by s2, both interpreted as appropriate to the LC_COLLATE category of the
     current locale.
     Returns
 

-
-
+
 
3   The wcscoll function returns an integer greater than, equal to, or less than zero,
     accordingly as the wide string pointed to by s1 is greater than, equal to, or less than the
-
-    wide string pointed to by s2 when both are interpreted as appropriate to the current
-    locale.
 

-
-
+
 

 
7.29.4.4.3 [The wcsncmp function]

-

-
-
-
1          #include <wchar.h>
+
+
1 Synopsis
+          #include <wchar.h>
            int wcsncmp(const wchar_t *s1, const wchar_t *s2,
                 size_t n);
     Description
 

-
-
+
 
2   The wcsncmp function compares not more than n wide characters (those that follow a
     null wide character are not compared) from the array pointed to by s1 to the array
     pointed to by s2.
     Returns
 

-
-
+
 
3   The wcsncmp function returns an integer greater than, equal to, or less than zero,
     accordingly as the possibly null-terminated array pointed to by s1 is greater than, equal
     to, or less than the possibly null-terminated array pointed to by s2.
 

-
-
+
 

 
7.29.4.4.4 [The wcsxfrm function]

-

-
-
-
1          #include <wchar.h>
+
+
1 Synopsis
+          #include <wchar.h>
            size_t wcsxfrm(wchar_t * restrict s1,
                 const wchar_t * restrict s2,
                 size_t n);
     Description
 

-
-
+
 
2   The wcsxfrm function transforms the wide string pointed to by s2 and places the
     resulting wide string into the array pointed to by s1. The transformation is such that if
     the wcscmp function is applied to two transformed wide strings, it returns a value greater
@@ -25111,244 +21628,202 @@ the specified values is outside the normal range, the characters stored are unsp
     n is zero, s1 is permitted to be a null pointer.
     Returns
 

-
-
+
 
3   The wcsxfrm function returns the length of the transformed wide string (not including
     the terminating null wide character). If the value returned is n or greater, the contents of
     the array pointed to by s1 are indeterminate.
 

-
-
+
 
4   EXAMPLE The value of the following expression is the length of the array needed to hold the
     transformation of the wide string pointed to by s:
             1 + wcsxfrm(NULL, s, 0)
 
 

-
-
+
 

 
7.29.4.4.5 [The wmemcmp function]

-

-
-
-
1           #include <wchar.h>
+
+
1 Synopsis
+           #include <wchar.h>
             int wmemcmp(const wchar_t *s1, const wchar_t *s2,
                  size_t n);
     Description
 

-
-
+
 
2   The wmemcmp function compares the first n wide characters of the object pointed to by
     s1 to the first n wide characters of the object pointed to by s2.
     Returns
 

-
-
+
 
3   The wmemcmp function returns an integer greater than, equal to, or less than zero,
     accordingly as the object pointed to by s1 is greater than, equal to, or less than the object
     pointed to by s2.
 

-
-
+
 

 
7.29.4.5 [Wide string search functions]

-
 Wide string search functions
-

-
-
+
 

 
7.29.4.5.1 [The wcschr function]

-

-
-
-
1           #include <wchar.h>
+
+
1 Synopsis
+           #include <wchar.h>
             wchar_t *wcschr(const wchar_t *s, wchar_t c);
     Description
 

-
-
+
 
2   The wcschr function locates the first occurrence of c in the wide string pointed to by s.
     The terminating null wide character is considered to be part of the wide string.
     Returns
 

-
-
+
 
3   The wcschr function returns a pointer to the located wide character, or a null pointer if
     the wide character does not occur in the wide string.
 

-
-
+
 

 
7.29.4.5.2 [The wcscspn function]

-

-
-
-
1           #include <wchar.h>
+
+
1 Synopsis
+           #include <wchar.h>
             size_t wcscspn(const wchar_t *s1, const wchar_t *s2);
     Description
 

-
-
+
 
2   The wcscspn function computes the length of the maximum initial segment of the wide
     string pointed to by s1 which consists entirely of wide characters not from the wide
     string pointed to by s2.
 
     Returns
 

-
-
+
 
3   The wcscspn function returns the length of the segment.
 

-
-
+
 

 
7.29.4.5.3 [The wcspbrk function]

-

-
-
-
1          #include <wchar.h>
+
+
1 Synopsis
+          #include <wchar.h>
            wchar_t *wcspbrk(const wchar_t *s1, const wchar_t *s2);
     Description
 

-
-
+
 
2   The wcspbrk function locates the first occurrence in the wide string pointed to by s1 of
     any wide character from the wide string pointed to by s2.
     Returns
 

-
-
+
 
3   The wcspbrk function returns a pointer to the wide character in s1, or a null pointer if
     no wide character from s2 occurs in s1.
 

-
-
+
 

 
7.29.4.5.4 [The wcsrchr function]

-

-
-
-
1          #include <wchar.h>
+
+
1 Synopsis
+          #include <wchar.h>
            wchar_t *wcsrchr(const wchar_t *s, wchar_t c);
     Description
 

-
-
+
 
2   The wcsrchr function locates the last occurrence of c in the wide string pointed to by
     s. The terminating null wide character is considered to be part of the wide string.
     Returns
 

-
-
+
 
3   The wcsrchr function returns a pointer to the wide character, or a null pointer if c does
     not occur in the wide string.
 

-
-
+
 

 
7.29.4.5.5 [The wcsspn function]

-

-
-
-
1          #include <wchar.h>
+
+
1 Synopsis
+          #include <wchar.h>
            size_t wcsspn(const wchar_t *s1, const wchar_t *s2);
     Description
 

-
-
+
 
2   The wcsspn function computes the length of the maximum initial segment of the wide
     string pointed to by s1 which consists entirely of wide characters from the wide string
     pointed to by s2.
     Returns
 

-
-
+
 
3   The wcsspn function returns the length of the segment.
 

-
-
+
 

 
7.29.4.5.6 [The wcsstr function]

-

-
-
-
1           #include <wchar.h>
+
+
1 Synopsis
+           #include <wchar.h>
             wchar_t *wcsstr(const wchar_t *s1, const wchar_t *s2);
     Description
 

-
-
+
 
2   The wcsstr function locates the first occurrence in the wide string pointed to by s1 of
     the sequence of wide characters (excluding the terminating null wide character) in the
     wide string pointed to by s2.
     Returns
 

-
-
+
 
3   The wcsstr function returns a pointer to the located wide string, or a null pointer if the
     wide string is not found. If s2 points to a wide string with zero length, the function
     returns s1.
 

-
-
+
 

 
7.29.4.5.7 [The wcstok function]

-

-
-
-
1           #include <wchar.h>
+
+
1 Synopsis
+           #include <wchar.h>
             wchar_t *wcstok(wchar_t * restrict s1,
                  const wchar_t * restrict s2,
                  wchar_t ** restrict ptr);
     Description
 

-
-
+
 
2   A sequence of calls to the wcstok function breaks the wide string pointed to by s1 into
     a sequence of tokens, each of which is delimited by a wide character from the wide string
     pointed to by s2. The third argument points to a caller-provided wchar_t pointer into
     which the wcstok function stores information necessary for it to continue scanning the
     same wide string.
 

-
-
+
 
3   The first call in a sequence has a non-null first argument and stores an initial value in the
     object pointed to by ptr. Subsequent calls in the sequence have a null first argument and
     the object pointed to by ptr is required to have the value stored by the previous call in
     the sequence, which is then updated. The separator wide string pointed to by s2 may be
     different from call to call.
 

-
-
+
 
4   The first call in the sequence searches the wide string pointed to by s1 for the first wide
     character that is not contained in the current separator wide string pointed to by s2. If no
     such wide character is found, then there are no tokens in the wide string pointed to by s1
     and the wcstok function returns a null pointer. If such a wide character is found, it is
     the start of the first token.
 

-
-
+
 
5   The wcstok function then searches from there for a wide character that is contained in
     the current separator wide string. If no such wide character is found, the current token
     extends to the end of the wide string pointed to by s1, and subsequent searches in the
     same wide string for a token return a null pointer. If such a wide character is found, it is
     overwritten by a null wide character, which terminates the current token.
 

-
-
+
 
6   In all cases, the wcstok function stores sufficient information in the pointer pointed to
     by ptr so that subsequent calls, with a null pointer for s1 and the unmodified pointer
     value for ptr, shall start searching just past the element overwritten by a null wide
     character (if any).
     Returns
 

-
-
+
 
7   The wcstok function returns a pointer to the first wide character of a token, or a null
     pointer if there is no token.
 

-
-
+
 
8   EXAMPLE
            #include <wchar.h>
            static wchar_t str1[] = L"?a???b,,,#c";
@@ -25361,91 +21836,71 @@ the specified values is outside the normal range, the characters stored are unsp
            t   =   wcstok(NULL,   L"?", &ptr1);          //   t   is a null pointer
 
 

-
-
+
 

 
7.29.4.5.8 [The wmemchr function]

-

-
-
-
1          #include <wchar.h>
+
+
1 Synopsis
+          #include <wchar.h>
            wchar_t *wmemchr(const wchar_t *s, wchar_t c,
                 size_t n);
     Description
 

-
-
+
 
2   The wmemchr function locates the first occurrence of c in the initial n wide characters of
     the object pointed to by s.
     Returns
 

-
-
+
 
3   The wmemchr function returns a pointer to the located wide character, or a null pointer if
     the wide character does not occur in the object.
 

-
-
+
 

 
7.29.4.6 [Miscellaneous functions]

-
 Miscellaneous functions
-

-
-
+
 

 
7.29.4.6.1 [The wcslen function]

-

-
-
-
1           #include <wchar.h>
+
+
1 Synopsis
+           #include <wchar.h>
             size_t wcslen(const wchar_t *s);
     Description
 

-
-
+
 
2   The wcslen function computes the length of the wide string pointed to by s.
     Returns
 

-
-
+
 
3   The wcslen function returns the number of wide characters that precede the terminating
     null wide character.
 

-
-
+
 

 
7.29.4.6.2 [The wmemset function]

-

-
-
-
1           #include <wchar.h>
+
+
1 Synopsis
+           #include <wchar.h>
             wchar_t *wmemset(wchar_t *s, wchar_t c, size_t n);
     Description
 

-
-
+
 
2   The wmemset function copies the value of c into each of the first n wide characters of
     the object pointed to by s.
     Returns
 

-
-
+
 
3   The wmemset function returns the value of s.
 

-
-
+
 

 
7.29.5 [Wide character time conversion functions]

-
 Wide character time conversion functions
-

-
-
+
 

 
7.29.5.1 [The wcsftime function]

-

-
-
-
1           #include <time.h>
+
+
1 Synopsis
+           #include <time.h>
             #include <wchar.h>
             size_t wcsftime(wchar_t * restrict s,
                  size_t maxsize,
@@ -25453,8 +21908,7 @@ the specified values is outside the normal range, the characters stored are unsp
                  const struct tm * restrict timeptr);
     Description
 

-
-
+
 
2   The wcsftime function is equivalent to the strftime function, except that:
     -- The argument s points to the initial element of an array of wide characters into which
        the generated output is to be placed.
@@ -25464,34 +21918,28 @@ the specified values is outside the normal range, the characters stored are unsp
     -- The return value indicates the number of wide characters.
     Returns
 

-
-
+
 
3   If the total number of resulting wide characters including the terminating null wide
     character is not more than maxsize, the wcsftime function returns the number of
     wide characters placed into the array pointed to by s not including the terminating null
     wide character. Otherwise, zero is returned and the contents of the array are
     indeterminate.
 

-
-
+
 

 
7.29.6 [Extended multibyte/wide character conversion utilities]

-

-
-
+
 
1   The header <wchar.h> declares an extended set of functions useful for conversion
     between multibyte characters and wide characters.
 

-
-
-
2   Most of the following functions -- those that are listed as ``restartable'', 7.29.6.3 and
-     7.29.6.4 -- take as a last argument a pointer to an object of type mbstate_t that is used
+
+
2   Most of the following functions -- those that are listed as ``restartable'', 7.29.6.3 and
+     7.29.6.4 -- take as a last argument a pointer to an object of type mbstate_t that is used
     to describe the current conversion state from a particular multibyte character sequence to
     a wide character sequence (or the reverse) under the rules of a particular setting for the
     LC_CTYPE category of the current locale.
 

-
-
+
 
3   The initial conversion state corresponds, for a conversion in either direction, to the
     beginning of a new multibyte character in the initial shift state. A zero-valued
     mbstate_t object is (at least) one way to describe an initial conversion state. A zero-
@@ -25500,112 +21948,90 @@ the specified values is outside the normal range, the characters stored are unsp
     been altered by any of the functions described in this subclause, and is then used with a
     different multibyte character sequence, or in the other conversion direction, or with a
     different LC_CTYPE category setting than on earlier function calls, the behavior is
-    undefined.348)
+    undefined.[348]
 

-
 
 
Footnote 348) Thus, a particular mbstate_t object can be used, for example, with both the mbrtowc and
          mbsrtowcs functions as long as they are used to step sequentially through the same multibyte
          character string.
 

 
-
+
 
4   On entry, each function takes the described conversion state (either internal or pointed to
     by an argument) as current. The conversion state described by the referenced object is
     altered as needed to track the shift state, and the position within a multibyte character, for
     the associated multibyte character sequence.
 
 

-
-
+
 

 
7.29.6.1 [Single-byte/wide character conversion functions]

-
 Single-byte/wide character conversion functions
-

-
-
+
 

 
7.29.6.1.1 [The btowc function]

-

-
-
-
1           #include <wchar.h>
+
+
1 Synopsis
+           #include <wchar.h>
             wint_t btowc(int c);
     Description
 

-
-
+
 
2   The btowc function determines whether c constitutes a valid single-byte character in the
     initial shift state.
     Returns
 

-
-
+
 
3   The btowc function returns WEOF if c has the value EOF or if (unsigned char)c
     does not constitute a valid single-byte character in the initial shift state. Otherwise, it
     returns the wide character representation of that character.
 

-
-
+
 

 
7.29.6.1.2 [The wctob function]

-

-
-
-
1           #include <wchar.h>
+
+
1 Synopsis
+           #include <wchar.h>
             int wctob(wint_t c);
     Description
 

-
-
+
 
2   The wctob function determines whether c corresponds to a member of the extended
     character set whose multibyte character representation is a single byte when in the initial
     shift state.
     Returns
 

-
-
+
 
3   The wctob function returns EOF if c does not correspond to a multibyte character with
     length one in the initial shift state. Otherwise, it returns the single-byte representation of
     that character as an unsigned char converted to an int.
 

-
-
+
 

 
7.29.6.2 [Conversion state functions]

-
 Conversion state functions
-

-
-
+
 

 
7.29.6.2.1 [The mbsinit function]

-

-
-
-
1           #include <wchar.h>
+
+
1 Synopsis
+           #include <wchar.h>
             int mbsinit(const mbstate_t *ps);
     Description
 

-
-
+
 
2   If ps is not a null pointer, the mbsinit function determines whether the referenced
     mbstate_t object describes an initial conversion state.
 
     Returns
 

-
-
+
 
3   The mbsinit function returns nonzero if ps is a null pointer or if the referenced object
     describes an initial conversion state; otherwise, it returns zero.
 

-
-
+
 

 
7.29.6.3 [Restartable multibyte/wide character conversion functions]

-

-
-
-
1   These functions differ from the corresponding multibyte character functions of 7.22.7
+
+
1   These functions differ from the corresponding multibyte character functions of 7.22.7
     (mblen, mbtowc, and wctomb) in that they have an extra parameter, ps, of type
     pointer to mbstate_t that points to an object that can completely describe the current
     conversion state of the associated multibyte character sequence. If ps is a null pointer,
@@ -25614,60 +22040,51 @@ the specified values is outside the normal range, the characters stored are unsp
     races with other calls to the same function in this case. The implementation behaves as if
     no library function calls these functions with a null pointer for ps.
 

-
-
+
 
2   Also unlike their corresponding functions, the return value does not represent whether the
     encoding is state-dependent.
 

-
-
+
 

 
7.29.6.3.1 [The mbrlen function]

-

-
-
-
1          #include <wchar.h>
+
+
1 Synopsis
+          #include <wchar.h>
            size_t mbrlen(const char * restrict s,
                 size_t n,
                 mbstate_t * restrict ps);
     Description
 

-
-
+
 
2   The mbrlen function is equivalent to the call:
            mbrtowc(NULL, s, n, ps != NULL ? ps : &internal)
     where internal is the mbstate_t object for the mbrlen function, except that the
     expression designated by ps is evaluated only once.
     Returns
 

-
-
+
 
3   The mbrlen function returns a value between zero and n, inclusive, (size_t)(-2),
     or (size_t)(-1).
-    Forward references: the mbrtowc function (7.29.6.3.2).
+    Forward references: the mbrtowc function (7.29.6.3.2).
 

-
-
+
 

 
7.29.6.3.2 [The mbrtowc function]

-

-
-
-
1           #include <wchar.h>
+
+
1 Synopsis
+           #include <wchar.h>
             size_t mbrtowc(wchar_t * restrict pwc,
                  const char * restrict s,
                  size_t n,
                  mbstate_t * restrict ps);
     Description
 

-
-
+
 
2   If s is a null pointer, the mbrtowc function is equivalent to the call:
                     mbrtowc(NULL, "", 1, ps)
     In this case, the values of the parameters pwc and n are ignored.
 

-
-
+
 
3   If s is not a null pointer, the mbrtowc function inspects at most n bytes beginning with
     the byte pointed to by s to determine the number of bytes needed to complete the next
     multibyte character (including any shift sequences). If the function determines that the
@@ -25677,8 +22094,7 @@ the specified values is outside the normal range, the characters stored are unsp
     character, the resulting state described is the initial conversion state.
     Returns
 

-
-
+
 
4   The mbrtowc function returns the first of the following that applies (given the current
     conversion state):
     0                     if the next n or fewer bytes complete the multibyte character that
@@ -25688,39 +22104,35 @@ the specified values is outside the normal range, the characters stored are unsp
                        of bytes that complete the multibyte character.
     (size_t)(-2) if the next n bytes contribute to an incomplete (but potentially valid)
                  multibyte character, and all n bytes have been processed (no value is
-                 stored).349)
+                 stored).[349]
     (size_t)(-1) if an encoding error occurs, in which case the next n or fewer bytes
                  do not contribute to a complete and valid multibyte character (no
                  value is stored); the value of the macro EILSEQ is stored in errno,
                  and the conversion state is unspecified.
 
 

-
 
 
Footnote 349) When n has at least the value of the MB_CUR_MAX macro, this case can only occur if s points at a
          sequence of redundant shift sequences (for implementations with state-dependent encodings).
 

 
-
+
 

 
7.29.6.3.3 [The wcrtomb function]

-

-
-
-
1           #include <wchar.h>
+
+
1 Synopsis
+           #include <wchar.h>
             size_t wcrtomb(char * restrict s,
                  wchar_t wc,
                  mbstate_t * restrict ps);
     Description
 

-
-
+
 
2   If s is a null pointer, the wcrtomb function is equivalent to the call
                     wcrtomb(buf, L'\0', ps)
     where buf is an internal buffer.
 

-
-
+
 
3   If s is not a null pointer, the wcrtomb function determines the number of bytes needed
     to represent the multibyte character that corresponds to the wide character given by wc
     (including any shift sequences), and stores the multibyte character representation in the
@@ -25729,21 +22141,17 @@ the specified values is outside the normal range, the characters stored are unsp
     to restore the initial shift state; the resulting state described is the initial conversion state.
     Returns
 

-
-
+
 
4   The wcrtomb function returns the number of bytes stored in the array object (including
     any shift sequences). When wc is not a valid wide character, an encoding error occurs:
     the function stores the value of the macro EILSEQ in errno and returns
     (size_t)(-1); the conversion state is unspecified.
 

-
-
+
 

 
7.29.6.4 [Restartable multibyte/wide string conversion functions]

-

-
-
-
1   These functions differ from the corresponding multibyte string functions of 7.22.8
+
+
1   These functions differ from the corresponding multibyte string functions of 7.22.8
     (mbstowcs and wcstombs) in that they have an extra parameter, ps, of type pointer to
     mbstate_t that points to an object that can completely describe the current conversion
     state of the associated multibyte character sequence. If ps is a null pointer, each function
@@ -25752,29 +22160,25 @@ the specified values is outside the normal range, the characters stored are unsp
     calls to the same function in this case. The implementation behaves as if no library
     function calls these functions with a null pointer for ps.
 

-
-
+
 
2   Also unlike their corresponding functions, the conversion source parameter, src, has a
     pointer-to-pointer type. When the function is storing the results of conversions (that is,
     when dst is not a null pointer), the pointer object pointed to by this parameter is updated
     to reflect the amount of the source processed by that invocation.
 

-
-
+
 

 
7.29.6.4.1 [The mbsrtowcs function]

-

-
-
-
1            #include <wchar.h>
+
+
1 Synopsis
+            #include <wchar.h>
              size_t mbsrtowcs(wchar_t * restrict dst,
                   const char ** restrict src,
                   size_t len,
                   mbstate_t * restrict ps);
     Description
 

-
-
+
 
2   The mbsrtowcs function converts a sequence of multibyte characters that begins in the
     conversion state described by the object pointed to by ps, from the array indirectly
     pointed to by src into a sequence of corresponding wide characters. If dst is not a null
@@ -25782,15 +22186,14 @@ the specified values is outside the normal range, the characters stored are unsp
     continues up to and including a terminating null character, which is also stored.
     Conversion stops earlier in two cases: when a sequence of bytes is encountered that does
     not form a valid multibyte character, or (if dst is not a null pointer) when len wide
-    characters have been stored into the array pointed to by dst.350) Each conversion takes
+    characters have been stored into the array pointed to by dst.[350] Each conversion takes
     place as if by a call to the mbrtowc function.
 

-
 
 
Footnote 350) Thus, the value of len is ignored if dst is a null pointer.
 

 
-
+
 
3   If dst is not a null pointer, the pointer object pointed to by src is assigned either a null
     pointer (if conversion stopped due to reaching a terminating null character) or the address
     just past the last multibyte character converted (if any). If conversion stopped due to
@@ -25798,8 +22201,7 @@ the specified values is outside the normal range, the characters stored are unsp
     described is the initial conversion state.
     Returns
 

-
-
+
 
4   If the input conversion encounters a sequence of bytes that do not form a valid multibyte
     character, an encoding error occurs: the mbsrtowcs function stores the value of the
     macro EILSEQ in errno and returns (size_t)(-1); the conversion state is
@@ -25807,22 +22209,19 @@ the specified values is outside the normal range, the characters stored are unsp
     converted, not including the terminating null character (if any).
 
 

-
-
+
 

 
7.29.6.4.2 [The wcsrtombs function]

-

-
-
-
1           #include <wchar.h>
+
+
1 Synopsis
+           #include <wchar.h>
             size_t wcsrtombs(char * restrict dst,
                  const wchar_t ** restrict src,
                  size_t len,
                  mbstate_t * restrict ps);
     Description
 

-
-
+
 
2   The wcsrtombs function converts a sequence of wide characters from the array
     indirectly pointed to by src into a sequence of corresponding multibyte characters that
     begins in the conversion state described by the object pointed to by ps. If dst is not a
@@ -25832,15 +22231,14 @@ the specified values is outside the normal range, the characters stored are unsp
     not correspond to a valid multibyte character, or (if dst is not a null pointer) when the
     next multibyte character would exceed the limit of len total bytes to be stored into the
     array pointed to by dst. Each conversion takes place as if by a call to the wcrtomb
-    function.351)
+    function.[351]
 

-
 
 
Footnote 351) If conversion stops because a terminating null wide character has been reached, the bytes stored
          include those necessary to reach the initial shift state immediately before the null byte.
 

 
-
+
 
3   If dst is not a null pointer, the pointer object pointed to by src is assigned either a null
     pointer (if conversion stopped due to reaching a terminating null wide character) or the
     address just past the last wide character converted (if any). If conversion stopped due to
@@ -25848,8 +22246,7 @@ the specified values is outside the normal range, the characters stored are unsp
     conversion state.
     Returns
 

-
-
+
 
4   If conversion stops because a wide character is reached that does not correspond to a
     valid multibyte character, an encoding error occurs: the wcsrtombs function stores the
     value of the macro EILSEQ in errno and returns (size_t)(-1); the conversion
@@ -25857,31 +22254,24 @@ the specified values is outside the normal range, the characters stored are unsp
     character sequence, not including the terminating null character (if any).
 
 

-
-
+
 

-
7.30 [Wide character classification and mapping utilities ]

-
 Wide character classification and mapping utilities 
-

-
-
+
7.30 [Wide character classification and mapping utilities <wctype.h>]

+
 

 
7.30.1 [Introduction]

-

-
-
+
 
1   The header <wctype.h> defines one macro, and declares three data types and many
-    functions.352)
+    functions.[352]
 

-
 
-
Footnote 352) See ``future library directions'' (7.31.17).
+
Footnote 352) See ``future library directions'' (7.31.17).
 

 
-
+
 
2   The types declared are
               wint_t
-    described in 7.29.1;
+    described in 7.29.1;
               wctrans_t
     which is a scalar type that can hold values which represent locale-specific character
     mappings; and
@@ -25889,324 +22279,261 @@ the specified values is outside the normal range, the characters stored are unsp
     which is a scalar type that can hold values which represent locale-specific character
     classifications.
 

-
-
-
3   The macro defined is WEOF (described in 7.29.1).
+
+
3   The macro defined is WEOF (described in 7.29.1).
 

-
-
+
 
4   The functions declared are grouped as follows:
     -- Functions that provide wide character classification;
     -- Extensible functions that provide wide character classification;
     -- Functions that provide wide character case mapping;
     -- Extensible functions that provide wide character mapping.
 

-
-
+
 
5   For all functions described in this subclause that accept an argument of type wint_t, the
     value shall be representable as a wchar_t or shall equal the value of the macro WEOF. If
     this argument has any other value, the behavior is undefined.
 

-
-
+
 
6   The behavior of these functions is affected by the LC_CTYPE category of the current
     locale.
 
 

-
-
+
 

 
7.30.2 [Wide character classification utilities]

-

-
-
+
 
1   The header <wctype.h> declares several functions useful for classifying wide
     characters.
 

-
-
+
 
2   The term printing wide character refers to a member of a locale-specific set of wide
     characters, each of which occupies at least one printing position on a display device. The
     term control wide character refers to a member of a locale-specific set of wide characters
     that are not printing wide characters.
 

-
-
+
 

 
7.30.2.1 [Wide character classification functions]

-

-
-
+
 
1   The functions in this subclause return nonzero (true) if and only if the value of the
     argument wc conforms to that in the description of the function.
 

-
-
+
 
2   Each of the following functions returns true for each wide character that corresponds (as
     if by a call to the wctob function) to a single-byte character for which the corresponding
-    character classification function from 7.4.1 returns true, except that the iswgraph and
+    character classification function from 7.4.1 returns true, except that the iswgraph and
     iswpunct functions may differ with respect to wide characters other than L' ' that are
-    both printing and white-space wide characters.353)
-    Forward references: the wctob function (7.29.6.1.2).
+    both printing and white-space wide characters.[353]
+    Forward references: the wctob function (7.29.6.1.2).
 

-
 
 
Footnote 353) For example, if the expression isalpha(wctob(wc)) evaluates to true, then the call
          iswalpha(wc) also returns true. But, if the expression isgraph(wctob(wc)) evaluates to true
          (which cannot occur for wc == L' ' of course), then either iswgraph(wc) or iswprint(wc)
          && iswspace(wc) is true, but not both.
+    wide characters for which none of iswcntrl, iswdigit, iswpunct, or iswspace
+    is true.354)
 

 
-
+
 

 
7.30.2.1.1 [The iswalnum function]

-

-
-
-
1           #include <wctype.h>
+
+
1 Synopsis
+           #include <wctype.h>
             int iswalnum(wint_t wc);
     Description
 

-
-
+
 
2   The iswalnum function tests for any wide character for which iswalpha or
     iswdigit is true.
 

-
-
+
 

 
7.30.2.1.2 [The iswalpha function]

-

-
-
-
1           #include <wctype.h>
+
+
1 Synopsis
+           #include <wctype.h>
             int iswalpha(wint_t wc);
     Description
 

-
-
+
 
2   The iswalpha function tests for any wide character for which iswupper or
     iswlower is true, or any wide character that is one of a locale-specific set of alphabetic
-
-    wide characters for which none of iswcntrl, iswdigit, iswpunct, or iswspace
-    is true.354)
 

-
-
-
Footnote 354) The functions iswlower and iswupper test true or false separately for each of these additional
-         wide characters; all four combinations are possible.
-

-
-
+
 

 
7.30.2.1.3 [The iswblank function]

-

-
-
-
1           #include <wctype.h>
+
+
1 Synopsis
+           #include <wctype.h>
             int iswblank(wint_t wc);
     Description
 

-
-
+
 
2   The iswblank function tests for any wide character that is a standard blank wide
     character or is one of a locale-specific set of wide characters for which iswspace is true
     and that is used to separate words within a line of text. The standard blank wide
     characters are the following: space (L' '), and horizontal tab (L'\t'). In the "C"
     locale, iswblank returns true only for the standard blank characters.
 

-
-
+
 

 
7.30.2.1.4 [The iswcntrl function]

-

-
-
-
1           #include <wctype.h>
+
+
1 Synopsis
+           #include <wctype.h>
             int iswcntrl(wint_t wc);
     Description
 

-
-
+
 
2   The iswcntrl function tests for any control wide character.
 

-
-
+
 

 
7.30.2.1.5 [The iswdigit function]

-

-
-
-
1           #include <wctype.h>
+
+
1 Synopsis
+           #include <wctype.h>
             int iswdigit(wint_t wc);
     Description
 

-
-
+
 
2   The iswdigit function tests for any wide character that corresponds to a decimal-digit
-    character (as defined in 5.2.1).
+    character (as defined in 5.2.1).
 

-
-
+
 

 
7.30.2.1.6 [The iswgraph function]

-

-
-
-
1           #include <wctype.h>
+
+
1 Synopsis
+           #include <wctype.h>
             int iswgraph(wint_t wc);
-
-    Description
 

-
-
+
 
2   The iswgraph function tests for any wide character for which iswprint is true and
-    iswspace is false.355)
+    iswspace is false.[355]
 

-
 
 
Footnote 355) Note that the behavior of the iswgraph and iswpunct functions may differ from their
-         corresponding functions in 7.4.1 with respect to printing, white-space, single-byte execution
+         corresponding functions in 7.4.1 with respect to printing, white-space, single-byte execution
          characters other than ' '.
+    Description
 

 
-
+
 

 
7.30.2.1.7 [The iswlower function]

-

-
-
-
1           #include <wctype.h>
+
+
1 Synopsis
+           #include <wctype.h>
             int iswlower(wint_t wc);
     Description
 

-
-
+
 
2   The iswlower function tests for any wide character that corresponds to a lowercase
     letter or is one of a locale-specific set of wide characters for which none of iswcntrl,
     iswdigit, iswpunct, or iswspace is true.
 

-
-
+
 

 
7.30.2.1.8 [The iswprint function]

-

-
-
-
1           #include <wctype.h>
+
+
1 Synopsis
+           #include <wctype.h>
             int iswprint(wint_t wc);
     Description
 

-
-
+
 
2   The iswprint function tests for any printing wide character.
 

-
-
+
 

 
7.30.2.1.9 [The iswpunct function]

-

-
-
-
1           #include <wctype.h>
+
+
1 Synopsis
+           #include <wctype.h>
             int iswpunct(wint_t wc);
     Description
 

-
-
+
 
2   The iswpunct function tests for any printing wide character that is one of a locale-
     specific set of punctuation wide characters for which neither iswspace nor iswalnum
-    is true.355)
+    is true.[355]
 

-
 
 
Footnote 355) Note that the behavior of the iswgraph and iswpunct functions may differ from their
-         corresponding functions in 7.4.1 with respect to printing, white-space, single-byte execution
+         corresponding functions in 7.4.1 with respect to printing, white-space, single-byte execution
          characters other than ' '.
+    Description
 

 
-
+
 

 
7.30.2.1.10 [The iswspace function]

-

-
-
-
1           #include <wctype.h>
+
+
1 Synopsis
+           #include <wctype.h>
             int iswspace(wint_t wc);
-
-    Description
 

-
-
+
 
2   The iswspace function tests for any wide character that corresponds to a locale-specific
     set of white-space wide characters for which none of iswalnum, iswgraph, or
     iswpunct is true.
 

-
-
+
 

 
7.30.2.1.11 [The iswupper function]

-

-
-
-
1           #include <wctype.h>
+
+
1 Synopsis
+           #include <wctype.h>
             int iswupper(wint_t wc);
     Description
 

-
-
+
 
2   The iswupper function tests for any wide character that corresponds to an uppercase
     letter or is one of a locale-specific set of wide characters for which none of iswcntrl,
     iswdigit, iswpunct, or iswspace is true.
 

-
-
+
 

 
7.30.2.1.12 [The iswxdigit function]

-

-
-
-
1           #include <wctype.h>
+
+
1 Synopsis
+           #include <wctype.h>
             int iswxdigit(wint_t wc);
     Description
 

-
-
+
 
2   The iswxdigit function tests for any wide character that corresponds to a
-    hexadecimal-digit character (as defined in 6.4.4.1).
+    hexadecimal-digit character (as defined in 6.4.4.1).
 

-
-
+
 

 
7.30.2.2 [Extensible wide character classification functions]

-

-
-
+
 
1   The functions wctype and iswctype provide extensible wide character classification
     as well as testing equivalent to that performed by the functions described in the previous
-    subclause (7.30.2.1).
+    subclause (7.30.2.1).
 

-
-
+
 

 
7.30.2.2.1 [The iswctype function]

-

-
-
-
1           #include <wctype.h>
+
+
1 Synopsis
+           #include <wctype.h>
             int iswctype(wint_t wc, wctype_t desc);
     Description
 

-
-
+
 
2   The iswctype function determines whether the wide character wc has the property
     described by desc. The current setting of the LC_CTYPE category shall be the same as
     during the call to wctype that returned the value desc.
 

-
-
+
 
3   Each of the following expressions has a truth-value equivalent to the call to the wide
-    character classification function (7.30.2.1) in the comment that follows the expression:
+    character classification function (7.30.2.1) in the comment that follows the expression:
            iswctype(wc,       wctype("alnum"))              //   iswalnum(wc)
            iswctype(wc,       wctype("alpha"))              //   iswalpha(wc)
            iswctype(wc,       wctype("blank"))              //   iswblank(wc)
@@ -26221,190 +22548,151 @@ the specified values is outside the normal range, the characters stored are unsp
            iswctype(wc,       wctype("xdigit"))             //   iswxdigit(wc)
     Returns
 

-
-
+
 
4   The iswctype function returns nonzero (true) if and only if the value of the wide
     character wc has the property described by desc. If desc is zero, the iswctype
     function returns zero (false).
-    Forward references: the wctype function (7.30.2.2.2).
+    Forward references: the wctype function (7.30.2.2.2).
 

-
-
+
 

 
7.30.2.2.2 [The wctype function]

-

-
-
-
1          #include <wctype.h>
+
+
1 Synopsis
+          #include <wctype.h>
            wctype_t wctype(const char *property);
     Description
 

-
-
+
 
2   The wctype function constructs a value with type wctype_t that describes a class of
     wide characters identified by the string argument property.
 

-
-
+
 
3   The strings listed in the description of the iswctype function shall be valid in all
     locales as property arguments to the wctype function.
     Returns
 

-
-
+
 
4   If property identifies a valid class of wide characters according to the LC_CTYPE
     category of the current locale, the wctype function returns a nonzero value that is valid
     as the second argument to the iswctype function; otherwise, it returns zero.
 

-
-
+
 

 
7.30.3 [Wide character case mapping utilities]

-

-
-
+
 
1   The header <wctype.h> declares several functions useful for mapping wide characters.
 

-
-
+
 

 
7.30.3.1 [Wide character case mapping functions]

-
 Wide character case mapping functions
-

-
-
+
 

 
7.30.3.1.1 [The towlower function]

-

-
-
-
1           #include <wctype.h>
+
+
1 Synopsis
+           #include <wctype.h>
             wint_t towlower(wint_t wc);
     Description
 

-
-
+
 
2   The towlower function converts an uppercase letter to a corresponding lowercase letter.
     Returns
 

-
-
+
 
3   If the argument is a wide character for which iswupper is true and there are one or
     more corresponding wide characters, as specified by the current locale, for which
     iswlower is true, the towlower function returns one of the corresponding wide
     characters (always the same one for any given locale); otherwise, the argument is
     returned unchanged.
 

-
-
+
 

 
7.30.3.1.2 [The towupper function]

-

-
-
-
1           #include <wctype.h>
+
+
1 Synopsis
+           #include <wctype.h>
             wint_t towupper(wint_t wc);
     Description
 

-
-
+
 
2   The towupper function converts a lowercase letter to a corresponding uppercase letter.
     Returns
 

-
-
+
 
3   If the argument is a wide character for which iswlower is true and there are one or
     more corresponding wide characters, as specified by the current locale, for which
     iswupper is true, the towupper function returns one of the corresponding wide
     characters (always the same one for any given locale); otherwise, the argument is
     returned unchanged.
 

-
-
+
 

 
7.30.3.2 [Extensible wide character case mapping functions]

-

-
-
+
 
1   The functions wctrans and towctrans provide extensible wide character mapping as
     well as case mapping equivalent to that performed by the functions described in the
-    previous subclause (7.30.3.1).
+    previous subclause (7.30.3.1).
 

-
-
+
 

 
7.30.3.2.1 [The towctrans function]

-

-
-
-
1          #include <wctype.h>
+
+
1 Synopsis
+          #include <wctype.h>
            wint_t towctrans(wint_t wc, wctrans_t desc);
     Description
 

-
-
+
 
2   The towctrans function maps the wide character wc using the mapping described by
     desc. The current setting of the LC_CTYPE category shall be the same as during the call
     to wctrans that returned the value desc.
 

-
-
+
 
3   Each of the following expressions behaves the same as the call to the wide character case
-    mapping function (7.30.3.1) in the comment that follows the expression:
+    mapping function (7.30.3.1) in the comment that follows the expression:
            towctrans(wc, wctrans("tolower"))                       // towlower(wc)
            towctrans(wc, wctrans("toupper"))                       // towupper(wc)
     Returns
 

-
-
+
 
4   The towctrans function returns the mapped value of wc using the mapping described
     by desc. If desc is zero, the towctrans function returns the value of wc.
 

-
-
+
 

 
7.30.3.2.2 [The wctrans function]

-

-
-
-
1          #include <wctype.h>
+
+
1 Synopsis
+          #include <wctype.h>
            wctrans_t wctrans(const char *property);
     Description
 

-
-
+
 
2   The wctrans function constructs a value with type wctrans_t that describes a
     mapping between wide characters identified by the string argument property.
 

-
-
+
 
3   The strings listed in the description of the towctrans function shall be valid in all
     locales as property arguments to the wctrans function.
     Returns
 

-
-
+
 
4   If property identifies a valid mapping of wide characters according to the LC_CTYPE
     category of the current locale, the wctrans function returns a nonzero value that is valid
     as the second argument to the towctrans function; otherwise, it returns zero.
 

-
-
+
 

 
7.31 [Future library directions]

-

-
-
+
 
1   The following names are grouped under individual headers for convenience. All external
     names described below are reserved no matter what headers are included by the program.
 

-
-
+
 

-
7.31.1 [Complex arithmetic ]

-

-
-
+
7.31.1 [Complex arithmetic <complex.h>]

+
 
1   The function names
          cerf                cexpm1              clog2
          cerfc               clog10              clgamma
@@ -26412,73 +22700,52 @@ the specified values is outside the normal range, the characters stored are unsp
     and the same names suffixed with f or l may be added to the declarations in the
     <complex.h> header.
 

-
-
+
 

-
7.31.2 [Character handling ]

-

-
-
+
7.31.2 [Character handling <ctype.h>]

+
 
1   Function names that begin with either is or to, and a lowercase letter may be added to
     the declarations in the <ctype.h> header.
 

-
-
+
 

-
7.31.3 [Errors ]

-

-
-
+
7.31.3 [Errors <errno.h>]

+
 
1   Macros that begin with E and a digit or E and an uppercase letter may be added to the
     macros defined in the <errno.h> header.
 

-
-
+
 

-
7.31.4 [Floating-point environment ]

-

-
-
+
7.31.4 [Floating-point environment <fenv.h>]

+
 
1   Macros that begin with FE_ and an uppercase letter may be added to the macros defined
     in the <fenv.h> header.
 

-
-
+
 

-
7.31.5 [Format conversion of integer types ]

-

-
-
+
7.31.5 [Format conversion of integer types <inttypes.h>]

+
 
1   Macros that begin with either PRI or SCN, and either a lowercase letter or X may be
     added to the macros defined in the <inttypes.h> header.
 

-
-
+
 

-
7.31.6 [Localization ]

-

-
-
+
7.31.6 [Localization <locale.h>]

+
 
1   Macros that begin with LC_ and an uppercase letter may be added to the macros defined
     in the <locale.h> header.
 

-
-
+
 

-
7.31.7 [Signal handling ]

-

-
-
+
7.31.7 [Signal handling <signal.h>]

+
 
1   Macros that begin with either SIG and an uppercase letter or SIG_ and an uppercase
     letter may be added to the macros defined in the <signal.h> header.
 

-
-
+
 

-
7.31.8 [Atomics ]

-

-
-
+
7.31.8 [Atomics <stdatomic.h>]

+
 
1   Macros that begin with ATOMIC_ and an uppercase letter may be added to the macros
     defined in the <stdatomic.h> header. Typedef names that begin with either
     atomic_ or memory_, and a lowercase letter may be added to the declarations in the
@@ -26488,137 +22755,102 @@ the specified values is outside the normal range, the characters stored are unsp
     <stdatomic.h> header. Function names that begin with atomic_ and a lowercase
     letter may be added to the declarations in the <stdatomic.h> header.
 

-
-
+
 

-
7.31.9 [Boolean type and values ]

-

-
-
+
7.31.9 [Boolean type and values <stdbool.h>]

+
 
1   The ability to undefine and perhaps then redefine the macros bool, true, and false is
     an obsolescent feature.
 

-
-
+
 

-
7.31.10 [Integer types ]

-

-
-
+
7.31.10 [Integer types <stdint.h>]

+
 
1   Typedef names beginning with int or uint and ending with _t may be added to the
     types defined in the <stdint.h> header. Macro names beginning with INT or UINT
     and ending with _MAX, _MIN, or _C may be added to the macros defined in the
     <stdint.h> header.
 

-
-
+
 

-
7.31.11 [Input/output ]

-

-
-
+
7.31.11 [Input/output <stdio.h>]

+
 
1   Lowercase letters may be added to the conversion specifiers and length modifiers in
     fprintf and fscanf. Other characters may be used in extensions.
 

-
-
+
 
2   The use of ungetc on a binary stream where the file position indicator is zero prior to
     the call is an obsolescent feature.
 

-
-
+
 

-
7.31.12 [General utilities ]

-

-
-
+
7.31.12 [General utilities <stdlib.h>]

+
 
1   Function names that begin with str and a lowercase letter may be added to the
     declarations in the <stdlib.h> header.
 

-
-
+
 

-
7.31.13 [String handling ]

-

-
-
+
7.31.13 [String handling <string.h>]

+
 
1   Function names that begin with str, mem, or wcs and a lowercase letter may be added
     to the declarations in the <string.h> header.
 

-
-
+
 

-
7.31.14 [Date and time ]

-
 Date and time 
-    Macros beginning with TIME_ and an uppercase letter may be added to the macros in the
-     header.
+
7.31.14 [Date and time <time.h>]

+
Macros beginning with TIME_ and an uppercase letter may be added to the macros in the
+    <time.h> header.
 

-
-
+
 

-
7.31.15 [Threads ]

-

-
-
+
7.31.15 [Threads <threads.h>]

+
 
1   Function names, type names, and enumeration constants that begin with either cnd_,
     mtx_, thrd_, or tss_, and a lowercase letter may be added to the declarations in the
     <threads.h> header.
 

-
-
+
 

-
7.31.16 [Extended multibyte and wide character utilities ]

-

-
-
+
7.31.16 [Extended multibyte and wide character utilities <wchar.h>]

+
 
1   Function names that begin with wcs and a lowercase letter may be added to the
     declarations in the <wchar.h> header.
 

-
-
+
 
2   Lowercase letters may be added to the conversion specifiers and length modifiers in
     fwprintf and fwscanf. Other characters may be used in extensions.
 

-
-
+
 

 
7.31.17 [Wide character classification and mapping utilities]

-

-
-
-
1   Function names that begin with is or to and a lowercase letter may be added to the
+
+
1 <wctype.h>
+   Function names that begin with is or to and a lowercase letter may be added to the
     declarations in the <wctype.h> header.
                                                  Annex A
                                                (informative)
 

-
-
+
 

 
A. [Language syntax summary]

-

-
-
-
1   NOTE   The notation is described in 6.1.
+
+
1   NOTE   The notation is described in 6.1.
 
 

-
-
+
 

 
A.1 [Lexical grammar]

-
 Lexical grammar
-

-
-
+
 

 
A.1.1 [Lexical elements]

-
 Lexical elements
-    (6.4) token:
+
(6.4) token:
                    keyword
                    identifier
                    constant
                    string-literal
                    punctuator
-    (6.4) preprocessing-token:
+    (6.4) preprocessing-token:
                   header-name
                   identifier
                   pp-number
@@ -26627,12 +22859,10 @@ the specified values is outside the normal range, the characters stored are unsp
                   punctuator
                   each non-white-space character that cannot be one of the above
 

-
-
+
 

 
A.1.2 [Keywords]

-
 Keywords
-(6.4.1) keyword: one of
+
(6.4.1) keyword: one of
               auto                      if                       unsigned
               break                     inline                   void
               case                      int                      volatile
@@ -26649,209 +22879,195 @@ the specified values is outside the normal range, the characters stored are unsp
               for                       typedef                  _Thread_local
               goto                      union
 

-
-
+
 

 
A.1.3 [Identifiers]

-
 Identifiers
-(6.4.2.1) identifier:
+
(6.4.2.1) identifier:
                identifier-nondigit
                identifier identifier-nondigit
                identifier digit
-(6.4.2.1) identifier-nondigit:
+(6.4.2.1) identifier-nondigit:
                nondigit
                universal-character-name
                other implementation-defined characters
-(6.4.2.1) nondigit: one of
+(6.4.2.1) nondigit: one of
               _ a b           c    d   e   f    g   h    i   j   k   l   m
                    n o        p    q   r   s    t   u    v   w   x   y   z
                    A B        C    D   E   F    G   H    I   J   K   L   M
                    N O        P    Q   R   S    T   U    V   W   X   Y   Z
-(6.4.2.1) digit: one of
+(6.4.2.1) digit: one of
                0 1 2          3    4   5   6    7   8    9
 

-
-
+
 

 
A.1.4 [Universal character names]

-
 Universal character names
-(6.4.3) universal-character-name:
+
(6.4.3) universal-character-name:
               \u hex-quad
               \U hex-quad hex-quad
-(6.4.3) hex-quad:
+(6.4.3) hex-quad:
               hexadecimal-digit hexadecimal-digit
                            hexadecimal-digit hexadecimal-digit
 

-
-
+
 

 
A.1.5 [Constants]

-
 Constants
-(6.4.4) constant:
+
(6.4.4) constant:
               integer-constant
               floating-constant
               enumeration-constant
               character-constant
-(6.4.4.1) integer-constant:
+(6.4.4.1) integer-constant:
                decimal-constant integer-suffixopt
                octal-constant integer-suffixopt
                hexadecimal-constant integer-suffixopt
-(6.4.4.1) decimal-constant:
+(6.4.4.1) decimal-constant:
               nonzero-digit
               decimal-constant digit
-(6.4.4.1) octal-constant:
+(6.4.4.1) octal-constant:
                0
                octal-constant octal-digit
-(6.4.4.1) hexadecimal-constant:
+(6.4.4.1) hexadecimal-constant:
               hexadecimal-prefix hexadecimal-digit
               hexadecimal-constant hexadecimal-digit
-(6.4.4.1) hexadecimal-prefix: one of
+(6.4.4.1) hexadecimal-prefix: one of
               0x 0X
-(6.4.4.1) nonzero-digit: one of
+(6.4.4.1) nonzero-digit: one of
               1 2 3 4 5              6      7   8   9
-(6.4.4.1) octal-digit: one of
+(6.4.4.1) octal-digit: one of
                0 1 2 3           4   5      6   7
-(6.4.4.1) hexadecimal-digit: one of
+(6.4.4.1) hexadecimal-digit: one of
               0 1 2 3 4 5                6      7    8   9
               a b c d e f
               A B C D E F
-(6.4.4.1) integer-suffix:
+(6.4.4.1) integer-suffix:
                unsigned-suffix long-suffixopt
                unsigned-suffix long-long-suffix
                long-suffix unsigned-suffixopt
                long-long-suffix unsigned-suffixopt
-(6.4.4.1) unsigned-suffix: one of
+(6.4.4.1) unsigned-suffix: one of
                u U
-(6.4.4.1) long-suffix: one of
+(6.4.4.1) long-suffix: one of
                l L
-(6.4.4.1) long-long-suffix: one of
+(6.4.4.1) long-long-suffix: one of
                ll LL
-(6.4.4.2) floating-constant:
+(6.4.4.2) floating-constant:
                 decimal-floating-constant
                 hexadecimal-floating-constant
-(6.4.4.2) decimal-floating-constant:
+(6.4.4.2) decimal-floating-constant:
               fractional-constant exponent-partopt floating-suffixopt
               digit-sequence exponent-part floating-suffixopt
-(6.4.4.2) hexadecimal-floating-constant:
+(6.4.4.2) hexadecimal-floating-constant:
               hexadecimal-prefix hexadecimal-fractional-constant
                              binary-exponent-part floating-suffixopt
               hexadecimal-prefix hexadecimal-digit-sequence
                              binary-exponent-part floating-suffixopt
-(6.4.4.2) fractional-constant:
+(6.4.4.2) fractional-constant:
                digit-sequenceopt . digit-sequence
                digit-sequence .
-(6.4.4.2) exponent-part:
+(6.4.4.2) exponent-part:
               e signopt digit-sequence
               E signopt digit-sequence
-(6.4.4.2) sign: one of
+(6.4.4.2) sign: one of
                + -
 
-(6.4.4.2) digit-sequence:
+(6.4.4.2) digit-sequence:
                digit
                digit-sequence digit
-(6.4.4.2) hexadecimal-fractional-constant:
+(6.4.4.2) hexadecimal-fractional-constant:
               hexadecimal-digit-sequenceopt .
                              hexadecimal-digit-sequence
               hexadecimal-digit-sequence .
-(6.4.4.2) binary-exponent-part:
+(6.4.4.2) binary-exponent-part:
                p signopt digit-sequence
                P signopt digit-sequence
-(6.4.4.2) hexadecimal-digit-sequence:
+(6.4.4.2) hexadecimal-digit-sequence:
               hexadecimal-digit
               hexadecimal-digit-sequence hexadecimal-digit
-(6.4.4.2) floating-suffix: one of
+(6.4.4.2) floating-suffix: one of
                 f l F L
-(6.4.4.3) enumeration-constant:
+(6.4.4.3) enumeration-constant:
               identifier
-(6.4.4.4) character-constant:
-              ' c-char-sequence '
-              L' c-char-sequence '
-              u' c-char-sequence '
-              U' c-char-sequence '
-(6.4.4.4) c-char-sequence:
+(6.4.4.4) character-constant:
+              ' c-char-sequence '
+              L' c-char-sequence '
+              u' c-char-sequence '
+              U' c-char-sequence '
+(6.4.4.4) c-char-sequence:
                c-char
                c-char-sequence c-char
-(6.4.4.4) c-char:
+(6.4.4.4) c-char:
                any member of the source character set except
-                            the single-quote ', backslash \, or new-line character
+                            the single-quote ', backslash \, or new-line character
                escape-sequence
-(6.4.4.4) escape-sequence:
+(6.4.4.4) escape-sequence:
               simple-escape-sequence
               octal-escape-sequence
               hexadecimal-escape-sequence
               universal-character-name
-(6.4.4.4) simple-escape-sequence: one of
-              \' \" \? \\
+(6.4.4.4) simple-escape-sequence: one of
+              \' \" \? \\
               \a \b \f \n \r \t                   \v
-(6.4.4.4) octal-escape-sequence:
+(6.4.4.4) octal-escape-sequence:
                \ octal-digit
                \ octal-digit octal-digit
                \ octal-digit octal-digit octal-digit
-(6.4.4.4) hexadecimal-escape-sequence:
+(6.4.4.4) hexadecimal-escape-sequence:
               \x hexadecimal-digit
               hexadecimal-escape-sequence hexadecimal-digit
 

-
-
+
 

 
A.1.6 [String literals]

-
 String literals
-(6.4.5) string-literal:
-               encoding-prefixopt " s-char-sequenceopt "
-(6.4.5) encoding-prefix:
+
(6.4.5) string-literal:
+               encoding-prefixopt " s-char-sequenceopt "
+(6.4.5) encoding-prefix:
               u8
               u
               U
               L
-(6.4.5) s-char-sequence:
+(6.4.5) s-char-sequence:
                s-char
                s-char-sequence s-char
-(6.4.5) s-char:
+(6.4.5) s-char:
                any member of the source character set except
-                            the double-quote ", backslash \, or new-line character
+                            the double-quote ", backslash \, or new-line character
                escape-sequence
 

-
-
+
 

 
A.1.7 [Punctuators]

-
 Punctuators
-(6.4.6) punctuator: one of
-              [ ] ( ) { } . ->
-              ++ -- & * + - ~ !
-              / % << >> < > <= >=                      ==      !=    ^    |   &&   ||
+
(6.4.6) punctuator: one of
+              [ ] ( ) { } . ->
+              ++ -- & * + - ~ !
+              / % << >> < > <= >=                      ==      !=    ^    |   &&   ||
               ? : ; ...
-              = *= /= %= += -= <<=                     >>=      &=       ^=   |=
+              = *= /= %= += -= <<=                     >>=      &=       ^=   |=
               , # ##
-              <: :> <% %> %: %:%:
+              <: :> <% %> %: %:%:
 

-
-
+
 

 
A.1.8 [Header names]

-
 Header names
-(6.4.7) header-name:
-              < h-char-sequence >
-              " q-char-sequence "
-(6.4.7) h-char-sequence:
+
(6.4.7) header-name:
+              < h-char-sequence >
+              " q-char-sequence "
+(6.4.7) h-char-sequence:
               h-char
               h-char-sequence h-char
-(6.4.7) h-char:
+(6.4.7) h-char:
               any member of the source character set except
-                           the new-line character and >
-(6.4.7) q-char-sequence:
+                           the new-line character and >
+(6.4.7) q-char-sequence:
               q-char
               q-char-sequence q-char
-(6.4.7) q-char:
+(6.4.7) q-char:
               any member of the source character set except
-                           the new-line character and "
+                           the new-line character and "
 

-
-
+
 

 
A.1.9 [Preprocessing numbers]

-
 Preprocessing numbers
-(6.4.8) pp-number:
+
(6.4.8) pp-number:
               digit
               . digit
               pp-number   digit
@@ -26862,45 +23078,40 @@ the specified values is outside the normal range, the characters stored are unsp
               pp-number   P sign
               pp-number   .
 

-
-
+
 

 
A.2 [Phrase structure grammar]

-
 Phrase structure grammar
-

-
-
+
 

 
A.2.1 [Expressions]

-
 Expressions
-(6.5.1) primary-expression:
+
(6.5.1) primary-expression:
               identifier
               constant
               string-literal
               ( expression )
               generic-selection
-(6.5.1.1) generic-selection:
+(6.5.1.1) generic-selection:
               _Generic ( assignment-expression , generic-assoc-list )
-(6.5.1.1) generic-assoc-list:
+(6.5.1.1) generic-assoc-list:
               generic-association
               generic-assoc-list , generic-association
-(6.5.1.1) generic-association:
+(6.5.1.1) generic-association:
               type-name : assignment-expression
               default : assignment-expression
-(6.5.2) postfix-expression:
+(6.5.2) postfix-expression:
                primary-expression
                postfix-expression [ expression ]
                postfix-expression ( argument-expression-listopt )
                postfix-expression . identifier
-               postfix-expression -> identifier
+               postfix-expression -> identifier
                postfix-expression ++
                postfix-expression --
                ( type-name ) { initializer-list }
                ( type-name ) { initializer-list , }
-(6.5.2) argument-expression-list:
+(6.5.2) argument-expression-list:
              assignment-expression
              argument-expression-list , assignment-expression
-(6.5.3) unary-expression:
+(6.5.3) unary-expression:
               postfix-expression
               ++ unary-expression
               -- unary-expression
@@ -26909,91 +23120,89 @@ the specified values is outside the normal range, the characters stored are unsp
               sizeof ( type-name )
               _Alignof ( type-name )
 
-(6.5.3) unary-operator: one of
-              & * + - ~                !
-(6.5.4) cast-expression:
+(6.5.3) unary-operator: one of
+              & * + - ~                !
+(6.5.4) cast-expression:
                unary-expression
                ( type-name ) cast-expression
-(6.5.5) multiplicative-expression:
+(6.5.5) multiplicative-expression:
                cast-expression
                multiplicative-expression * cast-expression
                multiplicative-expression / cast-expression
                multiplicative-expression % cast-expression
-(6.5.6) additive-expression:
+(6.5.6) additive-expression:
                multiplicative-expression
                additive-expression + multiplicative-expression
                additive-expression - multiplicative-expression
-(6.5.7) shift-expression:
+(6.5.7) shift-expression:
                 additive-expression
-                shift-expression << additive-expression
-                shift-expression >> additive-expression
-(6.5.8) relational-expression:
+                shift-expression << additive-expression
+                shift-expression >> additive-expression
+(6.5.8) relational-expression:
                shift-expression
-               relational-expression   <    shift-expression
-               relational-expression   >    shift-expression
-               relational-expression   <=   shift-expression
-               relational-expression   >=   shift-expression
-(6.5.9) equality-expression:
+               relational-expression   <    shift-expression
+               relational-expression   >    shift-expression
+               relational-expression   <=   shift-expression
+               relational-expression   >=   shift-expression
+(6.5.9) equality-expression:
                relational-expression
                equality-expression == relational-expression
                equality-expression != relational-expression
-(6.5.10) AND-expression:
+(6.5.10) AND-expression:
              equality-expression
-             AND-expression & equality-expression
-(6.5.11) exclusive-OR-expression:
+             AND-expression & equality-expression
+(6.5.11) exclusive-OR-expression:
               AND-expression
               exclusive-OR-expression ^ AND-expression
-(6.5.12) inclusive-OR-expression:
+(6.5.12) inclusive-OR-expression:
                exclusive-OR-expression
                inclusive-OR-expression | exclusive-OR-expression
-(6.5.13) logical-AND-expression:
+(6.5.13) logical-AND-expression:
               inclusive-OR-expression
-              logical-AND-expression && inclusive-OR-expression
-(6.5.14) logical-OR-expression:
+              logical-AND-expression && inclusive-OR-expression
+(6.5.14) logical-OR-expression:
               logical-AND-expression
               logical-OR-expression || logical-AND-expression
-(6.5.15) conditional-expression:
+(6.5.15) conditional-expression:
               logical-OR-expression
               logical-OR-expression ? expression : conditional-expression
-(6.5.16) assignment-expression:
+(6.5.16) assignment-expression:
               conditional-expression
               unary-expression assignment-operator assignment-expression
-(6.5.16) assignment-operator: one of
-              = *= /= %= +=                -=    <<=     >>=       &=    ^=   |=
-(6.5.17) expression:
+(6.5.16) assignment-operator: one of
+              = *= /= %= +=                -=    <<=     >>=       &=    ^=   |=
+(6.5.17) expression:
               assignment-expression
               expression , assignment-expression
-(6.6) constant-expression:
+(6.6) constant-expression:
               conditional-expression
 

-
-
+
 

 
A.2.2 [Declarations]

-
 Declarations
-(6.7) declaration:
+
(6.7) declaration:
                declaration-specifiers init-declarator-listopt ;
                static_assert-declaration
-(6.7) declaration-specifiers:
+(6.7) declaration-specifiers:
                storage-class-specifier declaration-specifiersopt
                type-specifier declaration-specifiersopt
                type-qualifier declaration-specifiersopt
                function-specifier declaration-specifiersopt
                alignment-specifier declaration-specifiersopt
-(6.7) init-declarator-list:
+(6.7) init-declarator-list:
                init-declarator
                init-declarator-list , init-declarator
-(6.7) init-declarator:
+(6.7) init-declarator:
                declarator
                declarator = initializer
-(6.7.1) storage-class-specifier:
+(6.7.1) storage-class-specifier:
               typedef
               extern
               static
               _Thread_local
               auto
               register
-(6.7.2) type-specifier:
+(6.7.2) type-specifier:
                void
                char
                short
@@ -27009,55 +23218,55 @@ the specified values is outside the normal range, the characters stored are unsp
                struct-or-union-specifier
                enum-specifier
                typedef-name
-(6.7.2.1) struct-or-union-specifier:
+(6.7.2.1) struct-or-union-specifier:
                struct-or-union identifieropt { struct-declaration-list }
                struct-or-union identifier
-(6.7.2.1) struct-or-union:
+(6.7.2.1) struct-or-union:
                struct
                union
-(6.7.2.1) struct-declaration-list:
+(6.7.2.1) struct-declaration-list:
                struct-declaration
                struct-declaration-list struct-declaration
-(6.7.2.1) struct-declaration:
+(6.7.2.1) struct-declaration:
                specifier-qualifier-list struct-declarator-listopt ;
                static_assert-declaration
 
-(6.7.2.1) specifier-qualifier-list:
+(6.7.2.1) specifier-qualifier-list:
                type-specifier specifier-qualifier-listopt
                type-qualifier specifier-qualifier-listopt
-(6.7.2.1) struct-declarator-list:
+(6.7.2.1) struct-declarator-list:
                struct-declarator
                struct-declarator-list , struct-declarator
-(6.7.2.1) struct-declarator:
+(6.7.2.1) struct-declarator:
                declarator
                declaratoropt : constant-expression
-(6.7.2.2) enum-specifier:
+(6.7.2.2) enum-specifier:
               enum identifieropt { enumerator-list }
               enum identifieropt { enumerator-list , }
               enum identifier
-(6.7.2.2) enumerator-list:
+(6.7.2.2) enumerator-list:
               enumerator
               enumerator-list , enumerator
-(6.7.2.2) enumerator:
+(6.7.2.2) enumerator:
               enumeration-constant
               enumeration-constant = constant-expression
-(6.7.2.4) atomic-type-specifier:
+(6.7.2.4) atomic-type-specifier:
               _Atomic ( type-name )
-(6.7.3) type-qualifier:
+(6.7.3) type-qualifier:
               const
               restrict
               volatile
               _Atomic
-(6.7.4) function-specifier:
+(6.7.4) function-specifier:
                inline
                _Noreturn
-(6.7.5) alignment-specifier:
+(6.7.5) alignment-specifier:
               _Alignas ( type-name )
               _Alignas ( constant-expression )
-(6.7.6) declarator:
+(6.7.6) declarator:
               pointeropt direct-declarator
 
-(6.7.6) direct-declarator:
+(6.7.6) direct-declarator:
                identifier
                ( declarator )
                direct-declarator [ type-qualifier-listopt assignment-expressionopt ]
@@ -27066,30 +23275,30 @@ the specified values is outside the normal range, the characters stored are unsp
                direct-declarator [ type-qualifier-listopt * ]
                direct-declarator ( parameter-type-list )
                direct-declarator ( identifier-listopt )
-(6.7.6) pointer:
+(6.7.6) pointer:
                * type-qualifier-listopt
                * type-qualifier-listopt pointer
-(6.7.6) type-qualifier-list:
+(6.7.6) type-qualifier-list:
               type-qualifier
               type-qualifier-list type-qualifier
-(6.7.6) parameter-type-list:
+(6.7.6) parameter-type-list:
              parameter-list
              parameter-list , ...
-(6.7.6) parameter-list:
+(6.7.6) parameter-list:
              parameter-declaration
              parameter-list , parameter-declaration
-(6.7.6) parameter-declaration:
+(6.7.6) parameter-declaration:
              declaration-specifiers declarator
              declaration-specifiers abstract-declaratoropt
-(6.7.6) identifier-list:
+(6.7.6) identifier-list:
                 identifier
                 identifier-list , identifier
-(6.7.7) type-name:
+(6.7.7) type-name:
               specifier-qualifier-list abstract-declaratoropt
-(6.7.7) abstract-declarator:
+(6.7.7) abstract-declarator:
               pointer
               pointeropt direct-abstract-declarator
-(6.7.7) direct-abstract-declarator:
+(6.7.7) direct-abstract-declarator:
                ( abstract-declarator )
                direct-abstract-declaratoropt [ type-qualifier-listopt
                               assignment-expressionopt ]
@@ -27099,115 +23308,109 @@ the specified values is outside the normal range, the characters stored are unsp
                               assignment-expression ]
                direct-abstract-declaratoropt [ * ]
                direct-abstract-declaratoropt ( parameter-type-listopt )
-(6.7.8) typedef-name:
+(6.7.8) typedef-name:
               identifier
-(6.7.9) initializer:
+(6.7.9) initializer:
                 assignment-expression
                 { initializer-list }
                 { initializer-list , }
-(6.7.9) initializer-list:
+(6.7.9) initializer-list:
                 designationopt initializer
                 initializer-list , designationopt initializer
-(6.7.9) designation:
+(6.7.9) designation:
               designator-list =
-(6.7.9) designator-list:
+(6.7.9) designator-list:
               designator
               designator-list designator
-(6.7.9) designator:
+(6.7.9) designator:
               [ constant-expression ]
               . identifier
-(6.7.10) static_assert-declaration:
+(6.7.10) static_assert-declaration:
                _Static_assert ( constant-expression , string-literal ) ;
 

-
-
+
 

 
A.2.3 [Statements]

-
 Statements
-(6.8) statement:
+
(6.8) statement:
               labeled-statement
               compound-statement
               expression-statement
               selection-statement
               iteration-statement
               jump-statement
-(6.8.1) labeled-statement:
+(6.8.1) labeled-statement:
                identifier : statement
                case constant-expression : statement
                default : statement
-(6.8.2) compound-statement:
+(6.8.2) compound-statement:
              { block-item-listopt }
-(6.8.2) block-item-list:
+(6.8.2) block-item-list:
                block-item
                block-item-list block-item
-(6.8.2) block-item:
+(6.8.2) block-item:
                declaration
                statement
-(6.8.3) expression-statement:
+(6.8.3) expression-statement:
               expressionopt ;
-(6.8.4) selection-statement:
+(6.8.4) selection-statement:
                if ( expression ) statement
                if ( expression ) statement else statement
                switch ( expression ) statement
-(6.8.5) iteration-statement:
+(6.8.5) iteration-statement:
                 while ( expression ) statement
                 do statement while ( expression ) ;
                 for ( expressionopt ; expressionopt ; expressionopt ) statement
                 for ( declaration expressionopt ; expressionopt ) statement
-(6.8.6) jump-statement:
+(6.8.6) jump-statement:
               goto identifier ;
               continue ;
               break ;
               return expressionopt ;
 

-
-
+
 

 
A.2.4 [External definitions]

-
 External definitions
-(6.9) translation-unit:
+
(6.9) translation-unit:
                external-declaration
                translation-unit external-declaration
-(6.9) external-declaration:
+(6.9) external-declaration:
                function-definition
                declaration
-(6.9.1) function-definition:
+(6.9.1) function-definition:
                declaration-specifiers declarator declaration-listopt compound-statement
-(6.9.1) declaration-list:
+(6.9.1) declaration-list:
               declaration
               declaration-list declaration
 

-
-
+
 

 
A.3 [Preprocessing directives]

-
 Preprocessing directives
-(6.10) preprocessing-file:
+
(6.10) preprocessing-file:
               groupopt
-(6.10) group:
+(6.10) group:
                 group-part
                 group group-part
-(6.10) group-part:
+(6.10) group-part:
               if-section
               control-line
               text-line
               # non-directive
-(6.10) if-section:
+(6.10) if-section:
                 if-group elif-groupsopt else-groupopt endif-line
-(6.10) if-group:
+(6.10) if-group:
                # if     constant-expression new-line groupopt
                # ifdef identifier new-line groupopt
                # ifndef identifier new-line groupopt
-(6.10) elif-groups:
+(6.10) elif-groups:
                elif-group
                elif-groups elif-group
-(6.10) elif-group:
+(6.10) elif-group:
                # elif         constant-expression new-line groupopt
-(6.10) else-group:
+(6.10) else-group:
                # else        new-line groupopt
-(6.10) endif-line:
+(6.10) endif-line:
                # endif       new-line
-(6.10) control-line:
+(6.10) control-line:
               # include pp-tokens new-line
               # define identifier replacement-list new-line
               # define identifier lparen identifier-listopt )
@@ -27220,43 +23423,36 @@ the specified values is outside the normal range, the characters stored are unsp
               # error   pp-tokensopt new-line
               # pragma pp-tokensopt new-line
               #         new-line
-(6.10) text-line:
+(6.10) text-line:
                pp-tokensopt new-line
-(6.10) non-directive:
+(6.10) non-directive:
               pp-tokens new-line
-(6.10) lparen:
+(6.10) lparen:
                  a ( character not immediately preceded by white-space
-(6.10) replacement-list:
+(6.10) replacement-list:
               pp-tokensopt
-(6.10) pp-tokens:
+(6.10) pp-tokens:
               preprocessing-token
               pp-tokens preprocessing-token
-(6.10) new-line:
+(6.10) new-line:
               the new-line character
                                   Annex B
                                 (informative)
 

-
-
+
 

 
B. [Library summary]

-
 Library summary
-

-
-
+
 

-
B.1 [Diagnostics ]

-
 Diagnostics 
-        NDEBUG
+
B.1 [Diagnostics <assert.h>]

+
NDEBUG
         static_assert
         void assert(scalar expression);
 

-
-
+
 

-
B.2 [Complex ]

-
 Complex 
-        _ _STDC_NO_COMPLEX_ _              imaginary
+
B.2 [Complex <complex.h>]

+
_ _STDC_NO_COMPLEX_ _              imaginary
         complex                            _Imaginary_I
         _Complex_I                         I
         #pragma STDC CX_LIMITED_RANGE on-off-switch
@@ -27333,12 +23529,10 @@ the specified values is outside the normal range, the characters stored are unsp
         float crealf(float complex z);
         long double creall(long double complex z);
 

-
-
+
 

-
B.3 [Character handling ]

-
 Character handling 
-        int   isalnum(int c);
+
B.3 [Character handling <ctype.h>]

+
int   isalnum(int c);
         int   isalpha(int c);
         int   isblank(int c);
         int   iscntrl(int c);
@@ -27353,21 +23547,17 @@ the specified values is outside the normal range, the characters stored are unsp
         int   tolower(int c);
         int   toupper(int c);
 

-
-
+
 

-
B.4 [Errors ]

-
 Errors 
-        EDOM           EILSEQ             ERANGE           errno
+
B.4 [Errors <errno.h>]

+
EDOM           EILSEQ             ERANGE           errno
         _ _STDC_WANT_LIB_EXT1_ _
         errno_t
 

-
-
+
 

-
B.5 [Floating-point environment ]

-
 Floating-point environment 
-        fenv_t                FE_OVERFLOW              FE_TOWARDZERO
+
B.5 [Floating-point environment <fenv.h>]

+
fenv_t                FE_OVERFLOW              FE_TOWARDZERO
         fexcept_t             FE_UNDERFLOW             FE_UPWARD
         FE_DIVBYZERO          FE_ALL_EXCEPT            FE_DFL_ENV
         FE_INEXACT            FE_DOWNWARD
@@ -27387,12 +23577,10 @@ the specified values is outside the normal range, the characters stored are unsp
       int   fesetenv(const fenv_t *envp);
       int   feupdateenv(const fenv_t *envp);
 

-
-
+
 

-
B.6 [Characteristics of floating types ]

-
 Characteristics of floating types 
-      FLT_ROUNDS              DBL_DIG                  FLT_MAX
+
B.6 [Characteristics of floating types <float.h>]

+
FLT_ROUNDS              DBL_DIG                  FLT_MAX
       FLT_EVAL_METHOD         LDBL_DIG                 DBL_MAX
       FLT_HAS_SUBNORM         FLT_MIN_EXP              LDBL_MAX
       DBL_HAS_SUBNORM         DBL_MIN_EXP              FLT_EPSILON
@@ -27407,12 +23595,10 @@ the specified values is outside the normal range, the characters stored are unsp
       DECIMAL_DIG             DBL_MAX_10_EXP
       FLT_DIG                 LDBL_MAX_10_EXP
 

-
-
+
 

-
B.7 [Format conversion of integer types ]

-
 Format conversion of integer types 
-      imaxdiv_t
+
B.7 [Format conversion of integer types <inttypes.h>]

+
imaxdiv_t
       PRIdN         PRIdLEASTN       PRIdFASTN             PRIdMAX   PRIdPTR
       PRIiN         PRIiLEASTN       PRIiFASTN             PRIiMAX   PRIiPTR
       PRIoN         PRIoLEASTN       PRIoFASTN             PRIoMAX   PRIoPTR
@@ -27436,42 +23622,34 @@ the specified values is outside the normal range, the characters stored are unsp
         uintmax_t wcstoumax(const wchar_t * restrict nptr,
                 wchar_t ** restrict endptr, int base);
 

-
-
+
 

-
B.8 [Alternative spellings ]

-
 Alternative spellings 
-        and            bitor              not_eq           xor
+
B.8 [Alternative spellings <iso646.h>]

+
and            bitor              not_eq           xor
         and_eq         compl              or               xor_eq
         bitand         not                or_eq
 

-
-
+
 

-
B.9 [Sizes of integer types ]

-
 Sizes of integer types 
-        CHAR_BIT       CHAR_MAX           INT_MIN          ULONG_MAX
+
B.9 [Sizes of integer types <limits.h>]

+
CHAR_BIT       CHAR_MAX           INT_MIN          ULONG_MAX
         SCHAR_MIN      MB_LEN_MAX         INT_MAX          LLONG_MIN
         SCHAR_MAX      SHRT_MIN           UINT_MAX         LLONG_MAX
         UCHAR_MAX      SHRT_MAX           LONG_MIN         ULLONG_MAX
         CHAR_MIN       USHRT_MAX          LONG_MAX
 

-
-
+
 

-
B.10 [Localization ]

-
 Localization 
-        struct lconv   LC_ALL             LC_CTYPE         LC_NUMERIC
+
B.10 [Localization <locale.h>]

+
struct lconv   LC_ALL             LC_CTYPE         LC_NUMERIC
         NULL           LC_COLLATE         LC_MONETARY      LC_TIME
         char *setlocale(int category, const char *locale);
         struct lconv *localeconv(void);
 

-
-
+
 

-
B.11 [Mathematics ]

-
 Mathematics 
-        float_t               FP_INFINITE              FP_FAST_FMAL
+
B.11 [Mathematics <math.h>]

+
float_t               FP_INFINITE              FP_FAST_FMAL
         double_t              FP_NAN                   FP_ILOGB0
         HUGE_VAL              FP_NORMAL                FP_ILOGBNAN
         HUGE_VALF             FP_SUBNORMAL             MATH_ERRNO
@@ -27669,51 +23847,41 @@ the specified values is outside the normal range, the characters stored are unsp
       int islessgreater(real-floating x, real-floating y);
       int isunordered(real-floating x, real-floating y);
 

-
-
+
 

-
B.12 [Nonlocal jumps ]

-
 Nonlocal jumps 
-      jmp_buf
+
B.12 [Nonlocal jumps <setjmp.h>]

+
jmp_buf
       int setjmp(jmp_buf env);
       _Noreturn void longjmp(jmp_buf env, int val);
 

-
-
+
 

-
B.13 [Signal handling ]

-
 Signal handling 
-      sig_atomic_t   SIG_IGN            SIGILL           SIGTERM
+
B.13 [Signal handling <signal.h>]

+
sig_atomic_t   SIG_IGN            SIGILL           SIGTERM
       SIG_DFL        SIGABRT            SIGINT
       SIG_ERR        SIGFPE             SIGSEGV
       void (*signal(int sig, void (*func)(int)))(int);
       int raise(int sig);
 

-
-
+
 

-
B.14 [Alignment ]

-
 Alignment 
-        alignas
+
B.14 [Alignment <stdalign.h>]

+
alignas
         _ _alignas_is_defined
 

-
-
+
 

-
B.15 [Variable arguments ]

-
 Variable arguments 
-        va_list
+
B.15 [Variable arguments <stdarg.h>]

+
va_list
         type va_arg(va_list ap, type);
         void va_copy(va_list dest, va_list src);
         void va_end(va_list ap);
         void va_start(va_list ap, parmN);
 

-
-
+
 

-
B.16 [Atomics ]

-
 Atomics 
-        ATOMIC_BOOL_LOCK_FREE      atomic_uint
+
B.16 [Atomics <stdatomic.h>]

+
ATOMIC_BOOL_LOCK_FREE      atomic_uint
         ATOMIC_CHAR_LOCK_FREE      atomic_long
         ATOMIC_CHAR16_T_LOCK_FREE  atomic_ulong
         ATOMIC_CHAR32_T_LOCK_FREE  atomic_llong
@@ -27778,33 +23946,27 @@ the specified values is outside the normal range, the characters stored are unsp
       void atomic_flag_clear_explicit(
             volatile atomic_flag *object, memory_order order);
 

-
-
+
 

-
B.17 [Boolean type and values ]

-
 Boolean type and values 
-        bool
+
B.17 [Boolean type and values <stdbool.h>]

+
bool
         true
         false
         _ _bool_true_false_are_defined
 

-
-
+
 

-
B.18 [Common definitions ]

-
 Common definitions 
-        ptrdiff_t       max_align_t        NULL
+
B.18 [Common definitions <stddef.h>]

+
ptrdiff_t       max_align_t        NULL
         size_t          wchar_t
         offsetof(type, member-designator)
         _ _STDC_WANT_LIB_EXT1_ _
         rsize_t
 

-
-
+
 

-
B.19 [Integer types ]

-
 Integer types 
-        intN_t                 INT_LEASTN_MIN           PTRDIFF_MAX
+
B.19 [Integer types <stdint.h>]

+
intN_t                 INT_LEASTN_MIN           PTRDIFF_MAX
         uintN_t                INT_LEASTN_MAX           SIG_ATOMIC_MIN
         int_leastN_t           UINT_LEASTN_MAX          SIG_ATOMIC_MAX
         uint_leastN_t          INT_FASTN_MIN            SIZE_MAX
@@ -27820,12 +23982,10 @@ the specified values is outside the normal range, the characters stored are unsp
         _ _STDC_WANT_LIB_EXT1_ _
         RSIZE_MAX
 

-
-
+
 

-
B.20 [Input/output ]

-
 Input/output 
-      size_t        _IOLBF             FILENAME_MAX     TMP_MAX
+
B.20 [Input/output <stdio.h>]

+
size_t        _IOLBF             FILENAME_MAX     TMP_MAX
       FILE          _IONBF             L_tmpnam         stderr
       fpos_t        BUFSIZ             SEEK_CUR         stdin
       NULL          EOF                SEEK_END         stdout
@@ -27944,12 +24104,10 @@ the specified values is outside the normal range, the characters stored are unsp
            va_list arg);
       char *gets_s(char *s, rsize_t n);
 

-
-
+
 

-
B.21 [General utilities ]

-
 General utilities 
-        size_t       ldiv_t             EXIT_FAILURE     MB_CUR_MAX
+
B.21 [General utilities <stdlib.h>]

+
size_t       ldiv_t             EXIT_FAILURE     MB_CUR_MAX
         wchar_t      lldiv_t            EXIT_SUCCESS
         div_t        NULL               RAND_MAX
         double atof(const char *nptr);
@@ -28044,19 +24202,15 @@ the specified values is outside the normal range, the characters stored are unsp
              char * restrict dst, rsize_t dstmax,
              const wchar_t * restrict src, rsize_t len);
 

-
-
+
 

-
B.22 [_Noreturn ]

-
 _Noreturn 
-        noreturn
+
B.22 [_Noreturn <stdnoreturn.h>]

+
noreturn
 

-
-
+
 

-
B.23 [String handling ]

-
 String handling 
-        size_t
+
B.23 [String handling <string.h>]

+
size_t
         NULL
       void *memcpy(void * restrict s1,
            const void * restrict s2, size_t n);
@@ -28119,12 +24273,10 @@ the specified values is outside the normal range, the characters stored are unsp
         size_t strerrorlen_s(errno_t errnum);
         size_t strnlen_s(const char *s, size_t maxsize);
 

-
-
+
 

-
B.24 [Type-generic math ]

-
 Type-generic math 
-        acos         sqrt               fmod             nextafter
+
B.24 [Type-generic math <tgmath.h>]

+
acos         sqrt               fmod             nextafter
         asin         fabs               frexp            nexttoward
         atan         atan2              hypot            remainder
         acosh        cbrt               ilogb            remquo
@@ -28140,13 +24292,11 @@ the specified values is outside the normal range, the characters stored are unsp
         log          fmax               lround           cproj
         pow          fmin               nearbyint        creal
 

-
-
+
 

-
B.25 [Threads ]

-
 Threads 
-        thread_local                    once_flag
-        ONCE_FLAG_INIT                  mtx_plain                      
+
B.25 [Threads <threads.h>]

+
thread_local                    once_flag
+        ONCE_FLAG_INIT                  mtx_plain
         TSS_DTOR_ITERATIONS             mtx_recursive
         cnd_t                           mtx_timed
         thrd_t                          thrd_timedout
@@ -28185,12 +24335,10 @@ the specified values is outside the normal range, the characters stored are unsp
       void *tss_get(tss_t key);
       int tss_set(tss_t key, void *val);
 

-
-
+
 

-
B.26 [Date and time ]

-
 Date and time 
-      NULL                 size_t                   struct timespec
+
B.26 [Date and time <time.h>]

+
NULL                 size_t                   struct timespec
       CLOCKS_PER_SEC       clock_t                  struct tm
       TIME_UTC             time_t
       clock_t clock(void);
@@ -28219,12 +24367,10 @@ the specified values is outside the normal range, the characters stored are unsp
         struct tm *localtime_s(const time_t * restrict timer,
              struct tm * restrict result);
 

-
-
+
 

-
B.27 [Unicode utilities ]

-
 Unicode utilities 
-        mbstate_t    size_t             char16_t         char32_t
+
B.27 [Unicode utilities <uchar.h>]

+
mbstate_t    size_t             char16_t         char32_t
         size_t mbrtoc16(char16_t * restrict pc16,
              const char * restrict s, size_t n,
              mbstate_t * restrict ps);
@@ -28236,12 +24382,10 @@ the specified values is outside the normal range, the characters stored are unsp
         size_t c32rtomb(char * restrict s, char32_t c32,
              mbstate_t * restrict ps);
 

-
-
+
 

-
B.28 [Extended multibyte/wide character utilities ]

-
 Extended multibyte/wide character utilities 
-        wchar_t             wint_t                   WCHAR_MAX
+
B.28 [Extended multibyte/wide character utilities <wchar.h>]

+
wchar_t             wint_t                   WCHAR_MAX
         size_t              struct tm                WCHAR_MIN
         mbstate_t           NULL                     WEOF
         int fwprintf(FILE * restrict stream,
@@ -28419,12 +24563,10 @@ the specified values is outside the normal range, the characters stored are unsp
            const wchar_t ** restrict src, rsize_t len,
            mbstate_t * restrict ps);
 

-
-
+
 

-
B.29 [Wide character classification and mapping utilities ]

-
 Wide character classification and mapping utilities 
-      wint_t         wctrans_t         wctype_t         WEOF
+
B.29 [Wide character classification and mapping utilities <wctype.h>]

+
wint_t         wctrans_t         wctype_t         WEOF
       int iswalnum(wint_t wc);
       int iswalpha(wint_t wc);
       int iswblank(wint_t wc);
@@ -28446,109 +24588,87 @@ the specified values is outside the normal range, the characters stored are unsp
                                            Annex C
                                          (informative)
 

-
-
+
 

 
C. [Sequence points]

-

-
-
-
1   The following are the sequence points described in 5.1.2.3:
+
+
1   The following are the sequence points described in 5.1.2.3:
     -- Between the evaluations of the function designator and actual arguments in a function
-       call and the actual call. (6.5.2.2).
+       call and the actual call. (6.5.2.2).
     -- Between the evaluations of the first and second operands of the following operators:
-       logical AND && (6.5.13); logical OR || (6.5.14); comma , (6.5.17).
+       logical AND && (6.5.13); logical OR || (6.5.14); comma , (6.5.17).
     -- Between the evaluations of the first operand of the conditional ? : operator and
-       whichever of the second and third operands is evaluated (6.5.15).
-    -- The end of a full declarator: declarators (6.7.6);
+       whichever of the second and third operands is evaluated (6.5.15).
+    -- The end of a full declarator: declarators (6.7.6);
     -- Between the evaluation of a full expression and the next full expression to be
        evaluated. The following are full expressions: an initializer that is not part of a
-       compound literal (6.7.9); the expression in an expression statement (6.8.3); the
-       controlling expression of a selection statement (if or switch) (6.8.4); the
-       controlling expression of a while or do statement (6.8.5); each of the (optional)
-       expressions of a for statement (6.8.5.3); the (optional) expression in a return
-       statement (6.8.6.4).
-    -- Immediately before a library function returns (7.1.4).
+       compound literal (6.7.9); the expression in an expression statement (6.8.3); the
+       controlling expression of a selection statement (if or switch) (6.8.4); the
+       controlling expression of a while or do statement (6.8.5); each of the (optional)
+       expressions of a for statement (6.8.5.3); the (optional) expression in a return
+       statement (6.8.6.4).
+    -- Immediately before a library function returns (7.1.4).
     -- After the actions associated with each formatted input/output function conversion
-       specifier (7.21.6, 7.29.2).
+       specifier (7.21.6, 7.29.2).
     -- Immediately before and immediately after each call to a comparison function, and
        also between any call to a comparison function and any movement of the objects
-       passed as arguments to that call (7.22.5).
+       passed as arguments to that call (7.22.5).
                                          Annex D
                                         (normative)
 

-
-
+
 

 
D. [Universal character names for identifiers]

-

-
-
+
 
1   This clause lists the hexadecimal code values that are valid in universal character names
     in identifiers.
 

-
-
+
 

 
D.1 [Ranges of characters allowed]

-

-
-
+
 
1   00A8, 00AA, 00AD, 00AF, 00B2-00B5, 00B7-00BA, 00BC-00BE, 00C0-00D6,
     00D8-00F6, 00F8-00FF
 

-
-
+
 
2   0100-167F, 1681-180D, 180F-1FFF
 

-
-
+
 
3   200B-200D, 202A-202E, 203F-2040, 2054, 2060-206F
 

-
-
+
 
4   2070-218F, 2460-24FF, 2776-2793, 2C00-2DFF, 2E80-2FFF
 

-
-
+
 
5   3004-3007, 3021-302F, 3031-303F
 

-
-
+
 
6   3040-D7FF
 

-
-
+
 
7   F900-FD3D, FD40-FDCF, FDF0-FE44, FE47-FFFD
 

-
-
+
 
8   10000-1FFFD, 20000-2FFFD, 30000-3FFFD, 40000-4FFFD, 50000-5FFFD,
     60000-6FFFD, 70000-7FFFD, 80000-8FFFD, 90000-9FFFD, A0000-AFFFD,
     B0000-BFFFD, C0000-CFFFD, D0000-DFFFD, E0000-EFFFD
 

-
-
+
 

 
D.2 [Ranges of characters disallowed initially]

-

-
-
+
 
1   0300-036F, 1DC0-1DFF, 20D0-20FF, FE20-FE2F
                                          Annex E
                                        (informative)
 

-
-
+
 

 
E. [Implementation limits]

-

-
-
+
 
1   The contents of the header <limits.h> are given below, in alphabetical order. The
     minimum magnitudes shown shall be replaced by implementation-defined magnitudes
     with the same sign. The values shall all be constant expressions suitable for use in #if
-    preprocessing directives. The components are described further in 5.2.4.2.1.
+    preprocessing directives. The components are described further in 5.2.4.2.1.
             #define    CHAR_BIT                               8
             #define    CHAR_MAX          UCHAR_MAX or SCHAR_MAX
             #define    CHAR_MIN                  0 or SCHAR_MIN
@@ -28569,22 +24689,19 @@ the specified values is outside the normal range, the characters stored are unsp
             #define    ULONG_MAX                     4294967295
             #define    ULLONG_MAX          18446744073709551615
 

-
-
+
 
2   The contents of the header <float.h> are given below. All integer values, except
     FLT_ROUNDS, shall be constant expressions suitable for use in #if preprocessing
     directives; all floating values shall be constant expressions. The components are
-    described further in 5.2.4.2.2.
+    described further in 5.2.4.2.2.
 

-
-
+
 
3   The values given in the following list shall be replaced by implementation-defined
     expressions:
             #define FLT_EVAL_METHOD
             #define FLT_ROUNDS
 

-
-
+
 
4   The values given in the following list shall be replaced by implementation-defined
     constant expressions that are greater or equal in magnitude (absolute value) to those
     shown, with the same sign:
@@ -28612,16 +24729,14 @@ the specified values is outside the normal range, the characters stored are unsp
            #define    LDBL_MIN_10_EXP                              -37
            #define    LDBL_MIN_EXP
 

-
-
+
 
5   The values given in the following list shall be replaced by implementation-defined
     constant expressions with values that are greater than or equal to those shown:
            #define DBL_MAX                                        1E+37
            #define FLT_MAX                                        1E+37
            #define LDBL_MAX                                       1E+37
 

-
-
+
 
6   The values given in the following list shall be replaced by implementation-defined
     constant expressions with (positive) values that are less than or equal to those shown:
            #define    DBL_EPSILON                                  1E-9
@@ -28633,19 +24748,13 @@ the specified values is outside the normal range, the characters stored are unsp
                                                Annex F
                                               (normative)
 

-
-
+
 

 
F. [IEC 60559 floating-point arithmetic]

-
 IEC 60559 floating-point arithmetic
-

-
-
+
 

 
F.1 [Introduction]

-

-
-
+
 
1   This annex specifies C language support for the IEC 60559 floating-point standard. The
     IEC 60559 floating-point standard is specifically Binary floating-point arithmetic for
     microprocessor systems, second edition (IEC 60559:1989), previously designated
@@ -28654,30 +24763,29 @@ the specified values is outside the normal range, the characters stored are unsp
     Arithmetic (ANSI/IEEE 854-1987) generalizes the binary standard to remove
     dependencies on radix and word length. IEC 60559 generally refers to the floating-point
     standard, as in IEC 60559 operation, IEC 60559 format, etc. An implementation that
-    defines _ _STDC_IEC_559_ _ shall conform to the specifications in this annex.356)
+    defines _ _STDC_IEC_559_ _ shall conform to the specifications in this annex.[356]
     Where a binding between the C language and IEC 60559 is indicated, the
     IEC 60559-specified behavior is adopted by reference, unless stated otherwise. Since
     negative and positive infinity are representable in IEC 60559 formats, all real numbers lie
     within the range of representable values.
 

+
+
Footnote 356) Implementations that do not define _ _STDC_IEC_559_ _ are not required to conform to these
+         specifications.
+

 
-
+
 

 
F.2 [Types]

-

-
-
+
 
1   The C floating types match the IEC 60559 formats as follows:
     -- The float type matches the IEC 60559 single format.
     -- The double type matches the IEC 60559 double format.
-    -- The long double type matches an IEC 60559 extended format,357) else a
+    -- The long double type matches an IEC 60559 extended format,[357] else a
        non-IEC 60559 extended format, else the IEC 60559 double format.
     Any non-IEC 60559 extended format used for the long double type shall have more
-    precision than IEC 60559 double and at least the range of IEC 60559 double.358)
-
-    Recommended practice
+    precision than IEC 60559 double and at least the range of IEC 60559 double.[358]
 

-
 
 
Footnote 357) ``Extended'' is IEC 60559's double-extended data format. Extended refers to both the common 80-bit
          and quadruple 128-bit IEC 60559 formats.
@@ -28686,60 +24794,23 @@ the specified values is outside the normal range, the characters stored are unsp
 
 
Footnote 358) A non-IEC 60559 long double type is required to provide infinity and NaNs, as its values include
          all double values.
+    Recommended practice
 

 
-
+
 
2   The long double type should match an IEC 60559 extended format.
 

-
-
+
 

 
F.2.1 [Infinities, signed zeros, and NaNs]

-

-
-
-
1   This specification does not define the behavior of signaling NaNs.359) It generally uses
+
+
1   This specification does not define the behavior of signaling NaNs.[359] It generally uses
     the term NaN to denote quiet NaNs. The NAN and INFINITY macros and the nan
     functions in <math.h> provide designations for IEC 60559 NaNs and infinities.
 

-
 
 
Footnote 359) Since NaNs created by IEC 60559 operations are always quiet, quiet NaNs (along with infinities) are
          sufficient for closure of the arithmetic.
-

-
-
-

-
F.3 [Operators and functions]

-

-
-
-
1   C operators and functions provide IEC 60559 required and recommended facilities as
-    listed below.
-    -- The +, -, *, and / operators provide the IEC 60559 add, subtract, multiply, and
-       divide operations.
-    -- The sqrt functions in <math.h> provide the IEC 60559 square root operation.
-    -- The remainder functions in <math.h> provide the IEC 60559 remainder
-       operation. The remquo functions in <math.h> provide the same operation but
-       with additional information.
-    -- The rint functions in <math.h> provide the IEC 60559 operation that rounds a
-       floating-point number to an integer value (in the same precision). The nearbyint
-       functions in <math.h> provide the nearbyinteger function recommended in the
-       Appendix to ANSI/IEEE 854.
-    -- The conversions for floating types provide the IEC 60559 conversions between
-       floating-point precisions.
-    -- The conversions from integer to floating types provide the IEC 60559 conversions
-       from integer to floating point.
-    -- The conversions from floating to integer types provide IEC 60559-like conversions
-       but always round toward zero.
-    -- The lrint and llrint functions in <math.h> provide the IEC 60559
-       conversions, which honor the directed rounding mode, from floating point to the
-       long int and long long int integer formats. The lrint and llrint
-       functions can be used to implement IEC 60559 conversions from floating to other
-       integer formats.
-    -- The translation time conversion of floating constants and the strtod, strtof,
-       strtold, fprintf, fscanf, and related library functions in <stdlib.h>,
-
    <stdio.h>, and <wchar.h> provide IEC 60559 binary-decimal conversions. The
    strtold function in <stdlib.h> provides the conv function recommended in the
    Appendix to ANSI/IEEE 854.
@@ -28777,7 +24848,6 @@ the specified values is outside the normal range, the characters stored are unsp
    Appendix to IEC 60559, but following the newer specifications in ANSI/IEEE 854.
 -- The nextafter and nexttoward functions in <math.h> provide the nextafter
    function recommended in the Appendix to IEC 60559 (but with a minor change to
-
         better handle signed zeros).
     -- The isfinite macro in <math.h> provides the finite function recommended in
        the Appendix to IEC 60559.
@@ -28787,25 +24857,52 @@ the specified values is outside the normal range, the characters stored are unsp
        conjunction with the number classification macros (FP_NAN, FP_INFINITE,
        FP_NORMAL, FP_SUBNORMAL, FP_ZERO), provide the facility of the class
        function recommended in the Appendix to IEC 60559 (except that the classification
-       macros defined in 7.12.3 do not distinguish signaling from quiet NaNs).
-

+       macros defined in 7.12.3 do not distinguish signaling from quiet NaNs).
+

 
-
+
+

+
F.3 [Operators and functions]

+
+
1   C operators and functions provide IEC 60559 required and recommended facilities as
+    listed below.
+    -- The +, -, *, and / operators provide the IEC 60559 add, subtract, multiply, and
+       divide operations.
+    -- The sqrt functions in <math.h> provide the IEC 60559 square root operation.
+    -- The remainder functions in <math.h> provide the IEC 60559 remainder
+       operation. The remquo functions in <math.h> provide the same operation but
+       with additional information.
+    -- The rint functions in <math.h> provide the IEC 60559 operation that rounds a
+       floating-point number to an integer value (in the same precision). The nearbyint
+       functions in <math.h> provide the nearbyinteger function recommended in the
+       Appendix to ANSI/IEEE 854.
+    -- The conversions for floating types provide the IEC 60559 conversions between
+       floating-point precisions.
+    -- The conversions from integer to floating types provide the IEC 60559 conversions
+       from integer to floating point.
+    -- The conversions from floating to integer types provide IEC 60559-like conversions
+       but always round toward zero.
+    -- The lrint and llrint functions in <math.h> provide the IEC 60559
+       conversions, which honor the directed rounding mode, from floating point to the
+       long int and long long int integer formats. The lrint and llrint
+       functions can be used to implement IEC 60559 conversions from floating to other
+       integer formats.
+    -- The translation time conversion of floating constants and the strtod, strtof,
+       strtold, fprintf, fscanf, and related library functions in <stdlib.h>,
+

+
 

 
F.4 [Floating to integer conversion]

-

-
-
-
1   If the integer type is _Bool, 6.3.1.2 applies and no floating-point exceptions are raised
+
+
1   If the integer type is _Bool, 6.3.1.2 applies and no floating-point exceptions are raised
     (even for NaN). Otherwise, if the floating value is infinite or NaN or if the integral part
     of the floating value exceeds the range of the integer type, then the ``invalid'' floating-
     point exception is raised and the resulting value is unspecified. Otherwise, the resulting
-    value is determined by 6.3.1.4. Conversion of an integral floating value that does not
+    value is determined by 6.3.1.4. Conversion of an integral floating value that does not
     exceed the range of the integer type raises no floating-point exceptions; whether
     conversion of a non-integral floating value raises the ``inexact'' floating-point exception is
-    unspecified.360)
+    unspecified.[360]
 

-
 
 
Footnote 360) ANSI/IEEE 854, but not IEC 60559 (ANSI/IEEE 754), directly specifies that floating-to-integer
          conversions raise the ``inexact'' floating-point exception for non-integer in-range values. In those
@@ -28814,16 +24911,13 @@ the specified values is outside the normal range, the characters stored are unsp
          <math.h>.
 

 
-
+
 

 
F.5 [Binary-decimal conversion]

-

-
-
+
 
1   Conversion from the widest supported IEC 60559 format to decimal with
-    DECIMAL_DIG digits and back is the identity function.361)
+    DECIMAL_DIG digits and back is the identity function.[361]
 

-
 
 
Footnote 361) If the minimum-width IEC 60559 extended format (64 bits of precision) is supported,
          DECIMAL_DIG shall be at least 21. If IEC 60559 double (53 bits of precision) is the widest
@@ -28831,7 +24925,7 @@ the specified values is outside the normal range, the characters stored are unsp
          DBL_DIG are 18 and 15, respectively, for these formats.)
 

 
-
+
 
2   Conversions involving IEC 60559 formats follow all pertinent recommended practice. In
     particular, conversion between any supported IEC 60559 format and decimal with
     DECIMAL_DIG or fewer significant digits is correctly rounded (honoring the current
@@ -28839,99 +24933,81 @@ the specified values is outside the normal range, the characters stored are unsp
     format to decimal with DECIMAL_DIG digits and back is the identity function.
 
 

-
-
+
 
3   Functions such as strtod that convert character sequences to floating types honor the
     rounding direction. Hence, if the rounding direction might be upward or downward, the
     implementation cannot convert a minus-signed sequence by negating the converted
     unsigned sequence.
 

-
-
+
 

 
F.6 [The return statement]

-
 The return statement
-    If the return expression is evaluated in a floating-point format different from the return
-    type, the expression is converted as if by assignment362) to the return type of the function
+
If the return expression is evaluated in a floating-point format different from the return
+    type, the expression is converted as if by assignment[362] to the return type of the function
     and the resulting value is returned to the caller.
 

-
 
 
Footnote 362) Assignment removes any extra range and precision.
 

 
-
+
 

 
F.7 [Contracted expressions]

-

-
-
+
 
1   A contracted expression is correctly rounded (once) and treats infinities, NaNs, signed
     zeros, subnormals, and the rounding directions in a manner consistent with the basic
     arithmetic operations covered by IEC 60559.
     Recommended practice
 

-
-
+
 
2   A contracted expression should raise floating-point exceptions in a manner generally
     consistent with the basic arithmetic operations.
 

-
-
+
 

 
F.8 [Floating-point environment]

-

-
-
+
 
1   The floating-point environment defined in <fenv.h> includes the IEC 60559 floating-
     point exception status flags and directed-rounding control modes. It includes also
     IEC 60559 dynamic rounding precision and trap enablement modes, if the
-    implementation supports them.363)
+    implementation supports them.[363]
 

-
 
 
Footnote 363) This specification does not require dynamic rounding precision nor trap enablement modes.
 

 
-
+
 

 
F.8.1 [Environment management]

-

-
-
+
 
1   IEC 60559 requires that floating-point operations implicitly raise floating-point exception
     status flags, and that rounding control modes can be set explicitly to affect result values of
     floating-point operations. When the state for the FENV_ACCESS pragma (defined in
     <fenv.h>) is ``on'', these changes to the floating-point state are treated as side effects
-    which respect sequence points.364)
+    which respect sequence points.[364]
 
 

-
 
 
Footnote 364) If the state for the FENV_ACCESS pragma is ``off'', the implementation is free to assume the floating-
          point control modes will be the default ones and the floating-point status flags will not be tested,
-         which allows certain optimizations (see F.9).
+         which allows certain optimizations (see F.9).
 

 
-
+
 

 
F.8.2 [Translation]

-

-
-
+
 
1   During translation the IEC 60559 default modes are in effect:
     -- The rounding direction mode is rounding to nearest.
     -- The rounding precision mode (if supported) is set so that results are not shortened.
     -- Trapping or stopping (if supported) is disabled on all floating-point exceptions.
     Recommended practice
 

-
-
+
 
2   The implementation should produce a diagnostic message for each translation-time
-    floating-point exception, other than ``inexact'';365) the implementation should then
+    floating-point exception, other than ``inexact'';[365] the implementation should then
     proceed with the translation of the program.
 

-
 
 
Footnote 365) As floating constants are converted to appropriate internal representations at translation time, their
          conversion is subject to default rounding modes and raises no execution-time floating-point exceptions
@@ -28939,12 +25015,10 @@ the specified values is outside the normal range, the characters stored are unsp
          strtod, provide execution-time conversion of numeric strings.
 

 
-
+
 

 
F.8.3 [Execution]

-

-
-
+
 
1   At program startup the floating-point environment is initialized as prescribed by
     IEC 60559:
     -- All floating-point exception status flags are cleared.
@@ -28953,20 +25027,16 @@ the specified values is outside the normal range, the characters stored are unsp
        shortened.
     -- Trapping or stopping (if supported) is disabled on all floating-point exceptions.
 

-
-
+
 

 
F.8.4 [Constant expressions]

-

-
-
+
 
1   An arithmetic constant expression of floating type, other than one in an initializer for an
     object that has static or thread storage duration, is evaluated (as if) during execution; thus,
     it is affected by any operative floating-point control modes and raises floating-point
     exceptions as required by IEC 60559 (provided the state for the FENV_ACCESS pragma
-    is ``on'').366)
+    is ``on'').[366]
 

-
 
 
Footnote 366) Where the state for the FENV_ACCESS pragma is ``on'', results of inexact expressions like 1.0/3.0
          are affected by rounding modes set at execution time, and expressions such as 0.0/0.0 and
@@ -28985,109 +25055,91 @@ the specified values is outside the normal range, the characters stored are unsp
              }
 

 
-
+
 
2   EXAMPLE
 

-
-
+
 
3   For the static initialization, the division is done at translation time, raising no (execution-time) floating-
     point exceptions. On the other hand, for the three automatic initializations the invalid division occurs at
     execution time.
 
 

-
-
+
 

 
F.8.5 [Initialization]

-

-
-
+
 
1   All computation for automatic initialization is done (as if) at execution time; thus, it is
     affected by any operative modes and raises floating-point exceptions as required by
     IEC 60559 (provided the state for the FENV_ACCESS pragma is ``on''). All computation
     for initialization of objects that have static or thread storage duration is done (as if) at
     translation time.
 

-
-
+
 
2   EXAMPLE
              #include <fenv.h>
              #pragma STDC FENV_ACCESS ON
              void f(void)
              {
-                   float u[] = { 1.1e75 };                  //   raises exceptions
-                   static float v = 1.1e75;                 //   does not raise exceptions
-                   float w = 1.1e75;                        //   raises exceptions
-                   double x = 1.1e75;                       //   may raise exceptions
-                   float y = 1.1e75f;                       //   may raise exceptions
-                   long double z = 1.1e75;                  //   does not raise exceptions
+                   float u[] = { 1.1e75 };                  //   raises exceptions
+                   static float v = 1.1e75;                 //   does not raise exceptions
+                   float w = 1.1e75;                        //   raises exceptions
+                   double x = 1.1e75;                       //   may raise exceptions
+                   float y = 1.1e75f;                       //   may raise exceptions
+                   long double z = 1.1e75;                  //   does not raise exceptions
                    /* ... */
              }
 

-
-
+
 
3   The static initialization of v raises no (execution-time) floating-point exceptions because its computation is
     done at translation time. The automatic initialization of u and w require an execution-time conversion to
-    float of the wider value 1.1e75, which raises floating-point exceptions. The automatic initializations
+    float of the wider value 1.1e75, which raises floating-point exceptions. The automatic initializations
     of x and y entail execution-time conversion; however, in some expression evaluation methods, the
-    conversions is not to a narrower format, in which case no floating-point exception is raised.367) The
+    conversions is not to a narrower format, in which case no floating-point exception is raised.[367] The
     automatic initialization of z entails execution-time conversion, but not to a narrower format, so no floating-
-    point exception is raised. Note that the conversions of the floating constants 1.1e75 and 1.1e75f to
-
-    their internal representations occur at translation time in all cases.
+    point exception is raised. Note that the conversions of the floating constants 1.1e75 and 1.1e75f to
 
 

-
 
 
Footnote 367) Use of float_t and double_t variables increases the likelihood of translation-time computation.
          For example, the automatic initialization
-                  double_t x = 1.1e75;
+                  double_t x = 1.1e75;
          could be done at translation time, regardless of the expression evaluation method.
+    their internal representations occur at translation time in all cases.
 

 
-
+
 

 
F.8.6 [Changing the environment]

-

-
-
-
1   Operations defined in 6.5 and functions and macros defined for the standard libraries
+
+
1   Operations defined in 6.5 and functions and macros defined for the standard libraries
     change floating-point status flags and control modes just as indicated by their
     specifications (including conformance to IEC 60559). They do not change flags or modes
     (so as to be detectable by the user) in any other cases.
 

-
-
+
 
2   If the argument to the feraiseexcept function in <fenv.h> represents IEC 60559
     valid coincident floating-point exceptions for atomic operations (namely ``overflow'' and
     ``inexact'', or ``underflow'' and ``inexact''), then ``overflow'' or ``underflow'' is raised
     before ``inexact''.
 

-
-
+
 

 
F.9 [Optimization]

-

-
-
+
 
1   This section identifies code transformations that might subvert IEC 60559-specified
     behavior, and others that do not.
 

-
-
+
 

 
F.9.1 [Global transformations]

-

-
-
+
 
1   Floating-point arithmetic operations and external function calls may entail side effects
     which optimization shall honor, at least where the state of the FENV_ACCESS pragma is
     ``on''. The flags and modes in the floating-point environment may be regarded as global
     variables; floating-point operations (+, *, etc.) implicitly read the modes and write the
     flags.
 

-
-
+
 
2   Concern about side effects may inhibit code motion and removal of seemingly useless
     code. For example, in
              #include <fenv.h>
@@ -29103,8 +25155,7 @@ the specified values is outside the normal range, the characters stored are unsp
     course these optimizations are valid if the implementation can rule out the nettlesome
     cases.)
 

-
-
+
 
3   This specification does not require support for trap handlers that maintain information
     about the order or count of floating-point exceptions. Therefore, between function calls,
     floating-point exceptions need not be precise: the actual order and number of occurrences
@@ -29112,28 +25163,25 @@ the specified values is outside the normal range, the characters stored are unsp
     the preceding loop could be treated as
              if (0 < n) x + 1;
 

-
-
+
 

 
F.9.2 [Expression transformations]

-

-
-
-
1   x /2  x × 0.5          Although similar transformations involving inexact constants
+
+
1   x /2  x \xD7 0.5          Although similar transformations involving inexact constants
                            generally do not yield numerically equivalent expressions, if the
                            constants are exact then such transformations can be made on
                            IEC 60559 machines and others that round perfectly.
-    1 × x and x /1  x The expressions 1 × x , x /1, and x are equivalent (on IEC 60559
-                      machines, among others).368)
+    1 \xD7 x and x /1  x The expressions 1 \xD7 x , x /1, and x are equivalent (on IEC 60559
+                      machines, among others).[368]
     x / x  1. 0            The expressions x / x and 1. 0 are not equivalent if x can be zero,
                            infinite, or NaN.
     x - y  x + (- y )      The expressions x - y , x + (- y ), and (- y ) + x are equivalent (on
                            IEC 60559 machines, among others).
     x - y  -( y - x )      The expressions x - y and -( y - x ) are not equivalent because 1 - 1
-                           is +0 but -(1 - 1) is -0 (in the default rounding direction).369)
+                           is +0 but -(1 - 1) is -0 (in the default rounding direction).[369]
     x - x  0. 0            The expressions x - x and 0. 0 are not equivalent if x is a NaN or
                            infinite.
-    0 × x  0. 0            The expressions 0 × x and 0. 0 are not equivalent if x is a NaN,
+    0 \xD7 x  0. 0            The expressions 0 \xD7 x and 0. 0 are not equivalent if x is a NaN,
                            infinite, or -0.
     x+0 x                  The expressions x + 0 and x are not equivalent if x is -0, because
                            (-0) + (+0) yields +0 (in the default rounding direction), not -0.
@@ -29146,7 +25194,6 @@ the specified values is outside the normal range, the characters stored are unsp
                            downward).
 
 

-
 
 
Footnote 368) Strict support for signaling NaNs -- not required by this specification -- would invalidate these and
          other transformations that remove arithmetic operators.
@@ -29155,18 +25202,16 @@ the specified values is outside the normal range, the characters stored are unsp
 
 
Footnote 369) IEC 60559 prescribes a signed zero to preserve mathematical identities across certain discontinuities.
          Examples include:
-            1/(1/ ± ) is ± 
+            1/(1/ \xB1 ) is \xB1
          and
             conj(csqrt( z )) is csqrt(conj( z )),
          for complex z .
 

 
-
+
 

 
F.9.3 [Relational operators]

-

-
-
+
 
1   x  x  false             The expression x  x is true if x is a NaN.
     x = x  true             The expression x = x is false if x is a NaN.
     x < y  isless( x , y ) (and similarly for , >, ) Though numerically equal, these
@@ -29179,8 +25224,7 @@ the specified values is outside the normal range, the characters stored are unsp
     The sense of relational operators shall be maintained. This includes handling unordered
     cases as expressed by the source code.
 

-
-
+
 
2   EXAMPLE
              // calls g and raises ``invalid'' if a and b are unordered
              if (a < b)
@@ -29212,461 +25256,351 @@ the specified values is outside the normal range, the characters stored are unsp
                   f();
 
 

-
-
+
 

 
F.9.4 [Constant arithmetic]

-

-
-
+
 
1   The implementation shall honor floating-point exceptions raised by execution-time
-    constant arithmetic wherever the state of the FENV_ACCESS pragma is ``on''. (See F.8.4
-    and F.8.5.) An operation on constants that raises no floating-point exception can be
+    constant arithmetic wherever the state of the FENV_ACCESS pragma is ``on''. (See F.8.4
+    and F.8.5.) An operation on constants that raises no floating-point exception can be
     folded during translation, except, if the state of the FENV_ACCESS pragma is ``on'', a
     further check is required to assure that changing the rounding direction to downward does
-    not alter the sign of the result,370) and implementations that support dynamic rounding
+    not alter the sign of the result,[370] and implementations that support dynamic rounding
     precision modes shall assure further that the result of the operation raises no floating-
     point exception when converted to the semantic type of the operation.
 

-
 
 
Footnote 370) 0 - 0 yields -0 instead of +0 just when the rounding direction is downward.
 

 
-
+
 

-
F.10 [Mathematics ]

-

-
-
+
F.10 [Mathematics <math.h>]

+
 
1   This subclause contains specifications of <math.h> facilities that are particularly suited
     for IEC 60559 implementations.
 

-
-
+
 
2   The Standard C macro HUGE_VAL and its float and long double analogs,
     HUGE_VALF and HUGE_VALL, expand to expressions whose values are positive
     infinities.
 

-
-
+
 
3   Special cases for functions in <math.h> are covered directly or indirectly by
-    IEC 60559. The functions that IEC 60559 specifies directly are identified in F.3. The
+    IEC 60559. The functions that IEC 60559 specifies directly are identified in F.3. The
     other functions in <math.h> treat infinities, NaNs, signed zeros, subnormals, and
     (provided the state of the FENV_ACCESS pragma is ``on'') the floating-point status flags
     in a manner consistent with the basic arithmetic operations covered by IEC 60559.
 

-
-
+
 
4   The expression math_errhandling & MATH_ERREXCEPT shall evaluate to a
     nonzero value.
 

-
-
+
 
5   The ``invalid'' and ``divide-by-zero'' floating-point exceptions are raised as specified in
     subsequent subclauses of this annex.
 

-
-
+
 
6   The ``overflow'' floating-point exception is raised whenever an infinity -- or, because of
     rounding direction, a maximal-magnitude finite number -- is returned in lieu of a value
     whose magnitude is too large.
 

-
-
+
 
7   The ``underflow'' floating-point exception is raised whenever a result is tiny (essentially
-    subnormal or zero) and suffers loss of accuracy.371)
+    subnormal or zero) and suffers loss of accuracy.[371]
 
 

-
 
 
Footnote 371) IEC 60559 allows different definitions of underflow. They all result in the same values, but differ on
          when the floating-point exception is raised.
 

 
-
+
 
8    Whether or when library functions raise the ``inexact'' floating-point exception is
      unspecified, unless explicitly specified otherwise.
 

-
-
+
 
9    Whether or when library functions raise an undeserved ``underflow'' floating-point
-     exception is unspecified.372) Otherwise, as implied by F.8.6, the <math.h> functions do
+     exception is unspecified.[372] Otherwise, as implied by F.8.6, the <math.h> functions do
      not raise spurious floating-point exceptions (detectable by the user), other than the
      ``inexact'' floating-point exception.
 

-
 
 
Footnote 372) It is intended that undeserved ``underflow'' and ``inexact'' floating-point exceptions are raised only if
           avoiding them would be too costly.
 

 
-
+
 
10   Whether the functions honor the rounding direction mode is implementation-defined,
      unless explicitly specified otherwise.
 

-
-
+
 
11   Functions with a NaN argument return a NaN result and raise no floating-point exception,
      except where stated otherwise.
 

-
-
+
 
12   The specifications in the following subclauses append to the definitions in <math.h>.
      For families of functions, the specifications apply to all of the functions even though only
-     the principal function is shown. Unless otherwise specified, where the symbol ``±''
+     the principal function is shown. Unless otherwise specified, where the symbol ``\xB1''
      occurs in both an argument and the result, the result has the same sign as the argument.
      Recommended practice
 

-
-
+
 
13   If a function with one or more NaN arguments returns a NaN result, the result should be
      the same as one of the NaN arguments (after possible type conversion), except perhaps
      for the sign.
 

-
-
+
 

 
F.10.1 [Trigonometric functions]

-
 Trigonometric functions
-

-
-
+
 

 
F.10.1.1 [The acos functions]

-

-
-
+
 
1    -- acos(1) returns +0.
      -- acos( x ) returns a NaN and raises the ``invalid'' floating-point exception for
         | x | > 1.
 

-
-
+
 

 
F.10.1.2 [The asin functions]

-

-
-
-
1    -- asin(±0) returns ±0.
+
+
1    -- asin(\xB10) returns \xB10.
      -- asin( x ) returns a NaN and raises the ``invalid'' floating-point exception for
         | x | > 1.
 
 

-
-
+
 

 
F.10.1.3 [The atan functions]

-

-
-
-
1   -- atan(±0) returns ±0.
-    -- atan(±) returns ± /2.
+
+
1   -- atan(\xB10) returns \xB10.
+    -- atan(\xB1) returns \xB1 /2.
 

-
-
+
 

 
F.10.1.4 [The atan2 functions]

-

-
-
-
1   -- atan2(±0, -0) returns ± .373)
-    -- atan2(±0, +0) returns ±0.
-    -- atan2(±0, x ) returns ± for x < 0.
-    -- atan2(±0, x ) returns ±0 for x > 0.
-    -- atan2( y , ±0) returns - /2 for y < 0.
-    -- atan2( y , ±0) returns  /2 for y > 0.
-    -- atan2(± y , -) returns ± for finite y > 0.
-    -- atan2(± y , +) returns ±0 for finite y > 0.
-    -- atan2(±, x ) returns ± /2 for finite x .
-    -- atan2(±, -) returns ±3 /4.
-    -- atan2(±, +) returns ± /4.
+
+
1   -- atan2(\xB10, -0) returns \xB1 .[373]
+    -- atan2(\xB10, +0) returns \xB10.
+    -- atan2(\xB10, x ) returns \xB1 for x < 0.
+    -- atan2(\xB10, x ) returns \xB10 for x > 0.
+    -- atan2( y , \xB10) returns - /2 for y < 0.
+    -- atan2( y , \xB10) returns  /2 for y > 0.
+    -- atan2(\xB1 y , -) returns \xB1 for finite y > 0.
+    -- atan2(\xB1 y , +) returns \xB10 for finite y > 0.
+    -- atan2(\xB1, x ) returns \xB1 /2 for finite x .
+    -- atan2(\xB1, -) returns \xB13 /4.
+    -- atan2(\xB1, +) returns \xB1 /4.
 

-
 
 
Footnote 373) atan2(0, 0) does not raise the ``invalid'' floating-point exception, nor does atan2( y ,   0) raise
          the ``divide-by-zero'' floating-point exception.
 

 
-
+
 

 
F.10.1.5 [The cos functions]

-

-
-
-
1   -- cos(±0) returns 1.
-    -- cos(±) returns a NaN and raises the ``invalid'' floating-point exception.
+
+
1   -- cos(\xB10) returns 1.
+    -- cos(\xB1) returns a NaN and raises the ``invalid'' floating-point exception.
 

-
-
+
 

 
F.10.1.6 [The sin functions]

-

-
-
-
1   -- sin(±0) returns ±0.
-    -- sin(±) returns a NaN and raises the ``invalid'' floating-point exception.
+
+
1   -- sin(\xB10) returns \xB10.
+    -- sin(\xB1) returns a NaN and raises the ``invalid'' floating-point exception.
 

-
-
+
 

 
F.10.1.7 [The tan functions]

-

-
-
-
1   -- tan(±0) returns ±0.
-    -- tan(±) returns a NaN and raises the ``invalid'' floating-point exception.
+
+
1   -- tan(\xB10) returns \xB10.
+    -- tan(\xB1) returns a NaN and raises the ``invalid'' floating-point exception.
 
 

-
-
+
 

 
F.10.2 [Hyperbolic functions]

-
 Hyperbolic functions
-

-
-
+
 

 
F.10.2.1 [The acosh functions]

-

-
-
+
 
1   -- acosh(1) returns +0.
     -- acosh( x ) returns a NaN and raises the ``invalid'' floating-point exception for x < 1.
     -- acosh(+) returns +.
 

-
-
+
 

 
F.10.2.2 [The asinh functions]

-

-
-
-
1   -- asinh(±0) returns ±0.
-    -- asinh(±) returns ±.
+
+
1   -- asinh(\xB10) returns \xB10.
+    -- asinh(\xB1) returns \xB1.
 

-
-
+
 

 
F.10.2.3 [The atanh functions]

-

-
-
-
1   -- atanh(±0) returns ±0.
-    -- atanh(±1) returns ± and raises the ``divide-by-zero'' floating-point exception.
+
+
1   -- atanh(\xB10) returns \xB10.
+    -- atanh(\xB11) returns \xB1 and raises the ``divide-by-zero'' floating-point exception.
     -- atanh( x ) returns a NaN and raises the ``invalid'' floating-point exception for
        | x | > 1.
 

-
-
+
 

 
F.10.2.4 [The cosh functions]

-

-
-
-
1   -- cosh(±0) returns 1.
-    -- cosh(±) returns +.
+
+
1   -- cosh(\xB10) returns 1.
+    -- cosh(\xB1) returns +.
 

-
-
+
 

 
F.10.2.5 [The sinh functions]

-

-
-
-
1   -- sinh(±0) returns ±0.
-    -- sinh(±) returns ±.
+
+
1   -- sinh(\xB10) returns \xB10.
+    -- sinh(\xB1) returns \xB1.
 

-
-
+
 

 
F.10.2.6 [The tanh functions]

-

-
-
-
1   -- tanh(±0) returns ±0.
-    -- tanh(±) returns ±1.
+
+
1   -- tanh(\xB10) returns \xB10.
+    -- tanh(\xB1) returns \xB11.
 

-
-
+
 

 
F.10.3 [Exponential and logarithmic functions]

-
 Exponential and logarithmic functions
-

-
-
+
 

 
F.10.3.1 [The exp functions]

-

-
-
-
1   -- exp(±0) returns 1.
+
+
1   -- exp(\xB10) returns 1.
     -- exp(-) returns +0.
     -- exp(+) returns +.
 

-
-
+
 

 
F.10.3.2 [The exp2 functions]

-

-
-
-
1   -- exp2(±0) returns 1.
+
+
1   -- exp2(\xB10) returns 1.
     -- exp2(-) returns +0.
     -- exp2(+) returns +.
 

-
-
+
 

 
F.10.3.3 [The expm1 functions]

-

-
-
-
1   -- expm1(±0) returns ±0.
+
+
1   -- expm1(\xB10) returns \xB10.
     -- expm1(-) returns -1.
     -- expm1(+) returns +.
 

-
-
+
 

 
F.10.3.4 [The frexp functions]

-

-
-
-
1   -- frexp(±0, exp) returns ±0, and stores 0 in the object pointed to by exp.
-    -- frexp(±, exp) returns ±, and stores an unspecified value in the object
+
+
1   -- frexp(\xB10, exp) returns \xB10, and stores 0 in the object pointed to by exp.
+    -- frexp(\xB1, exp) returns \xB1, and stores an unspecified value in the object
        pointed to by exp.
     -- frexp(NaN, exp) stores an unspecified value in the object pointed to by exp
        (and returns a NaN).
 

-
-
+
 
2   frexp raises no floating-point exceptions.
 

-
-
+
 
3   When the radix of the argument is a power of 2, the returned value is exact and is
     independent of the current rounding direction mode.
 

-
-
+
 
4   On a binary system, the body of the frexp function might be
             {
                    *exp = (value == 0) ? 0 : (int)(1 + logb(value));
                    return scalbn(value, -(*exp));
             }
 

-
-
+
 

 
F.10.3.5 [The ilogb functions]

-

-
-
+
 
1   When the correct result is representable in the range of the return type, the returned value
     is exact and is independent of the current rounding direction mode.
 

-
-
+
 
2   If the correct result is outside the range of the return type, the numeric result is
     unspecified and the ``invalid'' floating-point exception is raised.
 

-
-
+
 
3   ilogb( x ), for x zero, infinite, or NaN, raises the ``invalid'' floating-point exception and
-    returns the value specified in 7.12.6.5.
+    returns the value specified in 7.12.6.5.
 

-
-
+
 

 
F.10.3.6 [The ldexp functions]

-

-
-
+
 
1   On a binary system, ldexp(x, exp) is equivalent to scalbn(x, exp).
 

-
-
+
 

 
F.10.3.7 [The log functions]

-

-
-
-
1   -- log(±0) returns - and raises the ``divide-by-zero'' floating-point exception.
+
+
1   -- log(\xB10) returns - and raises the ``divide-by-zero'' floating-point exception.
     -- log(1) returns +0.
     -- log( x ) returns a NaN and raises the ``invalid'' floating-point exception for x < 0.
     -- log(+) returns +.
 

-
-
+
 

 
F.10.3.8 [The log10 functions]

-

-
-
-
1   -- log10(±0) returns - and raises the ``divide-by-zero'' floating-point exception.
+
+
1   -- log10(\xB10) returns - and raises the ``divide-by-zero'' floating-point exception.
     -- log10(1) returns +0.
     -- log10( x ) returns a NaN and raises the ``invalid'' floating-point exception for x < 0.
     -- log10(+) returns +.
 

-
-
+
 

 
F.10.3.9 [The log1p functions]

-

-
-
-
1   -- log1p(±0) returns ±0.
+
+
1   -- log1p(\xB10) returns \xB10.
     -- log1p(-1) returns - and raises the ``divide-by-zero'' floating-point exception.
     -- log1p( x ) returns a NaN and raises the ``invalid'' floating-point exception for
        x < -1.
     -- log1p(+) returns +.
 

-
-
+
 

 
F.10.3.10 [The log2 functions]

-

-
-
-
1   -- log2(±0) returns - and raises the ``divide-by-zero'' floating-point exception.
+
+
1   -- log2(\xB10) returns - and raises the ``divide-by-zero'' floating-point exception.
     -- log2(1) returns +0.
     -- log2( x ) returns a NaN and raises the ``invalid'' floating-point exception for x < 0.
     -- log2(+) returns +.
 

-
-
+
 

 
F.10.3.11 [The logb functions]

-

-
-
-
1   -- logb(±0) returns - and raises the ``divide-by-zero'' floating-point exception.
-    -- logb(±) returns +.
+
+
1   -- logb(\xB10) returns - and raises the ``divide-by-zero'' floating-point exception.
+    -- logb(\xB1) returns +.
 

-
-
+
 
2   The returned value is exact and is independent of the current rounding direction mode.
 

-
-
+
 

 
F.10.3.12 [The modf functions]

-

-
-
-
1   -- modf(± x , iptr) returns a result with the same sign as x .
-    -- modf(±, iptr) returns ±0 and stores ± in the object pointed to by iptr.
+
+
1   -- modf(\xB1 x , iptr) returns a result with the same sign as x .
+    -- modf(\xB1, iptr) returns \xB10 and stores \xB1 in the object pointed to by iptr.
     -- modf(NaN, iptr) stores a NaN in the object pointed to by iptr (and returns a
        NaN).
 

-
-
+
 
2   The returned values are exact and are independent of the current rounding direction
     mode.
 

-
-
+
 
3   modf behaves as though implemented by
             #include <math.h>
             #include <fenv.h>
@@ -29682,81 +25616,61 @@ the specified values is outside the normal range, the characters stored are unsp
                            value - (*iptr), value);
             }
 

-
-
+
 

 
F.10.3.13 [The scalbn and scalbln functions]

-

-
-
-
1   -- scalbn(±0, n) returns ±0.
+
+
1   -- scalbn(\xB10, n) returns \xB10.
     -- scalbn( x , 0) returns x .
-    -- scalbn(±, n) returns ±.
+    -- scalbn(\xB1, n) returns \xB1.
 

-
-
+
 
2   If the calculation does not overflow or underflow, the returned value is exact and
     independent of the current rounding direction mode.
 

-
-
+
 

 
F.10.4 [Power and absolute value functions]

-
 Power and absolute value functions
-

-
-
+
 

 
F.10.4.1 [The cbrt functions]

-

-
-
-
1   -- cbrt(±0) returns ±0.
-    -- cbrt(±) returns ±.
+
+
1   -- cbrt(\xB10) returns \xB10.
+    -- cbrt(\xB1) returns \xB1.
 

-
-
+
 

 
F.10.4.2 [The fabs functions]

-

-
-
-
1   -- fabs(±0) returns +0.
-    -- fabs(±) returns +.
+
+
1   -- fabs(\xB10) returns +0.
+    -- fabs(\xB1) returns +.
 

-
-
+
 
2   The returned value is exact and is independent of the current rounding direction mode.
 

-
-
+
 

 
F.10.4.3 [The hypot functions]

-

-
-
+
 
1   -- hypot( x , y ), hypot( y , x ), and hypot( x , - y ) are equivalent.
-    -- hypot( x , ±0) is equivalent to fabs( x ).
-    -- hypot(±, y ) returns +, even if y is a NaN.
+    -- hypot( x , \xB10) is equivalent to fabs( x ).
+    -- hypot(\xB1, y ) returns +, even if y is a NaN.
 

-
-
+
 

 
F.10.4.4 [The pow functions]

-

-
-
-
1   -- pow(±0, y ) returns ± and raises the ``divide-by-zero'' floating-point exception
+
+
1   -- pow(\xB10, y ) returns \xB1 and raises the ``divide-by-zero'' floating-point exception
        for y an odd integer < 0.
-    -- pow(±0, y ) returns + and raises the ``divide-by-zero'' floating-point exception
+    -- pow(\xB10, y ) returns + and raises the ``divide-by-zero'' floating-point exception
        for y < 0, finite, and not an odd integer.
-    -- pow(±0, -) returns + and may raise the ``divide-by-zero'' floating-point
+    -- pow(\xB10, -) returns + and may raise the ``divide-by-zero'' floating-point
        exception.
-    -- pow(±0, y ) returns ±0 for y an odd integer > 0.
-    -- pow(±0, y ) returns +0 for y > 0 and not an odd integer.
-    -- pow(-1, ±) returns 1.
+    -- pow(\xB10, y ) returns \xB10 for y an odd integer > 0.
+    -- pow(\xB10, y ) returns +0 for y > 0 and not an odd integer.
+    -- pow(-1, \xB1) returns 1.
     -- pow(+1, y ) returns 1 for any y , even a NaN.
-    -- pow( x , ±0) returns 1 for any x , even a NaN.
+    -- pow( x , \xB10) returns 1 for any x , even a NaN.
     -- pow( x , y ) returns a NaN and raises the ``invalid'' floating-point exception for
        finite x < 0 and finite non-integer y .
     -- pow( x , -) returns + for | x | < 1.
@@ -29770,49 +25684,34 @@ the specified values is outside the normal range, the characters stored are unsp
     -- pow(+, y ) returns +0 for y < 0.
     -- pow(+, y ) returns + for y > 0.
 

-
-
+
 

 
F.10.4.5 [The sqrt functions]

-

-
-
+
 
1   sqrt is fully specified as a basic arithmetic operation in IEC 60559. The returned value
     is dependent on the current rounding direction mode.
 

-
-
+
 

 
F.10.5 [Error and gamma functions]

-
 Error and gamma functions
-

-
-
+
 

 
F.10.5.1 [The erf functions]

-

-
-
-
1   -- erf(±0) returns ±0.
-    -- erf(±) returns ±1.
+
+
1   -- erf(\xB10) returns \xB10.
+    -- erf(\xB1) returns \xB11.
 

-
-
+
 

 
F.10.5.2 [The erfc functions]

-

-
-
+
 
1   -- erfc(-) returns 2.
     -- erfc(+) returns +0.
 

-
-
+
 

 
F.10.5.3 [The lgamma functions]

-

-
-
+
 
1   -- lgamma(1) returns +0.
     -- lgamma(2) returns +0.
     -- lgamma( x ) returns + and raises the ``divide-by-zero'' floating-point exception for
@@ -29820,42 +25719,31 @@ the specified values is outside the normal range, the characters stored are unsp
     -- lgamma(-) returns +.
     -- lgamma(+) returns +.
 

-
-
+
 

 
F.10.5.4 [The tgamma functions]

-

-
-
-
1   -- tgamma(±0) returns ± and raises the ``divide-by-zero'' floating-point exception.
+
+
1   -- tgamma(\xB10) returns \xB1 and raises the ``divide-by-zero'' floating-point exception.
     -- tgamma( x ) returns a NaN and raises the ``invalid'' floating-point exception for x a
        negative integer.
     -- tgamma(-) returns a NaN and raises the ``invalid'' floating-point exception.
     -- tgamma(+) returns +.
 
 

-
-
+
 

 
F.10.6 [Nearest integer functions]

-
 Nearest integer functions
-

-
-
+
 

 
F.10.6.1 [The ceil functions]

-

-
-
-
1   -- ceil(±0) returns ±0.
-    -- ceil(±) returns ±.
+
+
1   -- ceil(\xB10) returns \xB10.
+    -- ceil(\xB1) returns \xB1.
 

-
-
+
 
2   The returned value is independent of the current rounding direction mode.
 

-
-
+
 
3   The double version of ceil behaves as though implemented by
            #include <math.h>
            #include <fenv.h>
@@ -29870,62 +25758,47 @@ the specified values is outside the normal range, the characters stored are unsp
                 return result;
            }
 

-
-
+
 
4   The ceil functions may, but are not required to, raise the ``inexact'' floating-point
     exception for finite non-integer arguments, as this implementation does.
 

-
-
+
 

 
F.10.6.2 [The floor functions]

-

-
-
-
1   -- floor(±0) returns ±0.
-    -- floor(±) returns ±.
+
+
1   -- floor(\xB10) returns \xB10.
+    -- floor(\xB1) returns \xB1.
 

-
-
+
 
2   The returned value and is independent of the current rounding direction mode.
 

-
-
-
3   See the sample implementation for ceil in F.10.6.1. The floor functions may, but are
+
+
3   See the sample implementation for ceil in F.10.6.1. The floor functions may, but are
     not required to, raise the ``inexact'' floating-point exception for finite non-integer
     arguments, as that implementation does.
 

-
-
+
 

 
F.10.6.3 [The nearbyint functions]

-

-
-
+
 
1   The nearbyint functions use IEC 60559 rounding according to the current rounding
     direction. They do not raise the ``inexact'' floating-point exception if the result differs in
     value from the argument.
-    -- nearbyint(±0) returns ±0 (for all rounding directions).
-    -- nearbyint(±) returns ± (for all rounding directions).
+    -- nearbyint(\xB10) returns \xB10 (for all rounding directions).
+    -- nearbyint(\xB1) returns \xB1 (for all rounding directions).
 
 

-
-
+
 

 
F.10.6.4 [The rint functions]

-

-
-
+
 
1   The rint functions differ from the nearbyint functions only in that they do raise the
     ``inexact'' floating-point exception if the result differs in value from the argument.
 

-
-
+
 

 
F.10.6.5 [The lrint and llrint functions]

-

-
-
+
 
1   The lrint and llrint functions provide floating-to-integer conversion as prescribed
     by IEC 60559. They round according to the current rounding direction. If the rounded
     value is outside the range of the return type, the numeric result is unspecified and the
@@ -29933,22 +25806,17 @@ the specified values is outside the normal range, the characters stored are unsp
     exception and the result differs from the argument, they raise the ``inexact'' floating-point
     exception.
 

-
-
+
 

 
F.10.6.6 [The round functions]

-

-
-
-
1   -- round(±0) returns ±0.
-    -- round(±) returns ±.
+
+
1   -- round(\xB10) returns \xB10.
+    -- round(\xB1) returns \xB1.
 

-
-
+
 
2   The returned value is independent of the current rounding direction mode.
 

-
-
+
 
3   The double version of round behaves as though implemented by
             #include <math.h>
             #include <fenv.h>
@@ -29969,61 +25837,46 @@ the specified values is outside the normal range, the characters stored are unsp
     The round functions may, but are not required to, raise the ``inexact'' floating-point
     exception for finite non-integer numeric arguments, as this implementation does.
 

-
-
+
 

 
F.10.6.7 [The lround and llround functions]

-

-
-
+
 
1   The lround and llround functions differ from the lrint and llrint functions
     with the default rounding direction just in that the lround and llround functions
     round halfway cases away from zero and need not raise the ``inexact'' floating-point
     exception for non-integer arguments that round to within the range of the return type.
 

-
-
+
 

 
F.10.6.8 [The trunc functions]

-

-
-
+
 
1   The trunc functions use IEC 60559 rounding toward zero (regardless of the current
     rounding direction). The returned value is exact.
-    -- trunc(±0) returns ±0.
-    -- trunc(±) returns ±.
+    -- trunc(\xB10) returns \xB10.
+    -- trunc(\xB1) returns \xB1.
 

-
-
+
 
2   The returned value is independent of the current rounding direction mode. The trunc
     functions may, but are not required to, raise the ``inexact'' floating-point exception for
     finite non-integer arguments.
 

-
-
+
 

 
F.10.7 [Remainder functions]

-
 Remainder functions
-

-
-
+
 

 
F.10.7.1 [The fmod functions]

-

-
-
-
1   -- fmod(±0, y ) returns ±0 for y not zero.
+
+
1   -- fmod(\xB10, y ) returns \xB10 for y not zero.
     -- fmod( x , y ) returns a NaN and raises the ``invalid'' floating-point exception for x
        infinite or y zero (and neither is a NaN).
-    -- fmod( x , ±) returns x for x not infinite.
+    -- fmod( x , \xB1) returns x for x not infinite.
 

-
-
+
 
2   When subnormal results are supported, the returned value is exact and is independent of
     the current rounding direction mode.
 

-
-
+
 
3   The double version of fmod behaves as though implemented by
            #include <math.h>
            #include <fenv.h>
@@ -30036,165 +25889,117 @@ the specified values is outside the normal range, the characters stored are unsp
                 return copysign(result, x);
            }
 

-
-
+
 

 
F.10.7.2 [The remainder functions]

-

-
-
+
 
1   The remainder functions are fully specified as a basic arithmetic operation in
     IEC 60559.
 

-
-
+
 
2   When subnormal results are supported, the returned value is exact and is independent of
     the current rounding direction mode.
 

-
-
+
 

 
F.10.7.3 [The remquo functions]

-

-
-
+
 
1   The remquo functions follow the specifications for the remainder functions. They
     have no further specifications special to IEC 60559 implementations.
 

-
-
+
 
2   When subnormal results are supported, the returned value is exact and is independent of
     the current rounding direction mode.
 

-
-
+
 

 
F.10.8 [Manipulation functions]

-
 Manipulation functions
-

-
-
+
 

 
F.10.8.1 [The copysign functions]

-

-
-
+
 
1   copysign is specified in the Appendix to IEC 60559.
 

-
-
+
 
2   The returned value is exact and is independent of the current rounding direction mode.
 

-
-
+
 

 
F.10.8.2 [The nan functions]

-

-
-
+
 
1   All IEC 60559 implementations support quiet NaNs, in all floating formats.
 

-
-
+
 
2   The returned value is exact and is independent of the current rounding direction mode.
 

-
-
+
 

 
F.10.8.3 [The nextafter functions]

-

-
-
+
 
1   -- nextafter( x , y ) raises the ``overflow'' and ``inexact'' floating-point exceptions
        for x finite and the function value infinite.
     -- nextafter( x , y ) raises the ``underflow'' and ``inexact'' floating-point
        exceptions for the function value subnormal or zero and x  y .
 

-
-
+
 
2   Even though underflow or overflow can occur, the returned value is independent of the
     current rounding direction mode.
 

-
-
+
 

 
F.10.8.4 [The nexttoward functions]

-

-
-
+
 
1   No additional requirements beyond those on nextafter.
 

-
-
+
 
2   Even though underflow or overflow can occur, the returned value is independent of the
     current rounding direction mode.
 

-
-
+
 

 
F.10.9 [Maximum, minimum, and positive difference functions]

-
 Maximum, minimum, and positive difference functions
-

-
-
+
 

 
F.10.9.1 [The fdim functions]

-

-
-
+
 
1   No additional requirements.
 

-
-
+
 

 
F.10.9.2 [The fmax functions]

-

-
-
+
 
1   If just one argument is a NaN, the fmax functions return the other argument (if both
     arguments are NaNs, the functions return a NaN).
 

-
-
+
 
2   The returned value is exact and is independent of the current rounding direction mode.
 

-
-
-
3   The body of the fmax function might be374)
+
+
3   The body of the fmax function might be[374]
             { return (isgreaterequal(x, y) ||
                  isnan(y)) ? x : y; }
 

-
 
 
Footnote 374) Ideally, fmax would be sensitive to the sign of zero, for example fmax(-0. 0,   +0. 0) would
          return +0; however, implementation in software might be impractical.
 

 
-
+
 

 
F.10.9.3 [The fmin functions]

-

-
-
-
1   The fmin functions are analogous to the fmax functions (see F.10.9.2).
+
+
1   The fmin functions are analogous to the fmax functions (see F.10.9.2).
 

-
-
+
 
2   The returned value is exact and is independent of the current rounding direction mode.
 

-
-
+
 

 
F.10.10 [Floating multiply-add]

-
 Floating multiply-add
-

-
-
+
 

 
F.10.10.1 [The fma functions]

-

-
-
+
 
1   -- fma( x , y , z ) computes xy + z , correctly rounded once.
     -- fma( x , y , z ) returns a NaN and optionally raises the ``invalid'' floating-point
        exception if one of x and y is infinite, the other is zero, and z is a NaN.
@@ -30204,175 +26009,135 @@ the specified values is outside the normal range, the characters stored are unsp
        times y is an exact infinity and z is also an infinity but with the opposite sign.
 
 

-
-
+
 

 
F.10.11 [Comparison macros]

-

-
-
-
1   Relational operators and their corresponding comparison macros (7.12.14) produce
+
+
1   Relational operators and their corresponding comparison macros (7.12.14) produce
     equivalent result values, even if argument values are represented in wider formats. Thus,
     comparison macro arguments represented in formats wider than their semantic types are
     not converted to the semantic types, unless the wide evaluation method converts operands
     of relational operators to their semantic types. The standard wide evaluation methods
-    characterized by FLT_EVAL_METHOD equal to 1 or 2 (5.2.4.2.2), do not convert
+    characterized by FLT_EVAL_METHOD equal to 1 or 2 (5.2.4.2.2), do not convert
     operands of relational operators to their semantic types.
                                            Annex G
                                           (normative)
 

-
-
+
 

 
G. [IEC 60559-compatible complex arithmetic]

-
 IEC 60559-compatible complex arithmetic
-

-
-
+
 

 
G.1 [Introduction]

-

-
-
+
 
1   This annex supplements annex F to specify complex arithmetic for compatibility with
     IEC 60559 real floating-point arithmetic. An implementation that defines
-    _ _STDC_IEC_559_COMPLEX_ _ shall conform to the specifications in this annex.375)
+    _ _STDC_IEC_559_COMPLEX_ _ shall conform to the specifications in this annex.[375]
 

-
 
 
Footnote 375) Implementations that do not define _ _STDC_IEC_559_COMPLEX_ _ are not required to conform
          to these specifications.
 

 
-
+
 

 
G.2 [Types]

-

-
-
+
 
1   There is a new keyword _Imaginary, which is used to specify imaginary types. It is
     used as a type specifier within declaration specifiers in the same way as _Complex is
     (thus, _Imaginary float is a valid type name).
 

-
-
+
 
2   There are three imaginary types, designated as float _Imaginary, double
     _Imaginary, and long double _Imaginary. The imaginary types (along with
     the real floating and complex types) are floating types.
 

-
-
+
 
3   For imaginary types, the corresponding real type is given by deleting the keyword
     _Imaginary from the type name.
 

-
-
+
 
4   Each imaginary type has the same representation and alignment requirements as the
     corresponding real type. The value of an object of imaginary type is the value of the real
     representation times the imaginary unit.
 

-
-
+
 
5   The imaginary type domain comprises the imaginary types.
 

-
-
+
 

 
G.3 [Conventions]

-

-
-
+
 
1   A complex or imaginary value with at least one infinite part is regarded as an infinity
     (even if its other part is a NaN). A complex or imaginary value is a finite number if each
     of its parts is a finite number (neither infinite nor NaN). A complex or imaginary value is
     a zero if each of its parts is a zero.
 
 

-
-
+
 

 
G.4 [Conversions]

-
 Conversions
-

-
-
+
 

 
G.4.1 [Imaginary types]

-

-
-
+
 
1   Conversions among imaginary types follow rules analogous to those for real floating
     types.
 

-
-
+
 

 
G.4.2 [Real and imaginary]

-

-
-
-
1   When a value of imaginary type is converted to a real type other than _Bool,376) the
+
+
1   When a value of imaginary type is converted to a real type other than _Bool,[376] the
     result is a positive zero.
 

-
 
-
Footnote 376) See 6.3.1.2.
+
Footnote 376) See 6.3.1.2.
 

 
-
+
 
2   When a value of real type is converted to an imaginary type, the result is a positive
     imaginary zero.
 

-
-
+
 

 
G.4.3 [Imaginary and complex]

-

-
-
+
 
1   When a value of imaginary type is converted to a complex type, the real part of the
     complex result value is a positive zero and the imaginary part of the complex result value
     is determined by the conversion rules for the corresponding real types.
 

-
-
+
 
2   When a value of complex type is converted to an imaginary type, the real part of the
     complex value is discarded and the value of the imaginary part is converted according to
     the conversion rules for the corresponding real types.
 

-
-
+
 

 
G.5 [Binary operators]

-

-
-
-
1   The following subclauses supplement 6.5 in order to specify the type of the result for an
+
+
1   The following subclauses supplement 6.5 in order to specify the type of the result for an
     operation with an imaginary operand.
 

-
-
+
 
2   For most operand types, the value of the result of a binary operator with an imaginary or
     complex operand is completely determined, with reference to real arithmetic, by the usual
     mathematical formula. For some operand types, the usual mathematical formula is
     problematic because of its treatment of infinities and because of undue overflow or
-    underflow; in these cases the result satisfies certain properties (specified in G.5.1), but is
+    underflow; in these cases the result satisfies certain properties (specified in G.5.1), but is
     not completely determined.
 
 

-
-
+
 

 
G.5.1 [Multiplicative operators]

-

-
-
-
1   If one operand has real type and the other operand has imaginary type, then the result has
+
+
1 Semantics
+   If one operand has real type and the other operand has imaginary type, then the result has
     imaginary type. If both operands have imaginary type, then the result has real type. (If
     either operand has complex type, then the result has complex type.)
 

-
-
+
 
2   If the operands are not both complex, then the result and floating-point exception
     behavior of the * operator is defined by the usual mathematical formula:
            *                    u                      iv                      u + iv
@@ -30383,8 +26148,7 @@ the specified values is outside the normal range, the characters stored are unsp
 
            x + iy       ( xu) + i ( yu)         (- yv ) + i ( xv )
 

-
-
+
 
3   If the second operand is not complex, then the result and floating-point exception
     behavior of the / operator is defined by the usual mathematical formula:
            /                     u                          iv
@@ -30395,35 +26159,31 @@ the specified values is outside the normal range, the characters stored are unsp
 
            x + iy       ( x /u ) + i ( y /u )     ( y /v ) + i (- x /v )
 

-
-
+
 
4   The * and / operators satisfy the following infinity properties for all real, imaginary, and
-    complex operands:377)
+    complex operands:[377]
     -- if one operand is an infinity and the other operand is a nonzero finite number or an
        infinity, then the result of the * operator is an infinity;
     -- if the first operand is an infinity and the second operand is a finite number, then the
        result of the / operator is an infinity;
     -- if the first operand is a finite number and the second operand is an infinity, then the
        result of the / operator is a zero;
-
-    -- if the first operand is a nonzero finite number or an infinity and the second operand is
-       a zero, then the result of the / operator is an infinity.
 

-
 
 
Footnote 377) These properties are already implied for those cases covered in the tables, but are required for all cases
          (at least where the state for CX_LIMITED_RANGE is ``off'').
+    -- if the first operand is a nonzero finite number or an infinity and the second operand is
+       a zero, then the result of the / operator is an infinity.
 

 
-
+
 
5   If both operands of the * operator are complex or if the second operand of the / operator
     is complex, the operator raises floating-point exceptions if appropriate for the calculation
     of the parts of the result, and may raise spurious floating-point exceptions.
 

-
-
+
 
6   EXAMPLE 1 Multiplication of double _Complex operands could be implemented as follows. Note
-    that the imaginary unit I has imaginary type (see G.6).
+    that the imaginary unit I has imaginary type (see G.6).
              #include <math.h>
              #include <complex.h>
              /* Multiply z * w ... */
@@ -30473,14 +26233,12 @@ the specified values is outside the normal range, the characters stored are unsp
                      return x + I * y;
             }
 

-
-
+
 
7   This implementation achieves the required treatment of infinities at the cost of only one isnan test in
     ordinary (finite) cases. It is less than ideal in that undue overflow and underflow may occur.
 
 

-
-
+
 
8   EXAMPLE 2      Division of two double _Complex operands could be implemented as follows.
             #include <math.h>
             #include <complex.h>
@@ -30527,44 +26285,37 @@ the specified values is outside the normal range, the characters stored are unsp
                      return x + I * y;
             }
 

-
-
+
 
9   Scaling the denominator alleviates the main overflow and underflow problem, which is more serious than
     for multiplication. In the spirit of the multiplication example above, this code does not defend against
     overflow and underflow in the calculation of the numerator. Scaling with the scalbn function, instead of
     with division, provides better roundoff characteristics.
 
 

-
-
+
 

 
G.5.2 [Additive operators]

-

-
-
-
1   If both operands have imaginary type, then the result has imaginary type. (If one operand
+
+
1 Semantics
+   If both operands have imaginary type, then the result has imaginary type. (If one operand
     has real type and the other operand has imaginary type, or if either operand has complex
     type, then the result has complex type.)
 

-
-
+
 
2   In all cases the result and floating-point exception behavior of a + or - operator is defined
     by the usual mathematical formula:
            + or -              u                       iv                    u + iv
 
-           x                 x±u                     x ± iv              ( x ± u) ± iv
+           x                 x\xB1u                     x \xB1 iv              ( x \xB1 u) \xB1 iv
 
-           iy               ±u + iy                 i( y ± v)            ±u + i ( y ± v )
+           iy               \xB1u + iy                 i( y \xB1 v)            \xB1u + i ( y \xB1 v )
 
-           x + iy         ( x ± u) + iy           x + i( y ± v)       ( x ± u) + i ( y ± v)
+           x + iy         ( x \xB1 u) + iy           x + i( y \xB1 v)       ( x \xB1 u) + i ( y \xB1 v)
 

-
-
+
 

-
G.6 [Complex arithmetic ]

-

-
-
+
G.6 [Complex arithmetic <complex.h>]

+
 
1   The macros
             imaginary
     and
@@ -30572,51 +26323,45 @@ the specified values is outside the normal range, the characters stored are unsp
     are defined, respectively, as _Imaginary and a constant expression of type const
     float _Imaginary with the value of the imaginary unit. The macro
             I
-    is defined to be _Imaginary_I (not _Complex_I as stated in 7.3). Notwithstanding
-    the provisions of 7.1.3, a program may undefine and then perhaps redefine the macro
+    is defined to be _Imaginary_I (not _Complex_I as stated in 7.3). Notwithstanding
+    the provisions of 7.1.3, a program may undefine and then perhaps redefine the macro
     imaginary.
 

-
-
+
 
2   This subclause contains specifications for the <complex.h> functions that are
     particularly suited to IEC 60559 implementations. For families of functions, the
     specifications apply to all of the functions even though only the principal function is
 
-    shown. Unless otherwise specified, where the symbol ``±'' occurs in both an argument
+    shown. Unless otherwise specified, where the symbol ``\xB1'' occurs in both an argument
     and the result, the result has the same sign as the argument.
 

-
-
+
 
3   The functions are continuous onto both sides of their branch cuts, taking into account the
-    sign of zero. For example, csqrt(-2 ± i 0) = ±i     2.
+    sign of zero. For example, csqrt(-2 \xB1 i 0) = \xB1i     2.
 

-
-
+
 
4   Since complex and imaginary values are composed of real values, each function may be
     regarded as computing real values from real values. Except as noted, the functions treat
     real infinities, NaNs, signed zeros, subnormals, and the floating-point exception flags in a
-    manner consistent with the specifications for real functions in F.10.378)
+    manner consistent with the specifications for real functions in F.10.[378]
 

-
 
-
Footnote 378) As noted in G.3, a complex value with at least one infinite part is regarded as an infinity even if its
+
Footnote 378) As noted in G.3, a complex value with at least one infinite part is regarded as an infinity even if its
          other part is a NaN.
 

 
-
+
 
5   The functions cimag, conj, cproj, and creal are fully specified for all
-    implementations, including IEC 60559 ones, in 7.3.9. These functions raise no floating-
+    implementations, including IEC 60559 ones, in 7.3.9. These functions raise no floating-
     point exceptions.
 

-
-
+
 
6   Each of the functions cabs and carg is specified by a formula in terms of a real
     function (whose special cases are covered in annex F):
              cabs( x + iy ) = hypot( x , y )
              carg( x + iy ) = atan2( y , x )
 

-
-
+
 
7   Each of the functions casin, catan, ccos, csin, and ctan is specified implicitly by
     a formula in terms of other complex functions (whose special cases are specified below):
              casin( z )     =   -i casinh(iz )
@@ -30625,8 +26370,7 @@ the specified values is outside the normal range, the characters stored are unsp
              csin( z )      =   -i csinh(iz )
              ctan( z )      =   -i ctanh(iz )
 

-
-
+
 
8   For the other functions, the following subclauses specify behavior for special cases,
     including treatment of the ``invalid'' and ``divide-by-zero'' floating-point exceptions. For
     families of functions, the specifications apply to all of the functions even though only the
@@ -30635,27 +26379,20 @@ the specified values is outside the normal range, the characters stored are unsp
     the function f is also either even, f (- z ) = f ( z ), or odd, f (- z ) = - f ( z ), then the
     specifications for the first quadrant imply the specifications for the other three quadrants.
 

-
-
+
 
9   In the following subclauses, cis( y ) is defined as cos( y ) + i sin( y ).
 
 

-
-
+
 

 
G.6.1 [Trigonometric functions]

-
 Trigonometric functions
-

-
-
+
 

 
G.6.1.1 [The cacos functions]

-

-
-
+
 
1   -- cacos(conj( z )) = conj(cacos( z )).
-    -- cacos(±0 + i 0) returns  /2 - i 0.
-    -- cacos(±0 + i NaN) returns  /2 + i NaN.
+    -- cacos(\xB10 + i 0) returns  /2 - i 0.
+    -- cacos(\xB10 + i NaN) returns  /2 + i NaN.
     -- cacos( x + i ) returns  /2 - i , for finite x .
     -- cacos( x + i NaN) returns NaN + i NaN and optionally raises the ``invalid'' floating-
        point exception, for nonzero finite x .
@@ -30663,28 +26400,22 @@ the specified values is outside the normal range, the characters stored are unsp
     -- cacos(+ + iy ) returns +0 - i , for positive-signed finite y .
     -- cacos(- + i ) returns 3 /4 - i .
     -- cacos(+ + i ) returns  /4 - i .
-    -- cacos(± + i NaN) returns NaN ± i  (where the sign of the imaginary part of the
+    -- cacos(\xB1 + i NaN) returns NaN \xB1 i  (where the sign of the imaginary part of the
        result is unspecified).
     -- cacos(NaN + iy ) returns NaN + i NaN and optionally raises the ``invalid'' floating-
        point exception, for finite y .
     -- cacos(NaN + i ) returns NaN - i .
     -- cacos(NaN + i NaN) returns NaN + i NaN.
 

-
-
+
 

 
G.6.2 [Hyperbolic functions]

-
 Hyperbolic functions
-

-
-
+
 

 
G.6.2.1 [The cacosh functions]

-

-
-
+
 
1   -- cacosh(conj( z )) = conj(cacosh( z )).
-    -- cacosh(±0 + i 0) returns +0 + i /2.
+    -- cacosh(\xB10 + i 0) returns +0 + i /2.
     -- cacosh( x + i ) returns + + i /2, for finite x .
     -- cacosh( x + i NaN) returns NaN + i NaN and optionally raises the ``invalid''
        floating-point exception, for finite x .
@@ -30692,19 +26423,16 @@ the specified values is outside the normal range, the characters stored are unsp
     -- cacosh(+ + iy ) returns + + i 0, for positive-signed finite y .
     -- cacosh(- + i ) returns + + i 3 /4.
     -- cacosh(+ + i ) returns + + i /4.
-    -- cacosh(± + i NaN) returns + + i NaN.
+    -- cacosh(\xB1 + i NaN) returns + + i NaN.
     -- cacosh(NaN + iy ) returns NaN + i NaN and optionally raises the ``invalid''
        floating-point exception, for finite y .
     -- cacosh(NaN + i ) returns + + i NaN.
     -- cacosh(NaN + i NaN) returns NaN + i NaN.
 

-
-
+
 

 
G.6.2.2 [The casinh functions]

-

-
-
+
 
1   -- casinh(conj( z )) = conj(casinh( z )) and casinh is odd.
     -- casinh(+0 + i 0) returns 0 + i 0.
     -- casinh( x + i ) returns + + i /2 for positive-signed finite x .
@@ -30716,17 +26444,14 @@ the specified values is outside the normal range, the characters stored are unsp
     -- casinh(NaN + i 0) returns NaN + i 0.
     -- casinh(NaN + iy ) returns NaN + i NaN and optionally raises the ``invalid''
        floating-point exception, for finite nonzero y .
-    -- casinh(NaN + i ) returns ± + i NaN (where the sign of the real part of the result
+    -- casinh(NaN + i ) returns \xB1 + i NaN (where the sign of the real part of the result
        is unspecified).
     -- casinh(NaN + i NaN) returns NaN + i NaN.
 

-
-
+
 

 
G.6.2.3 [The catanh functions]

-

-
-
+
 
1   -- catanh(conj( z )) = conj(catanh( z )) and catanh is odd.
     -- catanh(+0 + i 0) returns +0 + i 0.
     -- catanh(+0 + i NaN) returns +0 + i NaN.
@@ -30741,22 +26466,19 @@ the specified values is outside the normal range, the characters stored are unsp
 
     -- catanh(NaN + iy ) returns NaN + i NaN and optionally raises the ``invalid''
        floating-point exception, for finite y .
-    -- catanh(NaN + i ) returns ±0 + i /2 (where the sign of the real part of the result is
+    -- catanh(NaN + i ) returns \xB10 + i /2 (where the sign of the real part of the result is
        unspecified).
     -- catanh(NaN + i NaN) returns NaN + i NaN.
 

-
-
+
 

 
G.6.2.4 [The ccosh functions]

-

-
-
+
 
1   -- ccosh(conj( z )) = conj(ccosh( z )) and ccosh is even.
     -- ccosh(+0 + i 0) returns 1 + i 0.
-    -- ccosh(+0 + i ) returns NaN ± i 0 (where the sign of the imaginary part of the
+    -- ccosh(+0 + i ) returns NaN \xB1 i 0 (where the sign of the imaginary part of the
        result is unspecified) and raises the ``invalid'' floating-point exception.
-    -- ccosh(+0 + i NaN) returns NaN ± i 0 (where the sign of the imaginary part of the
+    -- ccosh(+0 + i NaN) returns NaN \xB1 i 0 (where the sign of the imaginary part of the
        result is unspecified).
     -- ccosh( x + i ) returns NaN + i NaN and raises the ``invalid'' floating-point
        exception, for finite nonzero x .
@@ -30764,27 +26486,24 @@ the specified values is outside the normal range, the characters stored are unsp
        point exception, for finite nonzero x .
     -- ccosh(+ + i 0) returns + + i 0.
     -- ccosh(+ + iy ) returns + cis( y ), for finite nonzero y .
-    -- ccosh(+ + i ) returns ± + i NaN (where the sign of the real part of the result is
+    -- ccosh(+ + i ) returns \xB1 + i NaN (where the sign of the real part of the result is
        unspecified) and raises the ``invalid'' floating-point exception.
     -- ccosh(+ + i NaN) returns + + i NaN.
-    -- ccosh(NaN + i 0) returns NaN ± i 0 (where the sign of the imaginary part of the
+    -- ccosh(NaN + i 0) returns NaN \xB1 i 0 (where the sign of the imaginary part of the
        result is unspecified).
     -- ccosh(NaN + iy ) returns NaN + i NaN and optionally raises the ``invalid'' floating-
        point exception, for all nonzero numbers y .
     -- ccosh(NaN + i NaN) returns NaN + i NaN.
 

-
-
+
 

 
G.6.2.5 [The csinh functions]

-

-
-
+
 
1   -- csinh(conj( z )) = conj(csinh( z )) and csinh is odd.
     -- csinh(+0 + i 0) returns +0 + i 0.
-    -- csinh(+0 + i ) returns ±0 + i NaN (where the sign of the real part of the result is
+    -- csinh(+0 + i ) returns \xB10 + i NaN (where the sign of the real part of the result is
        unspecified) and raises the ``invalid'' floating-point exception.
-    -- csinh(+0 + i NaN) returns ±0 + i NaN (where the sign of the real part of the result is
+    -- csinh(+0 + i NaN) returns \xB10 + i NaN (where the sign of the real part of the result is
        unspecified).
     -- csinh( x + i ) returns NaN + i NaN and raises the ``invalid'' floating-point
        exception, for positive finite x .
@@ -30792,22 +26511,19 @@ the specified values is outside the normal range, the characters stored are unsp
        point exception, for finite nonzero x .
     -- csinh(+ + i 0) returns + + i 0.
     -- csinh(+ + iy ) returns + cis( y ), for positive finite y .
-    -- csinh(+ + i ) returns ± + i NaN (where the sign of the real part of the result is
+    -- csinh(+ + i ) returns \xB1 + i NaN (where the sign of the real part of the result is
        unspecified) and raises the ``invalid'' floating-point exception.
-    -- csinh(+ + i NaN) returns ± + i NaN (where the sign of the real part of the result
+    -- csinh(+ + i NaN) returns \xB1 + i NaN (where the sign of the real part of the result
        is unspecified).
     -- csinh(NaN + i 0) returns NaN + i 0.
     -- csinh(NaN + iy ) returns NaN + i NaN and optionally raises the ``invalid'' floating-
        point exception, for all nonzero numbers y .
     -- csinh(NaN + i NaN) returns NaN + i NaN.
 

-
-
+
 

 
G.6.2.6 [The ctanh functions]

-

-
-
+
 
1   -- ctanh(conj( z )) = conj(ctanh( z ))and ctanh is odd.
     -- ctanh(+0 + i 0) returns +0 + i 0.
     -- ctanh( x + i ) returns NaN + i NaN and raises the ``invalid'' floating-point
@@ -30815,30 +26531,24 @@ the specified values is outside the normal range, the characters stored are unsp
     -- ctanh( x + i NaN) returns NaN + i NaN and optionally raises the ``invalid'' floating-
        point exception, for finite x .
     -- ctanh(+ + iy ) returns 1 + i 0 sin(2 y ), for positive-signed finite y .
-    -- ctanh(+ + i ) returns 1 ± i 0 (where the sign of the imaginary part of the result
+    -- ctanh(+ + i ) returns 1 \xB1 i 0 (where the sign of the imaginary part of the result
        is unspecified).
-    -- ctanh(+ + i NaN) returns 1 ± i 0 (where the sign of the imaginary part of the
+    -- ctanh(+ + i NaN) returns 1 \xB1 i 0 (where the sign of the imaginary part of the
        result is unspecified).
     -- ctanh(NaN + i 0) returns NaN + i 0.
     -- ctanh(NaN + iy ) returns NaN + i NaN and optionally raises the ``invalid'' floating-
        point exception, for all nonzero numbers y .
     -- ctanh(NaN + i NaN) returns NaN + i NaN.
 

-
-
+
 

 
G.6.3 [Exponential and logarithmic functions]

-
 Exponential and logarithmic functions
-

-
-
+
 

 
G.6.3.1 [The cexp functions]

-

-
-
+
 
1   -- cexp(conj( z )) = conj(cexp( z )).
-    -- cexp(±0 + i 0) returns 1 + i 0.
+    -- cexp(\xB10 + i 0) returns 1 + i 0.
     -- cexp( x + i ) returns NaN + i NaN and raises the ``invalid'' floating-point
        exception, for finite x .
     -- cexp( x + i NaN) returns NaN + i NaN and optionally raises the ``invalid'' floating-
@@ -30846,26 +26556,23 @@ the specified values is outside the normal range, the characters stored are unsp
     -- cexp(+ + i 0) returns + + i 0.
     -- cexp(- + iy ) returns +0 cis( y ), for finite y .
     -- cexp(+ + iy ) returns + cis( y ), for finite nonzero y .
-    -- cexp(- + i ) returns ±0 ± i 0 (where the signs of the real and imaginary parts of
+    -- cexp(- + i ) returns \xB10 \xB1 i 0 (where the signs of the real and imaginary parts of
        the result are unspecified).
-    -- cexp(+ + i ) returns ± + i NaN and raises the ``invalid'' floating-point
+    -- cexp(+ + i ) returns \xB1 + i NaN and raises the ``invalid'' floating-point
        exception (where the sign of the real part of the result is unspecified).
-    -- cexp(- + i NaN) returns ±0 ± i 0 (where the signs of the real and imaginary parts
+    -- cexp(- + i NaN) returns \xB10 \xB1 i 0 (where the signs of the real and imaginary parts
        of the result are unspecified).
-    -- cexp(+ + i NaN) returns ± + i NaN (where the sign of the real part of the result
+    -- cexp(+ + i NaN) returns \xB1 + i NaN (where the sign of the real part of the result
        is unspecified).
     -- cexp(NaN + i 0) returns NaN + i 0.
     -- cexp(NaN + iy ) returns NaN + i NaN and optionally raises the ``invalid'' floating-
        point exception, for all nonzero numbers y .
     -- cexp(NaN + i NaN) returns NaN + i NaN.
 

-
-
+
 

 
G.6.3.2 [The clog functions]

-

-
-
+
 
1   -- clog(conj( z )) = conj(clog( z )).
     -- clog(-0 + i 0) returns - + i and raises the ``divide-by-zero'' floating-point
        exception.
@@ -30879,48 +26586,39 @@ the specified values is outside the normal range, the characters stored are unsp
     -- clog(+ + iy ) returns + + i 0, for finite positive-signed y .
     -- clog(- + i ) returns + + i 3 /4.
     -- clog(+ + i ) returns + + i /4.
-    -- clog(± + i NaN) returns + + i NaN.
+    -- clog(\xB1 + i NaN) returns + + i NaN.
     -- clog(NaN + iy ) returns NaN + i NaN and optionally raises the ``invalid'' floating-
        point exception, for finite y .
     -- clog(NaN + i ) returns + + i NaN.
     -- clog(NaN + i NaN) returns NaN + i NaN.
 

-
-
+
 

 
G.6.4 [Power and absolute-value functions]

-
 Power and absolute-value functions
-

-
-
+
 

 
G.6.4.1 [The cpow functions]

-

-
-
+
 
1   The cpow functions raise floating-point exceptions if appropriate for the calculation of
-    the parts of the result, and may also raise spurious floating-point exceptions.379)
+    the parts of the result, and may also raise spurious floating-point exceptions.[379]
 

-
 
 
Footnote 379) This allows cpow( z , c ) to be implemented as cexp(c      clog( z )) without precluding
          implementations that treat special cases more carefully.
 

 
-
+
 

 
G.6.4.2 [The csqrt functions]

-

-
-
+
 
1   -- csqrt(conj( z )) = conj(csqrt( z )).
-    -- csqrt(±0 + i 0) returns +0 + i 0.
+    -- csqrt(\xB10 + i 0) returns +0 + i 0.
     -- csqrt( x + i ) returns + + i , for all x (including NaN).
     -- csqrt( x + i NaN) returns NaN + i NaN and optionally raises the ``invalid'' floating-
        point exception, for finite x .
     -- csqrt(- + iy ) returns +0 + i , for finite positive-signed y .
     -- csqrt(+ + iy ) returns + + i 0, for finite positive-signed y .
-    -- csqrt(- + i NaN) returns NaN ± i  (where the sign of the imaginary part of the
+    -- csqrt(- + i NaN) returns NaN \xB1 i  (where the sign of the imaginary part of the
        result is unspecified).
     -- csqrt(+ + i NaN) returns + + i NaN.
     -- csqrt(NaN + iy ) returns NaN + i NaN and optionally raises the ``invalid'' floating-
@@ -30928,13 +26626,10 @@ the specified values is outside the normal range, the characters stored are unsp
     -- csqrt(NaN + i NaN) returns NaN + i NaN.
 
 

-
-
+
 

-
G.7 [Type-generic math ]

-

-
-
+
G.7 [Type-generic math <tgmath.h>]

+
 
1   Type-generic macros that accept complex arguments also accept imaginary arguments. If
     an argument is imaginary, the macro expands to an expression whose type is real,
     imaginary, or complex, as appropriate for the particular function: if the argument is
@@ -30942,8 +26637,7 @@ the specified values is outside the normal range, the characters stored are unsp
     types of sin, tan, sinh, tanh, asin, atan, asinh, and atanh are imaginary; and
     the types of the others are complex.
 

-
-
+
 
2   Given an imaginary argument, each of the type-generic macros cos, sin, tan, cosh,
     sinh, tanh, asin, atan, asinh, atanh is specified by a formula in terms of real
     functions:
@@ -30960,51 +26654,36 @@ the specified values is outside the normal range, the characters stored are unsp
                                           Annex H
                                         (informative)
 

-
-
+
 

 
H. [Language independent arithmetic]

-
 Language independent arithmetic
-

-
-
+
 

 
H.1 [Introduction]

-

-
-
+
 
1   This annex documents the extent to which the C language supports the ISO/IEC 10967-1
     standard for language-independent arithmetic (LIA-1). LIA-1 is more general than
     IEC 60559 (annex F) in that it covers integer and diverse floating-point arithmetics.
 

-
-
+
 

 
H.2 [Types]

-

-
-
+
 
1   The relevant C arithmetic types meet the requirements of LIA-1 types if an
     implementation adds notification of exceptional arithmetic operations and meets the 1
     unit in the last place (ULP) accuracy requirement (LIA-1 subclause 5.2.8).
 

-
-
+
 

 
H.2.1 [Boolean type]

-

-
-
+
 
1   The LIA-1 data type Boolean is implemented by the C data type bool with values of
     true and false, all from <stdbool.h>.
 

-
-
+
 

 
H.2.2 [Integer types]

-

-
-
+
 
1   The signed C integer types int, long int, long long int, and the corresponding
     unsigned types are compatible with LIA-1. If an implementation adds support for the
     LIA-1 exceptional values ``integer_overflow'' and ``undefined'', then those types are
@@ -31013,25 +26692,20 @@ the specified values is outside the normal range, the characters stored are unsp
     signed integer types as also being modulo need not detect integer overflow, in which case,
     only integer divide-by-zero need be detected.
 

-
-
+
 
2   The parameters for the integer data types can be accessed by the following:
     maxint        INT_MAX, LONG_MAX, LLONG_MAX, UINT_MAX, ULONG_MAX,
                   ULLONG_MAX
     minint        INT_MIN, LONG_MIN, LLONG_MIN
 

-
-
+
 
3   The parameter ``bounded'' is always true, and is not provided. The parameter ``minint''
     is always 0 for the unsigned types, and is not provided for those types.
 

-
-
+
 

 
H.2.2.1 [Integer operations]

-

-
-
+
 
1   The integer operations on integer types are the following:
     addI           x + y
     subI           x - y
@@ -31048,13 +26722,10 @@ the specified values is outside the normal range, the characters stored are unsp
     geqI           x >= y
     where x and y are expressions of the same integer type.
 

-
-
+
 

 
H.2.3 [Floating-point types]

-

-
-
+
 
1   The C floating-point types float, double, and long double are compatible with
     LIA-1. If an implementation adds support for the LIA-1 exceptional values
     ``underflow'', ``floating_overflow'', and ``"undefined'', then those types are conformant
@@ -31062,34 +26733,27 @@ the specified values is outside the normal range, the characters stored are unsp
     operations (see annex F) along with IEC 60559 status flags and traps has LIA-1
     conformant types.
 

-
-
+
 

 
H.2.3.1 [Floating-point parameters]

-

-
-
+
 
1   The parameters for a floating point data type can be accessed by the following:
     r              FLT_RADIX
     p              FLT_MANT_DIG, DBL_MANT_DIG, LDBL_MANT_DIG
     emax           FLT_MAX_EXP, DBL_MAX_EXP, LDBL_MAX_EXP
     emin           FLT_MIN_EXP, DBL_MIN_EXP, LDBL_MIN_EXP
 

-
-
+
 
2   The derived constants for the floating point types are accessed by the following:
     fmax           FLT_MAX, DBL_MAX, LDBL_MAX
     fminN          FLT_MIN, DBL_MIN, LDBL_MIN
     epsilon        FLT_EPSILON, DBL_EPSILON, LDBL_EPSILON
     rnd_style      FLT_ROUNDS
 

-
-
+
 

 
H.2.3.2 [Floating-point operations]

-

-
-
+
 
1   The floating-point operations on floating-point types are the following:
     addF           x + y
     subF           x - y
@@ -31097,7 +26761,7 @@ the specified values is outside the normal range, the characters stored are unsp
     divF           x / y
     negF           -x
     absF           fabsf(x), fabs(x), fabsl(x)
-    exponentF      1.f+logbf(x), 1.0+logb(x), 1.L+logbl(x)
+    exponentF      1.f+logbf(x), 1.0+logb(x), 1.L+logbl(x)
     scaleF         scalbnf(x, n), scalbn(x, n), scalbnl(x, n),
                    scalblnf(x, li), scalbln(x, li), scalblnl(x, li)
     intpartF       modff(x, &y), modf(x, &y), modfl(x, &y)
@@ -31111,18 +26775,14 @@ the specified values is outside the normal range, the characters stored are unsp
     where x and y are expressions of the same floating point type, n is of type int, and li
     is of type long int.
 

-
-
+
 

 
H.2.3.3 [Rounding styles]

-

-
-
+
 
1   The C Standard requires all floating types to use the same radix and rounding style, so
     that only one identifier for each is provided to map to LIA-1.
 

-
-
+
 
2   The FLT_ROUNDS parameter can be used to indicate the LIA-1 rounding styles:
     truncate       FLT_ROUNDS == 0
     nearest       FLT_ROUNDS == 1
@@ -31130,13 +26790,10 @@ the specified values is outside the normal range, the characters stored are unsp
     provided that an implementation extends FLT_ROUNDS to cover the rounding style used
     in all relevant LIA-1 operations, not just addition as in C.
 

-
-
+
 

 
H.2.4 [Type conversions]

-

-
-
+
 
1   The LIA-1 type conversions are the following type casts:
     cvtI'  I      (int)i, (long int)i, (long long int)i,
                   (unsigned int)i, (unsigned long int)i,
@@ -31147,8 +26804,7 @@ the specified values is outside the normal range, the characters stored are unsp
     cvtI  F       (float)i, (double)i, (long double)i
     cvtF'  F      (float)x, (double)x, (long double)x
 

-
-
+
 
2   In the above conversions from floating to integer, the use of (cast)x can be replaced with
     (cast)round(x), (cast)rint(x), (cast)nearbyint(x), (cast)trunc(x),
     (cast)ceil(x), or (cast)floor(x). In addition, C's floating-point to integer
@@ -31156,8 +26812,7 @@ the specified values is outside the normal range, the characters stored are unsp
     used. They all meet LIA-1's requirements on floating to integer rounding for in-range
     values. For out-of-range values, the conversions shall silently wrap for the modulo types.
 

-
-
+
 
3   The fmod() function is useful for doing silent wrapping to unsigned integer types, e.g.,
     fmod( fabs(rint(x)), 65536.0 ) or (0.0 <= (y = fmod( rint(x),
      65536.0 )) ? y : 65536.0 + y) will compute an integer value in the range 0.0
@@ -31167,77 +26822,61 @@ the specified values is outside the normal range, the characters stored are unsp
     range -32767.0 to +32768.0 which is not, in general, in the range of signed short
     int.
 

-
-
+
 
4   C's conversions (casts) from floating-point to floating-point can meet LIA-1
     requirements if an implementation uses round-to-nearest (IEC 60559 default).
 

-
-
+
 
5   C's conversions (casts) from integer to floating-point can meet LIA-1 requirements if an
     implementation uses round-to-nearest.
 

-
-
+
 

 
H.3 [Notification]

-

-
-
+
 
1   Notification is the process by which a user or program is informed that an exceptional
     arithmetic operation has occurred. C's operations are compatible with LIA-1 in that C
     allows an implementation to cause a notification to occur when any arithmetic operation
     returns an exceptional value as defined in LIA-1 clause 5.
 

-
-
+
 

 
H.3.1 [Notification alternatives]

-

-
-
+
 
1   LIA-1 requires at least the following two alternatives for handling of notifications:
     setting indicators or trap-and-terminate. LIA-1 allows a third alternative: trap-and-
     resume.
 

-
-
+
 
2   An implementation need only support a given notification alternative for the entire
     program. An implementation may support the ability to switch between notification
     alternatives during execution, but is not required to do so. An implementation can
     provide separate selection for each kind of notification, but this is not required.
 

-
-
+
 
3   C allows an implementation to provide notification. C's SIGFPE (for traps) and
     FE_INVALID, FE_DIVBYZERO, FE_OVERFLOW, FE_UNDERFLOW (for indicators)
     can provide LIA-1 notification.
 

-
-
+
 
4   C's signal handlers are compatible with LIA-1. Default handling of SIGFPE can
     provide trap-and-terminate behavior, except for those LIA-1 operations implemented by
     math library function calls. User-provided signal handlers for SIGFPE allow for trap-
     and-resume behavior with the same constraint.
 

-
-
+
 

 
H.3.1.1 [Indicators]

-

-
-
+
 
1   C's <fenv.h> status flags are compatible with the LIA-1 indicators.
 

-
-
+
 
2   The following mapping is for floating-point types:
     undefined                FE_INVALID, FE_DIVBYZERO
     floating_overflow        FE_OVERFLOW
     underflow                FE_UNDERFLOW
 

-
-
+
 
3   The floating-point indicator interrogation and manipulation operations are:
     set_indicators           feraiseexcept(i)
     clear_indicators         feclearexcept(i)
@@ -31245,41 +26884,33 @@ the specified values is outside the normal range, the characters stored are unsp
     current_indicators       fetestexcept(FE_ALL_EXCEPT)
     where i is an expression of type int representing a subset of the LIA-1 indicators.
 

-
-
+
 
4   C allows an implementation to provide the following LIA-1 required behavior: at
     program termination if any indicator is set the implementation shall send an unambiguous
     and ``hard to ignore'' message (see LIA-1 subclause 6.1.2)
 

-
-
+
 
5   LIA-1 does not make the distinction between floating-point and integer for ``undefined''.
     This documentation makes that distinction because <fenv.h> covers only the floating-
     point indicators.
 

-
-
+
 

 
H.3.1.2 [Traps]

-

-
-
+
 
1   C is compatible with LIA-1's trap requirements for arithmetic operations, but not for
     math library functions (which are not permitted to invoke a user's signal handler for
     SIGFPE). An implementation can provide an alternative of notification through
     termination with a ``hard-to-ignore'' message (see LIA-1 subclause 6.1.3).
 

-
-
+
 
2   LIA-1 does not require that traps be precise.
 

-
-
+
 
3   C does require that SIGFPE be the signal corresponding to LIA-1 arithmetic exceptions,
     if there is any signal raised for them.
 

-
-
+
 
4   C supports signal handlers for SIGFPE and allows trapping of LIA-1 arithmetic
     exceptions. When LIA-1 arithmetic exceptions do trap, C's signal-handler mechanism
     allows trap-and-terminate (either default implementation behavior or user replacement for
@@ -31287,1262 +26918,1145 @@ the specified values is outside the normal range, the characters stored are unsp
                                            Annex I
                                         (informative)
 

-
-
+
 

 
I. [Common warnings]

-

-
-
+
 
1   An implementation may generate warnings in many situations, none of which are
     specified as part of this International Standard. The following are a few of the more
     common situations.
 

-
-
-
2   -- A new struct or union type appears in a function prototype (6.2.1, 6.7.2.3).
+
+
2   -- A new struct or union type appears in a function prototype (6.2.1, 6.7.2.3).
     -- A block with initialization of an object that has automatic storage duration is jumped
-       into (6.2.4).
+       into (6.2.4).
     -- An implicit narrowing conversion is encountered, such as the assignment of a long
        int or a double to an int, or a pointer to void to a pointer to any type other than
-       a character type (6.3).
+       a character type (6.3).
     -- A hexadecimal floating constant cannot be represented exactly in its evaluation format
-       (6.4.4.2).
+       (6.4.4.2).
     -- An integer character constant includes more than one character or a wide character
-       constant includes more than one multibyte character (6.4.4.4).
-    -- The characters /* are found in a comment (6.4.7).
+       constant includes more than one multibyte character (6.4.4.4).
+    -- The characters /* are found in a comment (6.4.7).
     -- An ``unordered'' binary operator (not comma, &&, or ||) contains a side effect to an
        lvalue in one operand, and a side effect to, or an access to the value of, the identical
-       lvalue in the other operand (6.5).
-    -- A function is called but no prototype has been supplied (6.5.2.2).
+       lvalue in the other operand (6.5).
+    -- A function is called but no prototype has been supplied (6.5.2.2).
     -- The arguments in a function call do not agree in number and type with those of the
-       parameters in a function definition that is not a prototype (6.5.2.2).
-    -- An object is defined but not used (6.7).
+       parameters in a function definition that is not a prototype (6.5.2.2).
+    -- An object is defined but not used (6.7).
     -- A value is given to an object of an enumerated type other than by assignment of an
        enumeration constant that is a member of that type, or an enumeration object that has
        the same type, or the value of a function that returns the same enumerated type
-       (6.7.2.2).
-    -- An aggregate has a partly bracketed initialization (6.7.8).
-    -- A statement cannot be reached (6.8).
-    -- A statement with no apparent effect is encountered (6.8).
+       (6.7.2.2).
+    -- An aggregate has a partly bracketed initialization (6.7.8).
+    -- A statement cannot be reached (6.8).
+    -- A statement with no apparent effect is encountered (6.8).
     -- A constant expression is used as the controlling expression of a selection statement
-       (6.8.4).
+       (6.8.4).
     -- An incorrectly formed preprocessing group is encountered while skipping a
-       preprocessing group (6.10.1).
-    -- An unrecognized #pragma directive is encountered (6.10.6).
+       preprocessing group (6.10.1).
+    -- An unrecognized #pragma directive is encountered (6.10.6).
                                             Annex J
                                          (informative)
 

-
-
+
+

+
INTRODUCTION. [Introduction]

+
 

 
J. [Portability issues]

-

-
-
+
 
1   This annex collects some information about portability that appears in this International
     Standard.
 

-
-
+
 

 
J.1 [Unspecified behavior]

-

-
-
+
 
1   The following are unspecified:
-    -- The manner and timing of static initialization (5.1.2).
+    -- The manner and timing of static initialization (5.1.2).
     -- The termination status returned to the hosted environment if the return type of main
-       is not compatible with int (5.1.2.2.3).
+       is not compatible with int (5.1.2.2.3).
     -- The values of objects that are neither lock-free atomic objects nor of type volatile
        sig_atomic_t and the state of the floating-point environment, when the
-       processing of the abstract machine is interrupted by receipt of a signal (5.1.2.3).
+       processing of the abstract machine is interrupted by receipt of a signal (5.1.2.3).
     -- The behavior of the display device if a printing character is written when the active
-       position is at the final position of a line (5.2.2).
+       position is at the final position of a line (5.2.2).
     -- The behavior of the display device if a backspace character is written when the active
-       position is at the initial position of a line (5.2.2).
+       position is at the initial position of a line (5.2.2).
     -- The behavior of the display device if a horizontal tab character is written when the
-       active position is at or past the last defined horizontal tabulation position (5.2.2).
+       active position is at or past the last defined horizontal tabulation position (5.2.2).
     -- The behavior of the display device if a vertical tab character is written when the active
-       position is at or past the last defined vertical tabulation position (5.2.2).
+       position is at or past the last defined vertical tabulation position (5.2.2).
     -- How an extended source character that does not correspond to a universal character
-       name counts toward the significant initial characters in an external identifier (5.2.4.1).
-    -- Many aspects of the representations of types (6.2.6).
-    -- The value of padding bytes when storing values in structures or unions (6.2.6.1).
+       name counts toward the significant initial characters in an external identifier (5.2.4.1).
+    -- Many aspects of the representations of types (6.2.6).
+    -- The value of padding bytes when storing values in structures or unions (6.2.6.1).
     -- The values of bytes that correspond to union members other than the one last stored
-       into (6.2.6.1).
+       into (6.2.6.1).
     -- The representation used when storing a value in an object that has more than one
-       object representation for that value (6.2.6.1).
-    -- The values of any padding bits in integer representations (6.2.6.2).
+       object representation for that value (6.2.6.1).
+    -- The values of any padding bits in integer representations (6.2.6.2).
     -- Whether certain operators can generate negative zeros and whether a negative zero
-       becomes a normal zero when stored in an object (6.2.6.2).
-    -- Whether two string literals result in distinct arrays (6.4.5).
+       becomes a normal zero when stored in an object (6.2.6.2).
+    -- Whether two string literals result in distinct arrays (6.4.5).
     -- The order in which subexpressions are evaluated and the order in which side effects
        take place, except as specified for the function-call (), &&, ||, ? :, and comma
-       operators (6.5).
+       operators (6.5).
     -- The order in which the function designator, arguments, and subexpressions within the
-       arguments are evaluated in a function call (6.5.2.2).
+       arguments are evaluated in a function call (6.5.2.2).
     -- The order of side effects among compound literal initialization list expressions
-       (6.5.2.5).
-    -- The order in which the operands of an assignment operator are evaluated (6.5.16).
-    -- The alignment of the addressable storage unit allocated to hold a bit-field (6.7.2.1).
+       (6.5.2.5).
+    -- The order in which the operands of an assignment operator are evaluated (6.5.16).
+    -- The alignment of the addressable storage unit allocated to hold a bit-field (6.7.2.1).
     -- Whether a call to an inline function uses the inline definition or the external definition
-       of the function (6.7.4).
+       of the function (6.7.4).
     -- Whether or not a size expression is evaluated when it is part of the operand of a
        sizeof operator and changing the value of the size expression would not affect the
-       result of the operator (6.7.6.2).
+       result of the operator (6.7.6.2).
     -- The order in which any side effects occur among the initialization list expressions in
-       an initializer (6.7.9).
-    -- The layout of storage for function parameters (6.9.1).
+       an initializer (6.7.9).
+    -- The layout of storage for function parameters (6.9.1).
     -- When a fully expanded macro replacement list contains a function-like macro name
        as its last preprocessing token and the next preprocessing token from the source file is
        a (, and the fully expanded replacement of that macro ends with the name of the first
        macro and the next preprocessing token from the source file is again a (, whether that
-       is considered a nested replacement (6.10.3).
+       is considered a nested replacement (6.10.3).
     -- The order in which # and ## operations are evaluated during macro substitution
-       (6.10.3.2, 6.10.3.3).
+       (6.10.3.2, 6.10.3.3).
     -- The state of the floating-point status flags when execution passes from a part of the
        program translated with FENV_ACCESS ``off'' to a part translated with
-       FENV_ACCESS ``on'' (7.6.1).
+       FENV_ACCESS ``on'' (7.6.1).
     -- The order in which feraiseexcept raises floating-point exceptions, except as
-       stated in F.8.6 (7.6.2.3).
+       stated in F.8.6 (7.6.2.3).
     -- Whether math_errhandling is a macro or an identifier with external linkage
-       (7.12).
+       (7.12).
     -- The results of the frexp functions when the specified value is not a floating-point
-       number (7.12.6.4).
+       number (7.12.6.4).
     -- The numeric result of the ilogb functions when the correct value is outside the
-       range of the return type (7.12.6.5, F.10.3.5).
-    -- The result of rounding when the value is out of range (7.12.9.5, 7.12.9.7, F.10.6.5).
+       range of the return type (7.12.6.5, F.10.3.5).
+    -- The result of rounding when the value is out of range (7.12.9.5, 7.12.9.7, F.10.6.5).
     -- The value stored by the remquo functions in the object pointed to by quo when y is
-       zero (7.12.10.3).
+       zero (7.12.10.3).
     -- Whether a comparison macro argument that is represented in a format wider than its
-       semantic type is converted to the semantic type (7.12.14).
-    -- Whether setjmp is a macro or an identifier with external linkage (7.13).
+       semantic type is converted to the semantic type (7.12.14).
+    -- Whether setjmp is a macro or an identifier with external linkage (7.13).
     -- Whether va_copy and va_end are macros or identifiers with external linkage
-       (7.16.1).
+       (7.16.1).
     -- The hexadecimal digit before the decimal point when a non-normalized floating-point
-       number is printed with an a or A conversion specifier (7.21.6.1, 7.29.2.1).
+       number is printed with an a or A conversion specifier (7.21.6.1, 7.29.2.1).
     -- The value of the file position indicator after a successful call to the ungetc function
        for a text stream, or the ungetwc function for any stream, until all pushed-back
-       characters are read or discarded (7.21.7.10, 7.29.3.10).
-    -- The details of the value stored by the fgetpos function (7.21.9.1).
-    -- The details of the value returned by the ftell function for a text stream (7.21.9.4).
+       characters are read or discarded (7.21.7.10, 7.29.3.10).
+    -- The details of the value stored by the fgetpos function (7.21.9.1).
+    -- The details of the value returned by the ftell function for a text stream (7.21.9.4).
     -- Whether the strtod, strtof, strtold, wcstod, wcstof, and wcstold
        functions convert a minus-signed sequence to a negative number directly or by
        negating the value resulting from converting the corresponding unsigned sequence
-       (7.22.1.3, 7.29.4.1.1).
+       (7.22.1.3, 7.29.4.1.1).
     -- The order and contiguity of storage allocated by successive calls to the calloc,
-       malloc, and realloc functions (7.22.3).
+       malloc, and realloc functions (7.22.3).
     -- The amount of storage allocated by a successful call to the calloc, malloc, or
-       realloc function when 0 bytes was requested (7.22.3).
+       realloc function when 0 bytes was requested (7.22.3).
     -- Whether a call to the atexit function that does not happen before the exit
-       function is called will succeed (7.22.4.2).
+       function is called will succeed (7.22.4.2).
     -- Whether a call to the at_quick_exit function that does not happen before the
-       quick_exit function is called will succeed (7.22.4.3).
+       quick_exit function is called will succeed (7.22.4.3).
     -- Which of two elements that compare as equal is matched by the bsearch function
-       (7.22.5.1).
+       (7.22.5.1).
     -- The order of two elements that compare as equal in an array sorted by the qsort
-       function (7.22.5.2).
-    -- The encoding of the calendar time returned by the time function (7.27.2.4).
+       function (7.22.5.2).
+    -- The encoding of the calendar time returned by the time function (7.27.2.4).
     -- The characters stored by the strftime or wcsftime function if any of the time
-       values being converted is outside the normal range (7.27.3.5, 7.29.5.1).
+       values being converted is outside the normal range (7.27.3.5, 7.29.5.1).
     -- Whether an encoding error occurs if a wchar_t value that does not correspond to a
        member of the extended character set appears in the format string for a function in
-       7.29.2 or 7.29.5 and the specified semantics do not require that value to be processed
-       by wcrtomb (7.29.1).
-    -- The conversion state after an encoding error occurs (7.29.6.3.2, 7.29.6.3.3, 7.29.6.4.1,
-       7.29.6.4.2,
+       7.29.2 or 7.29.5 and the specified semantics do not require that value to be processed
+       by wcrtomb (7.29.1).
+    -- The conversion state after an encoding error occurs (7.29.6.3.2, 7.29.6.3.3, 7.29.6.4.1,
+       7.29.6.4.2,
     -- The resulting value when the ``invalid'' floating-point exception is raised during
-       IEC 60559 floating to integer conversion (F.4).
+       IEC 60559 floating to integer conversion (F.4).
     -- Whether conversion of non-integer IEC 60559 floating values to integer raises the
-       ``inexact'' floating-point exception (F.4).
+       ``inexact'' floating-point exception (F.4).
     -- Whether or when library functions in <math.h> raise the ``inexact'' floating-point
-       exception in an IEC 60559 conformant implementation (F.10).
+       exception in an IEC 60559 conformant implementation (F.10).
     -- Whether or when library functions in <math.h> raise an undeserved ``underflow''
-       floating-point exception in an IEC 60559 conformant implementation (F.10).
-    -- The exponent value stored by frexp for a NaN or infinity (F.10.3.4).
+       floating-point exception in an IEC 60559 conformant implementation (F.10).
+    -- The exponent value stored by frexp for a NaN or infinity (F.10.3.4).
     -- The numeric result returned by the lrint, llrint, lround, and llround
-       functions if the rounded value is outside the range of the return type (F.10.6.5,
-       F.10.6.7).
+       functions if the rounded value is outside the range of the return type (F.10.6.5,
+       F.10.6.7).
     -- The sign of one part of the complex result of several math functions for certain
-       special cases in IEC 60559 compatible implementations (G.6.1.1, G.6.2.2, G.6.2.3,
-       G.6.2.4, G.6.2.5, G.6.2.6, G.6.3.1, G.6.4.2).
+       special cases in IEC 60559 compatible implementations (G.6.1.1, G.6.2.2, G.6.2.3,
+       G.6.2.4, G.6.2.5, G.6.2.6, G.6.3.1, G.6.4.2).
 

-
-
+
 

 
J.2 [Undefined behavior]

-

-
-
+
 
1   The behavior is undefined in the following circumstances:
     -- A ``shall'' or ``shall not'' requirement that appears outside of a constraint is violated
        (clause 4).
     -- A nonempty source file does not end in a new-line character which is not immediately
        preceded by a backslash character or ends in a partial preprocessing token or
-       comment (5.1.1.2).
+       comment (5.1.1.2).
     -- Token concatenation produces a character sequence matching the syntax of a
-       universal character name (5.1.1.2).
+       universal character name (5.1.1.2).
     -- A program in a hosted environment does not define a function named main using one
-       of the specified forms (5.1.2.2.1).
-    -- The execution of a program contains a data race (5.1.2.4).
+       of the specified forms (5.1.2.2.1).
+    -- The execution of a program contains a data race (5.1.2.4).
     -- A character not in the basic source character set is encountered in a source file, except
        in an identifier, a character constant, a string literal, a header name, a comment, or a
-       preprocessing token that is never converted to a token (5.2.1).
+       preprocessing token that is never converted to a token (5.2.1).
     -- An identifier, comment, string literal, character constant, or header name contains an
-       invalid multibyte character or does not begin and end in the initial shift state (5.2.1.2).
+       invalid multibyte character or does not begin and end in the initial shift state (5.2.1.2).
     -- The same identifier has both internal and external linkage in the same translation unit
-       (6.2.2).
-    -- An object is referred to outside of its lifetime (6.2.4).
-    -- The value of a pointer to an object whose lifetime has ended is used (6.2.4).
+       (6.2.2).
+    -- An object is referred to outside of its lifetime (6.2.4).
+    -- The value of a pointer to an object whose lifetime has ended is used (6.2.4).
     -- The value of an object with automatic storage duration is used while it is
-       indeterminate (6.2.4, 6.7.9, 6.8).
+       indeterminate (6.2.4, 6.7.9, 6.8).
     -- A trap representation is read by an lvalue expression that does not have character type
-       (6.2.6.1).
+       (6.2.6.1).
     -- A trap representation is produced by a side effect that modifies any part of the object
-       using an lvalue expression that does not have character type (6.2.6.1).
+       using an lvalue expression that does not have character type (6.2.6.1).
     -- The operands to certain operators are such that they could produce a negative zero
-       result, but the implementation does not support negative zeros (6.2.6.2).
+       result, but the implementation does not support negative zeros (6.2.6.2).
     -- Two declarations of the same object or function specify types that are not compatible
-       (6.2.7).
+       (6.2.7).
     -- A program requires the formation of a composite type from a variable length array
-       type whose size is specified by an expression that is not evaluated (6.2.7).
+       type whose size is specified by an expression that is not evaluated (6.2.7).
     -- Conversion to or from an integer type produces a value outside the range that can be
-       represented (6.3.1.4).
+       represented (6.3.1.4).
     -- Demotion of one real floating type to another produces a value outside the range that
-       can be represented (6.3.1.5).
-    -- An lvalue does not designate an object when evaluated (6.3.2.1).
+       can be represented (6.3.1.5).
+    -- An lvalue does not designate an object when evaluated (6.3.2.1).
     -- A non-array lvalue with an incomplete type is used in a context that requires the value
-       of the designated object (6.3.2.1).
+       of the designated object (6.3.2.1).
     -- An lvalue designating an object of automatic storage duration that could have been
        declared with the register storage class is used in a context that requires the value
-       of the designated object, but the object is uninitialized. (6.3.2.1).
+       of the designated object, but the object is uninitialized. (6.3.2.1).
     -- An lvalue having array type is converted to a pointer to the initial element of the
-       array, and the array object has register storage class (6.3.2.1).
+       array, and the array object has register storage class (6.3.2.1).
 
     -- An attempt is made to use the value of a void expression, or an implicit or explicit
-       conversion (except to void) is applied to a void expression (6.3.2.2).
+       conversion (except to void) is applied to a void expression (6.3.2.2).
     -- Conversion of a pointer to an integer type produces a value outside the range that can
-       be represented (6.3.2.3).
+       be represented (6.3.2.3).
     -- Conversion between two pointer types produces a result that is incorrectly aligned
-       (6.3.2.3).
+       (6.3.2.3).
     -- A pointer is used to call a function whose type is not compatible with the referenced
-       type (6.3.2.3).
+       type (6.3.2.3).
     -- An unmatched ' or " character is encountered on a logical source line during
-       tokenization (6.4).
+       tokenization (6.4).
     -- A reserved keyword token is used in translation phase 7 or 8 for some purpose other
-       than as a keyword (6.4.1).
+       than as a keyword (6.4.1).
     -- A universal character name in an identifier does not designate a character whose
-       encoding falls into one of the specified ranges (6.4.2.1).
+       encoding falls into one of the specified ranges (6.4.2.1).
     -- The initial character of an identifier is a universal character name designating a digit
-       (6.4.2.1).
-    -- Two identifiers differ only in nonsignificant characters (6.4.2.1).
-    -- The identifier _ _func_ _ is explicitly declared (6.4.2.2).
-    -- The program attempts to modify a string literal (6.4.5).
+       (6.4.2.1).
+    -- Two identifiers differ only in nonsignificant characters (6.4.2.1).
+    -- The identifier _ _func_ _ is explicitly declared (6.4.2.2).
+    -- The program attempts to modify a string literal (6.4.5).
     -- The characters ', \, ", //, or /* occur in the sequence between the < and >
        delimiters, or the characters ', \, //, or /* occur in the sequence between the "
-       delimiters, in a header name preprocessing token (6.4.7).
+       delimiters, in a header name preprocessing token (6.4.7).
     -- A side effect on a scalar object is unsequenced relative to either a different side effect
        on the same scalar object or a value computation using the value of the same scalar
-       object (6.5).
-    -- An exceptional condition occurs during the evaluation of an expression (6.5).
+       object (6.5).
+    -- An exceptional condition occurs during the evaluation of an expression (6.5).
     -- An object has its stored value accessed other than by an lvalue of an allowable type
-       (6.5).
+       (6.5).
     -- For a call to a function without a function prototype in scope, the number of
-       arguments does not equal the number of parameters (6.5.2.2).
+       arguments does not equal the number of parameters (6.5.2.2).
     -- For call to a function without a function prototype in scope where the function is
        defined with a function prototype, either the prototype ends with an ellipsis or the
        types of the arguments after promotion are not compatible with the types of the
-       parameters (6.5.2.2).
+       parameters (6.5.2.2).
     -- For a call to a function without a function prototype in scope where the function is not
        defined with a function prototype, the types of the arguments after promotion are not
        compatible with those of the parameters after promotion (with certain exceptions)
-       (6.5.2.2).
+       (6.5.2.2).
     -- A function is defined with a type that is not compatible with the type (of the
-       expression) pointed to by the expression that denotes the called function (6.5.2.2).
-    -- A member of an atomic structure or union is accessed (6.5.2.3).
-    -- The operand of the unary * operator has an invalid value (6.5.3.2).
-    -- A pointer is converted to other than an integer or pointer type (6.5.4).
-    -- The value of the second operand of the / or % operator is zero (6.5.5).
+       expression) pointed to by the expression that denotes the called function (6.5.2.2).
+    -- A member of an atomic structure or union is accessed (6.5.2.3).
+    -- The operand of the unary * operator has an invalid value (6.5.3.2).
+    -- A pointer is converted to other than an integer or pointer type (6.5.4).
+    -- The value of the second operand of the / or % operator is zero (6.5.5).
     -- Addition or subtraction of a pointer into, or just beyond, an array object and an
        integer type produces a result that does not point into, or just beyond, the same array
-       object (6.5.6).
+       object (6.5.6).
     -- Addition or subtraction of a pointer into, or just beyond, an array object and an
        integer type produces a result that points just beyond the array object and is used as
-       the operand of a unary * operator that is evaluated (6.5.6).
+       the operand of a unary * operator that is evaluated (6.5.6).
     -- Pointers that do not point into, or just beyond, the same array object are subtracted
-       (6.5.6).
+       (6.5.6).
     -- An array subscript is out of range, even if an object is apparently accessible with the
        given subscript (as in the lvalue expression a[1][7] given the declaration int
-       a[4][5]) (6.5.6).
+       a[4][5]) (6.5.6).
     -- The result of subtracting two pointers is not representable in an object of type
-       ptrdiff_t (6.5.6).
+       ptrdiff_t (6.5.6).
     -- An expression is shifted by a negative number or by an amount greater than or equal
-       to the width of the promoted expression (6.5.7).
+       to the width of the promoted expression (6.5.7).
     -- An expression having signed promoted type is left-shifted and either the value of the
        expression is negative or the result of shifting would be not be representable in the
-       promoted type (6.5.7).
+       promoted type (6.5.7).
     -- Pointers that do not point to the same aggregate or union (nor just beyond the same
-       array object) are compared using relational operators (6.5.8).
+       array object) are compared using relational operators (6.5.8).
     -- An object is assigned to an inexactly overlapping object or to an exactly overlapping
-       object with incompatible type (6.5.16.1).
+       object with incompatible type (6.5.16.1).
     -- An expression that is required to be an integer constant expression does not have an
        integer type; has operands that are not integer constants, enumeration constants,
        character constants, sizeof expressions whose results are integer constants,
 
         _Alignof expressions, or immediately-cast floating constants; or contains casts
         (outside operands to sizeof and _Alignof operators) other than conversions of
-        arithmetic types to integer types (6.6).
+        arithmetic types to integer types (6.6).
     -- A constant expression in an initializer is not, or does not evaluate to, one of the
        following: an arithmetic constant expression, a null pointer constant, an address
        constant, or an address constant for a complete object type plus or minus an integer
-       constant expression (6.6).
+       constant expression (6.6).
     -- An arithmetic constant expression does not have arithmetic type; has operands that
        are not integer constants, floating constants, enumeration constants, character
        constants, sizeof expressions whose results are integer constants, or _Alignof
        expressions; or contains casts (outside operands to sizeof or _Alignof operators)
-       other than conversions of arithmetic types to arithmetic types (6.6).
+       other than conversions of arithmetic types to arithmetic types (6.6).
     -- The value of an object is accessed by an array-subscript [], member-access . or ->,
        address &, or indirection * operator or a pointer cast in creating an address constant
-       (6.6).
+       (6.6).
     -- An identifier for an object is declared with no linkage and the type of the object is
-       incomplete after its declarator, or after its init-declarator if it has an initializer (6.7).
+       incomplete after its declarator, or after its init-declarator if it has an initializer (6.7).
     -- A function is declared at block scope with an explicit storage-class specifier other
-       than extern (6.7.1).
+       than extern (6.7.1).
     -- A structure or union is defined without any named members (including those
-       specified indirectly via anonymous structures and unions) (6.7.2.1).
+       specified indirectly via anonymous structures and unions) (6.7.2.1).
     -- An attempt is made to access, or generate a pointer to just past, a flexible array
        member of a structure when the referenced object provides no elements for that array
-       (6.7.2.1).
+       (6.7.2.1).
     -- When the complete type is needed, an incomplete structure or union type is not
        completed in the same scope by another declaration of the tag that defines the content
-       (6.7.2.3).
+       (6.7.2.3).
     -- An attempt is made to modify an object defined with a const-qualified type through
-       use of an lvalue with non-const-qualified type (6.7.3).
+       use of an lvalue with non-const-qualified type (6.7.3).
     -- An attempt is made to refer to an object defined with a volatile-qualified type through
-       use of an lvalue with non-volatile-qualified type (6.7.3).
-    -- The specification of a function type includes any type qualifiers (6.7.3).
+       use of an lvalue with non-volatile-qualified type (6.7.3).
+    -- The specification of a function type includes any type qualifiers (6.7.3).
     -- Two qualified types that are required to be compatible do not have the identically
-       qualified version of a compatible type (6.7.3).
+       qualified version of a compatible type (6.7.3).
     -- An object which has been modified is accessed through a restrict-qualified pointer to
        a const-qualified type, or through a restrict-qualified pointer and another pointer that
 
-       are not both based on the same object (6.7.3.1).
+       are not both based on the same object (6.7.3.1).
     -- A restrict-qualified pointer is assigned a value based on another restricted pointer
        whose associated block neither began execution before the block associated with this
-       pointer, nor ended before the assignment (6.7.3.1).
+       pointer, nor ended before the assignment (6.7.3.1).
     -- A function with external linkage is declared with an inline function specifier, but is
-       not also defined in the same translation unit (6.7.4).
-    -- A function declared with a _Noreturn function specifier returns to its caller (6.7.4).
+       not also defined in the same translation unit (6.7.4).
+    -- A function declared with a _Noreturn function specifier returns to its caller (6.7.4).
     -- The definition of an object has an alignment specifier and another declaration of that
-       object has a different alignment specifier (6.7.5).
+       object has a different alignment specifier (6.7.5).
     -- Declarations of an object in different translation units have different alignment
-       specifiers (6.7.5).
+       specifiers (6.7.5).
     -- Two pointer types that are required to be compatible are not identically qualified, or
-       are not pointers to compatible types (6.7.6.1).
+       are not pointers to compatible types (6.7.6.1).
     -- The size expression in an array declaration is not a constant expression and evaluates
-       at program execution time to a nonpositive value (6.7.6.2).
+       at program execution time to a nonpositive value (6.7.6.2).
     -- In a context requiring two array types to be compatible, they do not have compatible
-       element types, or their size specifiers evaluate to unequal values (6.7.6.2).
+       element types, or their size specifiers evaluate to unequal values (6.7.6.2).
     -- A declaration of an array parameter includes the keyword static within the [ and
        ] and the corresponding argument does not provide access to the first element of an
-       array with at least the specified number of elements (6.7.6.3).
+       array with at least the specified number of elements (6.7.6.3).
     -- A storage-class specifier or type qualifier modifies the keyword void as a function
-       parameter type list (6.7.6.3).
+       parameter type list (6.7.6.3).
     -- In a context requiring two function types to be compatible, they do not have
        compatible return types, or their parameters disagree in use of the ellipsis terminator
        or the number and type of parameters (after default argument promotion, when there
        is no parameter type list or when one type is specified by a function definition with an
-       identifier list) (6.7.6.3).
-    -- The value of an unnamed member of a structure or union is used (6.7.9).
+       identifier list) (6.7.6.3).
+    -- The value of an unnamed member of a structure or union is used (6.7.9).
     -- The initializer for a scalar is neither a single expression nor a single expression
-       enclosed in braces (6.7.9).
+       enclosed in braces (6.7.9).
     -- The initializer for a structure or union object that has automatic storage duration is
        neither an initializer list nor a single expression that has compatible structure or union
-       type (6.7.9).
+       type (6.7.9).
     -- The initializer for an aggregate or union, other than an array initialized by a string
-       literal, is not a brace-enclosed list of initializers for its elements or members (6.7.9).
+       literal, is not a brace-enclosed list of initializers for its elements or members (6.7.9).
 
     -- An identifier with external linkage is used, but in the program there does not exist
        exactly one external definition for the identifier, or the identifier is not used and there
-       exist multiple external definitions for the identifier (6.9).
+       exist multiple external definitions for the identifier (6.9).
     -- A function definition includes an identifier list, but the types of the parameters are not
-       declared in a following declaration list (6.9.1).
+       declared in a following declaration list (6.9.1).
     -- An adjusted parameter type in a function definition is not a complete object type
-       (6.9.1).
+       (6.9.1).
     -- A function that accepts a variable number of arguments is defined without a
-       parameter type list that ends with the ellipsis notation (6.9.1).
+       parameter type list that ends with the ellipsis notation (6.9.1).
     -- The } that terminates a function is reached, and the value of the function call is used
-       by the caller (6.9.1).
+       by the caller (6.9.1).
     -- An identifier for an object with internal linkage and an incomplete type is declared
-       with a tentative definition (6.9.2).
+       with a tentative definition (6.9.2).
     -- The token defined is generated during the expansion of a #if or #elif
        preprocessing directive, or the use of the defined unary operator does not match
-       one of the two specified forms prior to macro replacement (6.10.1).
+       one of the two specified forms prior to macro replacement (6.10.1).
     -- The #include preprocessing directive that results after expansion does not match
-       one of the two header name forms (6.10.2).
+       one of the two header name forms (6.10.2).
     -- The character sequence in an #include preprocessing directive does not start with a
-       letter (6.10.2).
+       letter (6.10.2).
     -- There are sequences of preprocessing tokens within the list of macro arguments that
-       would otherwise act as preprocessing directives (6.10.3).
+       would otherwise act as preprocessing directives (6.10.3).
     -- The result of the preprocessing operator # is not a valid character string literal
-       (6.10.3.2).
+       (6.10.3.2).
     -- The result of the preprocessing operator ## is not a valid preprocessing token
-       (6.10.3.3).
+       (6.10.3.3).
     -- The #line preprocessing directive that results after expansion does not match one of
        the two well-defined forms, or its digit sequence specifies zero or a number greater
-       than 2147483647 (6.10.4).
+       than 2147483647 (6.10.4).
     -- A non-STDC #pragma preprocessing directive that is documented as causing
-       translation failure or some other form of undefined behavior is encountered (6.10.6).
+       translation failure or some other form of undefined behavior is encountered (6.10.6).
     -- A #pragma STDC preprocessing directive does not match one of the well-defined
-       forms (6.10.6).
+       forms (6.10.6).
     -- The name of a predefined macro, or the identifier defined, is the subject of a
-       #define or #undef preprocessing directive (6.10.8).
+       #define or #undef preprocessing directive (6.10.8).
 
     -- An attempt is made to copy an object to an overlapping object by use of a library
        function, other than as explicitly allowed (e.g., memmove) (clause 7).
     -- A file with the same name as one of the standard headers, not provided as part of the
        implementation, is placed in any of the standard places that are searched for included
-       source files (7.1.2).
-    -- A header is included within an external declaration or definition (7.1.2).
+       source files (7.1.2).
+    -- A header is included within an external declaration or definition (7.1.2).
     -- A function, object, type, or macro that is specified as being declared or defined by
        some standard header is used before any header that declares or defines it is included
-       (7.1.2).
+       (7.1.2).
     -- A standard header is included while a macro is defined with the same name as a
-       keyword (7.1.2).
+       keyword (7.1.2).
     -- The program attempts to declare a library function itself, rather than via a standard
-       header, but the declaration does not have external linkage (7.1.2).
-    -- The program declares or defines a reserved identifier, other than as allowed by 7.1.4
-       (7.1.3).
+       header, but the declaration does not have external linkage (7.1.2).
+    -- The program declares or defines a reserved identifier, other than as allowed by 7.1.4
+       (7.1.3).
     -- The program removes the definition of a macro whose name begins with an
-       underscore and either an uppercase letter or another underscore (7.1.3).
+       underscore and either an uppercase letter or another underscore (7.1.3).
     -- An argument to a library function has an invalid value or a type not expected by a
-       function with variable number of arguments (7.1.4).
+       function with variable number of arguments (7.1.4).
     -- The pointer passed to a library function array parameter does not have a value such
-       that all address computations and object accesses are valid (7.1.4).
+       that all address computations and object accesses are valid (7.1.4).
     -- The macro definition of assert is suppressed in order to access an actual function
-       (7.2).
-    -- The argument to the assert macro does not have a scalar type (7.2).
+       (7.2).
+    -- The argument to the assert macro does not have a scalar type (7.2).
     -- The CX_LIMITED_RANGE, FENV_ACCESS, or FP_CONTRACT pragma is used in
        any context other than outside all external declarations or preceding all explicit
-       declarations and statements inside a compound statement (7.3.4, 7.6.1, 7.12.2).
+       declarations and statements inside a compound statement (7.3.4, 7.6.1, 7.12.2).
     -- The value of an argument to a character handling function is neither equal to the value
-       of EOF nor representable as an unsigned char (7.4).
+       of EOF nor representable as an unsigned char (7.4).
     -- A macro definition of errno is suppressed in order to access an actual object, or the
-       program defines an identifier with the name errno (7.5).
+       program defines an identifier with the name errno (7.5).
     -- Part of the program tests floating-point status flags, sets floating-point control modes,
        or runs under non-default mode settings, but was translated with the state for the
-       FENV_ACCESS pragma ``off'' (7.6.1).
+       FENV_ACCESS pragma ``off'' (7.6.1).
     -- The exception-mask argument for one of the functions that provide access to the
        floating-point status flags has a nonzero value not obtained by bitwise OR of the
-       floating-point exception macros (7.6.2).
+       floating-point exception macros (7.6.2).
     -- The fesetexceptflag function is used to set floating-point status flags that were
        not specified in the call to the fegetexceptflag function that provided the value
-       of the corresponding fexcept_t object (7.6.2.4).
+       of the corresponding fexcept_t object (7.6.2.4).
     -- The argument to fesetenv or feupdateenv is neither an object set by a call to
-       fegetenv or feholdexcept, nor is it an environment macro (7.6.4.3, 7.6.4.4).
+       fegetenv or feholdexcept, nor is it an environment macro (7.6.4.3, 7.6.4.4).
     -- The value of the result of an integer arithmetic or conversion function cannot be
-       represented (7.8.2.1, 7.8.2.2, 7.8.2.3, 7.8.2.4, 7.22.6.1, 7.22.6.2, 7.22.1).
+       represented (7.8.2.1, 7.8.2.2, 7.8.2.3, 7.8.2.4, 7.22.6.1, 7.22.6.2, 7.22.1).
     -- The program modifies the string pointed to by the value returned by the setlocale
-       function (7.11.1.1).
+       function (7.11.1.1).
     -- The program modifies the structure pointed to by the value returned by the
-       localeconv function (7.11.2.1).
+       localeconv function (7.11.2.1).
     -- A macro definition of math_errhandling is suppressed or the program defines
-       an identifier with the name math_errhandling (7.12).
+       an identifier with the name math_errhandling (7.12).
     -- An argument to a floating-point classification or comparison macro is not of real
-       floating type (7.12.3, 7.12.14).
+       floating type (7.12.3, 7.12.14).
     -- A macro definition of setjmp is suppressed in order to access an actual function, or
-       the program defines an external identifier with the name setjmp (7.13).
+       the program defines an external identifier with the name setjmp (7.13).
     -- An invocation of the setjmp macro occurs other than in an allowed context
-       (7.13.2.1).
-    -- The longjmp function is invoked to restore a nonexistent environment (7.13.2.1).
+       (7.13.2.1).
+    -- The longjmp function is invoked to restore a nonexistent environment (7.13.2.1).
     -- After a longjmp, there is an attempt to access the value of an object of automatic
        storage duration that does not have volatile-qualified type, local to the function
        containing the invocation of the corresponding setjmp macro, that was changed
-       between the setjmp invocation and longjmp call (7.13.2.1).
-    -- The program specifies an invalid pointer to a signal handler function (7.14.1.1).
+       between the setjmp invocation and longjmp call (7.13.2.1).
+    -- The program specifies an invalid pointer to a signal handler function (7.14.1.1).
     -- A signal handler returns when the signal corresponded to a computational exception
-       (7.14.1.1).
+       (7.14.1.1).
     -- A signal handler called in response to SIGFPE, SIGILL, SIGSEGV, or any other
        implementation-defined value corresponding to a computational exception returns
-       (7.14.1.1).
+       (7.14.1.1).
     -- A signal occurs as the result of calling the abort or raise function, and the signal
-       handler calls the raise function (7.14.1.1).
+       handler calls the raise function (7.14.1.1).
 
     -- A signal occurs other than as the result of calling the abort or raise function, and
        the signal handler refers to an object with static or thread storage duration that is not a
        lock-free atomic object other than by assigning a value to an object declared as
        volatile sig_atomic_t, or calls any function in the standard library other
        than the abort function, the _Exit function, the quick_exit function, or the
-       signal function (for the same signal number) (7.14.1.1).
+       signal function (for the same signal number) (7.14.1.1).
     -- The value of errno is referred to after a signal occurred other than as the result of
        calling the abort or raise function and the corresponding signal handler obtained
-       a SIG_ERR return from a call to the signal function (7.14.1.1).
-    -- A signal is generated by an asynchronous signal handler (7.14.1.1).
-    -- The signal function is used in a multi-threaded program (7.14.1.1).
+       a SIG_ERR return from a call to the signal function (7.14.1.1).
+    -- A signal is generated by an asynchronous signal handler (7.14.1.1).
+    -- The signal function is used in a multi-threaded program (7.14.1.1).
     -- A function with a variable number of arguments attempts to access its varying
        arguments other than through a properly declared and initialized va_list object, or
-       before the va_start macro is invoked (7.16, 7.16.1.1, 7.16.1.4).
+       before the va_start macro is invoked (7.16, 7.16.1.1, 7.16.1.4).
     -- The macro va_arg is invoked using the parameter ap that was passed to a function
-       that invoked the macro va_arg with the same parameter (7.16).
+       that invoked the macro va_arg with the same parameter (7.16).
     -- A macro definition of va_start, va_arg, va_copy, or va_end is suppressed in
        order to access an actual function, or the program defines an external identifier with
-       the name va_copy or va_end (7.16.1).
+       the name va_copy or va_end (7.16.1).
     -- The va_start or va_copy macro is invoked without a corresponding invocation
-       of the va_end macro in the same function, or vice versa (7.16.1, 7.16.1.2, 7.16.1.3,
-         7.16.1.4).
+       of the va_end macro in the same function, or vice versa (7.16.1, 7.16.1.2, 7.16.1.3,
+         7.16.1.4).
     -- The type parameter to the va_arg macro is not such that a pointer to an object of
-       that type can be obtained simply by postfixing a * (7.16.1.1).
+       that type can be obtained simply by postfixing a * (7.16.1.1).
     -- The va_arg macro is invoked when there is no actual next argument, or with a
        specified type that is not compatible with the promoted type of the actual next
-       argument, with certain exceptions (7.16.1.1).
+       argument, with certain exceptions (7.16.1.1).
     -- The va_copy or va_start macro is called to initialize a va_list that was
        previously initialized by either macro without an intervening invocation of the
-       va_end macro for the same va_list (7.16.1.2, 7.16.1.4).
+       va_end macro for the same va_list (7.16.1.2, 7.16.1.4).
     -- The parameter parmN of a va_start macro is declared with the register
        storage class, with a function or array type, or with a type that is not compatible with
-       the type that results after application of the default argument promotions (7.16.1.4).
+       the type that results after application of the default argument promotions (7.16.1.4).
     -- The member designator parameter of an offsetof macro is an invalid right
-       operand of the . operator for the type parameter, or designates a bit-field (7.19).
+       operand of the . operator for the type parameter, or designates a bit-field (7.19).
     -- The argument in an instance of one of the integer-constant macros is not a decimal,
        octal, or hexadecimal constant, or it has a value that exceeds the limits for the
-       corresponding type (7.20.4).
+       corresponding type (7.20.4).
     -- A byte input/output function is applied to a wide-oriented stream, or a wide character
-       input/output function is applied to a byte-oriented stream (7.21.2).
+       input/output function is applied to a byte-oriented stream (7.21.2).
     -- Use is made of any portion of a file beyond the most recent wide character written to
-       a wide-oriented stream (7.21.2).
+       a wide-oriented stream (7.21.2).
     -- The value of a pointer to a FILE object is used after the associated file is closed
-       (7.21.3).
+       (7.21.3).
     -- The stream for the fflush function points to an input stream or to an update stream
-       in which the most recent operation was input (7.21.5.2).
+       in which the most recent operation was input (7.21.5.2).
     -- The string pointed to by the mode argument in a call to the fopen function does not
-       exactly match one of the specified character sequences (7.21.5.3).
+       exactly match one of the specified character sequences (7.21.5.3).
     -- An output operation on an update stream is followed by an input operation without an
        intervening call to the fflush function or a file positioning function, or an input
        operation on an update stream is followed by an output operation with an intervening
-       call to a file positioning function (7.21.5.3).
+       call to a file positioning function (7.21.5.3).
     -- An attempt is made to use the contents of the array that was supplied in a call to the
-       setvbuf function (7.21.5.6).
+       setvbuf function (7.21.5.6).
     -- There are insufficient arguments for the format in a call to one of the formatted
-       input/output functions, or an argument does not have an appropriate type (7.21.6.1,
-         7.21.6.2, 7.29.2.1, 7.29.2.2).
+       input/output functions, or an argument does not have an appropriate type (7.21.6.1,
+         7.21.6.2, 7.29.2.1, 7.29.2.2).
     -- The format in a call to one of the formatted input/output functions or to the
        strftime or wcsftime function is not a valid multibyte character sequence that
-       begins and ends in its initial shift state (7.21.6.1, 7.21.6.2, 7.27.3.5, 7.29.2.1, 7.29.2.2,
-         7.29.5.1).
+       begins and ends in its initial shift state (7.21.6.1, 7.21.6.2, 7.27.3.5, 7.29.2.1, 7.29.2.2,
+         7.29.5.1).
     -- In a call to one of the formatted output functions, a precision appears with a
-       conversion specifier other than those described (7.21.6.1, 7.29.2.1).
+       conversion specifier other than those described (7.21.6.1, 7.29.2.1).
     -- A conversion specification for a formatted output function uses an asterisk to denote
        an argument-supplied field width or precision, but the corresponding argument is not
-       provided (7.21.6.1, 7.29.2.1).
+       provided (7.21.6.1, 7.29.2.1).
     -- A conversion specification for a formatted output function uses a # or 0 flag with a
-       conversion specifier other than those described (7.21.6.1, 7.29.2.1).
+       conversion specifier other than those described (7.21.6.1, 7.29.2.1).
     -- A conversion specification for one of the formatted input/output functions uses a
-       length modifier with a conversion specifier other than those described (7.21.6.1,
-         7.21.6.2, 7.29.2.1, 7.29.2.2).
+       length modifier with a conversion specifier other than those described (7.21.6.1,
+         7.21.6.2, 7.29.2.1, 7.29.2.2).
 
     -- An s conversion specifier is encountered by one of the formatted output functions,
        and the argument is missing the null terminator (unless a precision is specified that
-       does not require null termination) (7.21.6.1, 7.29.2.1).
+       does not require null termination) (7.21.6.1, 7.29.2.1).
     -- An n conversion specification for one of the formatted input/output functions includes
-       any flags, an assignment-suppressing character, a field width, or a precision (7.21.6.1,
-         7.21.6.2, 7.29.2.1, 7.29.2.2).
+       any flags, an assignment-suppressing character, a field width, or a precision (7.21.6.1,
+         7.21.6.2, 7.29.2.1, 7.29.2.2).
     -- A % conversion specifier is encountered by one of the formatted input/output
-       functions, but the complete conversion specification is not exactly %% (7.21.6.1,
-         7.21.6.2, 7.29.2.1, 7.29.2.2).
+       functions, but the complete conversion specification is not exactly %% (7.21.6.1,
+         7.21.6.2, 7.29.2.1, 7.29.2.2).
     -- An invalid conversion specification is found in the format for one of the formatted
-       input/output functions, or the strftime or wcsftime function (7.21.6.1, 7.21.6.2,
-         7.27.3.5, 7.29.2.1, 7.29.2.2, 7.29.5.1).
+       input/output functions, or the strftime or wcsftime function (7.21.6.1, 7.21.6.2,
+         7.27.3.5, 7.29.2.1, 7.29.2.2, 7.29.5.1).
     -- The number of characters or wide characters transmitted by a formatted output
        function (or written to an array, or that would have been written to an array) is greater
-       than INT_MAX (7.21.6.1, 7.29.2.1).
+       than INT_MAX (7.21.6.1, 7.29.2.1).
     -- The number of input items assigned by a formatted input function is greater than
-       INT_MAX (7.21.6.2, 7.29.2.2).
+       INT_MAX (7.21.6.2, 7.29.2.2).
     -- The result of a conversion by one of the formatted input functions cannot be
        represented in the corresponding object, or the receiving object does not have an
-       appropriate type (7.21.6.2, 7.29.2.2).
+       appropriate type (7.21.6.2, 7.29.2.2).
     -- A c, s, or [ conversion specifier is encountered by one of the formatted input
        functions, and the array pointed to by the corresponding argument is not large enough
        to accept the input sequence (and a null terminator if the conversion specifier is s or
-       [) (7.21.6.2, 7.29.2.2).
+       [) (7.21.6.2, 7.29.2.2).
     -- A c, s, or [ conversion specifier with an l qualifier is encountered by one of the
        formatted input functions, but the input is not a valid multibyte character sequence
-       that begins in the initial shift state (7.21.6.2, 7.29.2.2).
+       that begins in the initial shift state (7.21.6.2, 7.29.2.2).
     -- The input item for a %p conversion by one of the formatted input functions is not a
-       value converted earlier during the same program execution (7.21.6.2, 7.29.2.2).
+       value converted earlier during the same program execution (7.21.6.2, 7.29.2.2).
     -- The vfprintf, vfscanf, vprintf, vscanf, vsnprintf, vsprintf,
        vsscanf, vfwprintf, vfwscanf, vswprintf, vswscanf, vwprintf, or
        vwscanf function is called with an improperly initialized va_list argument, or
        the argument is used (other than in an invocation of va_end) after the function
-       returns (7.21.6.8, 7.21.6.9, 7.21.6.10, 7.21.6.11, 7.21.6.12, 7.21.6.13, 7.21.6.14,
-         7.29.2.5, 7.29.2.6, 7.29.2.7, 7.29.2.8, 7.29.2.9, 7.29.2.10).
+       returns (7.21.6.8, 7.21.6.9, 7.21.6.10, 7.21.6.11, 7.21.6.12, 7.21.6.13, 7.21.6.14,
+         7.29.2.5, 7.29.2.6, 7.29.2.7, 7.29.2.8, 7.29.2.9, 7.29.2.10).
     -- The contents of the array supplied in a call to the fgets or fgetws function are
-       used after a read error occurred (7.21.7.2, 7.29.3.2).
+       used after a read error occurred (7.21.7.2, 7.29.3.2).
     -- The file position indicator for a binary stream is used after a call to the ungetc
-       function where its value was zero before the call (7.21.7.10).
+       function where its value was zero before the call (7.21.7.10).
     -- The file position indicator for a stream is used after an error occurred during a call to
-       the fread or fwrite function (7.21.8.1, 7.21.8.2).
-    -- A partial element read by a call to the fread function is used (7.21.8.1).
+       the fread or fwrite function (7.21.8.1, 7.21.8.2).
+    -- A partial element read by a call to the fread function is used (7.21.8.1).
     -- The fseek function is called for a text stream with a nonzero offset and either the
        offset was not returned by a previous successful call to the ftell function on a
-       stream associated with the same file or whence is not SEEK_SET (7.21.9.2).
+       stream associated with the same file or whence is not SEEK_SET (7.21.9.2).
     -- The fsetpos function is called to set a position that was not returned by a previous
        successful call to the fgetpos function on a stream associated with the same file
-       (7.21.9.3).
+       (7.21.9.3).
     -- A non-null pointer returned by a call to the calloc, malloc, or realloc function
-       with a zero requested size is used to access an object (7.22.3).
+       with a zero requested size is used to access an object (7.22.3).
     -- The value of a pointer that refers to space deallocated by a call to the free or
-       realloc function is used (7.22.3).
+       realloc function is used (7.22.3).
     -- The alignment requested of the aligned_alloc function is not valid or not
        supported by the implementation, or the size requested is not an integral multiple of
-       the alignment (7.22.3.1).
+       the alignment (7.22.3.1).
     -- The pointer argument to the free or realloc function does not match a pointer
        earlier returned by a memory management function, or the space has been deallocated
-       by a call to free or realloc (7.22.3.3, 7.22.3.5).
-    -- The value of the object allocated by the malloc function is used (7.22.3.4).
+       by a call to free or realloc (7.22.3.3, 7.22.3.5).
+    -- The value of the object allocated by the malloc function is used (7.22.3.4).
     -- The value of any bytes in a new object allocated by the realloc function beyond
-       the size of the old object are used (7.22.3.5).
+       the size of the old object are used (7.22.3.5).
     -- The program calls the exit or quick_exit function more than once, or calls both
-       functions (7.22.4.4, 7.22.4.7).
+       functions (7.22.4.4, 7.22.4.7).
     -- During the call to a function registered with the atexit or at_quick_exit
        function, a call is made to the longjmp function that would terminate the call to the
-       registered function (7.22.4.4, 7.22.4.7).
+       registered function (7.22.4.4, 7.22.4.7).
     -- The string set up by the getenv or strerror function is modified by the program
-       (7.22.4.6, 7.24.6.2).
-    -- A signal is raised while the quick_exit function is executing (7.22.4.7).
+       (7.22.4.6, 7.24.6.2).
+    -- A signal is raised while the quick_exit function is executing (7.22.4.7).
     -- A command is executed through the system function in a way that is documented as
-       causing termination or some other form of undefined behavior (7.22.4.8).
+       causing termination or some other form of undefined behavior (7.22.4.8).
     -- A searching or sorting utility function is called with an invalid pointer argument, even
-       if the number of elements is zero (7.22.5).
+       if the number of elements is zero (7.22.5).
     -- The comparison function called by a searching or sorting utility function alters the
        contents of the array being searched or sorted, or returns ordering values
-       inconsistently (7.22.5).
+       inconsistently (7.22.5).
     -- The array being searched by the bsearch function does not have its elements in
-       proper order (7.22.5.1).
+       proper order (7.22.5.1).
     -- The current conversion state is used by a multibyte/wide character conversion
-       function after changing the LC_CTYPE category (7.22.7).
+       function after changing the LC_CTYPE category (7.22.7).
     -- A string or wide string utility function is instructed to access an array beyond the end
-       of an object (7.24.1, 7.29.4).
+       of an object (7.24.1, 7.29.4).
     -- A string or wide string utility function is called with an invalid pointer argument, even
-       if the length is zero (7.24.1, 7.29.4).
+       if the length is zero (7.24.1, 7.29.4).
     -- The contents of the destination array are used after a call to the strxfrm,
        strftime, wcsxfrm, or wcsftime function in which the specified length was
-       too small to hold the entire null-terminated result (7.24.4.5, 7.27.3.5, 7.29.4.4.4,
-         7.29.5.1).
+       too small to hold the entire null-terminated result (7.24.4.5, 7.27.3.5, 7.29.4.4.4,
+         7.29.5.1).
     -- The first argument in the very first call to the strtok or wcstok is a null pointer
-       (7.24.5.8, 7.29.4.5.7).
+       (7.24.5.8, 7.29.4.5.7).
     -- The type of an argument to a type-generic macro is not compatible with the type of
-       the corresponding parameter of the selected function (7.25).
+       the corresponding parameter of the selected function (7.25).
     -- A complex argument is supplied for a generic parameter of a type-generic macro that
-       has no corresponding complex function (7.25).
+       has no corresponding complex function (7.25).
     -- At least one member of the broken-down time passed to asctime contains a value
        outside its normal range, or the calculated year exceeds four digits or is less than the
-       year 1000 (7.27.3.1).
+       year 1000 (7.27.3.1).
     -- The argument corresponding to an s specifier without an l qualifier in a call to the
        fwprintf function does not point to a valid multibyte character sequence that
-       begins in the initial shift state (7.29.2.11).
+       begins in the initial shift state (7.29.2.11).
     -- In a call to the wcstok function, the object pointed to by ptr does not have the
-       value stored by the previous call for the same wide string (7.29.4.5.7).
-    -- An mbstate_t object is used inappropriately (7.29.6).
+       value stored by the previous call for the same wide string (7.29.4.5.7).
+    -- An mbstate_t object is used inappropriately (7.29.6).
     -- The value of an argument of type wint_t to a wide character classification or case
        mapping function is neither equal to the value of WEOF nor representable as a
-       wchar_t (7.30.1).
+       wchar_t (7.30.1).
 
     -- The iswctype function is called using a different LC_CTYPE category from the
        one in effect for the call to the wctype function that returned the description
-       (7.30.2.2.1).
+       (7.30.2.2.1).
     -- The towctrans function is called using a different LC_CTYPE category from the
        one in effect for the call to the wctrans function that returned the description
-       (7.30.3.2.1).
+       (7.30.3.2.1).
 

-
-
+
 

 
J.3 [Implementation-defined behavior]

-

-
-
+
 
1   A conforming implementation is required to document its choice of behavior in each of
     the areas listed in this subclause. The following are implementation-defined:
 

-
-
+
 

 
J.3.1 [Translation]

-

-
-
-
1   -- How a diagnostic is identified (3.10, 5.1.1.3).
+
+
1   -- How a diagnostic is identified (3.10, 5.1.1.3).
     -- Whether each nonempty sequence of white-space characters other than new-line is
-       retained or replaced by one space character in translation phase 3 (5.1.1.2).
+       retained or replaced by one space character in translation phase 3 (5.1.1.2).
 

-
-
+
 

 
J.3.2 [Environment]

-

-
-
+
 
1   -- The mapping between physical source file multibyte characters and the source
-       character set in translation phase 1 (5.1.1.2).
+       character set in translation phase 1 (5.1.1.2).
     -- The name and type of the function called at program startup in a freestanding
-       environment (5.1.2.1).
-    -- The effect of program termination in a freestanding environment (5.1.2.1).
-    -- An alternative manner in which the main function may be defined (5.1.2.2.1).
-    -- The values given to the strings pointed to by the argv argument to main (5.1.2.2.1).
-    -- What constitutes an interactive device (5.1.2.3).
+       environment (5.1.2.1).
+    -- The effect of program termination in a freestanding environment (5.1.2.1).
+    -- An alternative manner in which the main function may be defined (5.1.2.2.1).
+    -- The values given to the strings pointed to by the argv argument to main (5.1.2.2.1).
+    -- What constitutes an interactive device (5.1.2.3).
     -- Whether a program can have more than one thread of execution in a freestanding
-       environment (5.1.2.4).
-    -- The set of signals, their semantics, and their default handling (7.14).
+       environment (5.1.2.4).
+    -- The set of signals, their semantics, and their default handling (7.14).
     -- Signal values other than SIGFPE, SIGILL, and SIGSEGV that correspond to a
-       computational exception (7.14.1.1).
+       computational exception (7.14.1.1).
     -- Signals for which the equivalent of signal(sig, SIG_IGN); is executed at
-       program startup (7.14.1.1).
+       program startup (7.14.1.1).
     -- The set of environment names and the method for altering the environment list used
-       by the getenv function (7.22.4.6).
-    -- The manner of execution of the string by the system function (7.22.4.8).
+       by the getenv function (7.22.4.6).
+    -- The manner of execution of the string by the system function (7.22.4.8).
 

-
-
+
 

 
J.3.3 [Identifiers]

-

-
-
+
 
1   -- Which additional multibyte characters may appear in identifiers and their
-       correspondence to universal character names (6.4.2).
-    -- The number of significant initial characters in an identifier (5.2.4.1, 6.4.2).
+       correspondence to universal character names (6.4.2).
+    -- The number of significant initial characters in an identifier (5.2.4.1, 6.4.2).
 

-
-
+
 

 
J.3.4 [Characters]

-

-
-
-
1   -- The number of bits in a byte (3.6).
-    -- The values of the members of the execution character set (5.2.1).
+
+
1   -- The number of bits in a byte (3.6).
+    -- The values of the members of the execution character set (5.2.1).
     -- The unique value of the member of the execution character set produced for each of
-       the standard alphabetic escape sequences (5.2.2).
+       the standard alphabetic escape sequences (5.2.2).
     -- The value of a char object into which has been stored any character other than a
-       member of the basic execution character set (6.2.5).
+       member of the basic execution character set (6.2.5).
     -- Which of signed char or unsigned char has the same range, representation,
-       and behavior as ``plain'' char (6.2.5, 6.3.1.1).
+       and behavior as ``plain'' char (6.2.5, 6.3.1.1).
     -- The mapping of members of the source character set (in character constants and string
-       literals) to members of the execution character set (6.4.4.4, 5.1.1.2).
+       literals) to members of the execution character set (6.4.4.4, 5.1.1.2).
     -- The value of an integer character constant containing more than one character or
        containing a character or escape sequence that does not map to a single-byte
-       execution character (6.4.4.4).
+       execution character (6.4.4.4).
     -- The value of a wide character constant containing more than one multibyte character
        or a single multibyte character that maps to multiple members of the extended
        execution character set, or containing a multibyte character or escape sequence not
-       represented in the extended execution character set (6.4.4.4).
+       represented in the extended execution character set (6.4.4.4).
     -- The current locale used to convert a wide character constant consisting of a single
        multibyte character that maps to a member of the extended execution character set
-       into a corresponding wide character code (6.4.4.4).
+       into a corresponding wide character code (6.4.4.4).
     -- Whether differently-prefixed wide string literal tokens can be concatenated and, if so,
-       the treatment of the resulting multibyte character sequence (6.4.5).
+       the treatment of the resulting multibyte character sequence (6.4.5).
     -- The current locale used to convert a wide string literal into corresponding wide
-       character codes (6.4.5).
+       character codes (6.4.5).
     -- The value of a string literal containing a multibyte character or escape sequence not
-       represented in the execution character set (6.4.5).
+       represented in the execution character set (6.4.5).
     -- The encoding of any of wchar_t, char16_t, and char32_t where the
        corresponding  standard   encoding macro      (_ _STDC_ISO_10646_ _,
-       _ _STDC_UTF_16_ _, or _ _STDC_UTF_32_ _) is not defined (6.10.8.2).
+       _ _STDC_UTF_16_ _, or _ _STDC_UTF_32_ _) is not defined (6.10.8.2).
 
 

-
-
+
 

 
J.3.5 [Integers]

-

-
-
-
1   -- Any extended integer types that exist in the implementation (6.2.5).
+
+
1   -- Any extended integer types that exist in the implementation (6.2.5).
     -- Whether signed integer types are represented using sign and magnitude, two's
        complement, or ones' complement, and whether the extraordinary value is a trap
-       representation or an ordinary value (6.2.6.2).
+       representation or an ordinary value (6.2.6.2).
     -- The rank of any extended integer type relative to another extended integer type with
-       the same precision (6.3.1.1).
+       the same precision (6.3.1.1).
     -- The result of, or the signal raised by, converting an integer to a signed integer type
-       when the value cannot be represented in an object of that type (6.3.1.3).
-    -- The results of some bitwise operations on signed integers (6.5).
+       when the value cannot be represented in an object of that type (6.3.1.3).
+    -- The results of some bitwise operations on signed integers (6.5).
 

-
-
+
 

 
J.3.6 [Floating point]

-

-
-
+
 
1   -- The accuracy of the floating-point operations and of the library functions in
-       <math.h> and <complex.h> that return floating-point results (5.2.4.2.2).
+       <math.h> and <complex.h> that return floating-point results (5.2.4.2.2).
     -- The accuracy of the conversions between floating-point internal representations and
        string representations performed by the library functions in <stdio.h>,
-       <stdlib.h>, and <wchar.h> (5.2.4.2.2).
+       <stdlib.h>, and <wchar.h> (5.2.4.2.2).
     -- The rounding behaviors characterized by non-standard values of FLT_ROUNDS
-       (5.2.4.2.2).
+       (5.2.4.2.2).
     -- The evaluation methods characterized by non-standard negative values of
-       FLT_EVAL_METHOD (5.2.4.2.2).
+       FLT_EVAL_METHOD (5.2.4.2.2).
     -- The direction of rounding when an integer is converted to a floating-point number that
-       cannot exactly represent the original value (6.3.1.4).
+       cannot exactly represent the original value (6.3.1.4).
     -- The direction of rounding when a floating-point number is converted to a narrower
-       floating-point number (6.3.1.5).
+       floating-point number (6.3.1.5).
     -- How the nearest representable value or the larger or smaller representable value
        immediately adjacent to the nearest representable value is chosen for certain floating
-       constants (6.4.4.2).
+       constants (6.4.4.2).
     -- Whether and how floating expressions are contracted when not disallowed by the
-       FP_CONTRACT pragma (6.5).
-    -- The default state for the FENV_ACCESS pragma (7.6.1).
+       FP_CONTRACT pragma (6.5).
+    -- The default state for the FENV_ACCESS pragma (7.6.1).
     -- Additional floating-point exceptions, rounding          modes,     environments,   and
-       classifications, and their macro names (7.6, 7.12).
-    -- The default state for the FP_CONTRACT pragma (7.12.2).
+       classifications, and their macro names (7.6, 7.12).
+    -- The default state for the FP_CONTRACT pragma (7.12.2).
 

-
-
+
 

 
J.3.7 [Arrays and pointers]

-

-
-
-
1   -- The result of converting a pointer to an integer or vice versa (6.3.2.3).
+
+
1   -- The result of converting a pointer to an integer or vice versa (6.3.2.3).
     -- The size of the result of subtracting two pointers to elements of the same array
-       (6.5.6).
+       (6.5.6).
 

-
-
+
 

 
J.3.8 [Hints]

-

-
-
+
 
1   -- The extent to which suggestions made by using the register storage-class
-       specifier are effective (6.7.1).
+       specifier are effective (6.7.1).
     -- The extent to which suggestions made by using the inline function specifier are
-       effective (6.7.4).
+       effective (6.7.4).
 

-
-
+
 

 
J.3.9 [Structures, unions, enumerations, and bit-fields]

-

-
-
+
 
1   -- Whether a ``plain'' int bit-field is treated as a signed int bit-field or as an
-       unsigned int bit-field (6.7.2, 6.7.2.1).
+       unsigned int bit-field (6.7.2, 6.7.2.1).
     -- Allowable bit-field types other than _Bool, signed int, and unsigned int
-       (6.7.2.1).
-    -- Whether atomic types are permitted for bit-fields (6.7.2.1).
-    -- Whether a bit-field can straddle a storage-unit boundary (6.7.2.1).
-    -- The order of allocation of bit-fields within a unit (6.7.2.1).
-    -- The alignment of non-bit-field members of structures (6.7.2.1). This should present
+       (6.7.2.1).
+    -- Whether atomic types are permitted for bit-fields (6.7.2.1).
+    -- Whether a bit-field can straddle a storage-unit boundary (6.7.2.1).
+    -- The order of allocation of bit-fields within a unit (6.7.2.1).
+    -- The alignment of non-bit-field members of structures (6.7.2.1). This should present
        no problem unless binary data written by one implementation is read by another.
-    -- The integer type compatible with each enumerated type (6.7.2.2).
+    -- The integer type compatible with each enumerated type (6.7.2.2).
 

-
-
+
 

 
J.3.10 [Qualifiers]

-

-
-
-
1   -- What constitutes an access to an object that has volatile-qualified type (6.7.3).
+
+
1   -- What constitutes an access to an object that has volatile-qualified type (6.7.3).
 

-
-
+
 

 
J.3.11 [Preprocessing directives]

-

-
-
+
 
1   -- The locations within #pragma directives where header name preprocessing tokens
-       are recognized (6.4, 6.4.7).
+       are recognized (6.4, 6.4.7).
     -- How sequences in both forms of header names are mapped to headers or external
-       source file names (6.4.7).
+       source file names (6.4.7).
     -- Whether the value of a character constant in a constant expression that controls
        conditional inclusion matches the value of the same character constant in the
-       execution character set (6.10.1).
+       execution character set (6.10.1).
     -- Whether the value of a single-character character constant in a constant expression
-       that controls conditional inclusion may have a negative value (6.10.1).
+       that controls conditional inclusion may have a negative value (6.10.1).
     -- The places that are searched for an included < > delimited header, and how the places
-       are specified or the header is identified (6.10.2).
+       are specified or the header is identified (6.10.2).
     -- How the named source file is searched for in an included " " delimited header
-       (6.10.2).
+       (6.10.2).
     -- The method by which preprocessing tokens (possibly resulting from macro
-       expansion) in a #include directive are combined into a header name (6.10.2).
-    -- The nesting limit for #include processing (6.10.2).
+       expansion) in a #include directive are combined into a header name (6.10.2).
+    -- The nesting limit for #include processing (6.10.2).
     -- Whether the # operator inserts a \ character before the \ character that begins a
-       universal character name in a character constant or string literal (6.10.3.2).
-    -- The behavior on each recognized non-STDC #pragma directive (6.10.6).
+       universal character name in a character constant or string literal (6.10.3.2).
+    -- The behavior on each recognized non-STDC #pragma directive (6.10.6).
     -- The definitions for _ _DATE_ _ and _ _TIME_ _ when respectively, the date and
-       time of translation are not available (6.10.8.1).
+       time of translation are not available (6.10.8.1).
 

-
-
+
 

 
J.3.12 [Library functions]

-

-
-
+
 
1   -- Any library facilities available to a freestanding program, other than the minimal set
-       required by clause 4 (5.1.2.1).
-    -- The format of the diagnostic printed by the assert macro (7.2.1.1).
+       required by clause 4 (5.1.2.1).
+    -- The format of the diagnostic printed by the assert macro (7.2.1.1).
     -- The representation of the floating-point              status   flags   stored   by   the
-       fegetexceptflag function (7.6.2.2).
+       fegetexceptflag function (7.6.2.2).
     -- Whether the feraiseexcept function raises the ``inexact'' floating-point
        exception in addition to the ``overflow'' or ``underflow'' floating-point exception
-       (7.6.2.3).
+       (7.6.2.3).
     -- Strings other than "C" and "" that may be passed as the second argument to the
-       setlocale function (7.11.1.1).
+       setlocale function (7.11.1.1).
     -- The types defined for float_t and double_t when the value of the
-       FLT_EVAL_METHOD macro is less than 0 (7.12).
+       FLT_EVAL_METHOD macro is less than 0 (7.12).
     -- Domain errors for the mathematics functions, other than those required by this
-       International Standard (7.12.1).
+       International Standard (7.12.1).
     -- The values returned by the mathematics functions on domain errors or pole errors
-       (7.12.1).
+       (7.12.1).
     -- The values returned by the mathematics functions on underflow range errors, whether
        errno is set to the value of the macro ERANGE when the integer expression
        math_errhandling & MATH_ERRNO is nonzero, and whether the ``underflow''
        floating-point exception is raised when the integer expression math_errhandling
-       & MATH_ERREXCEPT is nonzero. (7.12.1).
+       & MATH_ERREXCEPT is nonzero. (7.12.1).
 
     -- Whether a domain error occurs or zero is returned when an fmod function has a
-       second argument of zero (7.12.10.1).
+       second argument of zero (7.12.10.1).
     -- Whether a domain error occurs or zero is returned when a remainder function has
-       a second argument of zero (7.12.10.2).
+       a second argument of zero (7.12.10.2).
     -- The base-2 logarithm of the modulus used by the remquo functions in reducing the
-       quotient (7.12.10.3).
+       quotient (7.12.10.3).
     -- Whether a domain error occurs or zero is returned when a remquo function has a
-       second argument of zero (7.12.10.3).
+       second argument of zero (7.12.10.3).
     -- Whether the equivalent of signal(sig, SIG_DFL); is executed prior to the call
-       of a signal handler, and, if not, the blocking of signals that is performed (7.14.1.1).
-    -- The null pointer constant to which the macro NULL expands (7.19).
+       of a signal handler, and, if not, the blocking of signals that is performed (7.14.1.1).
+    -- The null pointer constant to which the macro NULL expands (7.19).
     -- Whether the last line of a text stream requires a terminating new-line character
-       (7.21.2).
+       (7.21.2).
     -- Whether space characters that are written out to a text stream immediately before a
-       new-line character appear when read in (7.21.2).
+       new-line character appear when read in (7.21.2).
     -- The number of null characters that may be appended to data written to a binary
-       stream (7.21.2).
+       stream (7.21.2).
     -- Whether the file position indicator of an append-mode stream is initially positioned at
-       the beginning or end of the file (7.21.3).
+       the beginning or end of the file (7.21.3).
     -- Whether a write on a text stream causes the associated file to be truncated beyond that
-       point (7.21.3).
-    -- The characteristics of file buffering (7.21.3).
-    -- Whether a zero-length file actually exists (7.21.3).
-    -- The rules for composing valid file names (7.21.3).
-    -- Whether the same file can be simultaneously open multiple times (7.21.3).
-    -- The nature and choice of encodings used for multibyte characters in files (7.21.3).
-    -- The effect of the remove function on an open file (7.21.4.1).
+       point (7.21.3).
+    -- The characteristics of file buffering (7.21.3).
+    -- Whether a zero-length file actually exists (7.21.3).
+    -- The rules for composing valid file names (7.21.3).
+    -- Whether the same file can be simultaneously open multiple times (7.21.3).
+    -- The nature and choice of encodings used for multibyte characters in files (7.21.3).
+    -- The effect of the remove function on an open file (7.21.4.1).
     -- The effect if a file with the new name exists prior to a call to the rename function
-       (7.21.4.2).
+       (7.21.4.2).
     -- Whether an open temporary file is removed upon abnormal program termination
-       (7.21.4.3).
+       (7.21.4.3).
     -- Which changes of mode are permitted (if any), and under what circumstances
-       (7.21.5.4).
+       (7.21.5.4).
 
     -- The style used to print an infinity or NaN, and the meaning of any n-char or n-wchar
-       sequence printed for a NaN (7.21.6.1, 7.29.2.1).
-    -- The output for %p conversion in the fprintf or fwprintf function (7.21.6.1,
-         7.29.2.1).
+       sequence printed for a NaN (7.21.6.1, 7.29.2.1).
+    -- The output for %p conversion in the fprintf or fwprintf function (7.21.6.1,
+         7.29.2.1).
     -- The interpretation of a - character that is neither the first nor the last character, nor
        the second where a ^ character is the first, in the scanlist for %[ conversion in the
-       fscanf or fwscanf function (7.21.6.2, 7.29.2.1).
+       fscanf or fwscanf function (7.21.6.2, 7.29.2.1).
     -- The set of sequences matched by a %p conversion and the interpretation of the
-       corresponding input item in the fscanf or fwscanf function (7.21.6.2, 7.29.2.2).
+       corresponding input item in the fscanf or fwscanf function (7.21.6.2, 7.29.2.2).
     -- The value to which the macro errno is set by the fgetpos, fsetpos, or ftell
-       functions on failure (7.21.9.1, 7.21.9.3, 7.21.9.4).
+       functions on failure (7.21.9.1, 7.21.9.3, 7.21.9.4).
     -- The meaning of any n-char or n-wchar sequence in a string representing a NaN that is
        converted by the strtod, strtof, strtold, wcstod, wcstof, or wcstold
-       function (7.22.1.3, 7.29.4.1.1).
+       function (7.22.1.3, 7.29.4.1.1).
     -- Whether or not the strtod, strtof, strtold, wcstod, wcstof, or wcstold
-       function sets errno to ERANGE when underflow occurs (7.22.1.3, 7.29.4.1.1).
+       function sets errno to ERANGE when underflow occurs (7.22.1.3, 7.29.4.1.1).
     -- Whether the calloc, malloc, and realloc functions return a null pointer or a
-       pointer to an allocated object when the size requested is zero (7.22.3).
+       pointer to an allocated object when the size requested is zero (7.22.3).
     -- Whether open streams with unwritten buffered data are flushed, open streams are
        closed, or temporary files are removed when the abort or _Exit function is called
-       (7.22.4.1, 7.22.4.5).
+       (7.22.4.1, 7.22.4.5).
     -- The termination status returned to the host environment by the abort, exit,
-       _Exit, or quick_exit function (7.22.4.1, 7.22.4.4, 7.22.4.5, 7.22.4.7).
+       _Exit, or quick_exit function (7.22.4.1, 7.22.4.4, 7.22.4.5, 7.22.4.7).
     -- The value returned by the system function when its argument is not a null pointer
-       (7.22.4.8).
-    -- The range and precision of times representable in clock_t and time_t (7.27).                
-    -- The local time zone and Daylight Saving Time (7.27.1).
-    -- The era for the clock function (7.27.2.1).
-    -- The TIME_UTC epoch (7.27.2.5).
+       (7.22.4.8).
+    -- The range and precision of times representable in clock_t and time_t (7.27).
+    -- The local time zone and Daylight Saving Time (7.27.1).
+    -- The era for the clock function (7.27.2.1).
+    -- The TIME_UTC epoch (7.27.2.5).
     -- The replacement string for the %Z specifier to the strftime, and wcsftime
-       functions in the "C" locale (7.27.3.5, 7.29.5.1).
+       functions in the "C" locale (7.27.3.5, 7.29.5.1).
     -- Whether the functions in <math.h> honor the rounding direction mode in an
-       IEC 60559 conformant implementation, unless explicitly specified otherwise (F.10).
+       IEC 60559 conformant implementation, unless explicitly specified otherwise (F.10).
 
 

-
-
+
 

 
J.3.13 [Architecture]

-

-
-
+
 
1   -- The values or expressions assigned to the macros specified in the headers
-       <float.h>, <limits.h>, and <stdint.h> (5.2.4.2, 7.20.2, 7.20.3).
+       <float.h>, <limits.h>, and <stdint.h> (5.2.4.2, 7.20.2, 7.20.3).
     -- The result of attempting to indirectly access an object with automatic or thread
-       storage duration from a thread other than the one with which it is associated (6.2.4).
+       storage duration from a thread other than the one with which it is associated (6.2.4).
     -- The number, order, and encoding of bytes in any object (when not explicitly specified
-       in this International Standard) (6.2.6.1).
+       in this International Standard) (6.2.6.1).
     -- Whether any extended alignments are supported and the contexts in which they are
-       supported (6.2.8).
+       supported (6.2.8).
     -- Valid alignment values other than those returned by an _Alignof expression for
-       fundamental types, if any (6.2.8).
-    -- The value of the result of the sizeof and _Alignof operators (6.5.3.4).
+       fundamental types, if any (6.2.8).
+    -- The value of the result of the sizeof and _Alignof operators (6.5.3.4).
 

-
-
+
 

 
J.4 [Locale-specific behavior]

-

-
-
+
 
1   The following characteristics of a hosted environment are locale-specific and are required
     to be documented by the implementation:
     -- Additional members of the source and execution character sets beyond the basic
-       character set (5.2.1).
+       character set (5.2.1).
     -- The presence, meaning, and representation of additional multibyte characters in the
-       execution character set beyond the basic character set (5.2.1.2).
-    -- The shift states used for the encoding of multibyte characters (5.2.1.2).
-    -- The direction of writing of successive printing characters (5.2.2).
-    -- The decimal-point character (7.1.1).
-    -- The set of printing characters (7.4, 7.30.2).
-    -- The set of control characters (7.4, 7.30.2).
+       execution character set beyond the basic character set (5.2.1.2).
+    -- The shift states used for the encoding of multibyte characters (5.2.1.2).
+    -- The direction of writing of successive printing characters (5.2.2).
+    -- The decimal-point character (7.1.1).
+    -- The set of printing characters (7.4, 7.30.2).
+    -- The set of control characters (7.4, 7.30.2).
     -- The sets of characters tested for by the isalpha, isblank, islower, ispunct,
        isspace, isupper, iswalpha, iswblank, iswlower, iswpunct,
-       iswspace, or iswupper functions (7.4.1.2, 7.4.1.3, 7.4.1.7, 7.4.1.9, 7.4.1.10,
-       7.4.1.11, 7.30.2.1.2, 7.30.2.1.3, 7.30.2.1.7, 7.30.2.1.9, 7.30.2.1.10, 7.30.2.1.11).
-    -- The native environment (7.11.1.1).
-    -- Additional subject sequences accepted by the numeric conversion functions (7.22.1,
-       7.29.4.1).
-    -- The collation sequence of the execution character set (7.24.4.3, 7.29.4.4.2).
+       iswspace, or iswupper functions (7.4.1.2, 7.4.1.3, 7.4.1.7, 7.4.1.9, 7.4.1.10,
+       7.4.1.11, 7.30.2.1.2, 7.30.2.1.3, 7.30.2.1.7, 7.30.2.1.9, 7.30.2.1.10, 7.30.2.1.11).
+    -- The native environment (7.11.1.1).
+    -- Additional subject sequences accepted by the numeric conversion functions (7.22.1,
+       7.29.4.1).
+    -- The collation sequence of the execution character set (7.24.4.3, 7.29.4.4.2).
     -- The contents of the error message strings set up by the strerror function
-       (7.24.6.2).
-    -- The formats for time and date (7.27.3.5, 7.29.5.1).
-    -- Character mappings that are supported by the towctrans function (7.30.1).
-    -- Character classifications that are supported by the iswctype function (7.30.1).
+       (7.24.6.2).
+    -- The formats for time and date (7.27.3.5, 7.29.5.1).
+    -- Character mappings that are supported by the towctrans function (7.30.1).
+    -- Character classifications that are supported by the iswctype function (7.30.1).
 

-
-
+
 

 
J.5 [Common extensions]

-

-
-
+
 
1   The following extensions are widely used in many systems, but are not portable to all
     implementations. The inclusion of any extension that may cause a strictly conforming
     program to become invalid renders an implementation nonconforming. Examples of such
     extensions are new keywords, extra library functions declared in standard headers, or
     predefined macros with names that do not begin with an underscore.
 

-
-
+
 

 
J.5.1 [Environment arguments]

-

-
-
+
 
1   In a hosted environment, the main function receives a third argument, char *envp[],
     that points to a null-terminated array of pointers to char, each of which points to a string
     that provides information about the environment for this execution of the program
-    (5.1.2.2.1).
+    (5.1.2.2.1).
 

-
-
+
 

 
J.5.2 [Specialized identifiers]

-

-
-
+
 
1   Characters other than the underscore _, letters, and digits, that are not part of the basic
     source character set (such as the dollar sign $, or characters in national character sets)
-    may appear in an identifier (6.4.2).
+    may appear in an identifier (6.4.2).
 

-
-
+
 

 
J.5.3 [Lengths and cases of identifiers]

-

-
-
-
1   All characters in identifiers (with or without external linkage) are significant (6.4.2).
+
+
1   All characters in identifiers (with or without external linkage) are significant (6.4.2).
 

-
-
+
 

 
J.5.4 [Scopes of identifiers]

-

-
-
+
 
1   A function identifier, or the identifier of an object the declaration of which contains the
-    keyword extern, has file scope (6.2.1).
+    keyword extern, has file scope (6.2.1).
 

-
-
+
 

 
J.5.5 [Writable string literals]

-

-
-
+
 
1   String literals are modifiable (in which case, identical string literals should denote distinct
-    objects) (6.4.5).
+    objects) (6.4.5).
 

-
-
+
 

 
J.5.6 [Other arithmetic types]

-

-
-
+
 
1   Additional arithmetic types, such as _ _int128 or double double, and their
-    appropriate conversions are defined (6.2.5, 6.3.1). Additional floating types may have
+    appropriate conversions are defined (6.2.5, 6.3.1). Additional floating types may have
     more range or precision than long double, may be used for evaluating expressions of
     other floating types, and may be used to define float_t or double_t. Additional
     floating types may also have less range or precision than float.
 

-
-
+
 

 
J.5.7 [Function pointer casts]

-

-
-
+
 
1   A pointer to an object or to void may be cast to a pointer to a function, allowing data to
-    be invoked as a function (6.5.4).
+    be invoked as a function (6.5.4).
 

-
-
+
 
2   A pointer to a function may be cast to a pointer to an object or to void, allowing a
-    function to be inspected or modified (for example, by a debugger) (6.5.4).
+    function to be inspected or modified (for example, by a debugger) (6.5.4).
 

-
-
+
 

 
J.5.8 [Extended bit-field types]

-

-
-
+
 
1   A bit-field may be declared with a type other than _Bool, unsigned int, or
-    signed int, with an appropriate maximum width (6.7.2.1).
+    signed int, with an appropriate maximum width (6.7.2.1).
 

-
-
+
 

 
J.5.9 [The fortran keyword]

-

-
-
+
 
1   The fortran function specifier may be used in a function declaration to indicate that
     calls suitable for FORTRAN should be generated, or that a different representation for the
-    external name is to be generated (6.7.4).
+    external name is to be generated (6.7.4).
 

-
-
+
 

 
J.5.10 [The asm keyword]

-

-
-
+
 
1   The asm keyword may be used to insert assembly language directly into the translator
-    output (6.8). The most common implementation is via a statement of the form:
+    output (6.8). The most common implementation is via a statement of the form:
            asm ( character-string-literal );
 

-
-
+
 

 
J.5.11 [Multiple external definitions]

-

-
-
+
 
1   There may be more than one external definition for the identifier of an object, with or
     without the explicit use of the keyword extern; if the definitions disagree, or more than
-    one is initialized, the behavior is undefined (6.9.2).
+    one is initialized, the behavior is undefined (6.9.2).
 

-
-
+
 

 
J.5.12 [Predefined macro names]

-

-
-
+
 
1   Macro names that do not begin with an underscore, describing the translation and
     execution environments, are defined by the implementation before translation begins
-    (6.10.8).
+    (6.10.8).
 

-
-
+
 

 
J.5.13 [Floating-point status flags]

-

-
-
+
 
1   If any floating-point status flags are set on normal termination after all calls to functions
-    registered by the atexit function have been made (see 7.22.4.4), the implementation
+    registered by the atexit function have been made (see 7.22.4.4), the implementation
     writes some diagnostics indicating the fact to the stderr stream, if it is still open,
 

-
-
+
 

 
J.5.14 [Extra arguments for signal handlers]

-

-
-
+
 
1   Handlers for specific signals are called with extra arguments in addition to the signal
-    number (7.14.1.1).
+    number (7.14.1.1).
 

-
-
+
 

 
J.5.15 [Additional stream types and file-opening modes]

-

-
-
-
1   Additional mappings from files to streams are supported (7.21.2).
+
+
1   Additional mappings from files to streams are supported (7.21.2).
 

-
-
+
 
2   Additional file-opening modes may be specified by characters appended to the mode
-    argument of the fopen function (7.21.5.3).
+    argument of the fopen function (7.21.5.3).
 

-
-
+
 

 
J.5.16 [Defined file position indicator]

-

-
-
+
 
1   The file position indicator is decremented by each successful call to the ungetc or
-    ungetwc function for a text stream, except if its value was zero before a call (7.21.7.10, 7.29.3.10).
+    ungetwc function for a text stream, except if its value was zero before a call (7.21.7.10, 7.29.3.10).
 

-
-
+
 

 
J.5.17 [Math error reporting]

-

-
-
+
 
1   Functions declared in <complex.h> and <math.h> raise SIGFPE to report errors
-    instead of, or in addition to, setting errno or raising floating-point exceptions (7.3, 7.12).
+    instead of, or in addition to, setting errno or raising floating-point exceptions (7.3, 7.12).
                                            Annex K
                                           (normative)
 

-
-
+
 

 
K. [Bounds-checking interfaces]

-
 Bounds-checking interfaces
-

-
-
+
 

 
K.1 [Background]

-

-
-
+
 
1   Traditionally, the C Library has contained many functions that trust the programmer to
     provide output character arrays big enough to hold the result being produced. Not only
     do these functions not check that the arrays are big enough, they frequently lack the
@@ -32550,152 +28064,136 @@ the specified values is outside the normal range, the characters stored are unsp
     error-free code using the existing library, the library tends to promote programming styles
     that lead to mysterious failures if a result is too big for the provided array.
 

-
-
+
 
2   A common programming style is to declare character arrays large enough to handle most
     practical cases. However, if these arrays are not large enough to handle the resulting
     strings, data can be written past the end of the array overwriting other data and program
     structures. The program never gets any indication that a problem exists, and so never has
     a chance to recover or to fail gracefully.
 

-
-
+
 
3   Worse, this style of programming has compromised the security of computers and
     networks. Buffer overflows can often be exploited to run arbitrary code with the
     permissions of the vulnerable (defective) program.
 

-
-
+
 
4   If the programmer writes runtime checks to verify lengths before calling library
     functions, then those runtime checks frequently duplicate work done inside the library
     functions, which discover string lengths as a side effect of doing their job.
 

-
-
+
 
5   This annex provides alternative library functions that promote safer, more secure
     programming. The alternative functions verify that output buffers are large enough for
     the intended result and return a failure indicator if they are not. Data is never written past
     the end of an array. All string results are null terminated.
 

-
-
+
 
6   This annex also addresses another problem that complicates writing robust code:
     functions that are not reentrant because they return pointers to static objects owned by the
     function. Such functions can be troublesome since a previously returned result can
     change if the function is called again, perhaps by another thread.
 

-
-
+
 

 
K.2 [Scope]

-

-
-
+
 
1   This annex specifies a series of optional extensions that can be useful in the mitigation of
     security vulnerabilities in programs, and comprise new functions, macros, and types
     declared or defined in existing standard headers.
 

-
-
+
 
2   An implementation that defines _ _STDC_LIB_EXT1_ _ shall conform to the
-    specifications in this annex.380)
+    specifications in this annex.[380]
 

+
+
Footnote 380) Implementations that do not define _ _STDC_LIB_EXT1_ _ are not required to conform to these
+         specifications.
+

 
-
-
3   Subclause K.3 should be read as if it were merged into the parallel structure of named
+
+
3   Subclause K.3 should be read as if it were merged into the parallel structure of named
     subclauses of clause 7.
 

-
-
+
 

 
K.3 [Library]

-
 Library
-

-
-
+
 

 
K.3.1 [Introduction]

-
 Introduction
-

-
-
+
 

 
K.3.1.1 [Standard headers]

-

-
-
-
1   The functions, macros, and types declared or defined in K.3 and its subclauses are not
+
+
1   The functions, macros, and types declared or defined in K.3 and its subclauses are not
     declared or defined by their respective headers if _ _STDC_WANT_LIB_EXT1_ _ is
     defined as a macro which expands to the integer constant 0 at the point in the source file
     where the appropriate header is first included.
 

-
-
-
2   The functions, macros, and types declared or defined in K.3 and its subclauses are
+
+
2   The functions, macros, and types declared or defined in K.3 and its subclauses are
     declared and defined by their respective headers if _ _STDC_WANT_LIB_EXT1_ _ is
     defined as a macro which expands to the integer constant 1 at the point in the source file
-    where the appropriate header is first included.381)
+    where the appropriate header is first included.[381]
 

+
+
Footnote 381) Future revisions of this International Standard may define meanings for other values of
+         _ _STDC_WANT_LIB_EXT1_ _.
+

 
-
+
 
3   It is implementation-defined whether the functions, macros, and types declared or defined
-    in K.3 and its subclauses are declared or defined by their respective headers if
+    in K.3 and its subclauses are declared or defined by their respective headers if
     _ _STDC_WANT_LIB_EXT1_ _ is not defined as a macro at the point in the source file
-    where the appropriate header is first included.382)
+    where the appropriate header is first included.[382]
 

+
+
Footnote 382) Subclause 7.1.3 reserves certain names and patterns of names that an implementation may use in
+         headers. All other names are not reserved, and a conforming implementation is not permitted to use
+         them. While some of the names defined in K.3 and its subclauses are reserved, others are not. If an
+         unreserved name is defined in a header when _ _STDC_WANT_LIB_EXT1_ _ is defined as 0, the
+         implementation is not conforming.
+

 
-
+
 
4   Within a preprocessing translation unit, _ _STDC_WANT_LIB_EXT1_ _ shall be
-    defined identically for all inclusions of any headers from subclause K.3. If
+    defined identically for all inclusions of any headers from subclause K.3. If
     _ _STDC_WANT_LIB_EXT1_ _ is defined differently for any such inclusion, the
     implementation shall issue a diagnostic as if a preprocessor error directive were used.
 
 

-
-
+
 

 
K.3.1.2 [Reserved identifiers]

-

-
-
+
 
1   Each macro name in any of the following subclauses is reserved for use as specified if it
     is defined by any of its associated headers when included; unless explicitly stated
-    otherwise (see 7.1.4).
+    otherwise (see 7.1.4).
 

-
-
+
 
2   All identifiers with external linkage in any of the following subclauses are reserved for
     use as identifiers with external linkage if any of them are used by the program. None of
     them are reserved if none of them are used.
 

-
-
+
 
3   Each identifier with file scope listed in any of the following subclauses is reserved for use
     as a macro name and as an identifier with file scope in the same name space if it is
     defined by any of its associated headers when included.
 

-
-
+
 

 
K.3.1.3 [Use of errno]

-

-
-
+
 
1   An implementation may set errno for the functions defined in this annex, but is not
     required to.
 

-
-
+
 

 
K.3.1.4 [Runtime-constraint violations]

-

-
-
+
 
1   Most functions in this annex include as part of their specification a list of runtime-
     constraints. These runtime-constraints are requirements on the program using the
-    library.383)
+    library.[383]
 

-
 
 
Footnote 383) Although runtime-constraints replace many cases of undefined behavior, undefined behavior still
          exists in this annex. Implementations are free to detect any case of undefined behavior and treat it as a
@@ -32703,7 +28201,7 @@ the specified values is outside the normal range, the characters stored are unsp
          from the definition of undefined behavior.
 

 
-
+
 
2   Implementations shall verify that the runtime-constraints for a function are not violated
     by the program. If a runtime-constraint is violated, the implementation shall call the
     currently registered runtime-constraint handler (see set_constraint_handler_s
@@ -32711,112 +28209,91 @@ the specified values is outside the normal range, the characters stored are unsp
     function result in only one call to the runtime-constraint handler. It is unspecified which
     one of the multiple runtime-constraint violations cause the handler to be called.
 

-
-
+
 
3   If the runtime-constraints section for a function states an action to be performed when a
     runtime-constraint violation occurs, the function shall perform the action before calling
     the runtime-constraint handler. If the runtime-constraints section lists actions that are
     prohibited when a runtime-constraint violation occurs, then such actions are prohibited to
     the function both before calling the handler and after the handler returns.
 

-
-
+
 
4   The runtime-constraint handler might not return. If the handler does return, the library
     function whose runtime-constraint was violated shall return some indication of failure as
     given by the returns section in the function's specification.
 
 

-
-
+
 

-
K.3.2 [Errors ]

-

-
-
+
K.3.2 [Errors <errno.h>]

+
 
1   The header <errno.h> defines a type.
 

-
-
+
 
2   The type is
              errno_t
-    which is type int.384)
+    which is type int.[384]
 

-
 
 
Footnote 384) As a matter of programming style, errno_t may be used as the type of something that deals only
          with the values that might be found in errno. For example, a function which returns the value of
          errno might be declared as having the return type errno_t.
 

 
-
+
 

-
K.3.3 [Common definitions ]

-

-
-
+
K.3.3 [Common definitions <stddef.h>]

+
 
1   The header <stddef.h> defines a type.
 

-
-
+
 
2   The type is
              rsize_t
-    which is the type size_t.385)
+    which is the type size_t.[385]
 

-
 
 
Footnote 385) See the description of the RSIZE_MAX macro in <stdint.h>.
 

 
-
+
 

-
K.3.4 [Integer types ]

-

-
-
+
K.3.4 [Integer types <stdint.h>]

+
 
1   The header <stdint.h> defines a macro.
 

-
-
+
 
2   The macro is
              RSIZE_MAX
-    which expands to a value386) of type size_t. Functions that have parameters of type
+    which expands to a value[386] of type size_t. Functions that have parameters of type
     rsize_t consider it a runtime-constraint violation if the values of those parameters are
     greater than RSIZE_MAX.
     Recommended practice
 

-
 
 
Footnote 386) The macro RSIZE_MAX need not expand to a constant expression.
+    is no object size that is considered a runtime-constraint violation.
 

 
-
+
 
3   Extremely large object sizes are frequently a sign that an object's size was calculated
     incorrectly. For example, negative numbers appear as very large positive numbers when
     converted to an unsigned type like size_t. Also, some implementations do not support
     objects as large as the maximum value that can be represented by type size_t.
 

-
-
+
 
4   For those reasons, it is sometimes beneficial to restrict the range of object sizes to detect
     programming errors. For implementations targeting machines with large address spaces,
     it is recommended that RSIZE_MAX be defined as the smaller of the size of the largest
     object supported or (SIZE_MAX >> 1), even if this limit is smaller than the size of
     some legitimate, but very large, objects. Implementations targeting machines with small
     address spaces may wish to define RSIZE_MAX as SIZE_MAX, which means that there
-
-    is no object size that is considered a runtime-constraint violation.
 

-
-
+
 

-
K.3.5 [Input/output ]

-

-
-
+
K.3.5 [Input/output <stdio.h>]

+
 
1   The header <stdio.h> defines several macros and two types.
 

-
-
+
 
2   The macros are
            L_tmpnam_s
     which expands to an integer constant expression that is the size needed for an array of
@@ -32826,43 +28303,34 @@ the specified values is outside the normal range, the characters stored are unsp
     which expands to an integer constant expression that is the maximum number of unique
     file names that can be generated by the tmpnam_s function.
 

-
-
+
 
3   The types are
            errno_t
     which is type int; and
            rsize_t
     which is the type size_t.
 

-
-
+
 

 
K.3.5.1 [Operations on files]

-
 Operations on files
-

-
-
+
 

 
K.3.5.1.1 [The tmpfile_s function]

-

-
-
-
1          #define _ _STDC_WANT_LIB_EXT1_ _ 1
+
+
1 Synopsis
+          #define _ _STDC_WANT_LIB_EXT1_ _ 1
            #include <stdio.h>
            errno_t tmpfile_s(FILE * restrict * restrict streamptr);
     Runtime-constraints
 

-
-
+
 
2   streamptr shall not be a null pointer.
 

-
-
+
 
3   If there is a runtime-constraint violation, tmpfile_s does not attempt to create a file.
     Description
 

-
-
+
 
4   The tmpfile_s function creates a temporary binary file that is different from any other
     existing file and that will automatically be removed when it is closed or at program
     termination. If the program terminates abnormally, whether an open temporary file is
@@ -32870,8 +28338,7 @@ the specified values is outside the normal range, the characters stored are unsp
     with the meaning that mode has in the fopen_s function (including the mode's effect
     on exclusive access and file permissions).
 

-
-
+
 
5   If the file was created successfully, then the pointer to FILE pointed to by streamptr
     will be set to the pointer to the object controlling the opened file. Otherwise, the pointer
     to FILE pointed to by streamptr will be set to a null pointer.
@@ -32882,38 +28349,32 @@ the specified values is outside the normal range, the characters stored are unsp
     files (FOPEN_MAX).
     Returns
 

-
-
+
 
6   The tmpfile_s function returns zero if it created the file. If it did not create the file or
     there was a runtime-constraint violation, tmpfile_s returns a nonzero value.
 

-
-
+
 

 
K.3.5.1.2 [The tmpnam_s function]

-

-
-
-
1           #define _ _STDC_WANT_LIB_EXT1_ _ 1
+
+
1 Synopsis
+           #define _ _STDC_WANT_LIB_EXT1_ _ 1
             #include <stdio.h>
             errno_t tmpnam_s(char *s, rsize_t maxsize);
     Runtime-constraints
 

-
-
+
 
2   s shall not be a null pointer. maxsize shall be less than or equal to RSIZE_MAX.
     maxsize shall be greater than the length of the generated file name string.
     Description
 

-
-
+
 
3   The tmpnam_s function generates a string that is a valid file name and that is not the
-    same as the name of an existing file.387) The function is potentially capable of generating
+    same as the name of an existing file.[387] The function is potentially capable of generating
     TMP_MAX_S different strings, but any or all of them may already be in use by existing
     files and thus not be suitable return values. The lengths of these strings shall be less than
     the value of the L_tmpnam_s macro.
 

-
 
 
Footnote 387) Files created using strings generated by the tmpnam_s function are temporary only in the sense that
          their names should not collide with those generated by conventional naming rules for the
@@ -32924,28 +28385,26 @@ the specified values is outside the normal range, the characters stored are unsp
          generate the same temporary file names.
 

 
-
+
 
4   The tmpnam_s function generates a different string each time it is called.
 

-
-
+
 
5   It is assumed that s points to an array of at least maxsize characters. This array will be
     set to generated string, as specified below.
 
 

-
-
+
 
6    The implementation shall behave as if no library function except tmpnam calls the
-     tmpnam_s function.388)
+     tmpnam_s function.[388]
      Recommended practice
 

-
 
 
Footnote 388) An implementation may have tmpnam call tmpnam_s (perhaps so there is only one naming
           convention for temporary files), but this is not required.
+    Description
 

 
-
+
 
7    After a program obtains a file name using the tmpnam_s function and before the
      program creates a file with that name, the possibility exists that someone else may create
      a file with that same name. To avoid this race condition, the tmpfile_s function
@@ -32954,61 +28413,47 @@ the specified values is outside the normal range, the characters stored are unsp
      rather than a temporary file.
      Returns
 

-
-
+
 
8    If no suitable string can be generated, or if there is a runtime-constraint violation, the
      tmpnam_s function writes a null character to s[0] (only if s is not null and maxsize
      is greater than zero) and returns a nonzero value.
 

-
-
+
 
9    Otherwise, the tmpnam_s function writes the string in the array pointed to by s and
      returns zero.
      Environmental limits
 

-
-
+
 
10   The value of the macro TMP_MAX_S shall be at least 25.
 

-
-
+
 

 
K.3.5.2 [File access functions]

-
 File access functions
-

-
-
+
 

 
K.3.5.2.1 [The fopen_s function]

-

-
-
-
1           #define _ _STDC_WANT_LIB_EXT1_ _ 1
+
+
1 Synopsis
+           #define _ _STDC_WANT_LIB_EXT1_ _ 1
             #include <stdio.h>
             errno_t fopen_s(FILE * restrict * restrict streamptr,
                  const char * restrict filename,
                  const char * restrict mode);
      Runtime-constraints
 

-
-
+
 
2    None of streamptr, filename, or mode shall be a null pointer.
 

-
-
+
 
3    If there is a runtime-constraint violation, fopen_s does not attempt to open a file.
      Furthermore, if streamptr is not a null pointer, fopen_s sets *streamptr to the
      null pointer.
-
-    Description
 

-
-
+
 
4   The fopen_s function opens the file whose name is the string pointed to by
     filename, and associates a stream with it.
 

-
-
+
 
5   The mode string shall be as described for fopen, with the addition that modes starting
     with the character 'w' or 'a' may be preceded by the character 'u', see below:
     uw             truncate to zero length or create text file for writing, default
@@ -33032,46 +28477,39 @@ the specified values is outside the normal range, the characters stored are unsp
     ua+b or uab+   append; open or create binary file for update, writing at end-of-file,
                    default permissions
 

-
-
+
 
6   Opening a file with exclusive mode ('x' as the last character in the mode argument)
     fails if the file already exists or cannot be created.
 

-
-
+
 
7   To the extent that the underlying system supports the concepts, files opened for writing
     shall be opened with exclusive (also known as non-shared) access. If the file is being
     created, and the first character of the mode string is not 'u', to the extent that the
     underlying system supports it, the file shall have a file permission that prevents other
     users on the system from accessing the file. If the file is being created and first character
     of the mode string is 'u', then by the time the file has been closed, it shall have the
-    system default file access permissions.389)
+    system default file access permissions.[389]
 

-
 
 
Footnote 389) These are the same permissions that the file would have been created with by fopen.
-

-
-
-
8   If the file was opened successfully, then the pointer to FILE pointed to by streamptr
-    will be set to the pointer to the object controlling the opened file. Otherwise, the pointer
-
     to FILE pointed to by streamptr will be set to a null pointer.
     Returns
-

+

 
-
+
+
8   If the file was opened successfully, then the pointer to FILE pointed to by streamptr
+    will be set to the pointer to the object controlling the opened file. Otherwise, the pointer
+

+
 
9   The fopen_s function returns zero if it opened the file. If it did not open the file or if
     there was a runtime-constraint violation, fopen_s returns a nonzero value.
 

-
-
+
 

 
K.3.5.2.2 [The freopen_s function]

-

-
-
-
1          #define _ _STDC_WANT_LIB_EXT1_ _ 1
+
+
1 Synopsis
+          #define _ _STDC_WANT_LIB_EXT1_ _ 1
            #include <stdio.h>
            errno_t freopen_s(FILE * restrict * restrict newstreamptr,
                 const char * restrict filename,
@@ -33079,154 +28517,132 @@ the specified values is outside the normal range, the characters stored are unsp
                 FILE * restrict stream);
     Runtime-constraints
 

-
-
+
 
2   None of newstreamptr, mode, and stream shall be a null pointer.
 

-
-
+
 
3   If there is a runtime-constraint violation, freopen_s neither attempts to close any file
     associated with stream nor attempts to open a file. Furthermore, if newstreamptr is
     not a null pointer, fopen_s sets *newstreamptr to the null pointer.
     Description
 

-
-
+
 
4   The freopen_s function opens the file whose name is the string pointed to by
     filename and associates the stream pointed to by stream with it. The mode
     argument has the same meaning as in the fopen_s function (including the mode's effect
     on exclusive access and file permissions).
 

-
-
+
 
5   If filename is a null pointer, the freopen_s function attempts to change the mode of
     the stream to that specified by mode, as if the name of the file currently associated with
     the stream had been used. It is implementation-defined which changes of mode are
     permitted (if any), and under what circumstances.
 

-
-
+
 
6   The freopen_s function first attempts to close any file that is associated with stream.
     Failure to close the file is ignored. The error and end-of-file indicators for the stream are
     cleared.
 

-
-
+
 
7   If the file was opened successfully, then the pointer to FILE pointed to by
     newstreamptr will be set to the value of stream. Otherwise, the pointer to FILE
     pointed to by newstreamptr will be set to a null pointer.
     Returns
 

-
-
+
 
8   The freopen_s function returns zero if it opened the file. If it did not open the file or
     there was a runtime-constraint violation, freopen_s returns a nonzero value.
 
 

-
-
+
 

 
K.3.5.3 [Formatted input/output functions]

-

-
-
+
 
1   Unless explicitly stated otherwise, if the execution of a function described in this
     subclause causes copying to take place between objects that overlap, the objects take on
     unspecified values.
 

-
-
+
 

 
K.3.5.3.1 [The fprintf_s function]

-

-
-
-
1            #define _ _STDC_WANT_LIB_EXT1_ _ 1
+
+
1 Synopsis
+            #define _ _STDC_WANT_LIB_EXT1_ _ 1
              #include <stdio.h>
              int fprintf_s(FILE * restrict stream,
                   const char * restrict format, ...);
     Runtime-constraints
 

-
-
-
2   Neither stream nor format shall be a null pointer. The %n specifier390) (modified or
+
+
2   Neither stream nor format shall be a null pointer. The %n specifier[390] (modified or
     not by flags, field width, or precision) shall not appear in the string pointed to by
     format. Any argument to fprintf_s corresponding to a %s specifier shall not be a
     null pointer.
 

-
 
 
Footnote 390) It is not a runtime-constraint violation for the characters %n to appear in sequence in the string pointed
          at by format when those characters are not a interpreted as a %n specifier. For example, if the entire
          format string was %%n.
 

 
-
-
3   If there is a runtime-constraint violation,391) the fprintf_s function does not attempt
+
+
3   If there is a runtime-constraint violation,[391] the fprintf_s function does not attempt
     to produce further output, and it is unspecified to what extent fprintf_s produced
     output before discovering the runtime-constraint violation.
     Description
 

-
 
 
Footnote 391) Because an implementation may treat any undefined behavior as a runtime-constraint violation, an
          implementation may treat any unsupported specifiers in the string pointed to by format as a runtime-
          constraint violation.
 

 
-
+
 
4   The fprintf_s function is equivalent to the fprintf function except for the explicit
     runtime-constraints listed above.
     Returns
 

-
-
+
 
5   The fprintf_s function returns the number of characters transmitted, or a negative
     value if an output error, encoding error, or runtime-constraint violation occurred.
 
 

-
-
+
 

 
K.3.5.3.2 [The fscanf_s function]

-

-
-
-
1           #define _ _STDC_WANT_LIB_EXT1_ _ 1
+
+
1 Synopsis
+           #define _ _STDC_WANT_LIB_EXT1_ _ 1
             #include <stdio.h>
             int fscanf_s(FILE * restrict stream,
                  const char * restrict format, ...);
     Runtime-constraints
 

-
-
+
 
2   Neither stream nor format shall be a null pointer. Any argument indirected though in
     order to store converted input shall not be a null pointer.
 

-
-
-
3   If there is a runtime-constraint violation,392) the fscanf_s function does not attempt to
+
+
3   If there is a runtime-constraint violation,[392] the fscanf_s function does not attempt to
     perform further input, and it is unspecified to what extent fscanf_s performed input
     before discovering the runtime-constraint violation.
     Description
 

-
 
 
Footnote 392) Because an implementation may treat any undefined behavior as a runtime-constraint violation, an
          implementation may treat any unsupported specifiers in the string pointed to by format as a runtime-
          constraint violation.
 

 
-
+
 
4   The fscanf_s function is equivalent to fscanf except that the c, s, and [ conversion
     specifiers apply to a pair of arguments (unless assignment suppression is indicated by a
     *). The first of these arguments is the same as for fscanf. That argument is
     immediately followed in the argument list by the second argument, which has type
     rsize_t and gives the number of elements in the array pointed to by the first argument
     of the pair. If the first argument points to a scalar object, it is considered to be an array of
-    one element.393)
+    one element.[393]
 

-
 
 
Footnote 393) If the format is known at translation time, an implementation may issue a diagnostic for any argument
          used to store the result from a c, s, or [ conversion specifier if that argument is not followed by an
@@ -33238,23 +28654,20 @@ the specified values is outside the normal range, the characters stored are unsp
          using the hh length modifier, a length argument must follow the pointer argument. Another useful
          diagnostic could flag any non-pointer argument following format that did not have a type
          compatible with rsize_t.
+    fscanf_s function returns the number of input items assigned, which can be fewer than
+    provided for, or even zero, in the event of an early matching failure.
 

 
-
+
 
5   A matching failure occurs if the number of elements in a receiving object is insufficient to
     hold the converted input (including any trailing null character).
     Returns
 

-
-
+
 
6   The fscanf_s function returns the value of the macro EOF if an input failure occurs
     before any conversion or if there is a runtime-constraint violation. Otherwise, the
-
-    fscanf_s function returns the number of input items assigned, which can be fewer than
-    provided for, or even zero, in the event of an early matching failure.
 

-
-
+
 
7   EXAMPLE 1        The call:
              #define _ _STDC_WANT_LIB_EXT1_ _ 1
              #include <stdio.h>
@@ -33267,8 +28680,7 @@ the specified values is outside the normal range, the characters stored are unsp
     thompson\0.
 
 

-
-
+
 
8   EXAMPLE 2        The call:
              #define _ _STDC_WANT_LIB_EXT1_ _ 1
              #include <stdio.h>
@@ -33281,242 +28693,207 @@ the specified values is outside the normal range, the characters stored are unsp
     array of six characters to store it.
 
 

-
-
+
 

 
K.3.5.3.3 [The printf_s function]

-

-
-
-
1            #define _ _STDC_WANT_LIB_EXT1_ _ 1
+
+
1 Synopsis
+            #define _ _STDC_WANT_LIB_EXT1_ _ 1
              #include <stdio.h>
              int printf_s(const char * restrict format, ...);
     Runtime-constraints
 

-
-
-
2   format shall not be a null pointer. The %n specifier394) (modified or not by flags, field
+
+
2   format shall not be a null pointer. The %n specifier[394] (modified or not by flags, field
     width, or precision) shall not appear in the string pointed to by format. Any argument
     to printf_s corresponding to a %s specifier shall not be a null pointer.
 

-
 
 
Footnote 394) It is not a runtime-constraint violation for the characters %n to appear in sequence in the string pointed
          at by format when those characters are not a interpreted as a %n specifier. For example, if the entire
          format string was %%n.
+    Description
 

 
-
+
 
3   If there is a runtime-constraint violation, the printf_s function does not attempt to
     produce further output, and it is unspecified to what extent printf_s produced output
     before discovering the runtime-constraint violation.
-
-    Description
 

-
-
+
 
4   The printf_s function is equivalent to the printf function except for the explicit
     runtime-constraints listed above.
     Returns
 

-
-
+
 
5   The printf_s function returns the number of characters transmitted, or a negative
     value if an output error, encoding error, or runtime-constraint violation occurred.
 

-
-
+
 

 
K.3.5.3.4 [The scanf_s function]

-

-
-
-
1          #define _ _STDC_WANT_LIB_EXT1_ _ 1
+
+
1 Synopsis
+          #define _ _STDC_WANT_LIB_EXT1_ _ 1
            #include <stdio.h>
            int scanf_s(const char * restrict format, ...);
     Runtime-constraints
 

-
-
+
 
2   format shall not be a null pointer. Any argument indirected though in order to store
     converted input shall not be a null pointer.
 

-
-
+
 
3   If there is a runtime-constraint violation, the scanf_s function does not attempt to
     perform further input, and it is unspecified to what extent scanf_s performed input
     before discovering the runtime-constraint violation.
     Description
 

-
-
+
 
4   The scanf_s function is equivalent to fscanf_s with the argument stdin
     interposed before the arguments to scanf_s.
     Returns
 

-
-
+
 
5   The scanf_s function returns the value of the macro EOF if an input failure occurs
     before any conversion or if there is a runtime-constraint violation. Otherwise, the
     scanf_s function returns the number of input items assigned, which can be fewer than
     provided for, or even zero, in the event of an early matching failure.
 

-
-
+
 

 
K.3.5.3.5 [The snprintf_s function]

-

-
-
-
1          #define _ _STDC_WANT_LIB_EXT1_ _ 1
+
+
1 Synopsis
+          #define _ _STDC_WANT_LIB_EXT1_ _ 1
            #include <stdio.h>
            int snprintf_s(char * restrict s, rsize_t n,
                 const char * restrict format, ...);
     Runtime-constraints
 

-
-
+
 
2   Neither s nor format shall be a null pointer. n shall neither equal zero nor be greater
-    than RSIZE_MAX. The %n specifier395) (modified or not by flags, field width, or
+    than RSIZE_MAX. The %n specifier[395] (modified or not by flags, field width, or
     precision) shall not appear in the string pointed to by format. Any argument to
     snprintf_s corresponding to a %s specifier shall not be a null pointer. No encoding
     error shall occur.
 

-
 
 
Footnote 395) It is not a runtime-constraint violation for the characters %n to appear in sequence in the string pointed
          at by format when those characters are not a interpreted as a %n specifier. For example, if the entire
          format string was %%n.
 

 
-
+
 
3   If there is a runtime-constraint violation, then if s is not a null pointer and n is greater
     than zero and less than RSIZE_MAX, then the snprintf_s function sets s[0] to the
     null character.
     Description
 

-
-
+
 
4   The snprintf_s function is equivalent to the snprintf function except for the
     explicit runtime-constraints listed above.
 

-
-
+
 
5   The snprintf_s function, unlike sprintf_s, will truncate the result to fit within the
     array pointed to by s.
     Returns
 

-
-
+
 
6   The snprintf_s function returns the number of characters that would have been
     written had n been sufficiently large, not counting the terminating null character, or a
     negative value if a runtime-constraint violation occurred. Thus, the null-terminated
     output has been completely written if and only if the returned value is nonnegative and
     less than n.
 

-
-
+
 

 
K.3.5.3.6 [The sprintf_s function]

-

-
-
-
1            #define _ _STDC_WANT_LIB_EXT1_ _ 1
+
+
1 Synopsis
+            #define _ _STDC_WANT_LIB_EXT1_ _ 1
              #include <stdio.h>
              int sprintf_s(char * restrict s, rsize_t n,
                   const char * restrict format, ...);
     Runtime-constraints
 

-
-
+
 
2   Neither s nor format shall be a null pointer. n shall neither equal zero nor be greater
     than RSIZE_MAX. The number of characters (including the trailing null) required for the
     result to be written to the array pointed to by s shall not be greater than n. The %n
-    specifier396) (modified or not by flags, field width, or precision) shall not appear in the
+    specifier[396] (modified or not by flags, field width, or precision) shall not appear in the
     string pointed to by format. Any argument to sprintf_s corresponding to a %s
     specifier shall not be a null pointer. No encoding error shall occur.
 
 

-
 
 
Footnote 396) It is not a runtime-constraint violation for the characters %n to appear in sequence in the string pointed
          at by format when those characters are not a interpreted as a %n specifier. For example, if the entire
          format string was %%n.
 

 
-
+
 
3   If there is a runtime-constraint violation, then if s is not a null pointer and n is greater
     than zero and less than RSIZE_MAX, then the sprintf_s function sets s[0] to the
     null character.
     Description
 

-
-
+
 
4   The sprintf_s function is equivalent to the sprintf function except for the
     parameter n and the explicit runtime-constraints listed above.
 

-
-
+
 
5   The sprintf_s function, unlike snprintf_s, treats a result too big for the array
     pointed to by s as a runtime-constraint violation.
     Returns
 

-
-
+
 
6   If no runtime-constraint violation occurred, the sprintf_s function returns the number
     of characters written in the array, not counting the terminating null character. If an
     encoding error occurred, sprintf_s returns a negative value. If any other runtime-
     constraint violation occurred, sprintf_s returns zero.
 

-
-
+
 

 
K.3.5.3.7 [The sscanf_s function]

-

-
-
-
1          #define _ _STDC_WANT_LIB_EXT1_ _ 1
+
+
1 Synopsis
+          #define _ _STDC_WANT_LIB_EXT1_ _ 1
            #include <stdio.h>
            int sscanf_s(const char * restrict s,
                 const char * restrict format, ...);
     Runtime-constraints
 

-
-
+
 
2   Neither s nor format shall be a null pointer. Any argument indirected though in order
     to store converted input shall not be a null pointer.
 

-
-
+
 
3   If there is a runtime-constraint violation, the sscanf_s function does not attempt to
     perform further input, and it is unspecified to what extent sscanf_s performed input
     before discovering the runtime-constraint violation.
     Description
 

-
-
+
 
4   The sscanf_s function is equivalent to fscanf_s, except that input is obtained from
     a string (specified by the argument s) rather than from a stream. Reaching the end of the
     string is equivalent to encountering end-of-file for the fscanf_s function. If copying
     takes place between objects that overlap, the objects take on unspecified values.
     Returns
 

-
-
+
 
5   The sscanf_s function returns the value of the macro EOF if an input failure occurs
     before any conversion or if there is a runtime-constraint violation. Otherwise, the
     sscanf_s function returns the number of input items assigned, which can be fewer than
     provided for, or even zero, in the event of an early matching failure.
 
 

-
-
+
 

 
K.3.5.3.8 [The vfprintf_s function]

-

-
-
-
1            #define _ _STDC_WANT_LIB_EXT1_ _ 1
+
+
1 Synopsis
+            #define _ _STDC_WANT_LIB_EXT1_ _ 1
              #include <stdarg.h>
              #include <stdio.h>
              int vfprintf_s(FILE * restrict stream,
@@ -33524,187 +28901,161 @@ the specified values is outside the normal range, the characters stored are unsp
                   va_list arg);
     Runtime-constraints
 

-
-
-
2   Neither stream nor format shall be a null pointer. The %n specifier397) (modified or
+
+
2   Neither stream nor format shall be a null pointer. The %n specifier[397] (modified or
     not by flags, field width, or precision) shall not appear in the string pointed to by
     format. Any argument to vfprintf_s corresponding to a %s specifier shall not be a
     null pointer.
 

-
 
 
Footnote 397) It is not a runtime-constraint violation for the characters %n to appear in sequence in the string pointed
          at by format when those characters are not a interpreted as a %n specifier. For example, if the entire
          format string was %%n.
+    Runtime-constraints
 

 
-
+
 
3   If there is a runtime-constraint violation, the vfprintf_s function does not attempt to
     produce further output, and it is unspecified to what extent vfprintf_s produced
     output before discovering the runtime-constraint violation.
     Description
 

-
-
+
 
4   The vfprintf_s function is equivalent to the vfprintf function except for the
     explicit runtime-constraints listed above.
     Returns
 

-
-
+
 
5   The vfprintf_s function returns the number of characters transmitted, or a negative
     value if an output error, encoding error, or runtime-constraint violation occurred.
 

-
-
+
 

 
K.3.5.3.9 [The vfscanf_s function]

-

-
-
-
1            #define _ _STDC_WANT_LIB_EXT1_ _ 1
+
+
1 Synopsis
+            #define _ _STDC_WANT_LIB_EXT1_ _ 1
              #include <stdarg.h>
              #include <stdio.h>
              int vfscanf_s(FILE * restrict stream,
                   const char * restrict format,
                   va_list arg);
-
-    Runtime-constraints
 

-
-
+
 
2   Neither stream nor format shall be a null pointer. Any argument indirected though in
     order to store converted input shall not be a null pointer.
 

-
-
+
 
3   If there is a runtime-constraint violation, the vfscanf_s function does not attempt to
     perform further input, and it is unspecified to what extent vfscanf_s performed input
     before discovering the runtime-constraint violation.
     Description
 

-
-
+
 
4   The vfscanf_s function is equivalent to fscanf_s, with the variable argument list
     replaced by arg, which shall have been initialized by the va_start macro (and
     possibly subsequent va_arg calls). The vfscanf_s function does not invoke the
-    va_end macro.398)
+    va_end macro.[398]
     Returns
 

-
 
 
Footnote 398) As the functions vfprintf_s, vfscanf_s, vprintf_s, vscanf_s, vsnprintf_s,
          vsprintf_s, and vsscanf_s invoke the va_arg macro, the value of arg after the return is
          indeterminate.
 

 
-
+
 
5   The vfscanf_s function returns the value of the macro EOF if an input failure occurs
     before any conversion or if there is a runtime-constraint violation. Otherwise, the
     vfscanf_s function returns the number of input items assigned, which can be fewer
     than provided for, or even zero, in the event of an early matching failure.
 

-
-
+
 

 
K.3.5.3.10 [The vprintf_s function]

-

-
-
-
1            #define _ _STDC_WANT_LIB_EXT1_ _ 1
+
+
1 Synopsis
+            #define _ _STDC_WANT_LIB_EXT1_ _ 1
              #include <stdarg.h>
              #include <stdio.h>
              int vprintf_s(const char * restrict format,
                   va_list arg);
     Runtime-constraints
 

-
-
-
2   format shall not be a null pointer. The %n specifier399) (modified or not by flags, field
+
+
2   format shall not be a null pointer. The %n specifier[399] (modified or not by flags, field
     width, or precision) shall not appear in the string pointed to by format. Any argument
     to vprintf_s corresponding to a %s specifier shall not be a null pointer.
 

-
 
 
Footnote 399) It is not a runtime-constraint violation for the characters %n to appear in sequence in the string pointed
          at by format when those characters are not a interpreted as a %n specifier. For example, if the entire
          format string was %%n.
+    Description
 

 
-
+
 
3   If there is a runtime-constraint violation, the vprintf_s function does not attempt to
     produce further output, and it is unspecified to what extent vprintf_s produced output
     before discovering the runtime-constraint violation.
-
-    Description
 

-
-
+
 
4   The vprintf_s function is equivalent to the vprintf function except for the explicit
     runtime-constraints listed above.
     Returns
 

-
-
+
 
5   The vprintf_s function returns the number of characters transmitted, or a negative
     value if an output error, encoding error, or runtime-constraint violation occurred.
 

-
-
+
 

 
K.3.5.3.11 [The vscanf_s function]

-

-
-
-
1           #define _ _STDC_WANT_LIB_EXT1_ _ 1
+
+
1 Synopsis
+           #define _ _STDC_WANT_LIB_EXT1_ _ 1
             #include <stdarg.h>
             #include <stdio.h>
             int vscanf_s(const char * restrict format,
                  va_list arg);
     Runtime-constraints
 

-
-
+
 
2   format shall not be a null pointer. Any argument indirected though in order to store
     converted input shall not be a null pointer.
 

-
-
+
 
3   If there is a runtime-constraint violation, the vscanf_s function does not attempt to
     perform further input, and it is unspecified to what extent vscanf_s performed input
     before discovering the runtime-constraint violation.
     Description
 

-
-
+
 
4   The vscanf_s function is equivalent to scanf_s, with the variable argument list
     replaced by arg, which shall have been initialized by the va_start macro (and
     possibly subsequent va_arg calls). The vscanf_s function does not invoke the
-    va_end macro.400)
+    va_end macro.[400]
     Returns
 

-
 
 
Footnote 400) As the functions vfprintf_s, vfscanf_s, vprintf_s, vscanf_s, vsnprintf_s,
          vsprintf_s, and vsscanf_s invoke the va_arg macro, the value of arg after the return is
          indeterminate.
 

 
-
+
 
5   The vscanf_s function returns the value of the macro EOF if an input failure occurs
     before any conversion or if there is a runtime-constraint violation. Otherwise, the
     vscanf_s function returns the number of input items assigned, which can be fewer than
     provided for, or even zero, in the event of an early matching failure.
 
 

-
-
+
 

 
K.3.5.3.12 [The vsnprintf_s function]

-

-
-
-
1            #define _ _STDC_WANT_LIB_EXT1_ _ 1
+
+
1 Synopsis
+            #define _ _STDC_WANT_LIB_EXT1_ _ 1
              #include <stdarg.h>
              #include <stdio.h>
              int vsnprintf_s(char * restrict s, rsize_t n,
@@ -33712,40 +29063,35 @@ the specified values is outside the normal range, the characters stored are unsp
                   va_list arg);
     Runtime-constraints
 

-
-
+
 
2   Neither s nor format shall be a null pointer. n shall neither equal zero nor be greater
-    than RSIZE_MAX. The %n specifier401) (modified or not by flags, field width, or
+    than RSIZE_MAX. The %n specifier[401] (modified or not by flags, field width, or
     precision) shall not appear in the string pointed to by format. Any argument to
     vsnprintf_s corresponding to a %s specifier shall not be a null pointer. No encoding
     error shall occur.
 

-
 
 
Footnote 401) It is not a runtime-constraint violation for the characters %n to appear in sequence in the string pointed
          at by format when those characters are not a interpreted as a %n specifier. For example, if the entire
          format string was %%n.
 

 
-
+
 
3   If there is a runtime-constraint violation, then if s is not a null pointer and n is greater
     than zero and less than RSIZE_MAX, then the vsnprintf_s function sets s[0] to the
     null character.
     Description
 

-
-
+
 
4   The vsnprintf_s function is equivalent to the vsnprintf function except for the
     explicit runtime-constraints listed above.
 

-
-
+
 
5   The vsnprintf_s function, unlike vsprintf_s, will truncate the result to fit within
     the array pointed to by s.
     Returns
 

-
-
+
 
6   The vsnprintf_s function returns the number of characters that would have been
     written had n been sufficiently large, not counting the terminating null character, or a
     negative value if a runtime-constraint violation occurred. Thus, the null-terminated
@@ -33753,14 +29099,12 @@ the specified values is outside the normal range, the characters stored are unsp
     less than n.
 
 

-
-
+
 

 
K.3.5.3.13 [The vsprintf_s function]

-

-
-
-
1            #define _ _STDC_WANT_LIB_EXT1_ _ 1
+
+
1 Synopsis
+            #define _ _STDC_WANT_LIB_EXT1_ _ 1
              #include <stdarg.h>
              #include <stdio.h>
              int vsprintf_s(char * restrict s, rsize_t n,
@@ -33768,55 +29112,48 @@ the specified values is outside the normal range, the characters stored are unsp
                   va_list arg);
     Runtime-constraints
 

-
-
+
 
2   Neither s nor format shall be a null pointer. n shall neither equal zero nor be greater
     than RSIZE_MAX. The number of characters (including the trailing null) required for the
     result to be written to the array pointed to by s shall not be greater than n. The %n
-    specifier402) (modified or not by flags, field width, or precision) shall not appear in the
+    specifier[402] (modified or not by flags, field width, or precision) shall not appear in the
     string pointed to by format. Any argument to vsprintf_s corresponding to a %s
     specifier shall not be a null pointer. No encoding error shall occur.
 

-
 
 
Footnote 402) It is not a runtime-constraint violation for the characters %n to appear in sequence in the string pointed
          at by format when those characters are not a interpreted as a %n specifier. For example, if the entire
          format string was %%n.
 

 
-
+
 
3   If there is a runtime-constraint violation, then if s is not a null pointer and n is greater
     than zero and less than RSIZE_MAX, then the vsprintf_s function sets s[0] to the
     null character.
     Description
 

-
-
+
 
4   The vsprintf_s function is equivalent to the vsprintf function except for the
     parameter n and the explicit runtime-constraints listed above.
 

-
-
+
 
5   The vsprintf_s function, unlike vsnprintf_s, treats a result too big for the array
     pointed to by s as a runtime-constraint violation.
     Returns
 

-
-
+
 
6   If no runtime-constraint violation occurred, the vsprintf_s function returns the
     number of characters written in the array, not counting the terminating null character. If
     an encoding error occurred, vsprintf_s returns a negative value. If any other
     runtime-constraint violation occurred, vsprintf_s returns zero.
 
 

-
-
+
 

 
K.3.5.3.14 [The vsscanf_s function]

-

-
-
-
1          #define _ _STDC_WANT_LIB_EXT1_ _ 1
+
+
1 Synopsis
+          #define _ _STDC_WANT_LIB_EXT1_ _ 1
            #include <stdarg.h>
            #include <stdio.h>
            int vsscanf_s(const char * restrict s,
@@ -33824,65 +29161,53 @@ the specified values is outside the normal range, the characters stored are unsp
                 va_list arg);
     Runtime-constraints
 

-
-
+
 
2   Neither s nor format shall be a null pointer. Any argument indirected though in order
     to store converted input shall not be a null pointer.
 

-
-
+
 
3   If there is a runtime-constraint violation, the vsscanf_s function does not attempt to
     perform further input, and it is unspecified to what extent vsscanf_s performed input
     before discovering the runtime-constraint violation.
     Description
 

-
-
+
 
4   The vsscanf_s function is equivalent to sscanf_s, with the variable argument list
     replaced by arg, which shall have been initialized by the va_start macro (and
     possibly subsequent va_arg calls). The vsscanf_s function does not invoke the
-    va_end macro.403)
+    va_end macro.[403]
     Returns
 

-
 
 
Footnote 403) As the functions vfprintf_s, vfscanf_s, vprintf_s, vscanf_s, vsnprintf_s,
          vsprintf_s, and vsscanf_s invoke the va_arg macro, the value of arg after the return is
          indeterminate.
+    Runtime-constraints
 

 
-
+
 
5   The vsscanf_s function returns the value of the macro EOF if an input failure occurs
     before any conversion or if there is a runtime-constraint violation. Otherwise, the
     vscanf_s function returns the number of input items assigned, which can be fewer than
     provided for, or even zero, in the event of an early matching failure.
 

-
-
+
 

 
K.3.5.4 [Character input/output functions]

-
 Character input/output functions
-

-
-
+
 

 
K.3.5.4.1 [The gets_s function]

-

-
-
-
1          #define _ _STDC_WANT_LIB_EXT1_ _ 1
+
+
1 Synopsis
+          #define _ _STDC_WANT_LIB_EXT1_ _ 1
            #include <stdio.h>
            char *gets_s(char *s, rsize_t n);
-
-    Runtime-constraints
 

-
-
+
 
2   s shall not be a null pointer. n shall neither be equal to zero nor be greater than
     RSIZE_MAX. A new-line character, end-of-file, or read error shall occur within reading
-    n-1 characters from stdin.404)
+    n-1 characters from stdin.[404]
 

-
 
 
Footnote 404) The gets_s function, unlike the historical gets function, makes it a runtime-constraint violation for
          a line of input to overflow the buffer to store it. Unlike the fgets function, gets_s maintains a
@@ -33890,29 +29215,26 @@ the specified values is outside the normal range, the characters stored are unsp
          expect such a relationship.
 

 
-
+
 
3   If there is a runtime-constraint violation, s[0] is set to the null character, and characters
     are read and discarded from stdin until a new-line character is read, or end-of-file or a
     read error occurs.
     Description
 

-
-
+
 
4   The gets_s function reads at most one less than the number of characters specified by n
     from the stream pointed to by stdin, into the array pointed to by s. No additional
     characters are read after a new-line character (which is discarded) or after end-of-file.
     The discarded new-line character does not count towards number of characters read. A
     null character is written immediately after the last character read into the array.
 

-
-
+
 
5   If end-of-file is encountered and no characters have been read into the array, or if a read
     error occurs during the operation, then s[0] is set to the null character, and the other
     elements of s take unspecified values.
     Recommended practice
 

-
-
+
 
6   The fgets function allows properly-written programs to safely process input lines too
     long to store in the result array. In general this requires that callers of fgets pay
     attention to the presence or absence of a new-line character in the result array. Consider
@@ -33920,24 +29242,19 @@ the specified values is outside the normal range, the characters stored are unsp
     gets_s.
     Returns
 

-
-
+
 
7   The gets_s function returns s if successful. If there was a runtime-constraint violation,
     or if end-of-file is encountered and no characters have been read into the array, or if a
     read error occurs during the operation, then a null pointer is returned.
 
 

-
-
+
 

-
K.3.6 [General utilities ]

-

-
-
+
K.3.6 [General utilities <stdlib.h>]

+
 
1   The header <stdlib.h> defines three types.
 

-
-
+
 
2   The types are
             errno_t
     which is type int; and
@@ -33950,35 +29267,28 @@ the specified values is outside the normal range, the characters stored are unsp
                  void * restrict ptr,
                  errno_t error);
 

-
-
+
 

 
K.3.6.1 [Runtime-constraint handling]

-
 Runtime-constraint handling
-

-
-
+
 

 
K.3.6.1.1 [The set_constraint_handler_s function]

-

-
-
-
1           #define _ _STDC_WANT_LIB_EXT1_ _ 1
+
+
1 Synopsis
+           #define _ _STDC_WANT_LIB_EXT1_ _ 1
             #include <stdlib.h>
             constraint_handler_t set_constraint_handler_s(
                  constraint_handler_t handler);
     Description
 

-
-
+
 
2   The set_constraint_handler_s function sets the runtime-constraint handler to
     be handler. The runtime-constraint handler is the function to be called when a library
     function detects a runtime-constraint violation. Only the most recent handler registered
     with set_constraint_handler_s is called when a runtime-constraint violation
     occurs.
 

-
-
+
 
3   When the handler is called, it is passed the following arguments in the following order:
        1.   A pointer to a character string describing the runtime-constraint violation.
        2.   A null pointer or a pointer to an implementation defined object.
@@ -33987,36 +29297,31 @@ the specified values is outside the normal range, the characters stored are unsp
             errno_t is passed.
 
 

-
-
+
 
4   The implementation has a default constraint handler that is used if no calls to the
     set_constraint_handler_s function have been made. The behavior of the
     default handler is implementation-defined, and it may cause the program to exit or abort.
 

-
-
+
 
5   If the handler argument to set_constraint_handler_s is a null pointer, the
     implementation default handler becomes the current constraint handler.
     Returns
 

-
-
+
 
6   The set_constraint_handler_s function returns a pointer to the previously
-    registered handler.405)
+    registered handler.[405]
 

-
 
 
Footnote 405) If the previous handler was registered by calling set_constraint_handler_s with a null
          pointer argument, a pointer to the implementation default handler is returned (not NULL).
 

 
-
+
 

 
K.3.6.1.2 [The abort_handler_s function]

-

-
-
-
1           #define _ _STDC_WANT_LIB_EXT1_ _ 1
+
+
1 Synopsis
+           #define _ _STDC_WANT_LIB_EXT1_ _ 1
             #include <stdlib.h>
             void abort_handler_s(
                  const char * restrict msg,
@@ -34024,35 +29329,30 @@ the specified values is outside the normal range, the characters stored are unsp
                  errno_t error);
     Description
 

-
-
+
 
2   A pointer to the abort_handler_s function shall be a suitable argument to the
     set_constraint_handler_s function.
 

-
-
+
 
3   The abort_handler_s function writes a message on the standard error stream in an
     implementation-defined format. The message shall include the string pointed to by msg.
-    The abort_handler_s function then calls the abort function.406)
+    The abort_handler_s function then calls the abort function.[406]
     Returns
 

-
 
 
Footnote 406) Many implementations invoke a debugger when the abort function is called.
 

 
-
+
 
4   The abort_handler_s function does not return to its caller.
 
 

-
-
+
 

 
K.3.6.1.3 [The ignore_handler_s function]

-

-
-
-
1            #define _ _STDC_WANT_LIB_EXT1_ _ 1
+
+
1 Synopsis
+            #define _ _STDC_WANT_LIB_EXT1_ _ 1
              #include <stdlib.h>
              void ignore_handler_s(
                   const char * restrict msg,
@@ -34060,17 +29360,14 @@ the specified values is outside the normal range, the characters stored are unsp
                   errno_t error);
     Description
 

-
-
+
 
2   A pointer to the ignore_handler_s function shall be a suitable argument to the
     set_constraint_handler_s function.
 

-
-
-
3   The ignore_handler_s function simply returns to its caller.407)
+
+
3   The ignore_handler_s function simply returns to its caller.[407]
     Returns
 

-
 
 
Footnote 407) If the runtime-constraint handler is set to the ignore_handler_s function, any library function in
          which a runtime-constraint violation occurs will return to its caller. The caller can determine whether
@@ -34078,96 +29375,79 @@ the specified values is outside the normal range, the characters stored are unsp
          library function returns a nonzero errno_t).
 

 
-
+
 
4   The ignore_handler_s function returns no value.
 

-
-
+
 

 
K.3.6.2 [Communication with the environment]

-
 Communication with the environment
-

-
-
+
 

 
K.3.6.2.1 [The getenv_s function]

-

-
-
-
1            #define _ _STDC_WANT_LIB_EXT1_ _ 1
+
+
1 Synopsis
+            #define _ _STDC_WANT_LIB_EXT1_ _ 1
              #include <stdlib.h>
              errno_t getenv_s(size_t * restrict len,
                         char * restrict value, rsize_t maxsize,
                         const char * restrict name);
     Runtime-constraints
 

-
-
+
 
2   name shall not be a null pointer. maxsize shall neither equal zero nor be greater than
     RSIZE_MAX. If maxsize is not equal to zero, then value shall not be a null pointer.
 

-
-
+
 
3   If there is a runtime-constraint violation, the integer pointed to by len is set to 0 (if len
     is not null), and the environment list is not searched.
     Description
 

-
-
+
 
4   The getenv_s function searches an environment list , provided by the host environment,
     for a string that matches the string pointed to by name.
 
 

-
-
+
 
5   If that name is found then getenv_s performs the following actions. If len is not a
     null pointer, the length of the string associated with the matched list member is stored in
     the integer pointed to by len. If the length of the associated string is less than maxsize,
     then the associated string is copied to the array pointed to by value.
 

-
-
+
 
6   If that name is not found then getenv_s performs the following actions. If len is not
     a null pointer, zero is stored in the integer pointed to by len. If maxsize is greater than
     zero, then value[0] is set to the null character.
 

-
-
+
 
7   The set of environment names and the method for altering the environment list are
     implementation-defined. The getenv_s function need not avoid data races with other
-    threads of execution that modify the environment list.408)
+    threads of execution that modify the environment list.[408]
     Returns
 

-
 
 
Footnote 408) Many implementations provide non-standard functions that modify the environment list.
 

 
-
+
 
8   The getenv_s function returns zero if the specified name is found and the associated
     string was successfully stored in value. Otherwise, a nonzero value is returned.
 

-
-
+
 

 
K.3.6.3 [Searching and sorting utilities]

-

-
-
+
 
1   These utilities make use of a comparison function to search or sort arrays of unspecified
     type. Where an argument declared as size_t nmemb specifies the length of the array
     for a function, if nmemb has the value zero on a call to that function, then the comparison
     function is not called, a search finds no matching element, sorting performs no
     rearrangement, and the pointer to the array may be null.
 

-
-
+
 
2   The implementation shall ensure that the second argument of the comparison function
     (when called from bsearch_s), or both arguments (when called from qsort_s), are
-    pointers to elements of the array.409) The first argument when called from bsearch_s
+    pointers to elements of the array.[409] The first argument when called from bsearch_s
     shall equal key.
 

-
 
 
Footnote 409) That is, if the value passed is p, then the following expressions are always valid and nonzero:
                   ((char *)p - (char *)base) % size == 0
@@ -34175,33 +29455,29 @@ the specified values is outside the normal range, the characters stored are unsp
                   (char *)p < (char *)base + nmemb * size
 

 
-
+
 
3   The comparison function shall not alter the contents of either the array or search key. The
     implementation may reorder elements of the array between calls to the comparison
     function, but shall not otherwise alter the contents of any individual element.
 

-
-
+
 
4   When the same objects (consisting of size bytes, irrespective of their current positions
     in the array) are passed more than once to the comparison function, the results shall be
     consistent with one another. That is, for qsort_s they shall define a total ordering on
     the array, and for bsearch_s the same object shall always compare the same way with
     the key.
 

-
-
+
 
5   A sequence point occurs immediately before and immediately after each call to the
     comparison function, and also between any call to the comparison function and any
     movement of the objects passed as arguments to that call.
 

-
-
+
 

 
K.3.6.3.1 [The bsearch_s function]

-

-
-
-
1            #define _ _STDC_WANT_LIB_EXT1_ _ 1
+
+
1 Synopsis
+            #define _ _STDC_WANT_LIB_EXT1_ _ 1
              #include <stdlib.h>
              void *bsearch_s(const void *key, const void *base,
                   rsize_t nmemb, rsize_t size,
@@ -34210,38 +29486,31 @@ the specified values is outside the normal range, the characters stored are unsp
                   void *context);
     Runtime-constraints
 

-
-
+
 
2   Neither nmemb nor size shall be greater than RSIZE_MAX. If nmemb is not equal to
     zero, then none of key, base, or compar shall be a null pointer.
 

-
-
+
 
3   If there is a runtime-constraint violation, the bsearch_s function does not search the
     array.
     Description
 

-
-
+
 
4   The bsearch_s function searches an array of nmemb objects, the initial element of
     which is pointed to by base, for an element that matches the object pointed to by key.
     The size of each element of the array is specified by size.
 

-
-
+
 
5   The comparison function pointed to by compar is called with three arguments. The first
     two point to the key object and to an array element, in that order. The function shall
     return an integer less than, equal to, or greater than zero if the key object is considered,
     respectively, to be less than, to match, or to be greater than the array element. The array
     shall consist of: all the elements that compare less than, all the elements that compare
-    equal to, and all the elements that compare greater than the key object, in that order.410)
+    equal to, and all the elements that compare greater than the key object, in that order.[410]
     The third argument to the comparison function is the context argument passed to
     bsearch_s. The sole use of context by bsearch_s is to pass it to the comparison
-    function.411)
-
-    Returns
+    function.[411]
 

-
 
 
Footnote 410) In practice, this means that the entire array has been sorted according to the comparison function.
 

@@ -34249,21 +29518,20 @@ the specified values is outside the normal range, the characters stored are unsp
 
 
Footnote 411) The context argument is for the use of the comparison function in performing its duties. For
          example, it might specify a collating sequence used by the comparison function.
+    Returns
 

 
-
+
 
6   The bsearch_s function returns a pointer to a matching element of the array, or a null
     pointer if no match is found or there is a runtime-constraint violation. If two elements
     compare as equal, which element is matched is unspecified.
 

-
-
+
 

 
K.3.6.3.2 [The qsort_s function]

-

-
-
-
1           #define _ _STDC_WANT_LIB_EXT1_ _ 1
+
+
1 Synopsis
+           #define _ _STDC_WANT_LIB_EXT1_ _ 1
             #include <stdlib.h>
             errno_t qsort_s(void *base, rsize_t nmemb, rsize_t size,
                  int (*compar)(const void *x, const void *y,
@@ -34271,77 +29539,66 @@ the specified values is outside the normal range, the characters stored are unsp
                  void *context);
     Runtime-constraints
 

-
-
+
 
2   Neither nmemb nor size shall be greater than RSIZE_MAX. If nmemb is not equal to
     zero, then neither base nor compar shall be a null pointer.
 

-
-
+
 
3   If there is a runtime-constraint violation, the qsort_s function does not sort the array.
     Description
 

-
-
+
 
4   The qsort_s function sorts an array of nmemb objects, the initial element of which is
     pointed to by base. The size of each object is specified by size.
 

-
-
+
 
5   The contents of the array are sorted into ascending order according to a comparison
     function pointed to by compar, which is called with three arguments. The first two
     point to the objects being compared. The function shall return an integer less than, equal
     to, or greater than zero if the first argument is considered to be respectively less than,
     equal to, or greater than the second. The third argument to the comparison function is the
     context argument passed to qsort_s. The sole use of context by qsort_s is to
-    pass it to the comparison function.412)
+    pass it to the comparison function.[412]
 

-
 
 
Footnote 412) The context argument is for the use of the comparison function in performing its duties. For
          example, it might specify a collating sequence used by the comparison function.
 

 
-
+
 
6   If two elements compare as equal, their relative order in the resulting sorted array is
     unspecified.
     Returns
 

-
-
+
 
7   The qsort_s function returns zero if there was no runtime-constraint violation.
     Otherwise, a nonzero value is returned.
 
 

-
-
+
 

 
K.3.6.4 [Multibyte/wide character conversion functions]

-

-
-
+
 
1   The behavior of the multibyte character functions is affected by the LC_CTYPE category
     of the current locale. For a state-dependent encoding, each function is placed into its
     initial conversion state by a call for which its character pointer argument, s, is a null
     pointer. Subsequent calls with s as other than a null pointer cause the internal conversion
     state of the function to be altered as necessary. A call with s as a null pointer causes
     these functions to set the int pointed to by their status argument to a nonzero value if
-    encodings have state dependency, and zero otherwise.413) Changing the LC_CTYPE
+    encodings have state dependency, and zero otherwise.[413] Changing the LC_CTYPE
     category causes the conversion state of these functions to be indeterminate.
 

-
 
 
Footnote 413) If the locale employs special bytes to change the shift state, these bytes do not produce separate wide
          character codes, but are grouped with an adjacent multibyte character.
 

 
-
+
 

 
K.3.6.4.1 [The wctomb_s function]

-

-
-
-
1           #define _ _STDC_WANT_LIB_EXT1_ _ 1
+
+
1 Synopsis
+           #define _ _STDC_WANT_LIB_EXT1_ _ 1
             #include <stdlib.h>
             errno_t wctomb_s(int * restrict status,
                  char * restrict s,
@@ -34349,100 +29606,83 @@ the specified values is outside the normal range, the characters stored are unsp
                  wchar_t wc);
     Runtime-constraints
 

-
-
+
 
2   Let n denote the number of bytes needed to represent the multibyte character
     corresponding to the wide character given by wc (including any shift sequences).
 

-
-
+
 
3   If s is not a null pointer, then smax shall not be less than n, and smax shall not be
     greater than RSIZE_MAX. If s is a null pointer, then smax shall equal zero.
 

-
-
+
 
4   If there is a runtime-constraint violation, wctomb_s does not modify the int pointed to
     by status, and if s is not a null pointer, no more than smax elements in the array
     pointed to by s will be accessed.
     Description
 

-
-
+
 
5   The wctomb_s function determines n and stores the multibyte character representation
     of wc in the array whose first element is pointed to by s (if s is not a null pointer). The
     number of characters stored never exceeds MB_CUR_MAX or smax. If wc is a null wide
     character, a null byte is stored, preceded by any shift sequence needed to restore the
     initial shift state, and the function is left in the initial conversion state.
 

-
-
+
 
6   The implementation shall behave as if no library function calls the wctomb_s function.
 
 

-
-
+
 
7    If s is a null pointer, the wctomb_s function stores into the int pointed to by status a
      nonzero or zero value, if multibyte character encodings, respectively, do or do not have
      state-dependent encodings.
 

-
-
+
 
8    If s is not a null pointer, the wctomb_s function stores into the int pointed to by
      status either n or -1 if wc, respectively, does or does not correspond to a valid
      multibyte character.
 

-
-
+
 
9    In no case will the int pointed to by status be set to a value greater than the
      MB_CUR_MAX macro.
      Returns
 

-
-
+
 
10   The wctomb_s function returns zero if successful, and a nonzero value if there was a
      runtime-constraint violation or wc did not correspond to a valid multibyte character.
 

-
-
+
 

 
K.3.6.5 [Multibyte/wide string conversion functions]

-

-
-
+
 
1    The behavior of the multibyte string functions is affected by the LC_CTYPE category of
      the current locale.
 

-
-
+
 

 
K.3.6.5.1 [The mbstowcs_s function]

-

-
-
-
1            #include <stdlib.h>
+
+
1 Synopsis
+            #include <stdlib.h>
              errno_t mbstowcs_s(size_t * restrict retval,
                   wchar_t * restrict dst, rsize_t dstmax,
                   const char * restrict src, rsize_t len);
      Runtime-constraints
 

-
-
+
 
2    Neither retval nor src shall be a null pointer. If dst is not a null pointer, then
      neither len nor dstmax shall be greater than RSIZE_MAX. If dst is a null pointer,
      then dstmax shall equal zero. If dst is not a null pointer, then dstmax shall not equal
      zero. If dst is not a null pointer and len is not less than dstmax, then a null character
      shall occur within the first dstmax multibyte characters of the array pointed to by src.
 

-
-
+
 
3    If there is a runtime-constraint violation, then mbstowcs_s does the following. If
      retval is not a null pointer, then mbstowcs_s sets *retval to (size_t)(-1). If
      dst is not a null pointer and dstmax is greater than zero and less than RSIZE_MAX,
      then mbstowcs_s sets dst[0] to the null wide character.
      Description
 

-
-
+
 
4    The mbstowcs_s function converts a sequence of multibyte characters that begins in
      the initial shift state from the array pointed to by src into a sequence of corresponding
      wide characters. If dst is not a null pointer, the converted characters are stored into the
@@ -34450,59 +29690,52 @@ the specified values is outside the normal range, the characters stored are unsp
      character, which is also stored. Conversion stops earlier in two cases: when a sequence of
     bytes is encountered that does not form a valid multibyte character, or (if dst is not a
     null pointer) when len wide characters have been stored into the array pointed to by
-    dst.414) If dst is not a null pointer and no null wide character was stored into the array
+    dst.[414] If dst is not a null pointer and no null wide character was stored into the array
     pointed to by dst, then dst[len] is set to the null wide character. Each conversion
     takes place as if by a call to the mbrtowc function.
 

-
 
 
Footnote 414) Thus, the value of len is ignored if dst is a null pointer.
 

 
-
+
 
5   Regardless of whether dst is or is not a null pointer, if the input conversion encounters a
     sequence of bytes that do not form a valid multibyte character, an encoding error occurs:
     the mbstowcs_s function stores the value (size_t)(-1) into *retval.
     Otherwise, the mbstowcs_s function stores into *retval the number of multibyte
     characters successfully converted, not including the terminating null character (if any).
 

-
-
+
 
6   All elements following the terminating null wide character (if any) written by
     mbstowcs_s in the array of dstmax wide characters pointed to by dst take
-    unspecified values when mbstowcs_s returns.415)
+    unspecified values when mbstowcs_s returns.[415]
 

-
 
 
Footnote 415) This allows an implementation to attempt converting the multibyte string before discovering a
          terminating null character did not occur where required.
 

 
-
+
 
7   If copying takes place between objects that overlap, the objects take on unspecified
     values.
     Returns
 

-
-
+
 
8   The mbstowcs_s function returns zero if no runtime-constraint violation and no
     encoding error occurred. Otherwise, a nonzero value is returned.
 

-
-
+
 

 
K.3.6.5.2 [The wcstombs_s function]

-

-
-
-
1            #include <stdlib.h>
+
+
1 Synopsis
+            #include <stdlib.h>
              errno_t wcstombs_s(size_t * restrict retval,
                   char * restrict dst, rsize_t dstmax,
                   const wchar_t * restrict src, rsize_t len);
     Runtime-constraints
 

-
-
+
 
2   Neither retval nor src shall be a null pointer. If dst is not a null pointer, then
     neither len nor dstmax shall be greater than RSIZE_MAX. If dst is a null pointer,
     then dstmax shall equal zero. If dst is not a null pointer, then dstmax shall not equal
@@ -34511,16 +29744,14 @@ the specified values is outside the normal range, the characters stored are unsp
     reached or because an encoding error occurred.
 
 

-
-
+
 
3   If there is a runtime-constraint violation, then wcstombs_s does the following. If
     retval is not a null pointer, then wcstombs_s sets *retval to (size_t)(-1). If
     dst is not a null pointer and dstmax is greater than zero and less than RSIZE_MAX,
     then wcstombs_s sets dst[0] to the null character.
     Description
 

-
-
+
 
4   The wcstombs_s function converts a sequence of wide characters from the array
     pointed to by src into a sequence of corresponding multibyte characters that begins in
     the initial shift state. If dst is not a null pointer, the converted characters are then stored
@@ -34535,9 +29766,8 @@ the specified values is outside the normal range, the characters stored are unsp
     If the conversion stops without converting a null wide character and dst is not a null
     pointer, then a null character is stored into the array pointed to by dst immediately
     following any multibyte characters already stored. Each conversion takes place as if by a
-    call to the wcrtomb function.416)
+    call to the wcrtomb function.[416]
 

-
 
 
Footnote 416) If conversion stops because a terminating null wide character has been reached, the bytes stored
          include those necessary to reach the initial shift state immediately before the null byte. However, if
@@ -34545,7 +29775,7 @@ the specified values is outside the normal range, the characters stored are unsp
          terminated, but might not end in the initial shift state.
 

 
-
+
 
5   Regardless of whether dst is or is not a null pointer, if the input conversion encounters a
     wide character that does not correspond to a valid multibyte character, an encoding error
     occurs: the wcstombs_s function stores the value (size_t)(-1) into *retval.
@@ -34553,116 +29783,94 @@ the specified values is outside the normal range, the characters stored are unsp
     resulting multibyte character sequence, not including the terminating null character (if
     any).
 

-
-
+
 
6   All elements following the terminating null character (if any) written by wcstombs_s
     in the array of dstmax elements pointed to by dst take unspecified values when
-    wcstombs_s returns.417)
+    wcstombs_s returns.[417]
 

-
 
 
Footnote 417) When len is not less than dstmax, the implementation might fill the array before discovering a
          runtime-constraint violation.
+    Returns
 

 
-
+
 
7   If copying takes place between objects that overlap, the objects take on unspecified
     values.
-
-    Returns
 

-
-
+
 
8   The wcstombs_s function returns zero if no runtime-constraint violation and no
     encoding error occurred. Otherwise, a nonzero value is returned.
 

-
-
+
 

-
K.3.7 [String handling ]

-

-
-
+
K.3.7 [String handling <string.h>]

+
 
1   The header <string.h> defines two types.
 

-
-
+
 
2   The types are
            errno_t
     which is type int; and
            rsize_t
     which is the type size_t.
 

-
-
+
 

 
K.3.7.1 [Copying functions]

-
 Copying functions
-

-
-
+
 

 
K.3.7.1.1 [The memcpy_s function]

-

-
-
-
1          #define _ _STDC_WANT_LIB_EXT1_ _ 1
+
+
1 Synopsis
+          #define _ _STDC_WANT_LIB_EXT1_ _ 1
            #include <string.h>
            errno_t memcpy_s(void * restrict s1, rsize_t s1max,
                 const void * restrict s2, rsize_t n);
     Runtime-constraints
 

-
-
+
 
2   Neither s1 nor s2 shall be a null pointer. Neither s1max nor n shall be greater than
     RSIZE_MAX. n shall not be greater than s1max. Copying shall not take place between
     objects that overlap.
 

-
-
+
 
3   If there is a runtime-constraint violation, the memcpy_s function stores zeros in the first
     s1max characters of the object pointed to by s1 if s1 is not a null pointer and s1max is
     not greater than RSIZE_MAX.
     Description
 

-
-
+
 
4   The memcpy_s function copies n characters from the object pointed to by s2 into the
     object pointed to by s1.
     Returns
 

-
-
+
 
5   The memcpy_s function returns zero if there was no runtime-constraint violation.
     Otherwise, a nonzero value is returned.
 

-
-
+
 

 
K.3.7.1.2 [The memmove_s function]

-

-
-
-
1           #define _ _STDC_WANT_LIB_EXT1_ _ 1
+
+
1 Synopsis
+           #define _ _STDC_WANT_LIB_EXT1_ _ 1
             #include <string.h>
             errno_t memmove_s(void *s1, rsize_t s1max,
                  const void *s2, rsize_t n);
     Runtime-constraints
 

-
-
+
 
2   Neither s1 nor s2 shall be a null pointer. Neither s1max nor n shall be greater than
     RSIZE_MAX. n shall not be greater than s1max.
 

-
-
+
 
3   If there is a runtime-constraint violation, the memmove_s function stores zeros in the
     first s1max characters of the object pointed to by s1 if s1 is not a null pointer and
     s1max is not greater than RSIZE_MAX.
     Description
 

-
-
+
 
4   The memmove_s function copies n characters from the object pointed to by s2 into the
     object pointed to by s1. This copying takes place as if the n characters from the object
     pointed to by s2 are first copied into a temporary array of n characters that does not
@@ -34670,75 +29878,65 @@ the specified values is outside the normal range, the characters stored are unsp
     array are copied into the object pointed to by s1.
     Returns
 

-
-
+
 
5   The memmove_s function returns zero if there was no runtime-constraint violation.
     Otherwise, a nonzero value is returned.
 

-
-
+
 

 
K.3.7.1.3 [The strcpy_s function]

-

-
-
-
1           #define _ _STDC_WANT_LIB_EXT1_ _ 1
+
+
1 Synopsis
+           #define _ _STDC_WANT_LIB_EXT1_ _ 1
             #include <string.h>
             errno_t strcpy_s(char * restrict s1,
                  rsize_t s1max,
                  const char * restrict s2);
     Runtime-constraints
 

-
-
+
 
2   Neither s1 nor s2 shall be a null pointer. s1max shall not be greater than RSIZE_MAX.
     s1max shall not equal zero. s1max shall be greater than strnlen_s(s2, s1max).
     Copying shall not take place between objects that overlap.
 

-
-
+
 
3   If there is a runtime-constraint violation, then if s1 is not a null pointer and s1max is
     greater than zero and not greater than RSIZE_MAX, then strcpy_s sets s1[0] to the
     null character.
 
     Description
 

-
-
+
 
4   The strcpy_s function copies the string pointed to by s2 (including the terminating
     null character) into the array pointed to by s1.
 

-
-
+
 
5   All elements following the terminating null character (if any) written by strcpy_s in
     the array of s1max characters pointed to by s1 take unspecified values when
-    strcpy_s returns.418)
+    strcpy_s returns.[418]
     Returns
 

-
 
 
Footnote 418) This allows an implementation to copy characters from s2 to s1 while simultaneously checking if
          any of those characters are null. Such an approach might write a character to every element of s1
          before discovering that the first element should be set to the null character.
 

 
-
-
6   The strcpy_s function returns zero419) if there was no runtime-constraint violation.
+
+
6   The strcpy_s function returns zero[419] if there was no runtime-constraint violation.
     Otherwise, a nonzero value is returned.
 

-
 
 
Footnote 419) A zero return value implies that all of the requested characters from the string pointed to by s2 fit
          within the array pointed to by s1 and that the result in s1 is null terminated.
 

 
-
+
 

 
K.3.7.1.4 [The strncpy_s function]

-

-
-
-
1           #define _ _STDC_WANT_LIB_EXT1_ _ 1
+
+
1 Synopsis
+           #define _ _STDC_WANT_LIB_EXT1_ _ 1
             #include <string.h>
             errno_t strncpy_s(char * restrict s1,
                  rsize_t s1max,
@@ -34746,53 +29944,47 @@ the specified values is outside the normal range, the characters stored are unsp
                  rsize_t n);
     Runtime-constraints
 

-
-
+
 
2   Neither s1 nor s2 shall be a null pointer. Neither s1max nor n shall be greater than
     RSIZE_MAX. s1max shall not equal zero. If n is not less than s1max, then s1max
     shall be greater than strnlen_s(s2, s1max). Copying shall not take place between
     objects that overlap.
 

-
-
+
 
3   If there is a runtime-constraint violation, then if s1 is not a null pointer and s1max is
     greater than zero and not greater than RSIZE_MAX, then strncpy_s sets s1[0] to the
     null character.
     Description
 

-
-
+
 
4   The strncpy_s function copies not more than n successive characters (characters that
     follow a null character are not copied) from the array pointed to by s2 to the array
     pointed to by s1. If no null character was copied from s2, then s1[n] is set to a null
     character.
 
 

-
-
+
 
5   All elements following the terminating null character (if any) written by strncpy_s in
     the array of s1max characters pointed to by s1 take unspecified values when
-    strncpy_s returns.420)
+    strncpy_s returns.[420]
     Returns
 

-
 
 
Footnote 420) This allows an implementation to copy characters from s2 to s1 while simultaneously checking if
          any of those characters are null. Such an approach might write a character to every element of s1
          before discovering that the first element should be set to the null character.
 

 
-
-
6   The strncpy_s function returns zero421) if there was no runtime-constraint violation.
+
+
6   The strncpy_s function returns zero[421] if there was no runtime-constraint violation.
     Otherwise, a nonzero value is returned.
 

-
 
 
Footnote 421) A zero return value implies that all of the requested characters from the string pointed to by s2 fit
          within the array pointed to by s1 and that the result in s1 is null terminated.
 

 
-
+
 
7   EXAMPLE 1 The strncpy_s function can be used to copy a string without the danger that the result
     will not be null terminated or that characters will be written past the end of the destination array.
             #define _ _STDC_WANT_LIB_EXT1_ _ 1
@@ -34810,86 +30002,75 @@ the specified values is outside the normal range, the characters stored are unsp
     The third call will assign to r3 the value zero and to dst3 the sequence good\0.
 
 

-
-
+
 

 
K.3.7.2 [Concatenation functions]

-
 Concatenation functions
-

-
-
+
 

 
K.3.7.2.1 [The strcat_s function]

-

-
-
-
1           #define _ _STDC_WANT_LIB_EXT1_ _ 1
+
+
1 Synopsis
+           #define _ _STDC_WANT_LIB_EXT1_ _ 1
             #include <string.h>
             errno_t strcat_s(char * restrict s1,
                  rsize_t s1max,
                  const char * restrict s2);
     Runtime-constraints
 

-
-
+
 
2   Let m denote the value s1max - strnlen_s(s1, s1max) upon entry to
     strcat_s.
 
 

-
-
+
 
3   Neither s1 nor s2 shall be a null pointer. s1max shall not be greater than RSIZE_MAX.
-    s1max shall not equal zero. m shall not equal zero.422) m shall be greater than
+    s1max shall not equal zero. m shall not equal zero.[422] m shall be greater than
     strnlen_s(s2, m ). Copying shall not take place between objects that overlap.
 

-
 
 
Footnote 422) Zero means that s1 was not null terminated upon entry to strcat_s.
 

 
-
+
 
4   If there is a runtime-constraint violation, then if s1 is not a null pointer and s1max is
     greater than zero and not greater than RSIZE_MAX, then strcat_s sets s1[0] to the
     null character.
     Description
 

-
-
+
 
5   The strcat_s function appends a copy of the string pointed to by s2 (including the
     terminating null character) to the end of the string pointed to by s1. The initial character
     from s2 overwrites the null character at the end of s1.
 

-
-
+
 
6   All elements following the terminating null character (if any) written by strcat_s in
     the array of s1max characters pointed to by s1 take unspecified values when
-    strcat_s returns.423)
+    strcat_s returns.[423]
     Returns
 

-
 
 
Footnote 423) This allows an implementation to append characters from s2 to s1 while simultaneously checking if
          any of those characters are null. Such an approach might write a character to every element of s1
          before discovering that the first element should be set to the null character.
 

 
-
-
7   The strcat_s function returns zero424) if there was no runtime-constraint violation.
+
+
7   The strcat_s function returns zero[424] if there was no runtime-constraint violation.
     Otherwise, a nonzero value is returned.
 

-
 
 
Footnote 424) A zero return value implies that all of the requested characters from the string pointed to by s2 were
          appended to the string pointed to by s1 and that the result in s1 is null terminated.
+    than m , then m shall be greater than strnlen_s(s2, m ). Copying shall not take
+    place between objects that overlap.
 

 
-
+
 

 
K.3.7.2.2 [The strncat_s function]

-

-
-
-
1           #define _ _STDC_WANT_LIB_EXT1_ _ 1
+
+
1 Synopsis
+           #define _ _STDC_WANT_LIB_EXT1_ _ 1
             #include <string.h>
             errno_t strncat_s(char * restrict s1,
                  rsize_t s1max,
@@ -34897,63 +30078,56 @@ the specified values is outside the normal range, the characters stored are unsp
                  rsize_t n);
     Runtime-constraints
 

-
-
+
 
2   Let m denote the value s1max - strnlen_s(s1, s1max) upon entry to
     strncat_s.
 

-
-
+
 
3   Neither s1 nor s2 shall be a null pointer. Neither s1max nor n shall be greater than
-    RSIZE_MAX. s1max shall not equal zero. m shall not equal zero.425) If n is not less
-
-    than m , then m shall be greater than strnlen_s(s2, m ). Copying shall not take
-    place between objects that overlap.
+    RSIZE_MAX. s1max shall not equal zero. m shall not equal zero.[425] If n is not less
 

-
 
 
Footnote 425) Zero means that s1 was not null terminated upon entry to strncat_s.
 

 
-
+
 
4   If there is a runtime-constraint violation, then if s1 is not a null pointer and s1max is
     greater than zero and not greater than RSIZE_MAX, then strncat_s sets s1[0] to the
     null character.
     Description
 

-
-
+
 
5   The strncat_s function appends not more than n successive characters (characters
     that follow a null character are not copied) from the array pointed to by s2 to the end of
     the string pointed to by s1. The initial character from s2 overwrites the null character at
     the end of s1. If no null character was copied from s2, then s1[s1max-m+n] is set to
     a null character.
 

-
-
+
 
6   All elements following the terminating null character (if any) written by strncat_s in
     the array of s1max characters pointed to by s1 take unspecified values when
-    strncat_s returns.426)
+    strncat_s returns.[426]
     Returns
 

-
 
 
Footnote 426) This allows an implementation to append characters from s2 to s1 while simultaneously checking if
          any of those characters are null. Such an approach might write a character to every element of s1
          before discovering that the first element should be set to the null character.
 

 
-
-
7   The strncat_s function returns zero427) if there was no runtime-constraint violation.
+
+
7   The strncat_s function returns zero[427] if there was no runtime-constraint violation.
     Otherwise, a nonzero value is returned.
 

-
 
 
Footnote 427) A zero return value implies that all of the requested characters from the string pointed to by s2 were
          appended to the string pointed to by s1 and that the result in s1 is null terminated.
+    After the second call r2 will have the value zero and s2 will contain the sequence hello\0.
+    After the third call r3 will have a nonzero value and s3 will contain the sequence \0.
+    After the fourth call r4 will have the value zero and s4 will contain the sequence abcdef\0.
 

 
-
+
 
8   EXAMPLE 1 The strncat_s function can be used to copy a string without the danger that the result
     will not be null terminated or that characters will be written past the end of the destination array.
             #define _ _STDC_WANT_LIB_EXT1_ _ 1
@@ -34971,25 +30145,16 @@ the specified values is outside the normal range, the characters stored are unsp
             r4 = strncat_s(s4, 7, "defghijklmn", 3);
     After the first call r1 will have the value zero and s1 will contain the sequence goodbye\0.
 
-    After the second call r2 will have the value zero and s2 will contain the sequence hello\0.
-    After the third call r3 will have a nonzero value and s3 will contain the sequence \0.
-    After the fourth call r4 will have the value zero and s4 will contain the sequence abcdef\0.
-
 

-
-
+
 

 
K.3.7.3 [Search functions]

-
 Search functions
-

-
-
+
 

 
K.3.7.3.1 [The strtok_s function]

-

-
-
-
1           #define _ _STDC_WANT_LIB_EXT1_ _ 1
+
+
1 Synopsis
+           #define _ _STDC_WANT_LIB_EXT1_ _ 1
             #include <string.h>
             char *strtok_s(char * restrict s1,
                  rsize_t * restrict s1max,
@@ -34997,30 +30162,26 @@ the specified values is outside the normal range, the characters stored are unsp
                  char ** restrict ptr);
     Runtime-constraints
 

-
-
+
 
2   None of s1max, s2, or ptr shall be a null pointer. If s1 is a null pointer, then *ptr
     shall not be a null pointer. The value of *s1max shall not be greater than RSIZE_MAX.
     The end of the token found shall occur within the first *s1max characters of s1 for the
     first call, and shall occur within the first *s1max characters of where searching resumes
     on subsequent calls.
 

-
-
+
 
3   If there is a runtime-constraint violation, the strtok_s function does not indirect
     through the s1 or s2 pointers, and does not store a value in the object pointed to by ptr.
     Description
 

-
-
+
 
4   A sequence of calls to the strtok_s function breaks the string pointed to by s1 into a
     sequence of tokens, each of which is delimited by a character from the string pointed to
     by s2. The fourth argument points to a caller-provided char pointer into which the
     strtok_s function stores information necessary for it to continue scanning the same
     string.
 

-
-
+
 
5   The first call in a sequence has a non-null first argument and s1max points to an object
     whose value is the number of elements in the character array pointed to by the first
     argument. The first call stores an initial value in the object pointed to by ptr and
@@ -35030,36 +30191,31 @@ the specified values is outside the normal range, the characters stored are unsp
     previous call in the sequence, which are then updated. The separator string pointed to by
     s2 may be different from call to call.
 

-
-
+
 
6   The first call in the sequence searches the string pointed to by s1 for the first character
     that is not contained in the current separator string pointed to by s2. If no such character
     is found, then there are no tokens in the string pointed to by s1 and the strtok_s
     function returns a null pointer. If such a character is found, it is the start of the first token.
 

-
-
+
 
7    The strtok_s function then searches from there for the first character in s1 that is
      contained in the current separator string. If no such character is found, the current token
      extends to the end of the string pointed to by s1, and subsequent searches in the same
      string for a token return a null pointer. If such a character is found, it is overwritten by a
      null character, which terminates the current token.
 

-
-
+
 
8    In all cases, the strtok_s function stores sufficient information in the pointer pointed
      to by ptr so that subsequent calls, with a null pointer for s1 and the unmodified pointer
      value for ptr, shall start searching just past the element overwritten by a null character
      (if any).
      Returns
 

-
-
+
 
9    The strtok_s function returns a pointer to the first character of a token, or a null
      pointer if there is no token or there is a runtime-constraint violation.
 

-
-
+
 
10   EXAMPLE
              #define _ _STDC_WANT_LIB_EXT1_ _ 1
              #include <string.h>
@@ -35074,234 +30230,156 @@ the specified values is outside the normal range, the characters stored are unsp
              t   =   strtok_s(NULL,   &max1,   "#,", &ptr1);       //   t   points to the token "c"
              t   =   strtok_s(NULL,   &max1,   "?", &ptr1);        //   t   is a null pointer
 

-
-
+
 

 
K.3.7.4 [Miscellaneous functions]

-
 Miscellaneous functions
-

-
-
+
 

 
K.3.7.4.1 [The memset_s function]

-

-
-
-
1            #define _ _STDC_WANT_LIB_EXT1_ _ 1
+
+
1 Synopsis
+            #define _ _STDC_WANT_LIB_EXT1_ _ 1
              #include <string.h>
              errno_t memset_s(void *s, rsize_t smax, int c, rsize_t n)
      Runtime-constraints
 

-
-
+
 
2    s shall not be a null pointer. Neither smax nor n shall be greater than RSIZE_MAX. n
      shall not be greater than smax.
 

-
-
+
 
3    If there is a runtime-constraint violation, then if s is not a null pointer and smax is not
      greater than RSIZE_MAX, the memset_s function stores the value of c (converted to an
      unsigned char) into each of the first smax characters of the object pointed to by s.
 
     Description
 

-
-
+
 
4   The memset_s function copies the value of c (converted to an unsigned char) into
     each of the first n characters of the object pointed to by s. Unlike memset, any call to
     the memset_s function shall be evaluated strictly according to the rules of the abstract
-    machine as described in (5.1.2.3). That is, any call to the memset_s function shall
+    machine as described in (5.1.2.3). That is, any call to the memset_s function shall
     assume that the memory indicated by s and n may be accessible in the future and thus
     must contain the values indicated by c.
     Returns
 

-
-
+
 
5   The memset_s function returns zero if there was no runtime-constraint violation.
     Otherwise, a nonzero value is returned.
 

-
-
+
 

 
K.3.7.4.2 [The strerror_s function]

-

-
-
-
1          #define _ _STDC_WANT_LIB_EXT1_ _ 1
+
+
1 Synopsis
+          #define _ _STDC_WANT_LIB_EXT1_ _ 1
            #include <string.h>
            errno_t strerror_s(char *s, rsize_t maxsize,
                 errno_t errnum);
     Runtime-constraints
 

-
-
+
 
2   s shall not be a null pointer. maxsize shall not be greater than RSIZE_MAX.
     maxsize shall not equal zero.
 

-
-
+
 
3   If there is a runtime-constraint violation, then the array (if any) pointed to by s is not
     modified.
     Description
 

-
-
+
 
4   The strerror_s function maps the number in errnum to a locale-specific message
     string. Typically, the values for errnum come from errno, but strerror_s shall
     map any value of type int to a message.
 

-
-
+
 
5   If the length of the desired string is less than maxsize, then the string is copied to the
     array pointed to by s.
 

-
-
+
 
6   Otherwise, if maxsize is greater than zero, then maxsize-1 characters are copied
     from the string to the array pointed to by s and then s[maxsize-1] is set to the null
     character. Then, if maxsize is greater than 3, then s[maxsize-2],
     s[maxsize-3], and s[maxsize-4] are set to the character period (.).
     Returns
 

-
-
+
 
7   The strerror_s function returns zero if the length of the desired string was less than
     maxsize and there was no runtime-constraint violation. Otherwise, the strerror_s
     function returns a nonzero value.
 
 

-
-
+
 

 
K.3.7.4.3 [The strerrorlen_s function]

-

-
-
-
1           #define _ _STDC_WANT_LIB_EXT1_ _ 1
+
+
1 Synopsis
+           #define _ _STDC_WANT_LIB_EXT1_ _ 1
             #include <string.h>
             size_t strerrorlen_s(errno_t errnum);
     Description
 

-
-
+
 
2   The strerrorlen_s function calculates the length of the (untruncated) locale-specific
     message string that the strerror_s function maps to errnum.
     Returns
 

-
-
+
 
3   The strerrorlen_s function returns the number of characters (not including the null
     character) in the full message string.
 

-
-
+
 

 
K.3.7.4.4 [The strnlen_s function]

-

-
-
-
1           #define _ _STDC_WANT_LIB_EXT1_ _ 1
+
+
1 Synopsis
+           #define _ _STDC_WANT_LIB_EXT1_ _ 1
             #include <string.h>
             size_t strnlen_s(const char *s, size_t maxsize);
     Description
 

-
-
+
 
2   The strnlen_s function computes the length of the string pointed to by s.
     Returns
 

-
-
-
3   If s is a null pointer,428) then the strnlen_s function returns zero.
+
+
3   If s is a null pointer,[428] then the strnlen_s function returns zero.
 

-
 
 
Footnote 428) Note that the strnlen_s function has no runtime-constraints. This lack of runtime-constraints
          along with the values returned for a null pointer or an unterminated string argument make
          strnlen_s useful in algorithms that gracefully handle such exceptional data.
 

 
-
+
 
4   Otherwise, the strnlen_s function returns the number of characters that precede the
     terminating null character. If there is no null character in the first maxsize characters of
     s then strnlen_s returns maxsize. At most the first maxsize characters of s shall
     be accessed by strnlen_s.
 
 

-
-
+
 

-
K.3.8 [Date and time ]

-

-
-
+
K.3.8 [Date and time <time.h>]

+
 
1   The header <time.h> defines two types.
 

-
-
+
 
2   The types are
             errno_t
     which is type int; and
             rsize_t
     which is the type size_t.
 

-
-
+
 

 
K.3.8.1 [Components of time]

-

-
-
+
 
1   A broken-down time is normalized if the values of the members of the tm structure are in
-    their normal rages.429)
+    their normal rages.[429]
 

-
 
-
Footnote 429) The normal ranges are defined in 7.27.1.
-

-
-
-

-
K.3.8.2 [Time conversion functions]

-

-
-
-
1   Like the strftime function, the asctime_s and ctime_s functions do not return a
-    pointer to a static object, and other library functions are permitted to call them.
-

-
-
-

-
K.3.8.2.1 [The asctime_s function]

-

-
-
-
1           #define _ _STDC_WANT_LIB_EXT1_ _ 1
-            #include <time.h>
-            errno_t asctime_s(char *s, rsize_t maxsize,
-                 const struct tm *timeptr);
-    Runtime-constraints
-

-
-
-
2   Neither s nor timeptr shall be a null pointer. maxsize shall not be less than 26 and
-    shall not be greater than RSIZE_MAX. The broken-down time pointed to by timeptr
-    shall be normalized. The calendar year represented by the broken-down time pointed to
-    by timeptr shall not be less than calendar year 0 and shall not be greater than calendar
-    year 9999.
-

-
-
-
3   If there is a runtime-constraint violation, there is no attempt to convert the time, and
-    s[0] is set to a null character if s is not a null pointer and maxsize is not zero and is
-    not greater than RSIZE_MAX.
-    Description
-

-
-
-
4   The asctime_s function converts the normalized broken-down time in the structure
-    pointed to by timeptr into a 26 character (including the null character) string in the
-
+
Footnote 429) The normal ranges are defined in 7.27.1.
     form
             Sun Sep 16 01:03:52 1973\n\0
     The fields making up this string are (in order):
@@ -35333,38 +30411,68 @@ the specified values is outside the normal range, the characters stored are unsp
     behavior. If you do not require the exact form of the result string produced by the
     asctime_s function, consider using the strftime function instead.
     Returns
-

+

 
-
+
+

+
K.3.8.2 [Time conversion functions]

+
+
1   Like the strftime function, the asctime_s and ctime_s functions do not return a
+    pointer to a static object, and other library functions are permitted to call them.
+

+
+

+
K.3.8.2.1 [The asctime_s function]

+
+
1 Synopsis
+           #define _ _STDC_WANT_LIB_EXT1_ _ 1
+            #include <time.h>
+            errno_t asctime_s(char *s, rsize_t maxsize,
+                 const struct tm *timeptr);
+    Runtime-constraints
+

+
+
2   Neither s nor timeptr shall be a null pointer. maxsize shall not be less than 26 and
+    shall not be greater than RSIZE_MAX. The broken-down time pointed to by timeptr
+    shall be normalized. The calendar year represented by the broken-down time pointed to
+    by timeptr shall not be less than calendar year 0 and shall not be greater than calendar
+    year 9999.
+

+
+
3   If there is a runtime-constraint violation, there is no attempt to convert the time, and
+    s[0] is set to a null character if s is not a null pointer and maxsize is not zero and is
+    not greater than RSIZE_MAX.
+    Description
+

+
+
4   The asctime_s function converts the normalized broken-down time in the structure
+    pointed to by timeptr into a 26 character (including the null character) string in the
+

+
 
5   The asctime_s function returns zero if the time was successfully converted and stored
     into the array pointed to by s. Otherwise, it returns a nonzero value.
 

-
-
+
 

 
K.3.8.2.2 [The ctime_s function]

-

-
-
-
1          #define _ _STDC_WANT_LIB_EXT1_ _ 1
+
+
1 Synopsis
+          #define _ _STDC_WANT_LIB_EXT1_ _ 1
            #include <time.h>
            errno_t ctime_s(char *s, rsize_t maxsize,
                 const time_t *timer);
     Runtime-constraints
 

-
-
+
 
2   Neither s nor timer shall be a null pointer. maxsize shall not be less than 26 and
     shall not be greater than RSIZE_MAX.
 

-
-
+
 
3   If there is a runtime-constraint violation, s[0] is set to a null character if s is not a null
     pointer and maxsize is not equal zero and is not greater than RSIZE_MAX.
     Description
 

-
-
+
 
4   The ctime_s function converts the calendar time pointed to by timer to local time in
     the form of a string. It is equivalent to
            asctime_s(s, maxsize, localtime_s(timer))
@@ -35374,190 +30482,157 @@ the specified values is outside the normal range, the characters stored are unsp
     ctime_s function, consider using the strftime function instead.
     Returns
 

-
-
+
 
5   The ctime_s function returns zero if the time was successfully converted and stored
     into the array pointed to by s. Otherwise, it returns a nonzero value.
 

-
-
+
 

 
K.3.8.2.3 [The gmtime_s function]

-

-
-
-
1          #define _ _STDC_WANT_LIB_EXT1_ _ 1
+
+
1 Synopsis
+          #define _ _STDC_WANT_LIB_EXT1_ _ 1
            #include <time.h>
            struct tm *gmtime_s(const time_t * restrict timer,
                 struct tm * restrict result);
     Runtime-constraints
 

-
-
+
 
2   Neither timer nor result shall be a null pointer.
 

-
-
+
 
3   If there is a runtime-constraint violation, there is no attempt to convert the time.
     Description
 

-
-
+
 
4   The gmtime_s function converts the calendar time pointed to by timer into a broken-
     down time, expressed as UTC. The broken-down time is stored in the structure pointed
     to by result.
     Returns
 

-
-
+
 
5   The gmtime_s function returns result, or a null pointer if the specified time cannot
     be converted to UTC or there is a runtime-constraint violation.
 

-
-
+
 

 
K.3.8.2.4 [The localtime_s function]

-

-
-
-
1            #define _ _STDC_WANT_LIB_EXT1_ _ 1
+
+
1 Synopsis
+            #define _ _STDC_WANT_LIB_EXT1_ _ 1
              #include <time.h>
              struct tm *localtime_s(const time_t * restrict timer,
                   struct tm * restrict result);
     Runtime-constraints
 

-
-
+
 
2   Neither timer nor result shall be a null pointer.
 

-
-
+
 
3   If there is a runtime-constraint violation, there is no attempt to convert the time.
     Description
 

-
-
+
 
4   The localtime_s function converts the calendar time pointed to by timer into a
     broken-down time, expressed as local time. The broken-down time is stored in the
     structure pointed to by result.
     Returns
 

-
-
+
 
5   The localtime_s function returns result, or a null pointer if the specified time
     cannot be converted to local time or there is a runtime-constraint violation.
 

-
-
+
 

-
K.3.9 [Extended multibyte and wide character utilities ]

-

-
-
+
K.3.9 [Extended multibyte and wide character utilities <wchar.h>]

+
 
1   The header <wchar.h> defines two types.
 

-
-
+
 
2   The types are
              errno_t
     which is type int; and
              rsize_t
     which is the type size_t.
 

-
-
+
 
3   Unless explicitly stated otherwise, if the execution of a function described in this
     subclause causes copying to take place between objects that overlap, the objects take on
     unspecified values.
 

-
-
+
 

 
K.3.9.1 [Formatted wide character input/output functions]

-
 Formatted wide character input/output functions
-

-
-
+
 

 
K.3.9.1.1 [The fwprintf_s function]

-

-
-
-
1           #define _ _STDC_WANT_LIB_EXT1_ _ 1
+
+
1 Synopsis
+           #define _ _STDC_WANT_LIB_EXT1_ _ 1
             #include <wchar.h>
             int fwprintf_s(FILE * restrict stream,
                  const wchar_t * restrict format, ...);
     Runtime-constraints
 

-
-
-
2   Neither stream nor format shall be a null pointer. The %n specifier430) (modified or
+
+
2   Neither stream nor format shall be a null pointer. The %n specifier[430] (modified or
     not by flags, field width, or precision) shall not appear in the wide string pointed to by
     format. Any argument to fwprintf_s corresponding to a %s specifier shall not be a
     null pointer.
 

-
 
 
Footnote 430) It is not a runtime-constraint violation for the wide characters %n to appear in sequence in the wide
          string pointed at by format when those wide characters are not a interpreted as a %n specifier. For
          example, if the entire format string was L"%%n".
 

 
-
+
 
3   If there is a runtime-constraint violation, the fwprintf_s function does not attempt to
     produce further output, and it is unspecified to what extent fwprintf_s produced
     output before discovering the runtime-constraint violation.
     Description
 

-
-
+
 
4   The fwprintf_s function is equivalent to the fwprintf function except for the
     explicit runtime-constraints listed above.
     Returns
 

-
-
+
 
5   The fwprintf_s function returns the number of wide characters transmitted, or a
     negative value if an output error, encoding error, or runtime-constraint violation occurred.
 

-
-
+
 

 
K.3.9.1.2 [The fwscanf_s function]

-

-
-
-
1           #define _ _STDC_WANT_LIB_EXT1_ _ 1
+
+
1 Synopsis
+           #define _ _STDC_WANT_LIB_EXT1_ _ 1
             #include <stdio.h>
             #include <wchar.h>
             int fwscanf_s(FILE * restrict stream,
                  const wchar_t * restrict format, ...);
     Runtime-constraints
 

-
-
+
 
2   Neither stream nor format shall be a null pointer. Any argument indirected though in
     order to store converted input shall not be a null pointer.
 
 

-
-
+
 
3   If there is a runtime-constraint violation, the fwscanf_s function does not attempt to
     perform further input, and it is unspecified to what extent fwscanf_s performed input
     before discovering the runtime-constraint violation.
     Description
 

-
-
+
 
4   The fwscanf_s function is equivalent to fwscanf except that the c, s, and [
     conversion specifiers apply to a pair of arguments (unless assignment suppression is
     indicated by a *). The first of these arguments is the same as for fwscanf. That
     argument is immediately followed in the argument list by the second argument, which has
     type size_t and gives the number of elements in the array pointed to by the first
     argument of the pair. If the first argument points to a scalar object, it is considered to be
-    an array of one element.431)
+    an array of one element.[431]
 

-
 
 
Footnote 431) If the format is known at translation time, an implementation may issue a diagnostic for any argument
          used to store the result from a c, s, or [ conversion specifier if that argument is not followed by an
@@ -35569,178 +30644,154 @@ the specified values is outside the normal range, the characters stored are unsp
          using the hh length modifier, a length argument must follow the pointer argument. Another useful
          diagnostic could flag any non-pointer argument following format that did not have a type
          compatible with rsize_t.
+    precision) shall not appear in the wide string pointed to by format. Any argument to
+    snwprintf_s corresponding to a %s specifier shall not be a null pointer. No encoding
+    error shall occur.
 

 
-
+
 
5   A matching failure occurs if the number of elements in a receiving object is insufficient to
     hold the converted input (including any trailing null character).
     Returns
 

-
-
+
 
6   The fwscanf_s function returns the value of the macro EOF if an input failure occurs
     before any conversion or if there is a runtime-constraint violation. Otherwise, the
     fwscanf_s function returns the number of input items assigned, which can be fewer
     than provided for, or even zero, in the event of an early matching failure.
 

-
-
+
 

 
K.3.9.1.3 [The snwprintf_s function]

-

-
-
-
1           #define _ _STDC_WANT_LIB_EXT1_ _ 1
+
+
1 Synopsis
+           #define _ _STDC_WANT_LIB_EXT1_ _ 1
             #include <wchar.h>
             int snwprintf_s(wchar_t * restrict s,
                  rsize_t n,
                  const wchar_t * restrict format, ...);
     Runtime-constraints
 

-
-
+
 
2   Neither s nor format shall be a null pointer. n shall neither equal zero nor be greater
-    than RSIZE_MAX. The %n specifier432) (modified or not by flags, field width, or
-
-    precision) shall not appear in the wide string pointed to by format. Any argument to
-    snwprintf_s corresponding to a %s specifier shall not be a null pointer. No encoding
-    error shall occur.
+    than RSIZE_MAX. The %n specifier[432] (modified or not by flags, field width, or
 

-
 
 
Footnote 432) It is not a runtime-constraint violation for the wide characters %n to appear in sequence in the wide
          string pointed at by format when those wide characters are not a interpreted as a %n specifier. For
          example, if the entire format string was L"%%n".
 

 
-
+
 
3   If there is a runtime-constraint violation, then if s is not a null pointer and n is greater
     than zero and less than RSIZE_MAX, then the snwprintf_s function sets s[0] to the
     null wide character.
     Description
 

-
-
+
 
4   The snwprintf_s function is equivalent to the swprintf function except for the
     explicit runtime-constraints listed above.
 

-
-
+
 
5   The snwprintf_s function, unlike swprintf_s, will truncate the result to fit within
     the array pointed to by s.
     Returns
 

-
-
+
 
6   The snwprintf_s function returns the number of wide characters that would have
     been written had n been sufficiently large, not counting the terminating wide null
     character, or a negative value if a runtime-constraint violation occurred. Thus, the null-
     terminated output has been completely written if and only if the returned value is
     nonnegative and less than n.
 

-
-
+
 

 
K.3.9.1.4 [The swprintf_s function]

-

-
-
-
1           #define _ _STDC_WANT_LIB_EXT1_ _ 1
+
+
1 Synopsis
+           #define _ _STDC_WANT_LIB_EXT1_ _ 1
             #include <wchar.h>
             int swprintf_s(wchar_t * restrict s, rsize_t n,
                  const wchar_t * restrict format, ...);
     Runtime-constraints
 

-
-
+
 
2   Neither s nor format shall be a null pointer. n shall neither equal zero nor be greater
     than RSIZE_MAX. The number of wide characters (including the trailing null) required
     for the result to be written to the array pointed to by s shall not be greater than n. The %n
-    specifier433) (modified or not by flags, field width, or precision) shall not appear in the
+    specifier[433] (modified or not by flags, field width, or precision) shall not appear in the
     wide string pointed to by format. Any argument to swprintf_s corresponding to a
     %s specifier shall not be a null pointer. No encoding error shall occur.
 
 

-
 
 
Footnote 433) It is not a runtime-constraint violation for the wide characters %n to appear in sequence in the wide
          string pointed at by format when those wide characters are not a interpreted as a %n specifier. For
          example, if the entire format string was L"%%n".
 

 
-
+
 
3   If there is a runtime-constraint violation, then if s is not a null pointer and n is greater
     than zero and less than RSIZE_MAX, then the swprintf_s function sets s[0] to the
     null wide character.
     Description
 

-
-
+
 
4   The swprintf_s function is equivalent to the swprintf function except for the
     explicit runtime-constraints listed above.
 

-
-
+
 
5   The swprintf_s function, unlike snwprintf_s, treats a result too big for the array
     pointed to by s as a runtime-constraint violation.
     Returns
 

-
-
+
 
6   If no runtime-constraint violation occurred, the swprintf_s function returns the
     number of wide characters written in the array, not counting the terminating null wide
     character. If an encoding error occurred or if n or more wide characters are requested to
     be written, swprintf_s returns a negative value. If any other runtime-constraint
     violation occurred, swprintf_s returns zero.
 

-
-
+
 

 
K.3.9.1.5 [The swscanf_s function]

-

-
-
-
1           #define _ _STDC_WANT_LIB_EXT1_ _ 1
+
+
1 Synopsis
+           #define _ _STDC_WANT_LIB_EXT1_ _ 1
             #include <wchar.h>
             int swscanf_s(const wchar_t * restrict s,
                  const wchar_t * restrict format, ...);
     Runtime-constraints
 

-
-
+
 
2   Neither s nor format shall be a null pointer. Any argument indirected though in order
     to store converted input shall not be a null pointer.
 

-
-
+
 
3   If there is a runtime-constraint violation, the swscanf_s function does not attempt to
     perform further input, and it is unspecified to what extent swscanf_s performed input
     before discovering the runtime-constraint violation.
     Description
 

-
-
+
 
4   The swscanf_s function is equivalent to fwscanf_s, except that the argument s
     specifies a wide string from which the input is to be obtained, rather than from a stream.
     Reaching the end of the wide string is equivalent to encountering end-of-file for the
     fwscanf_s function.
     Returns
 

-
-
+
 
5   The swscanf_s function returns the value of the macro EOF if an input failure occurs
     before any conversion or if there is a runtime-constraint violation. Otherwise, the
     swscanf_s function returns the number of input items assigned, which can be fewer
     than provided for, or even zero, in the event of an early matching failure.
 

-
-
+
 

 
K.3.9.1.6 [The vfwprintf_s function]

-

-
-
-
1           #define _ _STDC_WANT_LIB_EXT1_ _ 1
+
+
1 Synopsis
+           #define _ _STDC_WANT_LIB_EXT1_ _ 1
             #include <stdarg.h>
             #include <stdio.h>
             #include <wchar.h>
@@ -35749,93 +30800,80 @@ the specified values is outside the normal range, the characters stored are unsp
                  va_list arg);
     Runtime-constraints
 

-
-
-
2   Neither stream nor format shall be a null pointer. The %n specifier434) (modified or
+
+
2   Neither stream nor format shall be a null pointer. The %n specifier[434] (modified or
     not by flags, field width, or precision) shall not appear in the wide string pointed to by
     format. Any argument to vfwprintf_s corresponding to a %s specifier shall not be
     a null pointer.
 

-
 
 
Footnote 434) It is not a runtime-constraint violation for the wide characters %n to appear in sequence in the wide
          string pointed at by format when those wide characters are not a interpreted as a %n specifier. For
          example, if the entire format string was L"%%n".
+    Runtime-constraints
 

 
-
+
 
3   If there is a runtime-constraint violation, the vfwprintf_s function does not attempt
     to produce further output, and it is unspecified to what extent vfwprintf_s produced
     output before discovering the runtime-constraint violation.
     Description
 

-
-
+
 
4   The vfwprintf_s function is equivalent to the vfwprintf function except for the
     explicit runtime-constraints listed above.
     Returns
 

-
-
+
 
5   The vfwprintf_s function returns the number of wide characters transmitted, or a
     negative value if an output error, encoding error, or runtime-constraint violation occurred.
 

-
-
+
 

 
K.3.9.1.7 [The vfwscanf_s function]

-

-
-
-
1           #define _ _STDC_WANT_LIB_EXT1_ _ 1
+
+
1 Synopsis
+           #define _ _STDC_WANT_LIB_EXT1_ _ 1
             #include <stdarg.h>
             #include <stdio.h>
             #include <wchar.h>
             int vfwscanf_s(FILE * restrict stream,
                  const wchar_t * restrict format, va_list arg);
-
-    Runtime-constraints
 

-
-
+
 
2   Neither stream nor format shall be a null pointer. Any argument indirected though in
     order to store converted input shall not be a null pointer.
 

-
-
+
 
3   If there is a runtime-constraint violation, the vfwscanf_s function does not attempt to
     perform further input, and it is unspecified to what extent vfwscanf_s performed input
     before discovering the runtime-constraint violation.
     Description
 

-
-
+
 
4   The vfwscanf_s function is equivalent to fwscanf_s, with the variable argument
     list replaced by arg, which shall have been initialized by the va_start macro (and
     possibly subsequent va_arg calls). The vfwscanf_s function does not invoke the
-    va_end macro.435)
+    va_end macro.[435]
     Returns
 

-
 
 
Footnote 435) As the functions vfwscanf_s, vwscanf_s, and vswscanf_s invoke the va_arg macro, the
          value of arg after the return is indeterminate.
 

 
-
+
 
5   The vfwscanf_s function returns the value of the macro EOF if an input failure occurs
     before any conversion or if there is a runtime-constraint violation. Otherwise, the
     vfwscanf_s function returns the number of input items assigned, which can be fewer
     than provided for, or even zero, in the event of an early matching failure.
 

-
-
+
 

 
K.3.9.1.8 [The vsnwprintf_s function]

-

-
-
-
1           #define _ _STDC_WANT_LIB_EXT1_ _ 1
+
+
1 Synopsis
+           #define _ _STDC_WANT_LIB_EXT1_ _ 1
             #include <stdarg.h>
             #include <wchar.h>
             int vsnwprintf_s(wchar_t * restrict s,
@@ -35844,55 +30882,48 @@ the specified values is outside the normal range, the characters stored are unsp
                  va_list arg);
     Runtime-constraints
 

-
-
+
 
2   Neither s nor format shall be a null pointer. n shall neither equal zero nor be greater
-    than RSIZE_MAX. The %n specifier436) (modified or not by flags, field width, or
+    than RSIZE_MAX. The %n specifier[436] (modified or not by flags, field width, or
     precision) shall not appear in the wide string pointed to by format. Any argument to
     vsnwprintf_s corresponding to a %s specifier shall not be a null pointer. No
     encoding error shall occur.
 
 

-
 
 
Footnote 436) It is not a runtime-constraint violation for the wide characters %n to appear in sequence in the wide
          string pointed at by format when those wide characters are not a interpreted as a %n specifier. For
          example, if the entire format string was L"%%n".
 

 
-
+
 
3   If there is a runtime-constraint violation, then if s is not a null pointer and n is greater
     than zero and less than RSIZE_MAX, then the vsnwprintf_s function sets s[0] to
     the null wide character.
     Description
 

-
-
+
 
4   The vsnwprintf_s function is equivalent to the vswprintf function except for the
     explicit runtime-constraints listed above.
 

-
-
+
 
5   The vsnwprintf_s function, unlike vswprintf_s, will truncate the result to fit
     within the array pointed to by s.
     Returns
 

-
-
+
 
6   The vsnwprintf_s function returns the number of wide characters that would have
     been written had n been sufficiently large, not counting the terminating null character, or
     a negative value if a runtime-constraint violation occurred. Thus, the null-terminated
     output has been completely written if and only if the returned value is nonnegative and
     less than n.
 

-
-
+
 

 
K.3.9.1.9 [The vswprintf_s function]

-

-
-
-
1           #define _ _STDC_WANT_LIB_EXT1_ _ 1
+
+
1 Synopsis
+           #define _ _STDC_WANT_LIB_EXT1_ _ 1
             #include <stdarg.h>
             #include <wchar.h>
             int vswprintf_s(wchar_t * restrict s,
@@ -35901,56 +30932,48 @@ the specified values is outside the normal range, the characters stored are unsp
                  va_list arg);
     Runtime-constraints
 

-
-
+
 
2   Neither s nor format shall be a null pointer. n shall neither equal zero nor be greater
     than RSIZE_MAX. The number of wide characters (including the trailing null) required
     for the result to be written to the array pointed to by s shall not be greater than n. The %n
-    specifier437) (modified or not by flags, field width, or precision) shall not appear in the
+    specifier[437] (modified or not by flags, field width, or precision) shall not appear in the
     wide string pointed to by format. Any argument to vswprintf_s corresponding to a
     %s specifier shall not be a null pointer. No encoding error shall occur.
 

-
 
 
Footnote 437) It is not a runtime-constraint violation for the wide characters %n to appear in sequence in the wide
          string pointed at by format when those wide characters are not a interpreted as a %n specifier. For
          example, if the entire format string was L"%%n".
+    Description
 

 
-
+
 
3   If there is a runtime-constraint violation, then if s is not a null pointer and n is greater
     than zero and less than RSIZE_MAX, then the vswprintf_s function sets s[0] to the
     null wide character.
-
-    Description
 

-
-
+
 
4   The vswprintf_s function is equivalent to the vswprintf function except for the
     explicit runtime-constraints listed above.
 

-
-
+
 
5   The vswprintf_s function, unlike vsnwprintf_s, treats a result too big for the
     array pointed to by s as a runtime-constraint violation.
     Returns
 

-
-
+
 
6   If no runtime-constraint violation occurred, the vswprintf_s function returns the
     number of wide characters written in the array, not counting the terminating null wide
     character. If an encoding error occurred or if n or more wide characters are requested to
     be written, vswprintf_s returns a negative value. If any other runtime-constraint
     violation occurred, vswprintf_s returns zero.
 

-
-
+
 

 
K.3.9.1.10 [The vswscanf_s function]

-

-
-
-
1           #define _ _STDC_WANT_LIB_EXT1_ _ 1
+
+
1 Synopsis
+           #define _ _STDC_WANT_LIB_EXT1_ _ 1
             #include <stdarg.h>
             #include <wchar.h>
             int vswscanf_s(const wchar_t * restrict s,
@@ -35958,282 +30981,237 @@ the specified values is outside the normal range, the characters stored are unsp
                  va_list arg);
     Runtime-constraints
 

-
-
+
 
2   Neither s nor format shall be a null pointer. Any argument indirected though in order
     to store converted input shall not be a null pointer.
 

-
-
+
 
3   If there is a runtime-constraint violation, the vswscanf_s function does not attempt to
     perform further input, and it is unspecified to what extent vswscanf_s performed input
     before discovering the runtime-constraint violation.
     Description
 

-
-
+
 
4   The vswscanf_s function is equivalent to swscanf_s, with the variable argument
     list replaced by arg, which shall have been initialized by the va_start macro (and
     possibly subsequent va_arg calls). The vswscanf_s function does not invoke the
-    va_end macro.438)
-
-    Returns
+    va_end macro.[438]
 

-
 
 
Footnote 438) As the functions vfwscanf_s, vwscanf_s, and vswscanf_s invoke the va_arg macro, the
          value of arg after the return is indeterminate.
+    Returns
 

 
-
+
 
5   The vswscanf_s function returns the value of the macro EOF if an input failure occurs
     before any conversion or if there is a runtime-constraint violation. Otherwise, the
     vswscanf_s function returns the number of input items assigned, which can be fewer
     than provided for, or even zero, in the event of an early matching failure.
 

-
-
+
 

 
K.3.9.1.11 [The vwprintf_s function]

-

-
-
-
1           #define _ _STDC_WANT_LIB_EXT1_ _ 1
+
+
1 Synopsis
+           #define _ _STDC_WANT_LIB_EXT1_ _ 1
             #include <stdarg.h>
             #include <wchar.h>
             int vwprintf_s(const wchar_t * restrict format,
                  va_list arg);
     Runtime-constraints
 

-
-
-
2   format shall not be a null pointer. The %n specifier439) (modified or not by flags, field
+
+
2   format shall not be a null pointer. The %n specifier[439] (modified or not by flags, field
     width, or precision) shall not appear in the wide string pointed to by format. Any
     argument to vwprintf_s corresponding to a %s specifier shall not be a null pointer.
 

-
 
 
Footnote 439) It is not a runtime-constraint violation for the wide characters %n to appear in sequence in the wide
          string pointed at by format when those wide characters are not a interpreted as a %n specifier. For
          example, if the entire format string was L"%%n".
 

 
-
+
 
3   If there is a runtime-constraint violation, the vwprintf_s function does not attempt to
     produce further output, and it is unspecified to what extent vwprintf_s produced
     output before discovering the runtime-constraint violation.
     Description
 

-
-
+
 
4   The vwprintf_s function is equivalent to the vwprintf function except for the
     explicit runtime-constraints listed above.
     Returns
 

-
-
+
 
5   The vwprintf_s function returns the number of wide characters transmitted, or a
     negative value if an output error, encoding error, or runtime-constraint violation occurred.
 
 

-
-
+
 

 
K.3.9.1.12 [The vwscanf_s function]

-

-
-
-
1           #define _ _STDC_WANT_LIB_EXT1_ _ 1
+
+
1 Synopsis
+           #define _ _STDC_WANT_LIB_EXT1_ _ 1
             #include <stdarg.h>
             #include <wchar.h>
             int vwscanf_s(const wchar_t * restrict format,
                  va_list arg);
     Runtime-constraints
 

-
-
+
 
2   format shall not be a null pointer. Any argument indirected though in order to store
     converted input shall not be a null pointer.
 

-
-
+
 
3   If there is a runtime-constraint violation, the vwscanf_s function does not attempt to
     perform further input, and it is unspecified to what extent vwscanf_s performed input
     before discovering the runtime-constraint violation.
     Description
 

-
-
+
 
4   The vwscanf_s function is equivalent to wscanf_s, with the variable argument list
     replaced by arg, which shall have been initialized by the va_start macro (and
     possibly subsequent va_arg calls). The vwscanf_s function does not invoke the
-    va_end macro.440)
+    va_end macro.[440]
     Returns
 

-
 
 
Footnote 440) As the functions vfwscanf_s, vwscanf_s, and vswscanf_s invoke the va_arg macro, the
          value of arg after the return is indeterminate.
 

 
-
+
 
5   The vwscanf_s function returns the value of the macro EOF if an input failure occurs
     before any conversion or if there is a runtime-constraint violation. Otherwise, the
     vwscanf_s function returns the number of input items assigned, which can be fewer
     than provided for, or even zero, in the event of an early matching failure.
 

-
-
+
 

 
K.3.9.1.13 [The wprintf_s function]

-

-
-
-
1           #define _ _STDC_WANT_LIB_EXT1_ _ 1
+
+
1 Synopsis
+           #define _ _STDC_WANT_LIB_EXT1_ _ 1
             #include <wchar.h>
             int wprintf_s(const wchar_t * restrict format, ...);
     Runtime-constraints
 

-
-
-
2   format shall not be a null pointer. The %n specifier441) (modified or not by flags, field
-
-    width, or precision) shall not appear in the wide string pointed to by format. Any
-    argument to wprintf_s corresponding to a %s specifier shall not be a null pointer.
+
+
2   format shall not be a null pointer. The %n specifier[441] (modified or not by flags, field
 

-
 
 
Footnote 441) It is not a runtime-constraint violation for the wide characters %n to appear in sequence in the wide
          string pointed at by format when those wide characters are not a interpreted as a %n specifier. For
          example, if the entire format string was L"%%n".
+    width, or precision) shall not appear in the wide string pointed to by format. Any
+    argument to wprintf_s corresponding to a %s specifier shall not be a null pointer.
 

 
-
+
 
3   If there is a runtime-constraint violation, the wprintf_s function does not attempt to
     produce further output, and it is unspecified to what extent wprintf_s produced output
     before discovering the runtime-constraint violation.
     Description
 

-
-
+
 
4   The wprintf_s function is equivalent to the wprintf function except for the explicit
     runtime-constraints listed above.
     Returns
 

-
-
+
 
5   The wprintf_s function returns the number of wide characters transmitted, or a
     negative value if an output error, encoding error, or runtime-constraint violation occurred.
 

-
-
+
 

 
K.3.9.1.14 [The wscanf_s function]

-

-
-
-
1          #define _ _STDC_WANT_LIB_EXT1_ _ 1
+
+
1 Synopsis
+          #define _ _STDC_WANT_LIB_EXT1_ _ 1
            #include <wchar.h>
            int wscanf_s(const wchar_t * restrict format, ...);
     Runtime-constraints
 

-
-
+
 
2   format shall not be a null pointer. Any argument indirected though in order to store
     converted input shall not be a null pointer.
 

-
-
+
 
3   If there is a runtime-constraint violation, the wscanf_s function does not attempt to
     perform further input, and it is unspecified to what extent wscanf_s performed input
     before discovering the runtime-constraint violation.
     Description
 

-
-
+
 
4   The wscanf_s function is equivalent to fwscanf_s with the argument stdin
     interposed before the arguments to wscanf_s.
     Returns
 

-
-
+
 
5   The wscanf_s function returns the value of the macro EOF if an input failure occurs
     before any conversion or if there is a runtime-constraint violation. Otherwise, the
     wscanf_s function returns the number of input items assigned, which can be fewer than
     provided for, or even zero, in the event of an early matching failure.
 

-
-
+
 

 
K.3.9.2 [General wide string utilities]

-
 General wide string utilities
-

-
-
+
 

 
K.3.9.2.1 [Wide string copying functions]

-
 Wide string copying functions
-

-
-
+
 

 
K.3.9.2.1.1 [The wcscpy_s function]

-

-
-
-
1           #define _ _STDC_WANT_LIB_EXT1_ _ 1
+
+
1 Synopsis
+           #define _ _STDC_WANT_LIB_EXT1_ _ 1
             #include <wchar.h>
             errno_t wcscpy_s(wchar_t * restrict s1,
                  rsize_t s1max,
                  const wchar_t * restrict s2);
     Runtime-constraints
 

-
-
+
 
2   Neither s1 nor s2 shall be a null pointer. s1max shall not be greater than RSIZE_MAX.
     s1max shall not equal zero. s1max shall be greater than wcsnlen_s(s2, s1max).
     Copying shall not take place between objects that overlap.
 

-
-
+
 
3   If there is a runtime-constraint violation, then if s1 is not a null pointer and s1max is
     greater than zero and not greater than RSIZE_MAX, then wcscpy_s sets s1[0] to the
     null wide character.
     Description
 

-
-
+
 
4   The wcscpy_s function copies the wide string pointed to by s2 (including the
     terminating null wide character) into the array pointed to by s1.
 

-
-
+
 
5   All elements following the terminating null wide character (if any) written by
     wcscpy_s in the array of s1max wide characters pointed to by s1 take unspecified
-    values when wcscpy_s returns.442)
+    values when wcscpy_s returns.[442]
     Returns
 

-
 
 
Footnote 442) This allows an implementation to copy wide characters from s2 to s1 while simultaneously checking
          if any of those wide characters are null. Such an approach might write a wide character to every
          element of s1 before discovering that the first element should be set to the null wide character.
 

 
-
-
6   The wcscpy_s function returns zero443) if there was no runtime-constraint violation.
+
+
6   The wcscpy_s function returns zero[443] if there was no runtime-constraint violation.
     Otherwise, a nonzero value is returned.
-
-     K.3.9.2.1.2 The wcsncpy_s function
-     Synopsis
 

-
 
 
Footnote 443) A zero return value implies that all of the requested wide characters from the string pointed to by s2
          fit within the array pointed to by s1 and that the result in s1 is null terminated.
+     K.3.9.2.1.2 The wcsncpy_s function
+     Synopsis
 

 
-
+
 
7            #define _ _STDC_WANT_LIB_EXT1_ _ 1
              #include <wchar.h>
              errno_t wcsncpy_s(wchar_t * restrict s1,
@@ -36242,56 +31220,43 @@ the specified values is outside the normal range, the characters stored are unsp
                   rsize_t n);
      Runtime-constraints
 

-
-
+
 
8    Neither s1 nor s2 shall be a null pointer. Neither s1max nor n shall be greater than
      RSIZE_MAX. s1max shall not equal zero. If n is not less than s1max, then s1max
      shall be greater than wcsnlen_s(s2, s1max). Copying shall not take place between
      objects that overlap.
 

-
-
+
 
9    If there is a runtime-constraint violation, then if s1 is not a null pointer and s1max is
      greater than zero and not greater than RSIZE_MAX, then wcsncpy_s sets s1[0] to the
      null wide character.
      Description
 

-
-
+
 
10   The wcsncpy_s function copies not more than n successive wide characters (wide
      characters that follow a null wide character are not copied) from the array pointed to by
      s2 to the array pointed to by s1. If no null wide character was copied from s2, then
      s1[n] is set to a null wide character.
 

-
-
+
 
11   All elements following the terminating null wide character (if any) written by
      wcsncpy_s in the array of s1max wide characters pointed to by s1 take unspecified
-     values when wcsncpy_s returns.444)
+     values when wcsncpy_s returns.[444]
      Returns
 

-
 
 
Footnote 444) This allows an implementation to copy wide characters from s2 to s1 while simultaneously checking
           if any of those wide characters are null. Such an approach might write a wide character to every
           element of s1 before discovering that the first element should be set to the null wide character.
 

 
-
-
12   The wcsncpy_s function returns zero445) if there was no runtime-constraint violation.
+
+
12   The wcsncpy_s function returns zero[445] if there was no runtime-constraint violation.
      Otherwise, a nonzero value is returned.
 

-
 
 
Footnote 445) A zero return value implies that all of the requested wide characters from the string pointed to by s2
           fit within the array pointed to by s1 and that the result in s1 is null terminated.
-

-
-
-
13   EXAMPLE 1 The wcsncpy_s function can be used to copy a wide string without the danger that the
-     result will not be null terminated or that wide characters will be written past the end of the destination
-     array.
-
              #define _ _STDC_WANT_LIB_EXT1_ _ 1
              #include <wchar.h>
              /* ... */
@@ -36305,12 +31270,16 @@ the specified values is outside the normal range, the characters stored are unsp
      The first call will assign to r1 the value zero and to dst1 the sequence of wide characters hello\0.
      The second call will assign to r2 a nonzero value and to dst2 the sequence of wide characters \0.
      The third call will assign to r3 the value zero and to dst3 the sequence of wide characters good\0.
-
      K.3.9.2.1.3 The wmemcpy_s function
      Synopsis
-

+

 
-
+
+
13   EXAMPLE 1 The wcsncpy_s function can be used to copy a wide string without the danger that the
+     result will not be null terminated or that wide characters will be written past the end of the destination
+     array.
+

+
 
14           #define _ _STDC_WANT_LIB_EXT1_ _ 1
              #include <wchar.h>
              errno_t wmemcpy_s(wchar_t * restrict s1,
@@ -36319,54 +31288,46 @@ the specified values is outside the normal range, the characters stored are unsp
                   rsize_t n);
      Runtime-constraints
 

-
-
+
 
15   Neither s1 nor s2 shall be a null pointer. Neither s1max nor n shall be greater than
      RSIZE_MAX. n shall not be greater than s1max. Copying shall not take place between
      objects that overlap.
 

-
-
+
 
16   If there is a runtime-constraint violation, the wmemcpy_s function stores zeros in the
      first s1max wide characters of the object pointed to by s1 if s1 is not a null pointer and
      s1max is not greater than RSIZE_MAX.
      Description
 

-
-
+
 
17   The wmemcpy_s function copies n successive wide characters from the object pointed
      to by s2 into the object pointed to by s1.
      Returns
 

-
-
+
 
18   The wmemcpy_s function returns zero if there was no runtime-constraint violation.
      Otherwise, a nonzero value is returned.
      K.3.9.2.1.4 The wmemmove_s function
      Synopsis
 

-
-
+
 
19          #define _ _STDC_WANT_LIB_EXT1_ _ 1
             #include <wchar.h>
             errno_t wmemmove_s(wchar_t *s1, rsize_t s1max,
                  const wchar_t *s2, rsize_t n);
      Runtime-constraints
 

-
-
+
 
20   Neither s1 nor s2 shall be a null pointer. Neither s1max nor n shall be greater than
      RSIZE_MAX. n shall not be greater than s1max.
 

-
-
+
 
21   If there is a runtime-constraint violation, the wmemmove_s function stores zeros in the
      first s1max wide characters of the object pointed to by s1 if s1 is not a null pointer and
      s1max is not greater than RSIZE_MAX.
      Description
 

-
-
+
 
22   The wmemmove_s function copies n successive wide characters from the object pointed
      to by s2 into the object pointed to by s1. This copying takes place as if the n wide
      characters from the object pointed to by s2 are first copied into a temporary array of n
@@ -36374,87 +31335,74 @@ the specified values is outside the normal range, the characters stored are unsp
      wide characters from the temporary array are copied into the object pointed to by s1.
      Returns
 

-
-
+
 
23   The wmemmove_s function returns zero if there was no runtime-constraint violation.
      Otherwise, a nonzero value is returned.
 

-
-
+
 

 
K.3.9.2.2 [Wide string concatenation functions]

-
 Wide string concatenation functions
-

-
-
+
 

 
K.3.9.2.2.1 [The wcscat_s function]

-

-
-
-
1           #define _ _STDC_WANT_LIB_EXT1_ _ 1
+
+
1 Synopsis
+           #define _ _STDC_WANT_LIB_EXT1_ _ 1
             #include <wchar.h>
             errno_t wcscat_s(wchar_t * restrict s1,
                  rsize_t s1max,
                  const wchar_t * restrict s2);
      Runtime-constraints
 

-
-
+
 
2    Let m denote the value s1max - wcsnlen_s(s1, s1max) upon entry to
      wcscat_s.
 

-
-
+
 
3    Neither s1 nor s2 shall be a null pointer. s1max shall not be greater than RSIZE_MAX.
-     s1max shall not equal zero. m shall not equal zero.446) m shall be greater than
+     s1max shall not equal zero. m shall not equal zero.[446] m shall be greater than
      wcsnlen_s(s2, m ). Copying shall not take place between objects that overlap.
 
 

-
 
 
Footnote 446) Zero means that s1 was not null terminated upon entry to wcscat_s.
 

 
-
+
 
4    If there is a runtime-constraint violation, then if s1 is not a null pointer and s1max is
      greater than zero and not greater than RSIZE_MAX, then wcscat_s sets s1[0] to the
      null wide character.
      Description
 

-
-
+
 
5    The wcscat_s function appends a copy of the wide string pointed to by s2 (including
      the terminating null wide character) to the end of the wide string pointed to by s1. The
      initial wide character from s2 overwrites the null wide character at the end of s1.
 

-
-
+
 
6    All elements following the terminating null wide character (if any) written by
      wcscat_s in the array of s1max wide characters pointed to by s1 take unspecified
-     values when wcscat_s returns.447)
+     values when wcscat_s returns.[447]
      Returns
 

-
 
 
Footnote 447) This allows an implementation to append wide characters from s2 to s1 while simultaneously
           checking if any of those wide characters are null. Such an approach might write a wide character to
           every element of s1 before discovering that the first element should be set to the null wide character.
 

 
-
-
7    The wcscat_s function returns zero448) if there was no runtime-constraint violation.
+
+
7    The wcscat_s function returns zero[448] if there was no runtime-constraint violation.
      Otherwise, a nonzero value is returned.
      K.3.9.2.2.2 The wcsncat_s function
      Synopsis
 

-
 
 
Footnote 448) A zero return value implies that all of the requested wide characters from the wide string pointed to by
           s2 were appended to the wide string pointed to by s1 and that the result in s1 is null terminated.
 

 
-
+
 
8             #define _ _STDC_WANT_LIB_EXT1_ _ 1
               #include <wchar.h>
               errno_t wcsncat_s(wchar_t * restrict s1,
@@ -36463,63 +31411,56 @@ the specified values is outside the normal range, the characters stored are unsp
                    rsize_t n);
      Runtime-constraints
 

-
-
+
 
9    Let m denote the value s1max - wcsnlen_s(s1, s1max) upon entry to
      wcsncat_s.
 

-
-
+
 
10   Neither s1 nor s2 shall be a null pointer. Neither s1max nor n shall be greater than
-     RSIZE_MAX. s1max shall not equal zero. m shall not equal zero.449) If n is not less
+     RSIZE_MAX. s1max shall not equal zero. m shall not equal zero.[449] If n is not less
      than m , then m shall be greater than wcsnlen_s(s2, m ). Copying shall not take
      place between objects that overlap.
 
 

-
 
 
Footnote 449) Zero means that s1 was not null terminated upon entry to wcsncat_s.
 

 
-
+
 
11   If there is a runtime-constraint violation, then if s1 is not a null pointer and s1max is
      greater than zero and not greater than RSIZE_MAX, then wcsncat_s sets s1[0] to the
      null wide character.
      Description
 

-
-
+
 
12   The wcsncat_s function appends not more than n successive wide characters (wide
      characters that follow a null wide character are not copied) from the array pointed to by
      s2 to the end of the wide string pointed to by s1. The initial wide character from s2
      overwrites the null wide character at the end of s1. If no null wide character was copied
      from s2, then s1[s1max-m+n] is set to a null wide character.
 

-
-
+
 
13   All elements following the terminating null wide character (if any) written by
      wcsncat_s in the array of s1max wide characters pointed to by s1 take unspecified
-     values when wcsncat_s returns.450)
+     values when wcsncat_s returns.[450]
      Returns
 

-
 
 
Footnote 450) This allows an implementation to append wide characters from s2 to s1 while simultaneously
           checking if any of those wide characters are null. Such an approach might write a wide character to
           every element of s1 before discovering that the first element should be set to the null wide character.
 

 
-
-
14   The wcsncat_s function returns zero451) if there was no runtime-constraint violation.
+
+
14   The wcsncat_s function returns zero[451] if there was no runtime-constraint violation.
      Otherwise, a nonzero value is returned.
 

-
 
 
Footnote 451) A zero return value implies that all of the requested wide characters from the wide string pointed to by
           s2 were appended to the wide string pointed to by s1 and that the result in s1 is null terminated.
 

 
-
+
 
15   EXAMPLE 1 The wcsncat_s function can be used to copy a wide string without the danger that the
      result will not be null terminated or that wide characters will be written past the end of the destination
      array.
@@ -36542,20 +31483,15 @@ the specified values is outside the normal range, the characters stored are unsp
      After the fourth call r4 will have the value zero and s4 will be the wide character sequence abcdef\0.
 
 

-
-
+
 

 
K.3.9.2.3 [Wide string search functions]

-
 Wide string search functions
-

-
-
+
 

 
K.3.9.2.3.1 [The wcstok_s function]

-

-
-
-
1           #define _ _STDC_WANT_LIB_EXT1_ _ 1
+
+
1 Synopsis
+           #define _ _STDC_WANT_LIB_EXT1_ _ 1
             #include <wchar.h>
             wchar_t *wcstok_s(wchar_t * restrict s1,
                  rsize_t * restrict s1max,
@@ -36563,30 +31499,26 @@ the specified values is outside the normal range, the characters stored are unsp
                  wchar_t ** restrict ptr);
     Runtime-constraints
 

-
-
+
 
2   None of s1max, s2, or ptr shall be a null pointer. If s1 is a null pointer, then *ptr
     shall not be a null pointer. The value of *s1max shall not be greater than RSIZE_MAX.
     The end of the token found shall occur within the first *s1max wide characters of s1 for
     the first call, and shall occur within the first *s1max wide characters of where searching
     resumes on subsequent calls.
 

-
-
+
 
3   If there is a runtime-constraint violation, the wcstok_s function does not indirect
     through the s1 or s2 pointers, and does not store a value in the object pointed to by ptr.
     Description
 

-
-
+
 
4   A sequence of calls to the wcstok_s function breaks the wide string pointed to by s1
     into a sequence of tokens, each of which is delimited by a wide character from the wide
     string pointed to by s2. The fourth argument points to a caller-provided wchar_t
     pointer into which the wcstok_s function stores information necessary for it to
     continue scanning the same wide string.
 

-
-
+
 
5   The first call in a sequence has a non-null first argument and s1max points to an object
     whose value is the number of elements in the wide character array pointed to by the first
     argument. The first call stores an initial value in the object pointed to by ptr and
@@ -36596,37 +31528,32 @@ the specified values is outside the normal range, the characters stored are unsp
     previous call in the sequence, which are then updated. The separator wide string pointed
     to by s2 may be different from call to call.
 

-
-
+
 
6   The first call in the sequence searches the wide string pointed to by s1 for the first wide
     character that is not contained in the current separator wide string pointed to by s2. If no
     such wide character is found, then there are no tokens in the wide string pointed to by s1
     and the wcstok_s function returns a null pointer. If such a wide character is found, it is
     the start of the first token.
 

-
-
+
 
7    The wcstok_s function then searches from there for the first wide character in s1 that
      is contained in the current separator wide string. If no such wide character is found, the
      current token extends to the end of the wide string pointed to by s1, and subsequent
      searches in the same wide string for a token return a null pointer. If such a wide character
      is found, it is overwritten by a null wide character, which terminates the current token.
 

-
-
+
 
8    In all cases, the wcstok_s function stores sufficient information in the pointer pointed
      to by ptr so that subsequent calls, with a null pointer for s1 and the unmodified pointer
      value for ptr, shall start searching just past the element overwritten by a null wide
      character (if any).
      Returns
 

-
-
+
 
9    The wcstok_s function returns a pointer to the first wide character of a token, or a null
      pointer if there is no token or there is a runtime-constraint violation.
 

-
-
+
 
10   EXAMPLE
             #define _ _STDC_WANT_LIB_EXT1_ _ 1
             #include <wchar.h>
@@ -36641,104 +31568,82 @@ the specified values is outside the normal range, the characters stored are unsp
             t   =   wcstok_s(NULL,   &max1,   "#,", &ptr1);       //   t   points to the token "c"
             t   =   wcstok_s(NULL,   &max1,   "?", &ptr1);        //   t   is a null pointer
 

-
-
+
 

 
K.3.9.2.4 [Miscellaneous functions]

-
 Miscellaneous functions
-

-
-
+
 

 
K.3.9.2.4.1 [The wcsnlen_s function]

-

-
-
-
1           #define _ _STDC_WANT_LIB_EXT1_ _ 1
+
+
1 Synopsis
+           #define _ _STDC_WANT_LIB_EXT1_ _ 1
             #include <wchar.h>
             size_t wcsnlen_s(const wchar_t *s, size_t maxsize);
      Description
 

-
-
+
 
2    The wcsnlen_s function computes the length of the wide string pointed to by s.
      Returns
 

-
-
-
3    If s is a null pointer,452) then the wcsnlen_s function returns zero.
+
+
3    If s is a null pointer,[452] then the wcsnlen_s function returns zero.
 

-
 
 
Footnote 452) Note that the wcsnlen_s function has no runtime-constraints. This lack of runtime-constraints
          along with the values returned for a null pointer or an unterminated wide string argument make
          wcsnlen_s useful in algorithms that gracefully handle such exceptional data.
 

 
-
+
 
4    Otherwise, the wcsnlen_s function returns the number of wide characters that precede
      the terminating null wide character. If there is no null wide character in the first
      maxsize wide characters of s then wcsnlen_s returns maxsize. At most the first
 
     maxsize wide characters of s shall be accessed by wcsnlen_s.
 

-
-
+
 

 
K.3.9.3 [Extended multibyte/wide character conversion utilities]

-
 Extended multibyte/wide character conversion utilities
-

-
-
+
 

 
K.3.9.3.1 [Restartable multibyte/wide character conversion functions]

-

-
-
+
 
1   Unlike wcrtomb, wcrtomb_s does not permit the ps parameter (the pointer to the
     conversion state) to be a null pointer.
 

-
-
+
 

 
K.3.9.3.1.1 [The wcrtomb_s function]

-

-
-
+
 
1    Synopsis
 

-
-
+
 
2           #include <wchar.h>
             errno_t wcrtomb_s(size_t * restrict retval,
                  char * restrict s, rsize_t smax,
                  wchar_t wc, mbstate_t * restrict ps);
     Runtime-constraints
 

-
-
+
 
3   Neither retval nor ps shall be a null pointer. If s is not a null pointer, then smax
     shall not equal zero and shall not be greater than RSIZE_MAX. If s is not a null pointer,
     then smax shall be not be less than the number of bytes to be stored in the array pointed
     to by s. If s is a null pointer, then smax shall equal zero.
 

-
-
+
 
4   If there is a runtime-constraint violation, then wcrtomb_s does the following. If s is
     not a null pointer and smax is greater than zero and not greater than RSIZE_MAX, then
     wcrtomb_s sets s[0] to the null character. If retval is not a null pointer, then
     wcrtomb_s sets *retval to (size_t)(-1).
     Description
 

-
-
+
 
5   If s is a null pointer, the wcrtomb_s function is equivalent to the call
                     wcrtomb_s(&retval, buf, sizeof buf, L'\0', ps)
     where retval and buf are internal variables of the appropriate types, and the size of
     buf is greater than MB_CUR_MAX.
 

-
-
+
 
6   If s is not a null pointer, the wcrtomb_s function determines the number of bytes
     needed to represent the multibyte character that corresponds to the wide character given
     by wc (including any shift sequences), and stores the multibyte character representation
@@ -36748,8 +31653,7 @@ the specified values is outside the normal range, the characters stored are unsp
     conversion state.
 
 

-
-
+
 
7   If wc does not correspond to a valid multibyte character, an encoding error occurs: the
     wcrtomb_s function stores the value (size_t)(-1) into *retval and the
     conversion state is unspecified. Otherwise, the wcrtomb_s function stores into
@@ -36757,32 +31661,24 @@ the specified values is outside the normal range, the characters stored are unsp
     to by s.
     Returns
 

-
-
+
 
8   The wcrtomb_s function returns zero if no runtime-constraint violation and no
     encoding error occurred. Otherwise, a nonzero value is returned.
 

-
-
+
 

 
K.3.9.3.2 [Restartable multibyte/wide string conversion functions]

-

-
-
+
 
1   Unlike mbsrtowcs and wcsrtombs, mbsrtowcs_s and wcsrtombs_s do not
     permit the ps parameter (the pointer to the conversion state) to be a null pointer.
 

-
-
+
 

 
K.3.9.3.2.1 [The mbsrtowcs_s function]

-

-
-
+
 
1    Synopsis
 

-
-
+
 
2          #include <wchar.h>
            errno_t mbsrtowcs_s(size_t * restrict retval,
                 wchar_t * restrict dst, rsize_t dstmax,
@@ -36790,8 +31686,7 @@ the specified values is outside the normal range, the characters stored are unsp
                 mbstate_t * restrict ps);
     Runtime-constraints
 

-
-
+
 
3   None of retval, src, *src, or ps shall be null pointers. If dst is not a null pointer,
     then neither len nor dstmax shall be greater than RSIZE_MAX. If dst is a null
     pointer, then dstmax shall equal zero. If dst is not a null pointer, then dstmax shall
@@ -36799,16 +31694,14 @@ the specified values is outside the normal range, the characters stored are unsp
     character shall occur within the first dstmax multibyte characters of the array pointed to
     by *src.
 

-
-
+
 
4   If there is a runtime-constraint violation, then mbsrtowcs_s does the following. If
     retval is not a null pointer, then mbsrtowcs_s sets *retval to (size_t)(-1).
     If dst is not a null pointer and dstmax is greater than zero and less than RSIZE_MAX,
     then mbsrtowcs_s sets dst[0] to the null wide character.
     Description
 

-
-
+
 
5   The mbsrtowcs_s function converts a sequence of multibyte characters that begins in
     the conversion state described by the object pointed to by ps, from the array indirectly
     pointed to by src into a sequence of corresponding wide characters. If dst is not a null
@@ -36816,25 +31709,23 @@ the specified values is outside the normal range, the characters stored are unsp
     continues up to and including a terminating null character, which is also stored.
     Conversion stops earlier in two cases: when a sequence of bytes is encountered that does
     not form a valid multibyte character, or (if dst is not a null pointer) when len wide
-     characters have been stored into the array pointed to by dst.453) If dst is not a null
+     characters have been stored into the array pointed to by dst.[453] If dst is not a null
      pointer and no null wide character was stored into the array pointed to by dst, then
      dst[len] is set to the null wide character. Each conversion takes place as if by a call
      to the mbrtowc function.
 

-
 
 
Footnote 453) Thus, the value of len is ignored if dst is a null pointer.
 

 
-
+
 
6    If dst is not a null pointer, the pointer object pointed to by src is assigned either a null
      pointer (if conversion stopped due to reaching a terminating null character) or the address
      just past the last multibyte character converted (if any). If conversion stopped due to
      reaching a terminating null character and if dst is not a null pointer, the resulting state
      described is the initial conversion state.
 

-
-
+
 
7    Regardless of whether dst is or is not a null pointer, if the input conversion encounters a
      sequence of bytes that do not form a valid multibyte character, an encoding error occurs:
      the mbsrtowcs_s function stores the value (size_t)(-1) into *retval and the
@@ -36842,42 +31733,36 @@ the specified values is outside the normal range, the characters stored are unsp
      *retval the number of multibyte characters successfully converted, not including the
      terminating null character (if any).
 

-
-
+
 
8    All elements following the terminating null wide character (if any) written by
      mbsrtowcs_s in the array of dstmax wide characters pointed to by dst take
-     unspecified values when mbsrtowcs_s returns.454)
+     unspecified values when mbsrtowcs_s returns.[454]
 

-
 
 
Footnote 454) This allows an implementation to attempt converting the multibyte string before discovering a
           terminating null character did not occur where required.
+     Runtime-constraints
 

 
-
+
 
9    If copying takes place between objects that overlap, the objects take on unspecified
      values.
      Returns
 

-
-
+
 
10   The mbsrtowcs_s function returns zero if no runtime-constraint violation and no
      encoding error occurred. Otherwise, a nonzero value is returned.
      K.3.9.3.2.2 The wcsrtombs_s function
      Synopsis
 

-
-
+
 
11            #include <wchar.h>
               errno_t wcsrtombs_s(size_t * restrict retval,
                    char * restrict dst, rsize_t dstmax,
                    const wchar_t ** restrict src, rsize_t len,
                    mbstate_t * restrict ps);
-
-     Runtime-constraints
 

-
-
+
 
12   None of retval, src, *src, or ps shall be null pointers. If dst is not a null pointer,
      then neither len nor dstmax shall be greater than RSIZE_MAX. If dst is a null
      pointer, then dstmax shall equal zero. If dst is not a null pointer, then dstmax shall
@@ -36885,16 +31770,14 @@ the specified values is outside the normal range, the characters stored are unsp
      conversion shall have been stopped (see below) because a terminating null wide character
      was reached or because an encoding error occurred.
 

-
-
+
 
13   If there is a runtime-constraint violation, then wcsrtombs_s does the following. If
      retval is not a null pointer, then wcsrtombs_s sets *retval to (size_t)(-1).
      If dst is not a null pointer and dstmax is greater than zero and less than RSIZE_MAX,
      then wcsrtombs_s sets dst[0] to the null character.
      Description
 

-
-
+
 
14   The wcsrtombs_s function converts a sequence of wide characters from the array
      indirectly pointed to by src into a sequence of corresponding multibyte characters that
      begins in the conversion state described by the object pointed to by ps. If dst is not a
@@ -36910,9 +31793,8 @@ the specified values is outside the normal range, the characters stored are unsp
      If the conversion stops without converting a null wide character and dst is not a null
      pointer, then a null character is stored into the array pointed to by dst immediately
      following any multibyte characters already stored. Each conversion takes place as if by a
-     call to the wcrtomb function.455)
+     call to the wcrtomb function.[455]
 

-
 
 
Footnote 455) If conversion stops because a terminating null wide character has been reached, the bytes stored
           include those necessary to reach the initial shift state immediately before the null byte. However, if
@@ -36920,7 +31802,7 @@ the specified values is outside the normal range, the characters stored are unsp
           terminated, but might not end in the initial shift state.
 

 
-
+
 
15   If dst is not a null pointer, the pointer object pointed to by src is assigned either a null
      pointer (if conversion stopped due to reaching a terminating null wide character) or the
      address just past the last wide character converted (if any). If conversion stopped due to
@@ -36928,8 +31810,7 @@ the specified values is outside the normal range, the characters stored are unsp
      conversion state.
 
 

-
-
+
 
16   Regardless of whether dst is or is not a null pointer, if the input conversion encounters a
      wide character that does not correspond to a valid multibyte character, an encoding error
      occurs: the wcsrtombs_s function stores the value (size_t)(-1) into *retval
@@ -36937,233 +31818,119 @@ the specified values is outside the normal range, the characters stored are unsp
      into *retval the number of bytes in the resulting multibyte character sequence, not
      including the terminating null character (if any).
 

-
-
+
 
17   All elements following the terminating null character (if any) written by wcsrtombs_s
      in the array of dstmax elements pointed to by dst take unspecified values when
-     wcsrtombs_s returns.456)
+     wcsrtombs_s returns.[456]
 

-
 
 
Footnote 456) When len is not less than dstmax, the implementation might fill the array before discovering a
           runtime-constraint violation.
+                                                Annex L
+                                               (normative)
 

 
-
+
 
18   If copying takes place between objects that overlap, the objects take on unspecified
      values.
      Returns
 

-
-
+
 
19   The wcsrtombs_s function returns zero if no runtime-constraint violation and no
      encoding error occurred. Otherwise, a nonzero value is returned.
-
-                                                Annex L
-                                               (normative)
 

-
-
+
 

 
L. [Analyzability]

-
 Analyzability
-

-
-
+
 

 
L.1 [Scope]

-

-
-
+
 
1   This annex specifies optional behavior that can aid in the analyzability of C programs.
 

-
-
+
 
2   An implementation that defines _ _STDC_ANALYZABLE_ _ shall conform to the
-    specifications in this annex.457)
+    specifications in this annex.[457]
 

-
 
 
Footnote 457) Implementations that do not define _ _STDC_ANALYZABLE_ _ are not required to conform to these
          specifications.
 

 
-
+
 

 
L.2 [Definitions]

-
 Definitions
-

-
-
+
 

 
L.2.1 [Definitions]

-

-
-
+
 
1   out-of-bounds store
-    an (attempted) access (3.1) that, at run time, for a given computational state, would
+    an (attempted) access (3.1) that, at run time, for a given computational state, would
     modify (or, for an object declared volatile, fetch) one or more bytes that lie outside
     the bounds permitted by this Standard.
 

-
-
+
 

 
L.2.2 [Definitions]

-

-
-
+
 
1   bounded undefined behavior
-    undefined behavior (3.4.3) that does not perform an out-of-bounds store.
+    undefined behavior (3.4.3) that does not perform an out-of-bounds store.
 

-
-
+
 
2   NOTE 1    The behavior might perform a trap.
 
 

-
-
+
 
3   NOTE 2    Any values produced or stored might be indeterminate values.
 
 

-
-
+
 

 
L.2.3 [Definitions]

-

-
-
+
 
1   critical undefined behavior
     undefined behavior that is not bounded undefined behavior.
 

-
-
+
 
2   NOTE     The behavior might perform an out-of-bounds store or perform a trap.
-    457) Implementations that do not define _ _STDC_ANALYZABLE_ _ are not required to conform to these
-         specifications.
 
 

-
-
-
Footnote 457) Implementations that do not define _ _STDC_ANALYZABLE_ _ are not required to conform to these
-         specifications.
-

-
-
+
 

 
L.3 [Requirements]

-

-
-
-
1   If the program performs a trap (3.19.5), the implementation is permitted to invoke a
+
+
1   If the program performs a trap (3.19.5), the implementation is permitted to invoke a
     runtime-constraint handler. Any such semantics are implementation-defined.
 

-
-
+
 
2   All undefined behavior shall be limited to bounded undefined behavior, except for the
     following which are permitted to result in critical undefined behavior:
-    -- An object is referred to outside of its lifetime (6.2.4).
-    -- A store is performed to an object that has two incompatible declarations (6.2.7),
+    -- An object is referred to outside of its lifetime (6.2.4).
+    -- A store is performed to an object that has two incompatible declarations (6.2.7),
     -- A pointer is used to call a function whose type is not compatible with the referenced
-       type (6.2.7, 6.3.2.3, 6.5.2.2).
-    -- An lvalue does not designate an object when evaluated (6.3.2.1).
-    -- The program attempts to modify a string literal (6.4.5).
-    -- The operand of the unary * operator has an invalid value (6.5.3.2).
+       type (6.2.7, 6.3.2.3, 6.5.2.2).
+    -- An lvalue does not designate an object when evaluated (6.3.2.1).
+    -- The program attempts to modify a string literal (6.4.5).
+    -- The operand of the unary * operator has an invalid value (6.5.3.2).
     -- Addition or subtraction of a pointer into, or just beyond, an array object and an
        integer type produces a result that points just beyond the array object and is used as
-       the operand of a unary * operator that is evaluated (6.5.6).
+       the operand of a unary * operator that is evaluated (6.5.6).
     -- An attempt is made to modify an object defined with a const-qualified type through
-       use of an lvalue with non-const-qualified type (6.7.3).
+       use of an lvalue with non-const-qualified type (6.7.3).
     -- An argument to a function or macro defined in the standard library has an invalid
-       value or a type not expected by a function with variable number of arguments (7.1.4).
+       value or a type not expected by a function with variable number of arguments (7.1.4).
     -- The longjmp function is called with a jmp_buf argument where the most recent
        invocation of the setjmp macro in the same invocation of the program with the
        corresponding jmp_buf argument is nonexistent, or the invocation was from another
        thread of execution, or the function containing the invocation has terminated
        execution in the interim, or the invocation was within the scope of an identifier with
-       variably modified type and execution has left that scope in the interim (7.13.2.1).
+       variably modified type and execution has left that scope in the interim (7.13.2.1).
     -- The value of a pointer that refers to space deallocated by a call to the free or realloc
-       function is used (7.22.3).
+       function is used (7.22.3).
     -- A string or wide string utility function accesses an array beyond the end of an object
-       (7.24.1, 7.29.4).
+       (7.24.1, 7.29.4).
 
 

-
-
-

-
BIBLIOGRAPHY. [Bibliography]

-
                                      Bibliography
-        1.   ``The C Reference Manual'' by Dennis M. Ritchie, a version of which was
-             published in The C Programming Language by Brian W. Kernighan and Dennis
-             M. Ritchie, Prentice-Hall, Inc., (1978). Copyright owned by AT&T.
-        2.   1984 /usr/group Standard by the /usr/group Standards Committee, Santa Clara,
-             California, USA, November 1984.
-        3.   ANSI X3/TR-1-82 (1982), American National Dictionary for Information
-             Processing Systems, Information Processing Systems Technical Report.
-        4.   ANSI/IEEE 754-1985, American National Standard for Binary Floating-Point
-             Arithmetic .
-        5.   ANSI/IEEE 854-1988, American National Standard for Radix-Independent
-             Floating-Point Arithmetic .
-        6.   IEC 60559:1989, Binary floating-point arithmetic for microprocessor systems,
-             second edition (previously designated IEC 559:1989).
-        7.   ISO 31-11:1992, Quantities and units -- Part 11: Mathematical signs and
-             symbols for use in the physical sciences and technology .
-        8.   ISO/IEC 646:1991, Information technology -- ISO 7-bit coded character set for
-             information interchange.
-        9.   ISO/IEC 2382-1:1993, Information technology -- Vocabulary -- Part 1:
-             Fundamental terms.
-       10.   ISO 4217:1995, Codes for the representation of currencies and funds.
-       11.   ISO 8601:1988, Data elements and interchange formats -- Information
-             interchange -- Representation of dates and times.
-       12.   ISO/IEC 9899:1990, Programming languages -- C .
-       13.   ISO/IEC 9899/COR1:1994, Technical Corrigendum 1.
-       14.   ISO/IEC 9899/COR2:1996, Technical Corrigendum 2.
-       15.   ISO/IEC 9899/AMD1:1995, Amendment 1 to ISO/IEC 9899:1990 C Integrity .
-       16.   ISO/IEC 9899:1999, Programming languages -- C .
-       17.   ISO/IEC 9899:1999/Cor.1:2001, Technical Corrigendum 1.
-       18.   ISO/IEC 9899:1999/Cor.2:2004, Technical Corrigendum 2.
-       19.   ISO/IEC 9899:1999/Cor.3:2007, Technical Corrigendum 3.
-       20.    ISO/IEC 9945-2:1993, Information technology -- Portable Operating System
-              Interface (POSIX) -- Part 2: Shell and Utilities.
-       21.    ISO/IEC TR 10176:1998, Information technology -- Guidelines for the
-              preparation of programming language standards.
-       22.    ISO/IEC 10646-1:1993, Information technology -- Universal Multiple-Octet
-              Coded Character Set (UCS) -- Part 1: Architecture and Basic Multilingual Plane.
-       23.    ISO/IEC 10646-1/COR1:1996,          Technical       Corrigendum       1      to
-              ISO/IEC 10646-1:1993.
-       24.    ISO/IEC 10646-1/COR2:1998,          Technical       Corrigendum       2      to
-              ISO/IEC 10646-1:1993.
-       25.    ISO/IEC 10646-1/AMD1:1996, Amendment 1 to ISO/IEC 10646-1:1993
-              Transformation Format for 16 planes of group 00 (UTF-16).
-       26.    ISO/IEC 10646-1/AMD2:1996, Amendment 2 to ISO/IEC 10646-1:1993 UCS
-              Transformation Format 8 (UTF-8).
-       27.    ISO/IEC 10646-1/AMD3:1996, Amendment 3 to ISO/IEC 10646-1:1993.
-       28.    ISO/IEC 10646-1/AMD4:1996, Amendment 4 to ISO/IEC 10646-1:1993.
-       29.    ISO/IEC 10646-1/AMD5:1998, Amendment 5 to ISO/IEC 10646-1:1993 Hangul
-              syllables.
-       30.    ISO/IEC 10646-1/AMD6:1997,       Amendment      6   to   ISO/IEC 10646-1:1993
-              Tibetan.
-       31.    ISO/IEC 10646-1/AMD7:1997, Amendment 7 to ISO/IEC 10646-1:1993 33
-              additional characters.
-       32.    ISO/IEC 10646-1/AMD8:1997, Amendment 8 to ISO/IEC 10646-1:1993.
-       33.    ISO/IEC 10646-1/AMD9:1997,       Amendment      9   to   ISO/IEC 10646-1:1993
-              Identifiers for characters.
-       34.    ISO/IEC 10646-1/AMD10:1998, Amendment 10 to ISO/IEC 10646-1:1993
-              Ethiopic .
-       35.    ISO/IEC 10646-1/AMD11:1998, Amendment 11 to ISO/IEC 10646-1:1993
-              Unified Canadian Aboriginal Syllabics.
-       36.    ISO/IEC 10646-1/AMD12:1998, Amendment 12 to ISO/IEC 10646-1:1993
-              Cherokee.
-       37.    ISO/IEC 10967-1:1994, Information technology -- Language independent
-              arithmetic -- Part 1: Integer and floating point arithmetic .
-       38.   ISO/IEC TR 19769:2004, Information technology -- Programming languages,
-             their environments and system software interfaces -- Extensions for the
-             programming language C to support new character data types.
-       39.   ISO/IEC TR 24731-1:2007, Information technology -- Programming languages,
-             their environments and system software interfaces -- Extensions to the C library
-             -- Part 1: Bounds-checking interfaces.
-
-

-