boostorg/optional
1
0
Fork 1
mirror of https://github.com/boostorg/optional.git synced 2025-07-21 08:12:08 +02:00
Code Issues Packages Projects Releases Wiki Activity

Fixed typos.

Browse Source 
[SVN r17631]
This commit is contained in:
Thomas Witt
2003-02-25 10:29:21 +00:00
parent 741a64d96e
commit 93412ead09
1 changed files with 2 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
doc/optional.html
View File

@ -223,7 +223,7 @@ them. The problem resides in the shallow-copy of pointer semantics: if you need
a builtin or small POD, this technique is very poor in terms of required resources.
Optional objects are essentially values so it is very convenient to be able to use automatic
storage and deep-copy semantics to manipulate optional values just as we do with ordinary
values. Pointers do not have this semantics, so are unapprorpiate for the initialization and
values. Pointers do not have this semantics, so are unappropriate for the initialization and
transport of optional values, yet are quite convenient for handling the access to the
possible undefined value because of the idiomatic aid present in the OptionalPointee
concept incarnated by pointers. <br>
@ -805,7 +805,7 @@ class Fred
<HR>
<H2><A NAME="bool">A note about optional&lt;bool&gt;</A></H2>
<p><code>optional&ltbool&gt</code> should be used with special caution and consideration.</p>
<p><code>optional&lt;bool&gt;</code> should be used with special caution and consideration.</p>
<p>First, it is functionally similar to a tristate boolean (false,maybe,true)
-such as <u>boost::tribool</u> (not yet formally in boost)-,
except that in a tristate boolean, the <i>maybe</i> state