From e2222fbac46edfdcd3e3f7de33d8e515e58bc369 Mon Sep 17 00:00:00 2001 From: nsz Date: Thu, 21 Jul 2011 15:43:13 +0200 Subject: [PATCH] fix and order in section links --- ann2html.sh | 2 +- n1256.html | 1710 ++++++++++++++++++++--------------------- n1548.html | 2116 +++++++++++++++++++++++++-------------------------- 3 files changed, 1914 insertions(+), 1914 deletions(-) diff --git a/ann2html.sh b/ann2html.sh index 3e2e176..ad4413d 100755 --- a/ann2html.sh +++ b/ann2html.sh @@ -93,7 +93,7 @@ seencontents && !seenfore && /^[^@]/ { sect = $2 getline # todo hX, back to top - ss[sid] = sprintf("%s\n", sect, sect, slevel, $0, slevel) + ss[sid] = sprintf("%s\n", slevel, sect, sect, $0, slevel) if ($0 == "Index") ss[sid] = ss[sid] "
\n"
 	next
diff --git a/n1256.html b/n1256.html
index aa9717a..52cdafe 100644
--- a/n1256.html
+++ b/n1256.html
@@ -5,7 +5,7 @@ WG14/N1256                Committee Draft -- Septermber 7, 2007
-

Contents

 +

Contents

-

Foreword

 +

Foreword

ISO (the International Organization for Standardization) and IEC (the International Electrotechnical Commission) form the specialized system for worldwide @@ -476,7 +476,7 @@ WG14/N1256 Committee Draft -- Septermber 7, 2007 also for information only. -

Introduction

+

Introduction

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 @@ -515,7 +515,7 @@ WG14/N1256 Committee Draft -- Septermber 7, 2007 -

1. Scope

+

1. Scope

This International Standard specifies the form and establishes the interpretation of programs written in the C programming language.1) It specifies @@ -552,7 +552,7 @@ WG14/N1256 Committee Draft -- Septermber 7, 2007 data-processing systems. It is intended for use by implementors and programmers. -

2. Normative references

+

2. Normative references

The following normative documents contain provisions which, through reference in this text, constitute provisions of this International Standard. For dated references, @@ -584,7 +584,7 @@ WG14/N1256 Committee Draft -- Septermber 7, 2007 designated IEC 559:1989). -

3. Terms, definitions, and symbols

+

3. Terms, definitions, and symbols

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. @@ -593,7 +593,7 @@ WG14/N1256 Committee Draft -- Septermber 7, 2007 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

+

3.1

access <execution-time action> to read or modify the value of an object @@ -607,13 +607,13 @@ WG14/N1256 Committee Draft -- Septermber 7, 2007 NOTE 3 Expressions that are not evaluated do not access objects. -

3.2

+

3.2

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

+

3.3

argument actual argument @@ -622,12 +622,12 @@ WG14/N1256 Committee Draft -- Septermber 7, 2007 expression, or a sequence of preprocessing tokens in the comma-separated list bounded by the parentheses in a function-like macro invocation -

3.4

+

3.4

behavior external appearance or action -

3.4.1

+

3.4.1

implementation-defined behavior unspecified behavior where each implementation documents how the choice is made @@ -636,7 +636,7 @@ WG14/N1256 Committee Draft -- Septermber 7, 2007 when a signed integer is shifted right. -

3.4.2

+

3.4.2

locale-specific behavior behavior that depends on local conventions of nationality, culture, and language that each @@ -647,7 +647,7 @@ WG14/N1256 Committee Draft -- Septermber 7, 2007 characters other than the 26 lowercase Latin letters. -

3.4.3

+

3.4.3

undefined behavior behavior, upon use of a nonportable or erroneous program construct or of erroneous data, @@ -662,7 +662,7 @@ WG14/N1256 Committee Draft -- Septermber 7, 2007 EXAMPLE An example of undefined behavior is the behavior on integer overflow. -

3.4.4

+

3.4.4

