#include <boost/bind.hpp> is used instead of <boost/bind/bind.hpp> causing deprecation warning

Open
#21 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
50/100
Issue type
Bug
Clarity
Clearly specified
Activity status
Stale
Tech stack
cpp
Domain
tooling

Research direction

Start by reading fifo_worker.hpp and processor_container.hpp, then search the repository for uses of the Boost.Bind placeholders mentioned in the warning. Build the project to reproduce the deprecation warning and check whether the updated include requires any namespace changes. Done means the affected headers use the supported Boost.Bind header and the warning no longer appears without breaking existing usage.

Written by the indexing model from the issue text.

Description

The header files: fifo_worker.hpp and processor_container.hpp include <boost/bind.hpp> instead of <boost/bind/bind.hpp>

During complication this causes the following warning:

message : The practice of declaring the Bind placeholders (_1, _2, ...) in the global namespace is deprecated. Please use <boost/bind/bind.hpp> + using namespace boost::placeholders, or define BOOST_BIND_GLOBAL_PLACEHOLDERS to retain the current behavior.

Remark: using <boost/bind/bind.hpp> may be a breaking change for projects that rely implicit on the fact that <boost/bind.hpp> is used at the moment.

Dominant language
C++
Stars
32
Forks
43
PR merge metrics
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from boostorg/statechart

All issues in boostorg/statechart

Similar issues

More C++ issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.