Skip to content

Commit 6b9a4bf

Browse files
committed
Add hyphens to "Floating Point"
1 parent 1231163 commit 6b9a4bf

File tree

1 file changed

+17
-17
lines changed

1 file changed

+17
-17
lines changed

spec/float.dd

Lines changed: 17 additions & 17 deletions
Original file line numberDiff line numberDiff line change
@@ -1,10 +1,10 @@
11
Ddoc
22

3-
$(SPEC_S Floating Point,
3+
$(SPEC_S Floating-Point,
44

55
$(HEADERNAV_TOC)
66

7-
$(H2 $(LNAME2 fp_intermediate_values, Floating Point Intermediate Values))
7+
$(H2 $(LNAME2 fp_intermediate_values, Floating-Point Intermediate Values))
88

99
$(P On many computers, greater
1010
precision operations do not take any longer than lesser
@@ -15,7 +15,7 @@ $(H2 $(LNAME2 fp_intermediate_values, Floating Point Intermediate Values))
1515
of the best capabilities of target hardware.
1616
)
1717

18-
$(P For floating point operations and expression intermediate values,
18+
$(P For floating-point operations and expression intermediate values,
1919
a greater precision can be used than the type of the
2020
expression.
2121
Only the minimum precision is set by the types of the
@@ -43,14 +43,14 @@ $(H2 $(LNAME2 fp_intermediate_values, Floating Point Intermediate Values))
4343
$(LI data and function argument compatibility with C)
4444
)
4545

46-
$(H2 $(LNAME2 fp_const_folding, Floating Point Constant Folding))
46+
$(H2 $(LNAME2 fp_const_folding, Floating-Point Constant Folding))
4747

48-
$(P Regardless of the type of the operands, floating point
48+
$(P Regardless of the type of the operands, floating-point
4949
constant folding is done in $(D real) or greater precision.
5050
It is always done following IEEE 754 rules and round-to-nearest
5151
is used.)
5252

53-
$(P Floating point constants are internally represented in
53+
$(P Floating-point constants are internally represented in
5454
the implementation in at least $(D real) precision, regardless
5555
of the constant's type. The extra precision is available for
5656
constant folding. Committing to the precision of the result is
@@ -67,8 +67,8 @@ writeln(f - 0.2);
6767
static float f = 0.2f;
6868
writeln(f - 0.2);
6969
---
70-
$(P will print 2.98023e-09. Hex floating point constants can also
71-
be used when specific floating point bit patterns are needed that
70+
$(P will print 2.98023e-09. Hex floating-point constants can also
71+
be used when specific floating-point bit patterns are needed that
7272
are unaffected by rounding. To find the hex value of 0.2f:)
7373

7474
---
@@ -90,12 +90,12 @@ writeln(f - 0.2);
9090

9191
$(P Different compiler settings, optimization settings,
9292
and inlining settings can affect opportunities for constant
93-
folding, therefore the results of floating point calculations may differ
93+
folding, therefore the results of floating-point calculations may differ
9494
depending on those settings.)
9595

9696
$(H2 $(LNAME2 rounding_control, Rounding Control))
9797

98-
$(P IEEE 754 floating point arithmetic includes the ability to set 4
98+
$(P IEEE 754 floating-point arithmetic includes the ability to set 4
9999
different rounding modes.
100100
These are accessible via the functions in $(D core.stdc.fenv).
101101
)
@@ -109,7 +109,7 @@ $(H2 $(LNAME2 rounding_control, Rounding Control))
109109

110110
$(H2 $(LNAME2 esception_flags, Exception Flags))
111111

112-
$(P IEEE 754 floating point arithmetic can set several flags based on what
112+
$(P IEEE 754 floating-point arithmetic can set several flags based on what
113113
happened with a
114114
computation:)
115115

@@ -124,22 +124,22 @@ $(H2 $(LNAME2 esception_flags, Exception Flags))
124124

125125
$(P These flags can be set/reset via the functions in $(D core.stdc.fenv).)
126126

127-
$(H2 $(LNAME2 floating-point-transformations, Floating Point Transformations))
127+
$(H2 $(LNAME2 floating-point-transformations, Floating-Point Transformations))
128128

129129
$(P An implementation may perform transformations on
130-
floating point computations in order to reduce their strength,
130+
floating-point computations in order to reduce their strength,
131131
i.e. their runtime computation time.
132-
Because floating point math does not precisely follow mathematical
132+
Because floating-point math does not precisely follow mathematical
133133
rules, some transformations are not valid, even though some
134134
other programming languages still allow them.
135135
)
136136

137-
$(P The following transformations of floating point expressions
137+
$(P The following transformations of floating-point expressions
138138
are not allowed because under IEEE rules they could produce
139139
different results.
140140
)
141141

142-
$(TABLE2 Disallowed Floating Point Transformations,
142+
$(TABLE2 Disallowed Floating-Point Transformations,
143143
$(THEAD transformation, comments)
144144
$(TROW
145145
$(ARGS $(I x) + 0 $(RARR) $(I x)) , $(ARGS not valid if $(I x) is -0)
@@ -186,4 +186,4 @@ $(SPEC_SUBNAV_PREV_NEXT garbage, Garbage Collection, iasm, D x86 Inline Assemble
186186

187187
Macros:
188188
CHAPTER=29
189-
TITLE=Floating Point
189+
TITLE=Floating-Point

0 commit comments

Comments
 (0)