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

Tweak comments.

Browse Source
This commit is contained in:
Beman
2014-12-05 09:05:05 -05:00
parent b6c9150aea
commit db16b51b41
2 changed files with 7 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
example/endian_example.cpp
View File

@@ -23,8 +23,8 @@ using namespace boost::endian;
namespace namespace
{ {
// This is an extract from a very widely used GIS file format. Who knows // This is an extract from a very widely used GIS file format. Why the designer
// why a designer would mix big and little endians in the same file? But // decided to mix big and little endians in the same file is not known. But
// this is a real-world format and users wishing to write low level code // this is a real-world format and users wishing to write low level code
// manipulating these files have to deal with the mixed endianness. // manipulating these files have to deal with the mixed endianness.

5
include/boost/endian/buffers.hpp
View File

@@ -324,6 +324,11 @@ namespace endian
// the size and signedness of the desired integer and get the appropriate // the size and signedness of the desired integer and get the appropriate
// corresponding integer type for the interface. // corresponding integer type for the interface.
// Q: Should endian_buffer supply "value_type operator value_type() const noexcept"?
// A: No. The rationale for endian_buffers is to prevent high-cost hidden
// conversions. If an implicit conversion operator is supplied, hidden conversions
// can occur.
// unaligned big endian_buffer specialization // unaligned big endian_buffer specialization
template <typename T, std::size_t n_bits> template <typename T, std::size_t n_bits>
class endian_buffer< order::big, T, n_bits, align::no > class endian_buffer< order::big, T, n_bits, align::no >