Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

ICU-12505 U_HAVE_STD_ATOMICS, reduce & simplify configure options. #52

Merged
merged 1 commit into from
Aug 14, 2018

Conversation

aheninger
Copy link
Contributor

@aheninger aheninger commented Aug 10, 2018

Checklist
  • Issue filed at https://unicode-org.atlassian.net : ICU-______
  • Update PR title to include Issue number
  • Issue accepted
  • Tests included
  • Documentation is changed or added

@srl295
Copy link
Member

srl295 commented Aug 10, 2018

was #50 ?

@aheninger
Copy link
Contributor Author

Sorry about #50 & #51, stupid mistakes with wrong ticket numbers in PR name, branch names & commit messages, and I couldn't see how to fix the PR once created.

This PR is a first step towards eliminating all of the platform-specific atomic & mutex implementation code from ICU in favor of using only C++11 standard facilities. Portable! The C++ runtime library developers already have to deal with the platform issues, we shouldn't be doing it again in ICU code. The ICU platform code is messy, tricky, and in need of maintenance, esp. on Windows.

Retracting the autoconf tests will give a warning shot that full C++11 atomics support is expected, and that soon there will be no configurable work-around if it's missing.

@aheninger aheninger merged commit 8587900 into unicode-org:master Aug 14, 2018
@aheninger aheninger deleted the ICU-12505 branch August 14, 2018 18:47
hugovdm added a commit to hugovdm/icu that referenced this pull request Sep 5, 2020
ICU-20941 Support Mixed Units in NumberFormatter when using usage()
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants