feedc0de/boost_endian
1
0
Fork 0
forked from boostorg/endian
Code Pull Requests Activity

Fix typos in documentation

Browse Source 
Found and fixed while reading documentation
This commit is contained in:
Ben Wiederhake
2016-04-03 19:00:59 +02:00
parent 1b0a41e6cb
commit d1865063ad
2 changed files with 2 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
doc/index.html
View File

@ -458,7 +458,7 @@ performing a lot of arithmetic operations on the endian arithmetic types.</p>
<p><b>What is gained by using the buffer types rather than always just using the <p><b>What is gained by using the buffer types rather than always just using the
arithmetic types?</b></p> arithmetic types?</b></p>
<blockquote> <blockquote>
<p>Assurance than hidden conversions are not performed. This is of overriding <p>Assurance that hidden conversions are not performed. This is of overriding
importance to users concerned about achieving the ultimate in terms of speed. </p> importance to users concerned about achieving the ultimate in terms of speed. </p>
<p>&quot;Always just using the arithmetic types&quot; is fine for other users. When the <p>&quot;Always just using the arithmetic types&quot; is fine for other users. When the
ultimate in speed needs to be ensured, the arithmetic types can be used in the ultimate in speed needs to be ensured, the arithmetic types can be used in the

2
include/boost/endian/conversion.hpp
View File

@ -50,7 +50,7 @@ namespace endian
//--------------------------------------------------------------------------------------// //--------------------------------------------------------------------------------------//
// customization for exact-length arithmetic types. See doc/conversion.html/#FAQ. // customization for exact-length arithmetic types. See doc/conversion.html/#FAQ.
// Note: The omission of an overloads for the arithmetic type (typically long, or // Note: The omission of a overloads for the arithmetic type (typically long, or
// long long) not assigned to one of the exact length typedefs is a deliberate // long long) not assigned to one of the exact length typedefs is a deliberate
// design decision. Such overloads would be non-portable and thus error prone. // design decision. Such overloads would be non-portable and thus error prone.