Opened 10 years ago
Closed 9 years ago
#7501 closed Feature Requests (wontfix)
Decouple from time libraries
| Reported by: | Andrey Semashev | Owned by: | viboes |
|---|---|---|---|
| Milestone: | To Be Determined | Component: | thread |
| Version: | Boost 1.52.0 | Severity: | Problem |
| Keywords: | Cc: |
Description
In order to support more time libraries like Boost.DateTime and Boost.Chrono (e.g. std::chrono from C++11) and reduce library dependencies it is suggested to decouple Boost.Thread from Boost.DateTime and Boost.Chrono and introduce an abstraction layer for time units. Having done that, Boost.Thread should not depend on any time library, neither when being built nor when being used, except for its time-related features. The integration layer should include support for Boost.DateTime, Boost.Chrono and std::chrono.
The topic has been brought up in this thread:
Change History (2)
comment:1 by , 10 years ago
| Type: | Tasks → Feature Requests |
|---|
comment:2 by , 9 years ago
| Resolution: | → wontfix |
|---|---|
| Status: | new → closed |
Note:
See TracTickets
for help on using tickets.
I will take this in account once it is provided by Boost.Sync.