Examples about application definition part of GRP files

Example #1: multi part definition

Application: test
{
  HeaderPart
  {
     ...
  }
  HeaderPart
  {
     ...
  }
}

This example shows that application can contain any number of application parts. In this example the name of the application server program will be 'test.c'.

Example #2: case sensitivity

ApPlIcAtIoN: test1 { HeaderPart{} }

APPLICATION: test2
{
  HeaderPart {}
}

In this example the GRP file contains two applications. The Grapnel Compiler will generate two application server programs: 'test1.c' and 'test2.c'. Any number of applications can be defined in single GRP file. An other feature that reserved words are case indepent. In the example above the 'ApPlIcAtIoN' and the 'APPLICATION' means 'application'.

Example #3: source file handling

GRP file #1:

Application: test1 
{
  HeaderPart {}
}

GRP file #2:

Application: test2
{
  HeaderPart {}
}

This example contains two GRP files. If we compile them together then the Grapnel Compiler will concatenate these files and generate source files for both applications ('test1.c' and 'test2.c').

Example #4: concatenation of definitions

Application: test
{
  HeaderPart {}
}

Application: test
{
  ProgramPart {}
}

This GRP file defines two applications with same name. The Grapnel Compiler will concatenate these definitions together and generate only one source file ('test.c'). The generated file will contain informations picked up from header part defined in the first occurence of 'test' and from program part defined in the second occurence of the 'test'.

Unfortunately this feature does not work properly because the Compiler generates source files twice. The bug will be fixed as soon as possible.

Bug fixed: 18 Jul 1995.

Examples about header part.

Back to definition of GRP language.
Back to Grapnel Compiler.