EDL description

EDL descriptions are put into separate *.edl files, which contain the following data:

1. Process class name. The following declaration is used:

   entity <process class name>

2. [Optional] List of instances of components. The following declaration is used:

   components {

   <component instance name : component name>

   ...

   }

   Each component instance is indicated in a separate line. The component instance name must not contain any underscores _. The list can contain multiple instances of one component. Each component instance in the list has a unique name.

The EDL language is case sensitive.

Single-line comments and multi-line comments can be used in an EDL description.

Supported endpoints and the security interface can be defined in an EDL description the same way they are defined in a CDL description. However, this practice is not recommended because EDL descriptions and CDL descriptions are usually created by different participants of the development process for KasperskyOS-based solutions. CDL descriptions are created by developers of system programs and application software. EDL descriptions are created by developers that integrate system programs and application software into a unified solution.

Examples of EDL files

Hello.edl

// Class of processes that do not contain components.

entity Hello

Signald.edl

/* Class of processes that contain

* one instance of one component. */

entity kl.Signald

components {

signals : kl.Signals

}

LIGHTCRAFT.edl

/* Class of processes that contain

* two instances of different components. */

entity kl.drivers.LIGHTCRAFT

components {

KUSB : kl.drivers.KUSB

KIDF : kl.drivers.KIDF

}

Page top