You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/reference/api/platform/platform.md
+2-2Lines changed: 2 additions & 2 deletions
Original file line number
Diff line number
Diff line change
@@ -55,7 +55,7 @@ Serial serial(USBTX, USBRX);
55
55
56
56
The Callback class manages C/C++ function pointers so you don't have to. If you are asking yourself why you should use the Callback class, you should read the [Importance of State](/docs/development/reference/platform.html#the-importance-of-state) section.
57
57
58
-
#### Why should you use Callbacks?
58
+
##### Why should you use Callbacks?
59
59
60
60
Supporting all of the standard C++ function types is difficult for an API developer. An API developer must consider state, C++ Function objects, const correctness and volatile correctness.
61
61
@@ -69,7 +69,7 @@ Another useful C++ feature is volatile-correctness. When volatile-correctness is
69
69
70
70
C++ provides the tools to delegate this complexity to a single class. This class is the Callback class. The Callback class should be familiar to users of the std::function class that C++11 introduced and is available for older versions of C++.
71
71
72
-
<h4 id="the-importance-of-state">The importance of state</h4>
72
+
<h5 id="the-importance-of-state">The importance of state</h5>
73
73
74
74
Callbacks may have two important pieces of information, the code to execute and the state associated with the callback.
0 commit comments