Re: [boost] [boost::endian] Request for comments/interest (floatingpoint endian handling)

Subject: Re: [boost] [boost::endian] Request for comments/interest (floatingpoint endian handling)
From: vicente.botet (vicente.botet_at_[hidden])
Date: 2010-05-27 16:41:29

----- Original Message ----- 
From: "Cliff Green" <cliffg_at_[hidden]>
To: <boost_at_[hidden]>
Sent: Thursday, May 27, 2010 8:43 PM
Subject: Re: [boost] [boost::endian] Request for comments/interest (floatingpoint endian handling)

> 
> For generic endian conversions, keep in mind the restrictions for floating 
> point types (and other types with similar properties). It might be 
> worthwhile putting in an "is_integral" check in the generic function 
> implementations.
> 
...
> I can't remember if Beman's endian facilities addressed floating point 
> swapping, but any accepted Boost endian facility needs to address 
> non-integral types in some form or fashion (either by restricting, or 
> properly implementing).
> 
> I faintly remember some discussions on this subject in the Serialization 
> portable binary archive, or maybe in the Math floating point utilities, but 
> a quick glance at 1.43 documentation doesn't provide specific code for 
> endianness handling in either library (I may have missed it).

Beman's endian library restricts to interger types.

Vicente