2007-10-26 Glenn Humphrey <glenn.humphrey@OARcorp.com>

* user/rtmon.t: Fix report output.

2007-10-25	Glenn Humphrey <glenn.humphrey@OARcorp.com>

	* user/barrier.t, user/clock.t, user/concepts.t, user/cpuuse.t,
	user/init.t, user/intr.t, user/io.t, user/mp.t, user/rtmon.t,
	user/sem.t, user/stackchk.t, user/task.t, user/timer.t: Updated the
	Ada documentation to reflect the current binding.
This commit is contained in:
Glenn Humphrey
2007-10-26 21:34:57 +00:00
parent c4215bad1f
commit 1b03eed0e5
13 changed files with 99 additions and 152 deletions

View File

@@ -1,5 +1,5 @@
@c
@c COPYRIGHT (c) 1988-2002.
@c COPYRIGHT (c) 1988-2007.
@c On-Line Applications Research Corporation (OAR).
@c All rights reserved.
@c
@@ -59,9 +59,9 @@ 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 @code{@value{DIRPREFIX}build_name} routine
is provided to build an object name from four ASCII characters.
@ifset is-C
The following example illustrates this:
@ifset is-C
@example
rtems_object_name my_name;
@@ -69,6 +69,14 @@ my_name = rtems_build_name( 'L', 'I', 'T', 'E' );
@end example
@end ifset
@ifset is-Ada
@example
My_Name : RTEMS.Name;
My_Name = RTEMS.Build_Name( 'L', 'I', 'T', 'E' );
@end example
@end ifset
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
@@ -76,13 +84,13 @@ assign meaningful ASCII names to each task. A more convenient
approach would be to name them the binary values one through
one-hundred, respectively.
@ifset is-C
@findex rtems_get_object_name
RTEMS provides a helper routine, @code{@value{DIRPREFIX}get_object_name},
which can be used to obtain the name of any RTEMS object using just
its ID. This routine attempts to convert the name into a printable string.
@ifset is-C
The following example illustrates the use of this method to print
an object name: