Re: [boost] [Proto] Fw:[Spirit-general] Patch for compiling Karma without RTTI

Subject: Re: [boost] [Proto] Fw:[Spirit-general] Patch for compiling Karma without RTTI
From: Hartmut Kaiser (hartmut.kaiser_at_[hidden])
Date: 2010-10-08 07:33:31

> >   0x0.) There's a workaround header for compilers without
> > typeinfo/typeid in boost/detail/sp_typeinfo.hpp. It has a few macros
> > that uses real typeid/typeinfo if it exists, and the workaround if
> > not. The workaround was broken on GCC 4.5.1 and clang (rebuilt daily
> > from upstream trunk). I fixed the problem (static initialization
> > jazz).
> >
> >   0x1.) Spirit's hold_any uses typeinfo/typeid. I changed it to use
> > the aforementioned macros.
> >
> >   0x2.) Some debugging stuff in one proto file used RTTI. I changed it
> > to use the aforementioned macros.
> >
> > I haven't had a need for Qi/Lex yet. I'm currently putting the
> > finishing touches on the ariel driver. My intention is to use Qi for
> > my lightweight command line parsing needs, because it will be less
> > painful than spending half an hour browsing through LLVM doxygen to
> > figure out how their cl parser works. So, there might be another one
> > of these patches in the morning.
> >
> > Patch was generated via svn diff from the top of my local copy of the
> > Boost trunk (on Debian GNU/Linux).
> 
> I suggest sending an email to the Boost mailing list non-spirit related
> patches (and accompanying explanations). We don't have control over those
> parts (e.g. proto and boost/detail/sp_typeinfo.hpp)

I'll apply the Spirit part of the patch. 
Who is maintaining boost/detail/sp_typeinfo.hpp?

Regards Hartmut
---------------
http://boost-spirit.com