2014-04-28 20:15 GMT+08:00 Renato Forti :

Hi All,

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

- - Boost.Application - Boost.Shared_Library

non-sense. Boost.Shared_Library ? by what ?

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)

I will detach this part:

http://www.dokfile.com/appbeta4/docs/libs/application/doc/html/boost_applica...

Anyone have any comment/advises about it? Any suggestion? Anyone disagrees?

I await your comments, thanks! -- ReTF

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

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)