Re: [boost] [modularization] spirtit -> serialization

Subject: Re: [boost] [modularization] spirtit -> serialization
From: Andrey Semashev (andrey.semashev_at_[hidden])
Date: 2014-06-15 06:48:22

On Sunday 15 June 2014 12:13:08 Vicente J. Botet Escriba wrote:
> Le 14/06/14 18:34, Stephen Kelly a écrit :
> > Vicente J. Botet Escriba wrote:
> >>> Here is a graph which assumes the range->algorithm edge removal and
> >>> treats math<->lexical_cast as an incidental module:
> >>> 
> >>> http://www.steveire.com/boost/2014_jun_before-spirit-serialization.png
> >>> 
> >>> And after removing the serialization->spirit edge:
> >>> 
> >>> http://www.steveire.com/boost/2014_jun_after-spirit-serialization.png
> >> 
> >> I don't think the serialization -> spirit dependency must be removed
> >> forcedly. As I said in another post the opposite seems unuseful as the
> >> file is not used.
> > 
> > Let's try to keep the discussion to serialization and spirit. The other
> > things you note are off topic in this thread. Try to look only at the
> > interaction of serialization and spirit.
> 
> You could as well start a new thread for this dependency ;-)
> 
> > Look at
> > 
> >   http://www.steveire.com/boost/2014_jun_before-spirit-serialization.png
> > 
> > If you remove spirit->serialization, the cycle
> > 
> >   spirit -> pool -> thread -> date_time -> serialization [ -> spirit ]
> > 
> > still exists.
> > 
> > First question:
> >    Do you see that?
> 
> Yes, and I propose to create a date_time.serialization submodule that
> breaks the date_time -> serialization dependency.
> 
> date_time.serialization -> date_time serialization

The approach of extracting glue headers to separate submodules is not 
scalable. We have many other libraries using the same approach to optional 
dependencies.