diff options
| author | Chris Johns <chrisj@rtems.org> | 2016-02-18 10:32:05 +1100 |
|---|---|---|
| committer | Amar Takhar <verm@darkbeer.org> | 2016-05-02 20:51:26 -0400 |
| commit | f02e87257aa62bd8b78fb199a33a3cf1a5ad18be (patch) | |
| tree | b8a1480e099194ebea5f67a22e488567468abb22 /c_user/key_concepts.rst | |
| parent | Manually apply patch from textinfo dooc. (diff) | |
| download | rtems-docs-f02e87257aa62bd8b78fb199a33a3cf1a5ad18be.tar.bz2 | |
Fix the double quotes.
Diffstat (limited to 'c_user/key_concepts.rst')
| -rw-r--r-- | c_user/key_concepts.rst | 6 |
1 files changed, 4 insertions, 2 deletions
diff --git a/c_user/key_concepts.rst b/c_user/key_concepts.rst index 9927584..e9a3689 100644 --- a/c_user/key_concepts.rst +++ b/c_user/key_concepts.rst @@ -48,7 +48,7 @@ Although not required by RTEMS, object names are often composed of four ASCII characters which help identify that object. For example, a task which causes a light to blink might be called "LITE". The ``rtems_build_name`` routine is provided to build an object name from four ASCII characters. The following -example illustrates this: .. code:: c +example illustrates this: .. code:: c @@ -59,7 +59,9 @@ However, it is not required that the application use ASCII characters to build object names. For example, if an application requires one-hundred tasks, it would be difficult to assign meaningful ASCII names to each task. A more convenient approach would be to name them the binary values one through -one-hundred, respectively... index:: rtems_object_get_name +one-hundred, respectively. + +.. index:: rtems_object_get_name RTEMS provides a helper routine, ``rtems_object_get_name``, which can be used to obtain the name of any RTEMS object using just its ID. This routine |