Re: [Boost-bugs] [Boost C++ Libraries] #7301: Inconsistent use of load_/save_override for serialized file signature

Subject: Re: [Boost-bugs] [Boost C++ Libraries] #7301: Inconsistent use of load_/save_override for serialized file signature
From: Boost C++ Libraries (noreply_at_[hidden])
Date: 2012-08-29 16:43:43


#7301: Inconsistent use of load_/save_override for serialized file signature
-----------------------------------------------------+----------------------
  Reporter: Paul Barba <paul.barba@…> | Owner: ramey
      Type: Bugs | Status: assigned
 Milestone: To Be Determined | Component: serialization
   Version: Boost 1.51.0 | Severity: Problem
Resolution: | Keywords: serialization, save_override, file signature
-----------------------------------------------------+----------------------

Comment (by Paul Barba <paul.barba@…>):

 To add context, I went back and looked to see why a former colleague had
 overridden save_string() to begin with: Basically he switched the size_t
 for an unsigned int to induce x32/x64 compatibility into the binaries (the
 wisdom and correctness of such an operation being lengthy and off-topic.)
 In that sense supporting the load_override is preferable in that you
 retain the option of writing more portable string functions. However,
 since the goal of the binary archives is explicitly not 32/64 bit
 portability, it doesn't strike me as critical that that be supported here,
 only that the overrides be consistently used or ignored. Thus the first
 option is nicer in that judicious overrides can be used to overcome
 portability restraints, but I suspect there's a reason I don't know about
 that it's not done that way.

-- 
Ticket URL: <https://svn.boost.org/trac/boost/ticket/7301#comment:4>
Boost C++ Libraries <http://www.boost.org/>
Boost provides free peer-reviewed portable C++ source libraries.

This archive was generated by hypermail 2.1.7 : 2017-02-16 18:50:10 UTC