Subject: Re: [boost] [modularization] What is a module? What is a sub-module?
From: Rob Stewart (robertstewart_at_[hidden])
Date: 2014-09-24 11:11:34
On September 24, 2014 5:25:26 AM EDT, "Thijs (M.A.) van den Berg" <thijs_at_[hidden]> wrote:
>On Sep 24, 2014, at 11:07 AM, Rob Stewart <robertstewart_at_[hidden]>
>> On September 23, 2014 12:54:28 PM EDT, "BjÃ¸rn Roald"
>> 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.
I don't understand that.
>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.
Why wouldn't you refer to such things as sublibraries?
(Sent from my portable computation engine)
Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk