Re: [Boost-bugs] [Boost C++ Libraries] #1917: Boost.Signals crashes on MSVC9.0 with _HAS_ITERATOR_DEBUGGING=0

Subject: Re: [Boost-bugs] [Boost C++ Libraries] #1917: Boost.Signals crashes on MSVC9.0 with _HAS_ITERATOR_DEBUGGING=0
From: Boost C++ Libraries (noreply_at_[hidden])
Date: 2008-05-16 11:42:24

#1917: Boost.Signals crashes on MSVC9.0 with _HAS_ITERATOR_DEBUGGING=0
----------------------------+-----------------------------------------------
  Reporter:  ntr_at_[hidden]  |       Owner:  dgregor                                      
      Type:  Bugs           |      Status:  new                                          
 Milestone:  Boost 1.35.1   |   Component:  signals                                      
   Version:  Boost 1.35.0   |    Severity:  Problem                                      
Resolution:                 |    Keywords:  Boost.Signals MSVC9.0 _HAS_ITERATOR_DEBUGGING
----------------------------+-----------------------------------------------
Comment (by ntr_at_[hidden]):

 It seems this is related to the compilation of boost compared to
 application being compiled see:

 http://lists.boost.org/Archives/boost/2006/06/106314.php


 So yet another reason for header only libraries being preferred.

 Since this is probably not happening how can this be resolved with regard
 to compiling the boost libraries? Shouldn't the autolinkage model and
 library names be made to reflect this issue. I.e. there needs to be made
 another library name flag designated whether boost was build with either
 of the two definitions.

 Note I have not tested this yet, but it seems to be the problem.

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