unspecified behavior use of an unspecified value, or other behavior where this International Standard provides @@ -673,7 +673,7 @@ WG14/N1256 Committee Draft -- Septermber 7, 2007 evaluated. -

3.5

+

3.5

bit unit of data storage in the execution environment large enough to hold an object that may @@ -682,7 +682,7 @@ WG14/N1256 Committee Draft -- Septermber 7, 2007 NOTE It need not be possible to express the address of each individual bit of an object. -

3.6

+

3.6

byte addressable unit of data storage large enough to hold any member of the basic character @@ -696,20 +696,20 @@ WG14/N1256 Committee Draft -- Septermber 7, 2007 bit. -

3.7

+

3.7

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

3.7.1

+

3.7.1

character single-byte character <C> bit representation that fits in a byte -

3.7.2

+

3.7.2

multibyte character sequence of one or more bytes representing a member of the extended character set of @@ -718,49 +718,49 @@ WG14/N1256 Committee Draft -- Septermber 7, 2007 NOTE The extended character set is a superset of the basic character set. -

3.7.3

+

3.7.3

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

3.8

+

3.8

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

3.9

+

3.9

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

+

3.10

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

3.11

+

3.11

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

3.12

+

3.12

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

+

3.13

implementation limit restriction imposed upon programs by the implementation -

3.14

+

3.14

object region of data storage in the execution environment, the contents of which can represent @@ -770,7 +770,7 @@ WG14/N1256 Committee Draft -- Septermber 7, 2007 NOTE When referenced, an object may be interpreted as having a particular type; see 6.3.2.1. -

3.15

+

3.15

parameter formal parameter @@ -779,28 +779,28 @@ WG14/N1256 Committee Draft -- Septermber 7, 2007 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

+

3.16

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

+

3.17

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

3.17.1

+

3.17.1

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

3.17.2

+

3.17.2

indeterminate value either an unspecified value or a trap representation -

3.17.3

+

3.17.3

unspecified value valid value of the relevant type where this International Standard imposes no @@ -809,7 +809,7 @@ WG14/N1256 Committee Draft -- Septermber 7, 2007 NOTE An unspecified value cannot be a trap representation. -

3.18

+

3.18

??? x??? ceiling of x: the least integer greater than or equal to x @@ -817,7 +817,7 @@ WG14/N1256 Committee Draft -- Septermber 7, 2007 EXAMPLE ???2.4??? is 3, ???-2.4??? is -2. -

3.19

+

3.19

??? x??? floor of x: the greatest integer less than or equal to x @@ -825,7 +825,7 @@ WG14/N1256 Committee Draft -- Septermber 7, 2007 EXAMPLE ???2.4??? is 2, ???-2.4??? is -3. -

4. Conformance

+

4. Conformance

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 @@ -898,7 +898,7 @@ WG14/N1256 Committee Draft -- Septermber 7, 2007 implementation. -

5. Environment

+

5. Environment

An implementation translates C source files and executes C programs in two data- processing-system environments, which will be called the translation environment and @@ -908,11 +908,11 @@ WG14/N1256 Committee Draft -- Septermber 7, 2007

Forward references: In this clause, only a few of many possible forward references have been noted. -

5.1 Conceptual models

+

5.1 Conceptual models

-

5.1.1 Translation environment

 +

5.1.1 Translation environment

-
5.1.1.1 Program structure
 +
5.1.1.1 Program structure

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 @@ -927,7 +927,7 @@ WG14/N1256 Committee Draft -- Septermber 7, 2007

Forward references: linkages of identifiers (6.2.2), external definitions (6.9), preprocessing directives (6.10). -

5.1.1.2 Translation phases
+
5.1.1.2 Translation phases

The precedence among the syntax rules of translation is specified by the following phases.5) @@ -992,7 +992,7 @@ WG14/N1256 Committee Draft -- Septermber 7, 2007 character. -

5.1.1.3 Diagnostics
+
5.1.1.3 Diagnostics

A conforming implementation shall produce at least one diagnostic message (identified in an implementation-defined manner) if a preprocessing translation unit or translation unit @@ -1014,7 +1014,7 @@ WG14/N1256 Committee Draft -- Septermber 7, 2007 valid program is still correctly translated. It may also successfully translate an invalid program. -

