Re: [Boost-bugs] [Boost C++ Libraries] #2114: Patch for export symbols from shared library

Subject: Re: [Boost-bugs] [Boost C++ Libraries] #2114: Patch for export symbols from shared library
From: Boost C++ Libraries (noreply_at_[hidden])
Date: 2009-08-07 08:50:40

#2114: Patch for export symbols from shared library
----------------------------------------------------------------------------------+
 Reporter:  arhip                                                                 |       Owner:  johnmaddock
     Type:  Patches                                                               |      Status:  new        
Milestone:  To Be Determined                                                      |   Component:  config     
  Version:  Boost Development Trunk                                               |    Severity:  Cosmetic   
 Keywords:  symbol export shared library gcc exception dynamic shared object dso  |  
----------------------------------------------------------------------------------+

Comment(by arhipjan@…):

 Replying to [comment:13 johnmaddock]:
 > Is this nearly ready to go in Trunk now?
 >
 > Before it does at the very least we need:
 >
 >[snip]
 >Also do we need to re-export std lib exceptions from our SO's?  Do we
 have a dependency analysis to know when we need to use these (or that we
 don't need to)?
 >
 > John.

 JFYI, stdcxx library (at least of version 4.1.1 and later) [[BR]]
 already have default visibility for std::exception, std::bad_exception,
 i.e:
 {{{
 //exception header

 #pragma GCC visibility push(default)

 namespace std {

    class exception {/*...*/};
    class bad_exception {/*...*/};

 //...
 }}}
 Also logic_error, runtime_error don't cause abnormal program
 termination[[BR]]
 since they have key functions [[BR]]
 (i.e. at least one non-inline virtual function).

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