forked from boostorg/optional
Fix couple of typos
[SVN r19623]
This commit is contained in:
@ -240,7 +240,7 @@ them. The problem resides in the shallow-copy of pointer semantics: if you need
|
|||||||
However, it is particularly important that optional<> objects are not mistaken by pointers,
|
However, it is particularly important that optional<> objects are not mistaken by pointers,
|
||||||
they are not. <u><b>optional<> does not model a pointer</b></u>.
|
they are not. <u><b>optional<> does not model a pointer</b></u>.
|
||||||
For instance, optional<> has not shallow-copy so does not alias: two different optionals
|
For instance, optional<> has not shallow-copy so does not alias: two different optionals
|
||||||
never refer to the <i>same</i> value (but my have <i>equivalent</i> values).<br>
|
never refer to the <i>same</i> value (but may have <i>equivalent</i> values).<br>
|
||||||
The difference between an optional<T> and a pointer must be kept in mind, particularly
|
The difference between an optional<T> and a pointer must be kept in mind, particularly
|
||||||
because the semantics of relational operators are different: since optional<T>
|
because the semantics of relational operators are different: since optional<T>
|
||||||
is a value-wrapper, relational operators are deep: they compare optional values;
|
is a value-wrapper, relational operators are deep: they compare optional values;
|
||||||
@ -818,7 +818,7 @@ Using optional<bool> can lead to subtle errors due to the implicit bool co
|
|||||||
void foo ( bool v ) ;
|
void foo ( bool v ) ;
|
||||||
void bar()
|
void bar()
|
||||||
{
|
{
|
||||||
optional<bool> v = try();
|
optional<bool> v = Try();
|
||||||
|
|
||||||
// The following intended to pass the <b>value</b> of 'v' to foo():
|
// The following intended to pass the <b>value</b> of 'v' to foo():
|
||||||
foo(v);
|
foo(v);
|
||||||
|
Reference in New Issue
Block a user