5.1.2 Execution environments

+

5.1.2 Execution environments

Two execution environments are defined: freestanding and hosted. In both cases, program startup occurs when a designated C function is called by the execution @@ -1024,7 +1024,7 @@ WG14/N1256 Committee Draft -- Septermber 7, 2007 environment.

Forward references: storage durations of objects (6.2.4), initialization (6.7.8). -

5.1.2.1 Freestanding environment
+
5.1.2.1 Freestanding environment

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 @@ -1034,7 +1034,7 @@ WG14/N1256 Committee Draft -- Septermber 7, 2007 The effect of program termination in a freestanding environment is implementation- defined. -

5.1.2.2 Hosted environment
+
5.1.2.2 Hosted environment

A hosted environment need not be provided, but shall conform to the following specifications if present. @@ -1044,7 +1044,7 @@ WG14/N1256 Committee Draft -- Septermber 7, 2007 -

5.1.2.2.1 Program startup
+
5.1.2.2.1 Program startup

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 @@ -1084,7 +1084,7 @@ WG14/N1256 Committee Draft -- Septermber 7, 2007 char ** argv, and so on. -

5.1.2.2.2 Program execution
+
5.1.2.2.2 Program execution

In a hosted environment, a program may use all the functions, macros, type definitions, and objects described in the library clause (clause 7). @@ -1093,7 +1093,7 @@ WG14/N1256 Committee Draft -- Septermber 7, 2007 -

5.1.2.2.3 Program termination
+
5.1.2.2.3 Program termination

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 @@ -1107,7 +1107,7 @@ WG14/N1256 Committee Draft -- Septermber 7, 2007 will have ended in the former case, even where they would not have in the latter. -

5.1.2.3 Program execution
+
5.1.2.3 Program execution

The semantic descriptions in this International Standard describe the behavior of an abstract machine in which issues of optimization are irrelevant. @@ -1272,9 +1272,9 @@ WG14/N1256 Committee Draft -- Septermber 7, 2007 effects matter, freeing the implementations in other cases. -

5.2 Environmental considerations

+

5.2 Environmental considerations

-

5.2.1 Character sets

 +

5.2.1 Character sets

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 @@ -1326,7 +1326,7 @@ WG14/N1256 Committee Draft -- Septermber 7, 2007

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
+
5.2.1.1 Trigraph sequences

Before any other processing takes place, each occurrence of one of the following sequences of three characters (called trigraph sequences12)) is replaced with the @@ -1359,7 +1359,7 @@ WG14/N1256 Committee Draft -- Septermber 7, 2007 described in ISO/IEC 646, which is a subset of the seven-bit US ASCII code set. -

5.2.1.2 Multibyte characters
+
5.2.1.2 Multibyte characters

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 @@ -1390,7 +1390,7 @@ WG14/N1256 Committee Draft -- Septermber 7, 2007 of a sequence of valid multibyte characters. -

5.2.2 Character display semantics

+

5.2.2 Character display semantics

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 @@ -1428,7 +1428,7 @@ WG14/N1256 Committee Draft -- Septermber 7, 2007 International Standard.

Forward references: the isprint function (7.4.1.8), the fputc function (7.19.7.3). -

5.2.3 Signals and interrupts

+

5.2.3 Signals and interrupts

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, @@ -1437,14 +1437,14 @@ WG14/N1256 Committee Draft -- Septermber 7, 2007 image (the instructions that compose the executable representation of a function) on a per-invocation basis. -

5.2.4 Environmental limits

+

5.2.4 Environmental limits

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
+
5.2.4.1 Translation limits

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) @@ -1490,14 +1490,14 @@ WG14/N1256 Committee Draft -- Septermber 7, 2007

14) See ''future language directions'' (6.11.3). -

5.2.4.2 Numerical limits
+
5.2.4.2 Numerical limits

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). -

