Modify

Opened 5 years ago

Closed 5 years ago

Last modified 4 years ago

#7537 closed Feature Requests (fixed)

deprecate Mutex::scoped_lock and scoped_try_lock and boost::condition

Reported by: viboes Owned by: viboes
Milestone: Boost 1.53.0 Component: thread
Version: Boost 1.52.0 Severity: Cosmetic
Keywords: Cc:

Description

The Mutex::scoped_lock and scoped_try_lock make mutex types dependent from locks.

I would like to make them independent.

In addition they are there since 1.35. I think it is time the user moves to use the standard unique_lock.

The boost::condition condition is there since 1.35. I think it is time the user moves to use the standard condition_variable_any.

As usual, the user will have 6 releases to move. Two macros will be provided to enable/disable the inclusion of the deprecated features.

Attachments (0)

Change History (5)

comment:1 Changed 5 years ago by viboes

  • Status changed from new to assigned

comment:2 Changed 5 years ago by viboes

  • Milestone To Be Determined deleted

comment:3 Changed 5 years ago by viboes

  • Milestone set to Boost 1.53.0

comment:4 Changed 5 years ago by viboes

  • Resolution set to fixed
  • Status changed from assigned to closed

Committed revision [81667].

comment:5 Changed 4 years ago by kurt@…

Please reconsider this as std::condition_variable doesn't have support for thread interruption.

Add Comment

Modify Ticket

Change Properties
Set your email in Preferences
Action
as closed The owner will remain viboes.
The resolution will be deleted. Next status will be 'reopened'.
Author


E-mail address and user name can be saved in the Preferences.

 
Note: See TracTickets for help on using tickets.