Location via proxy:   [ UP ]  
[Report a bug]   [Manage cookies]                
Skip to content

Commit 926fbf9

Browse files
jensmaurertkoeppe
authored andcommitted
[expr] Replace 'could' and 'might'
as directed by ISO/CS.
1 parent fe22f09 commit 926fbf9

File tree

1 file changed

+9
-9
lines changed

1 file changed

+9
-9
lines changed

source/expressions.tex

Lines changed: 9 additions & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -114,7 +114,7 @@
114114
\begin{codeblock}
115115
a = (a + (b + 32765));
116116
\end{codeblock}
117-
since the values for \tcode{a} and \tcode{b} might have been,
117+
since the values for \tcode{a} and \tcode{b} can be,
118118
respectively, 4 and $-8$ or $-17$ and 12. However on a machine in which
119119
overflows do not produce an exception and in which the results of
120120
overflows are reversible, the above expression statement can be
@@ -173,7 +173,7 @@
173173
\pnum
174174
\begin{note}
175175
Historically, lvalues and rvalues were so-called
176-
because they could appear on the left- and right-hand side of an assignment
176+
because they appeared on the left- and right-hand side of an assignment
177177
(although this is no longer generally true);
178178
glvalues are ``generalized'' lvalues,
179179
prvalues are ``pure'' rvalues,
@@ -262,7 +262,7 @@
262262
\begin{note}
263263
There are no prvalue bit-fields; if a bit-field is converted to a
264264
prvalue\iref{conv.lval}, a prvalue of the type of the bit-field is
265-
created, which might then be promoted\iref{conv.prom}.
265+
created, which can then be promoted\iref{conv.prom}.
266266
\end{note}
267267

268268
\pnum
@@ -787,10 +787,10 @@
787787
can be converted to type \tcode{T2}
788788
if the qualification-combined type of \tcode{T1} and \tcode{T2} is \tcode{T2}.
789789
\begin{note}
790-
If a program could assign a pointer of type \tcode{T**} to a pointer of
790+
If a program were able to assign a pointer of type \tcode{T**} to a pointer of
791791
type \keyword{const} \tcode{T**} (that is, if line \#1 below were
792-
allowed), a program could inadvertently modify a const object
793-
(as it is done on line \#2). For example,
792+
allowed), it would be possible for a const object to be inadvertently modified
793+
(as is done on line \#2). For example,
794794
\begin{codeblock}
795795
int main() {
796796
const char c = 'c';
@@ -4197,7 +4197,7 @@
41974197

41984198
\pnum
41994199
\begin{note}
4200-
The mapping performed by \keyword{reinterpret_cast} might, or might not, produce a
4200+
The mapping performed by \keyword{reinterpret_cast} can produce a
42014201
representation different from the original value.
42024202
\end{note}
42034203

@@ -6922,8 +6922,8 @@
69226922
and the converted operand is used in place of the original operand for
69236923
the remainder of this subclause.
69246924
\begin{note}
6925-
The conversion might be ill-formed even if an implicit conversion
6926-
sequence could be formed.
6925+
It is possible for the conversion to be ill-formed even if an implicit conversion
6926+
sequence can be formed.
69276927
\end{note}
69286928

69296929
\pnum

0 commit comments

Comments
 (0)