5.2.4.2.1 Sizes of integer types
+
5.2.4.2.1 Sizes of integer types

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 @@ -1561,7 +1561,7 @@ WG14/N1256 Committee Draft -- Septermber 7, 2007

15) See 6.2.5. -

5.2.4.2.2 Characteristics of floating types
+
5.2.4.2.2 Characteristics of floating types

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 @@ -1829,9 +1829,9 @@ WG14/N1256 Committee Draft -- Septermber 7, 2007 limits are one less than shown here. -

6. Language

+

6. Language

-

6.1 Notation

 +

6.1 Notation

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 @@ -1847,9 +1847,9 @@ WG14/N1256 Committee Draft -- Septermber 7, 2007

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

6.2 Concepts

+

6.2 Concepts

-

6.2.1 Scopes of identifiers

 +

6.2.1 Scopes of identifiers

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 @@ -1901,7 +1901,7 @@ WG14/N1256 Committee Draft -- Septermber 7, 2007 (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

+

6.2.2 Linkages of identifiers

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 @@ -1949,7 +1949,7 @@ WG14/N1256 Committee Draft -- Septermber 7, 2007

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

6.2.3 Name spaces of identifiers

+

6.2.3 Name spaces of identifiers

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. @@ -1977,7 +1977,7 @@ WG14/N1256 Committee Draft -- Septermber 7, 2007

24) There is only one name space for tags even though three are possible. -

6.2.4 Storage durations of objects

+

6.2.4 Storage durations of objects

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. @@ -2028,7 +2028,7 @@ WG14/N1256 Committee Draft -- Septermber 7, 2007 embedded block prior to the declaration, leaves the scope of the declaration. -

6.2.5 Types

+

6.2.5 Types

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 @@ -2245,9 +2245,9 @@ WG14/N1256 Committee Draft -- Septermber 7, 2007 arguments to functions, return values from functions, and members of unions. -

6.2.6 Representations of types

+

6.2.6 Representations of types

-
6.2.6.1 General
 +
6.2.6.1 General

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

@@ -2317,7 +2317,7 @@ WG14/N1256 Committee Draft -- Septermber 7, 2007 on values of type T may distinguish between them. -

6.2.6.2 Integer types
+
6.2.6.2 Integer types

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 @@ -2387,7 +2387,7 @@ WG14/N1256 Committee Draft -- Septermber 7, 2007 bits. -

6.2.7 Compatible type and composite type

+

6.2.7 Compatible type and composite type

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, @@ -2444,7 +2444,7 @@ WG14/N1256 Committee Draft -- Septermber 7, 2007

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

6.3 Conversions

+

6.3 Conversions

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 @@ -2456,9 +2456,9 @@ WG14/N1256 Committee Draft -- Septermber 7, 2007 representation.

Forward references: cast operators (6.5.4). -

6.3.1 Arithmetic operands

+

6.3.1 Arithmetic operands

-
6.3.1.1 Boolean, characters, and integers
 +
6.3.1.1 Boolean, characters, and integers

Every integer type has an integer conversion rank defined as follows:

-

Annex D

 +

Annex D

                                      (normative)
@@ -20811,7 +20811,7 @@ WG14/N1256                Committee Draft -- Septermber 7, 2007
                     2107, 210A-2113, 2115, 2118-211D, 2124, 2126, 2128, 212A-2131,
                     2133-2138, 2160-2182, 3005-3007, 3021-3029
-

Annex E

 +

Annex E

                                     (informative)
@@ -20896,12 +20896,12 @@ WG14/N1256                Committee Draft -- Septermber 7, 2007
         #define    LDBL_EPSILON                               1E-9
         #define    LDBL_MIN                                  1E-37
-

Annex F

 +

Annex F

                                            (normative)
                        IEC 60559 floating-point arithmetic
-

F.1 Introduction

 +

F.1 Introduction

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 @@ -20915,7 +20915,7 @@ WG14/N1256 Committee Draft -- Septermber 7, 2007 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

+

F.2 Types

The C floating types match the IEC 60559 formats as follows:

-

F.4 Floating to integer conversion

 +

