previous contents index next
(Arrangements) Contents Index (..Source Code Components..)

2.2 Source Code Components

 

2.2.1 Character Set

A correct RDL or SDL source code consists of the following characters:

Small and capital letters
(Letter)
a, b, .. , z, A, B, .. , Z
(without ä, ö, ü, Ä, Ö, Ü)
Digits (Digit) 0, 1, .. , 9
Special characters
(just in strings)
+, -, *, % , /, & , |, =, >, <, !, (, ), [, ], { , } , ., :, ,, ;, _ , ', ä, ö, ü, Ä, Ö, Ü, ^, °, ", §, $, ?, \, `, ', @, ~, #, blank;
Separation signs blank, TAB, newline

 

Letters, digits and special characters together form the class Character.


 
Separation signs have to be used whenever identifiers or keywords are standing after one another. In all other cases they can be omitted. In general, it does not matter which separation sign is used, but it certainly is of advantage to organize the source code in lines and paragraphs, for it is easier to keep control of it. It is especially recommened to design the local rule table in a way which allows the recognition of its entries. Blanks, too, should be used to make it easier to read the code. But it is certainly necessary to keep tokens like identifiers, keywords and compounded assign operators (<=, ++ , ...) together, otherwise the compiler would not understand.
Also if we want a string to go on in the following line, we are not permitted to put separation signs between the backslash and the carriage return.
previous contents index next
(Arrangements) Contents Index (..Source Code Components..)