StarMirror/CppCoreGuidelines
1
0
Fork 0
mirror of https://github.com/isocpp/CppCoreGuidelines.git synced 2024-03-22 13:30:58 +08:00
Code Issues Projects Releases Wiki Activity

Fix some markdown warnings seen in the Travis CI checks

Browse Source
This commit is contained in:
Jonathan Wakely 2017-02-13 20:14:47 +00:00
parent 52ad087bb3
commit 464870c7d3
1 changed files with 2 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

3
CppCoreGuidelines.md
View File

@ -11976,7 +11976,7 @@ There are many tools "out there", both commercial and open-source tools, both re
Unfortunately people's needs and constraints differ so dramatically that we cannot make specific recommendations,
but we can mention:
* Static enforcement tools: both [clang](http://clang.llvm.org/docs/ThreadSafetyAnalysis.html)
* Static enforcement tools: both [clang](http://clang.llvm.org/docs/ThreadSafetyAnalysis.html)
and some older versions of [GCC](https://gcc.gnu.org/wiki/ThreadSafetyAnnotation)
have some support for static annotation of thread safety properties.
Consistent use of this technique turns many classes of thread-safety errors into compile-time errors.
@ -19409,6 +19409,7 @@ A relatively informal definition of terms used in the guidelines
This is our to-do list.
Eventually, the entries will become rules or parts of rules.
Alternatively, we will decide that no change is needed and delete the entry.
* No long-distance friendship
* Should physical design (what's in a file) and large-scale design (libraries, groups of libraries) be addressed?
* Namespaces