Project

General

Profile

Design #1259

ThreadsafeCounter is now obsolete?

Added by John Abbott about 5 years ago. Updated over 4 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Category:
Tidying
Start date:
25 Mar 2019
Due date:
% Done:

100%

Estimated time:
0.77 h
Spent time:

Description

C++14 atomic machine integers should render ThreadsafeCounter superfluous.

Check, and either clean up the code, or eliminate it.


Related issues

Related to CoCoALib - Feature #142: Improve threadsafetyIn Progress2012-04-30

Related to CoCoALib - Bug #784: threadsafety: Scott Meyers's advice about cached valuesIn Progress2015-10-12

Related to CoCoALib - Design #1225: Move to C++14 (skipping C++11)In Progress2018-09-06

History

#1 Updated by John Abbott about 5 years ago

#2 Updated by John Abbott about 5 years ago

  • Related to Bug #784: threadsafety: Scott Meyers's advice about cached values added

#3 Updated by John Abbott about 5 years ago

  • Related to Design #1225: Move to C++14 (skipping C++11) added

#4 Updated by John Abbott about 5 years ago

A quick grep shows that ThreadsafeCounter is used in just two places:
  • ring.C (for the ring ID)
  • symbol.C (for anonymous symbols)

#5 Updated by John Abbott about 5 years ago

  • Status changed from New to Resolved
  • Assignee set to John Abbott
  • % Done changed from 0 to 50

I have now removed ThreadsafeCounter from my own personal copy.
Everything compiles and all tests pass. :-)
Once I've got VPN working again, I can check in.

#6 Updated by John Abbott over 4 years ago

  • Status changed from Resolved to Closed
  • Target version changed from CoCoALib-0.99700 to CoCoALib-0.99650 November 2019
  • % Done changed from 50 to 100
  • Estimated time set to 0.77 h

Well, I am now sync'd with CVS, so presumably this also works fine for Anna.
Apparently I have deleted the source files, and the doc, and any examples.

Closing.

Also available in: Atom PDF