Re: [boost] spirit classic modularization

Subject: Re: [boost] spirit classic modularization
From: Robert Ramey (ramey_at_[hidden])
Date: 2012-05-21 17:20:49

Dave Abrahams wrote:
> While I was in Aspen I split Spirit and Spirit Classic into separate
> Git repositories:
>
>  https://github.com/boost-lib/spirit
>  https://github.com/boost-lib/spirit_classic

I prefer the above even though it would require that I make changes to 
serialization library
to explicitly select spirit_classic.  Right now the selection occurs
under the covers in a way which is not obvious to me.  It does
work which is good.  But still it hides what's going on which
usually comes back to haunt me.

Robert Ramey

>
> The manifest entries begin here, and as you can see, are quite
> long for these two libraries:
>
>  https://github.com/ryppl/boost-modularize/blob/master/manifest.txt#L643
>
> This is mostly due to the limited expressivity of the manifest
> language, but regardless...
>
> The question, for Spirit developers: which arrangement is better?
> Should both spirits go back into a single repository?