![]() |
![]() |
![]() |
![]() |
![]() |
Restrictions
Restrictions on the SDL System
The restrictions on the SDL system that can be validated with the SDL Explorer are basically the restrictions imposed by the SDL to C compilers. See Restrictions for more information.
In addition to these general restrictions, the following restrictions are specific to the SDL Explorer:
- Time is not represented in the state space explored by the explorer. This makes the behavior of "Now" expressions special. In the SDL Explorer, "Now" will always return 0.
- If user-defined types with dynamic memory allocation are used, the type must be implemented as a pointer to a data area. A function for freeing the memory must also be supplied. For more information, see More about Abstract Data Types.
- In some cases there will be problems when the name of an entity (system, block, process, channel) is identical to another entity. A conflict will for example appear when producing names for instances in MSC diagrams.
Restrictions on Monitor Input
There following restrictions apply to monitor input:
- A parameter to a monitor command may not contain more than 1,000 characters.
- On UNIX, control characters of different types may terminate the validation program. <Ctrl+C>, <Ctrl+D>, and <Ctrl+Z> are typical characters that might terminate a validation program.
Restrictions on Dynamic Checks
There are a number of dynamic checks that are not performed at all or performed at the C level by the C runtime system. A C runtime error will of course lead to the validation program being terminated. The following check is not made at the SDL level.
http://www.ibm.com/rational |
![]() |
![]() |
![]() |
![]() |