Using the (new) C++ standard library in boost::dll

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
3 messages Options
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Using the (new) C++ standard library in boost::dll

Boost - Users mailing list
The boost::dll depends on 4 different boost-libraries which all have counterparts in the C++17 standard library. Worse, two of them (system & filesystem) are not header-only libraries, so you need to link against these libraries.

Is it possible and planned to use the standard library counterparts as plug in replacement for these boost dependencies in a future release? In my opinion this would improve the usability massively, especially when you already use this counterparts in the rest of your program.

Best regards,
Benjamin

_______________________________________________
Boost-users mailing list
[hidden email]
https://lists.boost.org/mailman/listinfo.cgi/boost-users
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Using the (new) C++ standard library in boost::dll

Boost - Users mailing list
On 12.05.2017 17:04, Benjamin Buch via Boost-users wrote:
The boost::dll depends on 4 different boost-libraries which all have counterparts in the C++17 standard library. Worse, two of them (system & filesystem) are not header-only libraries, so you need to link against these libraries.

Is it possible and planned to use the standard library counterparts as plug in replacement for these boost dependencies in a future release? In my opinion this would improve the usability massively, especially when you already use this counterparts in the rest of your program.

Yeah, this question pops up often these post-C++11 days. I often encounter this dualism, for instance with using std::shared_ptr in the most of the code, and boost::shared_ptr in the parts that interface with some boost libraries that are not part of the standard (yet). I'm still waiting to see how Boost will tackle this, if at all. It may well be that the success of Boost in developing the standard C++ may also mark the beginning of it's demise as much of its precious functionality will be available as part of std::, and for the remaining parts the questions of the code maintenance will be gaining more and more importance.

Cheers,
Leon



_______________________________________________
Boost-users mailing list
[hidden email]
https://lists.boost.org/mailman/listinfo.cgi/boost-users
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Using the (new) C++ standard library in boost::dll

Boost - Users mailing list
On 5/12/2017 12:32 PM, Leon Mlakar via Boost-users wrote:

> On 12.05.2017 17:04, Benjamin Buch via Boost-users wrote:
>> The boost::dll depends on 4 different boost-libraries which all have
>> counterparts in the C++17 standard library. Worse, two of them (system
>> & filesystem) are not header-only libraries, so you need to link
>> against these libraries.
>>
>> Is it possible and planned to use the standard library counterparts as
>> plug in replacement for these boost dependencies in a future release?
>> In my opinion this would improve the usability massively, especially
>> when you already use this counterparts in the rest of your program.
>
> Yeah, this question pops up often these post-C++11 days. I often
> encounter this dualism, for instance with using std::shared_ptr in the
> most of the code, and boost::shared_ptr in the parts that interface with
> some boost libraries that are not part of the standard (yet). I'm still
> waiting to see how Boost will tackle this, if at all. It may well be
> that the success of Boost in developing the standard C++ may also mark
> the beginning of it's demise as much of its precious functionality will
> be available as part of std::, and for the remaining parts the questions
> of the code maintenance will be gaining more and more importance.

I created a library, called cxx_dual ( cxxd for short ) at
https://github.com/eldiener/cxx_dual, to solve the above problem for
library developers or for end-users in their own program code. But for
various reasons this library was not popular with other Boost
developers. Feel free to look at it and to post questions, bug reports,
or suggestions about it. The library also exists in the Boost Library
Incubator.

_______________________________________________
Boost-users mailing list
[hidden email]
https://lists.boost.org/mailman/listinfo.cgi/boost-users
Loading...