[modularization] request for a new modularization status for develop branch

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
8 messages Options
Reply | Threaded
Open this post in threaded view
|

[modularization] request for a new modularization status for develop branch

Vicente Botet
Hi Peter,

could you upload a new modularization status, as in
http://www.pdimov.com/tmp/report-d53f656/module-levels.html ?

Best,
Vicente

_______________________________________________
Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost
Reply | Threaded
Open this post in threaded view
|

Re: [modularization] request for a new modularization status for develop branch

Stephen Kelly-2
Vicente J. Botet Escriba wrote:

> Hi Peter,
>
> could you upload a new modularization status, as in
> http://www.pdimov.com/tmp/report-d53f656/module-levels.html ?

Things have not changed much since that.

If you want to work on removing cycles, then my recommendations (regarding
serialization -> spirit, range -> algorithm, mplcore -> mpl) should be
enough to keep you busy. After those changes are made, a new report becomes
worthwhile.

You will need to either make the recommended changes (or merge the pull
request), or if you don't feel like you are able to do that, then track down
the person who is and convince them to do the work.

Thanks,

Steve.



_______________________________________________
Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost
Reply | Threaded
Open this post in threaded view
|

Re: [modularization] request for a new modularization status for develop branch

Peter Dimov-2
In reply to this post by Vicente Botet
Vicente J. Botet Escriba wrote:
> Hi Peter,
>
> could you upload a new modularization status, as in
> http://www.pdimov.com/tmp/report-d53f656/module-levels.html ?

There you go:

http://www.pdimov.com/tmp/report-d5ca5be/module-levels.html


_______________________________________________
Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost
Reply | Threaded
Open this post in threaded view
|

Re: [modularization] request for a new modularization status for develop branch

Vicente Botet
Le 16/09/14 17:45, Peter Dimov a écrit :

> Vicente J. Botet Escriba wrote:
>> Hi Peter,
>>
>> could you upload a new modularization status, as in
>> http://www.pdimov.com/tmp/report-d53f656/module-levels.html ?
>
> There you go:
>
> http://www.pdimov.com/tmp/report-d5ca5be/module-levels.html
>
Thanks Peter,

Vicente

_______________________________________________
Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost
Reply | Threaded
Open this post in threaded view
|

Re: [modularization] request for a new modularization status for develop branch

Vicente Botet
In reply to this post by Peter Dimov-2
Le 16/09/14 17:45, Peter Dimov a écrit :

> Vicente J. Botet Escriba wrote:
>> Hi Peter,
>>
>> could you upload a new modularization status, as in
>> http://www.pdimov.com/tmp/report-d53f656/module-levels.html ?
>
> There you go:
>
> http://www.pdimov.com/tmp/report-d5ca5be/module-levels.html
>
>
>
Hi,

Lastly, there have been some changes that simplify the dependencies.

Even if we are not yet clear on the modularization goal, Peter please,
could you update the header dependencies status again? Maybe it is worth
changing the title to "Header Module Levels".

Thanks,
Vicente

_______________________________________________
Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost
Reply | Threaded
Open this post in threaded view
|

Re: [modularization] request for a new modularization status for develop branch

Robert Ramey
In reply to this post by Vicente Botet
Vicente Botet wrote
Hi Peter,

could you upload a new modularization status, as in
http://www.pdimov.com/tmp/report-d53f656/module-levels.html ?

Best,
Vicente
I find this extremely interesting.  Can we add this project to the boost tools as we have for BCP?

A couple of questions:
a) Level 11 - looks like there's a cycle for the algorithm->range->algorithm  and some others.  But since this is by module I'm not sure this is true.

b) of the different ways of counting dependency we've described - which is this?  That is it just headers? or doesn't include the library implementation.  Is it to build all tests/examples in the module, or is it some application which uses the module.

c) Does this mean that to build a module at level N it is sufficient and necessary to have available all the modules at levels less than N ?

d) probably off topic, but level 14 shows serialization dependent upon spirit. OK I get that.  But it also shows spirit dependent upon serialization - what's up with that?

I have some other questions as well, but that's enough for now

RObert Ramey
Reply | Threaded
Open this post in threaded view
|

Re: [modularization] request for a new modularization status for develop branch

Peter Dimov-2
Hi Robert,

Robert Ramey wrote:

> Vicente Botet wrote
> > Hi Peter,
> >
> > could you upload a new modularization status, as in
> > http://www.pdimov.com/tmp/report-d53f656/module-levels.html ?
> >
> > Best,
> > Vicente
>
> I find this extremely interesting.  Can we add this project to the boost
> tools as we have for BCP?

The tool itself is in tools/boostdep, but I haven't written any
documentation yet.

> A couple of questions:
> a) Level 11 - looks like there's a cycle for the
> algorithm->range->algorithm and some others.  But since this is by module
> I'm not sure this is true.

The range -> algorithm dependency has been removed by a recent pull request
from Stephen Kelly, so this cycle has at least been taken care of.

> b) of the different ways of counting dependency we've described - which is
> this?  That is it just headers? or doesn't include the library
> implementation.

Just headers.

> c) Does this mean that to build a module at level N it is sufficient and
> necessary to have available all the modules at levels less than N ?

Not necessarily to build, as it only tracks headers. If you include a header
of level N, compilation should succeed if you have everything <= N
installed, assuming prebuilt or header-only libraries. In the absence of
cycles, it would be < N.

> d) probably off topic, but level 14 shows serialization dependent upon
> spirit. OK I get that.  But it also shows spirit dependent upon
> serialization - what's up with that?

http://www.pdimov.com/tmp/report-d53f656/spirit.html#serialization

<boost/spirit/home/support/detail/lexer/serialise.hpp> includes
<boost/serialization/vector.hpp>.

There is a newer report at
http://www.pdimov.com/tmp/report-d5ca5be/module-levels.html by the way.


_______________________________________________
Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost
Reply | Threaded
Open this post in threaded view
|

Re: [modularization] request for a new modularization status for develop branch

Vicente Botet
Le 29/09/14 17:09, Peter Dimov a écrit :

> Hi Robert,
>
> Robert Ramey wrote:
>> Vicente Botet wrote
>> > Hi Peter,
>> >
>> > could you upload a new modularization status, as in
>> > http://www.pdimov.com/tmp/report-d53f656/module-levels.html ?
>> >
>> > Best,
>> > Vicente
>>
> There is a newer report at
> http://www.pdimov.com/tmp/report-d5ca5be/module-levels.html by the way.
>
>
It seems that this is the same you uploaded the last time

 > There you go:
 > http://www.pdimov.com/tmp/report-d5ca5be/module-levels.html

Vicente

_______________________________________________
Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost