Re: [Boost-bugs] [Boost C++ Libraries] #2771: Serialization documentation should make portability issues more obvious

Subject: Re: [Boost-bugs] [Boost C++ Libraries] #2771: Serialization documentation should make portability issues more obvious
From: Boost C++ Libraries (noreply_at_[hidden])
Date: 2009-02-19 16:40:27

#2771: Serialization documentation should make portability issues more obvious
-----------------------------------+----------------------------------------
  Reporter:  boost_at_[hidden]  |       Owner:  ramey         
      Type:  Bugs                  |      Status:  closed        
 Milestone:  Boost 1.39.0          |   Component:  serialization 
   Version:  Boost 1.37.0          |    Severity:  Not Applicable
Resolution:  fixed                 |    Keywords:                
-----------------------------------+----------------------------------------

Comment(by boost_at_[hidden]):

 Robert,

 I don't know how you can say for certain that it is portable. There is no
 reference to any standardese in the code.

 I agree, BOOST_CLASS_EXPORT is not portable. But if BOOST_CLASS_EXPORT is
 not portable, then the portability of the singleton almost doesn't matter!

 I will happily send you my tips and tricks. I have a bunch.

 By the way, if you are interested in the macro I wrote which roughly
 guarantees a function will be called before main, let me know. It falls
 back to the singleton above if the macro is not specialized for the
 current platform/compiler. It would raise the abstraction level, imo.

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