mirror of
https://github.com/boostorg/endian.git
synced 2025-07-30 04:27:24 +02:00
Tweak comments.
This commit is contained in:
@ -23,8 +23,8 @@ using namespace boost::endian;
|
||||
|
||||
namespace
|
||||
{
|
||||
// This is an extract from a very widely used GIS file format. Who knows
|
||||
// why a designer would mix big and little endians in the same file? But
|
||||
// This is an extract from a very widely used GIS file format. Why the designer
|
||||
// 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
|
||||
// manipulating these files have to deal with the mixed endianness.
|
||||
|
||||
|
@ -324,6 +324,11 @@ namespace endian
|
||||
// the size and signedness of the desired integer and get the appropriate
|
||||
// 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
|
||||
template <typename T, std::size_t n_bits>
|
||||
class endian_buffer< order::big, T, n_bits, align::no >
|
||||
|
Reference in New Issue
Block a user