On Thu, Jul 31, 2025 at 7:46 PM Artyom Beilis via Boost < boost@lists.boost.org> wrote:
On Thu, Jul 31, 2025 at 2:17 PM Darryl Green via Boost <boost@lists.boost.org> wrote:
I'm replying to this as someone who has used the old and new versions of Boost Process API. And migrated code (not hard) to the new API. And left code that I haven't had reason to update, using the old version of Boost, with the old API.
It isn't a question if it is hard or not... Most of the breaking so far was possible to fix this way or other.
The questions are
- Why do you need to _remove_ the API that hundreds of projects depend on?
It was not removed. The headers were moved into a v1 subfolder, and the content into a v1 namespace that can be inlined by defined BOOST_PROCESS_VERSION =1. So the required code refactor is replacing every instance `#include <boost/process`with `#include <boost/process/v1`. Security was among the reasons I decided to make v2 the default.
Artyom _______________________________________________ Boost mailing list -- boost@lists.boost.org To unsubscribe send an email to boost-leave@lists.boost.org https://lists.boost.org/mailman3/lists/boost.lists.boost.org/ Archived at: https://lists.boost.org/archives/list/boost@lists.boost.org/message/ASA7IOAY...