Download Real Time Developer Studio: User Manual

User Manual
"out" for output-only parameters, or "inout" for two-way parameters. The
operation properties are ignored.
Note: parameters declared as "out" and "inout" are both passed as references
to the method (<type>&).
Class constructor(s) and destructor are identified via the special names <<create>>
and <<delete>> respectively. As in C++, there may be several constructors with different parameters, but only one destructor. There must be no return type for any constructor or destructor.
Systems, blocks, processes, block classes and process classes may also be referenced in
class diagrams. In this case, they are represented as active classes, as explained in SDLRT specification. These active classes may not have attributes, which are meaningless in
this case. They may however have operations, representing incoming and outgoing signals for the object. These operations are indicated by special visibilities ’>’ for incoming
signals and ’<’ for outgoing ones. These pseudo-operations may only accept one in
parameter which is the data associated to the signal. For block and process classes, the
properties are used to indicate via which gate goes the signal ({via:<gate name>}).
Examples:
UserFactory
pDispatcherClass
-lastUserId: int = 0
+<<create>>()
-computeNextUserId(): int
+newUser(in userName: char*): User*
+getUser(in userName: char*): User*
>newFrontEnd(data: int*) {via:gFE}
>newBackEnd(data: int*) {via:gBE}
<setBackEnd(data: int*) {via:gFE}
5.2 - SDL-RT symbols syntax
5.2.1 Task block
The task block contains standard ANSI C code as it would be written in a text file.
Example
/* Say hi to your friend */
printf("Hello world !\n");
for (i=0;i<MAX;i++)
{
5.2.2 Next state
The syntax in the next state SDL graphical symbol is:
<new SDL state>
Of course, the new SDL state needs to be defined in the diagram.
Page 118
Real Time Developer Studio V4.1