Re: [Boost-bugs] [Boost C++ Libraries] #1732: Require clarification on boost::serialization::singleton

Subject: Re: [Boost-bugs] [Boost C++ Libraries] #1732: Require clarification on boost::serialization::singleton
From: Boost C++ Libraries (noreply_at_[hidden])
Date: 2008-03-31 15:55:30


#1732: Require clarification on boost::serialization::singleton
--------------------------------------------------------+-------------------
  Reporter: Sohail Somani <boost-trac_at_[hidden]> | Owner: ramey
      Type: Support Requests | Status: closed
 Milestone: To Be Determined | Component: serialization
   Version: Boost Development Trunk | Severity: Not Applicable
Resolution: fixed | Keywords:
--------------------------------------------------------+-------------------
Changes (by ramey):

  * status: new => closed
  * resolution: => fixed

Comment:

 We have found no standards conforming way to guarentee instantiation of
 code not explicitly refered to. Implementation of BOOST_CLASS_EXPORT
 requires this facility. Hence, implementation of BOOST_CLASS_EXPORT not
 guarenteed portable.

 However, we have been able to implement it on most widely used compilers.
 Typically this involves "exporting" for access by a DLL so that the
 compiler won't throw it away even though it's never explicitly referred
 to.

 Of course, each compiler is different so its possible that moving this
 code from one compiler to another will require some sort of enhance to
 make it work. The current method factors this problem into one place -
 boost::serialization::singleton - whereas before it was sprinkled all over
 the place

 Robert Ramey

--
Ticket URL: <http://svn.boost.org/trac/boost/ticket/1732#comment:2>
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:49:57 UTC