F.4 Floating to integer conversion

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 @@ -21048,7 +21048,7 @@ WG14/N1256 Committee Draft -- Septermber 7, 2007 <math.h>. -

F.5 Binary-decimal conversion

+

F.5 Binary-decimal conversion

Conversion from the widest supported IEC 60559 format to decimal with DECIMAL_DIG digits and back is the identity function.311) @@ -21076,7 +21076,7 @@ WG14/N1256 Committee Draft -- Septermber 7, 2007 DBL_DIG are 18 and 15, respectively, for these formats.) -

F.6 Contracted expressions

+

F.6 Contracted expressions

A contracted expression treats infinities, NaNs, signed zeros, subnormals, and the rounding directions in a manner consistent with the basic arithmetic operations covered @@ -21087,7 +21087,7 @@ WG14/N1256 Committee Draft -- Septermber 7, 2007 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

+

F.7 Floating-point environment

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 @@ -21098,7 +21098,7 @@ WG14/N1256 Committee Draft -- Septermber 7, 2007

312) This specification does not require dynamic rounding precision nor trap enablement modes. -

F.7.1 Environment management

+

F.7.1 Environment management

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 @@ -21112,7 +21112,7 @@ WG14/N1256 Committee Draft -- Septermber 7, 2007 which allows certain optimizations (see F.8). -

F.7.2 Translation

+

F.7.2 Translation

During translation the IEC 60559 default modes are in effect:

-

F.7.4 Constant expressions

 +

F.7.4 Constant expressions

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 @@ -21189,7 +21189,7 @@ WG14/N1256 Committee Draft -- Septermber 7, 2007 const static double one_third = 1.0/3.0; -

F.7.5 Initialization

+

F.7.5 Initialization

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 @@ -21235,7 +21235,7 @@ WG14/N1256 Committee Draft -- Septermber 7, 2007 could be done at translation time, regardless of the expression evaluation method. -

F.7.6 Changing the environment

+

F.7.6 Changing the environment

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 @@ -21247,12 +21247,12 @@ WG14/N1256 Committee Draft -- Septermber 7, 2007 ''inexact'', or ''underflow'' and ''inexact''), then ''overflow'' or ''underflow'' is raised before ''inexact''. -

F.8 Optimization

+

F.8 Optimization

This section identifies code transformations that might subvert IEC 60559-specified behavior, and others that do not. -

F.8.1 Global transformations

+

F.8.1 Global transformations

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 @@ -21285,7 +21285,7 @@ WG14/N1256 Committee Draft -- Septermber 7, 2007 

          if (0 < n) x + 1;
-

F.8.2 Expression transformations

 +

F.8.2 Expression transformations

x / 2 <-> x * 0.5 Although similar transformations involving inexact 

@@ -21348,7 +21348,7 @@ WG14/N1256                Committee Draft -- Septermber 7, 2007
  for complex z.
 
 
-
F.8.3 Relational operators

+
F.8.3 Relational operators

 

  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.
@@ -21401,7 +21401,7 @@ WG14/N1256                Committee Draft -- Septermber 7, 2007
                 f();
-

F.8.4 Constant arithmetic

 +

F.8.4 Constant arithmetic

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 @@ -21416,7 +21416,7 @@ WG14/N1256 Committee Draft -- Septermber 7, 2007

319) 0 - 0 yields -0 instead of +0 just when the rounding direction is downward. -

F.9 Mathematics

+

F.9 Mathematics

This subclause contains specifications of <math.h> facilities that are particularly suited for IEC 60559 implementations. @@ -21479,9 +21479,9 @@ WG14/N1256 Committee Draft -- Septermber 7, 2007 avoiding them would be too costly. -

F.9.1 Trigonometric functions

+

F.9.1 Trigonometric functions

-
F.9.1.1 The acos functions
 +
F.9.1.1 The acos functions

-
F.9.1.2 The asin functions
 +
F.9.1.2 The asin functions

-
F.9.1.3 The atan functions
 +
F.9.1.3 The atan functions

-
F.9.1.4 The atan2 functions
 +
F.9.1.4 The atan2 functions