Re: [boost] Request for comments on break up ‘Application’ into 2 libraries.

Hi Renato, Although plugin support is useful feature but it will raise many questions. I agree it would be better to strip Application from auxiliary features because not every application requires it (and it will be easier to go through review and approval process). Later when people will start using the library (and find new use cases) you can add new features naturally. There is no need for separate "boos::shared_library" or "boost::plugin" - eventually it will be extension of boost::application. Regards, Alexey.

On 28 Apr, 2014, at 8:15 pm, Renato Forti wrote:

Hi All,

Following suggestion of Niall Douglas, I am thinking in split the ‘Boost.Application’ in 2 libraries:

- - Boost.Application - Boost.Shared_Library

Thus, the ‘plug-in systems’ will be detached of ‘Boost.Application’ core and will become one new library, and ‘Application’ stay only providing abstraction of an application (no more plugin system)