make headlines within list 1st level list (else they are prone to be part of earlier bullet

This commit is contained in:
Thibault Kruse
2015-09-26 18:30:29 +02:00
parent 07ae55a037
commit d2ea0766b0

View File

@@ -5490,7 +5490,7 @@ the optimal strategy (for performance and ease of programming) is sometimes simp
If you have enough memory to handle your largest input, leak away, but be sure to give a good error message if you are wrong. If you have enough memory to handle your largest input, leak away, but be sure to give a good error message if you are wrong.
Here, we ignore such cases. Here, we ignore such cases.
Resource management rule summary: * Resource management rule summary:
* [R.1: Manage resources automatically using resource handles and RAII (resource acquisition is initialization)](#Rr-raii) * [R.1: Manage resources automatically using resource handles and RAII (resource acquisition is initialization)](#Rr-raii)
* [R.2: In interfaces, use raw pointers to denote individual objects (only)](#Rr-use-ptr) * [R.2: In interfaces, use raw pointers to denote individual objects (only)](#Rr-use-ptr)
@@ -5499,7 +5499,7 @@ Resource management rule summary:
* [R.5: Prefer scoped objects](#Rr-scoped) * [R.5: Prefer scoped objects](#Rr-scoped)
* [R.6: Avoid non-`const` global variables](#Rr-global) * [R.6: Avoid non-`const` global variables](#Rr-global)
Alocation and deallocation rule summary: * Alocation and deallocation rule summary:
* [R.10: Avoid `malloc()` and `free()`](#Rr-mallocfree) * [R.10: Avoid `malloc()` and `free()`](#Rr-mallocfree)
* [R.11: Avoid calling `new` and `delete` explicitly](#Rr-newdelete) * [R.11: Avoid calling `new` and `delete` explicitly](#Rr-newdelete)
@@ -5508,8 +5508,7 @@ Alocation and deallocation rule summary:
* [R.14: ??? array vs. pointer parameter](#Rr-ap) * [R.14: ??? array vs. pointer parameter](#Rr-ap)
* [R.15: Always overload matched allocation/deallocation pairs](#Rr-pair) * [R.15: Always overload matched allocation/deallocation pairs](#Rr-pair)
<a name ="Rr-summary-smartptrs"></a>Smart pointer rule summary: * <a name ="Rr-summary-smartptrs"></a>Smart pointer rule summary:
* [R.20: Use `unique_ptr` or `shared_ptr` to represent ownership](#Rr-owner) * [R.20: Use `unique_ptr` or `shared_ptr` to represent ownership](#Rr-owner)
* [R.21: Prefer `unique_ptr` over `shared_ptr` unless you need to share ownership](#Rr-unique) * [R.21: Prefer `unique_ptr` over `shared_ptr` unless you need to share ownership](#Rr-unique)
* [R.22: Use `make_shared()` to make `shared_ptr`s](#Rr-make_shared) * [R.22: Use `make_shared()` to make `shared_ptr`s](#Rr-make_shared)
@@ -5524,7 +5523,6 @@ Alocation and deallocation rule summary:
* [R.36: Take a `const shared_ptr<widget>&` parameter to express that it might retain a reference count to the object ???](#Rr-sharedptrparam-const&) * [R.36: Take a `const shared_ptr<widget>&` parameter to express that it might retain a reference count to the object ???](#Rr-sharedptrparam-const&)
* [R.37: Do not pass a pointer or reference obtained from an aliased smart pointer](#Rr-smartptrget) * [R.37: Do not pass a pointer or reference obtained from an aliased smart pointer](#Rr-smartptrget)
<a name ="Rr-raii"></a> <a name ="Rr-raii"></a>
### Rule R.1: Manage resources automatically using resource handles and RAII (resource acquisition is initialization) ### Rule R.1: Manage resources automatically using resource handles and RAII (resource acquisition is initialization)