Re: [Boost-bugs] [Boost C++ Libraries] #3777: basic_xml_grammar includes deprecated headers

Subject: Re: [Boost-bugs] [Boost C++ Libraries] #3777: basic_xml_grammar includes deprecated headers
From: Boost C++ Libraries (noreply_at_[hidden])
Date: 2009-12-20 18:21:07

#3777: basic_xml_grammar includes deprecated headers
-----------------------------------+----------------------------------------
  Reporter:  patrick@…             |       Owner:  ramey        
      Type:  Feature Requests      |      Status:  closed       
 Milestone:  Boost 1.42.0          |   Component:  serialization
   Version:  Boost 1.41.0          |    Severity:  Problem      
Resolution:  wontfix               |    Keywords:               
-----------------------------------+----------------------------------------

Comment(by patrick@…):

 Replying to [comment:1 ramey]:
 > unfortunately, this makes it impossible to use previous versions of
 spirit.
 >
 > The borland compiler will only work with spirit 1.6x. On the other hand
 the borland compiler can't build the current version of the serialization
 library.  But, I've still had hope that this would one day be fixed.  When
 I pointed this out on on the list I got a huge amount of grief.
 So if the borland compiler gets fixed you'll consider it?  These warnings
 are driving me nuts!  I thought this a good interim fix.  Still using
 exactly what you were using, just going through one less header to get
 there...which brings up the question--it's just because spirit 1.6x
 doesn't have the classic stuff...I suppose I could make the changes
 conditional on the compiler, but that would be ugly, no?  Less ugly if I
 used a using to bring in the classic stuff, but that's why they made the
 classic namespace in the first place--to cut down on the possibility of
 future name collisions between spirit and spirit::classic--but--what about
 a patch like that?  Would you consider it?
 >
 > Long term, a better solution would be to alter xml_grammar to work with
 the latest version of spirit.  Before doing this, one should check that it
 can be used in such a way as to be thread-safe as the current one can.  I
 have no plans to do this myself. (once is more than enough).
 LOL!  Who knows, when I'm between projects maybe I'll take an interest in
 this.
 >
 > So for now - nothing is going to changer here.
 >
 Sadness;)

 Patrick

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