Re: [boost] [modularization] What is a module? What is a sub-module?

Subject: Re: [boost] [modularization] What is a module? What is a sub-module?
From: Thijs (M.A.) van den Berg (thijs_at_[hidden])
Date: 2014-09-24 05:25:26

On Sep 24, 2014, at 11:07 AM, Rob Stewart <robertstewart_at_[hidden]> wrote:

> On September 23, 2014 12:54:28 PM EDT, "Bjørn Roald" <bjorn_at_[hidden]> wrote:
> If you still think there's something to a library that isn't part of a module, please explain. So far, they appear to be synonyms to me.
> 

Maybe rgis?

I can imagine one could have libraries that depends on well-defined *parts* of other libraries (but not all of it), and that those parts can be called modules. One would not call such a part a library -and also not list it on the public website as a boost library- because its functionality to specific / narrow. For developers is should have a clear identity and not break dependent  libraries when refactoring.