Syntax. Throughout this Agreement, whenever the context so requires, the singular shall include the plural, and the masculine gender shall include the feminine and neuter genders. The headings and captions of the various Sections hereof are for convenience only and they shall not limit, expand or otherwise affect the construction or interpretation of this Agreement.
Syntax. .1 Where the words ‘accepted’, ‘reviewed’, ‘designated’, ‘directed’, ‘inspected’, ‘instructed’, ‘permitted’, ‘required’, and ‘selected’ are used in the Contract Documents, they are deemed to be followed by the words ‘by the Consultant’, unless the context provides otherwise.
.2 Where the words ‘acceptable’, ‘submit’ and ‘satisfactory’ are used in the Contract Documents, they are deemed to be followed by the words ‘to the Consultant’, unless the context provides otherwise.
.3 Where the masculine is used in the Contract Documents, it shall be read and interpreted as if the feminine or neuter had been used when the context of the statement so requires, and the rest of the sentence, clause, paragraph or item shall be interpreted as if all changes in grammar, gender or terminology thereby rendered necessary had been made.
.4 The use of the words “include” or “including”, or variations thereof, is not limiting.
Syntax. As the context of this Agreement requires, the masculine gender shall include the feminine or the neuter.
Syntax. Whenever the feminine pronoun is used in this Agreement, it includes the masculine pronoun and vice-versa where the context so requires. Where the singular is used, it may also be deemed to mean plural and vice-versa. The provisions of this Agreement shall be read with all generic, grammatical, singular and plural changes as required by the circumstances.
Syntax. Throughout this Stock Option Certificate, whenever the context so requires, the singular shall include the plural, and the masculine gender shall include the feminine and neuter genders. The headings and captions of the various Sections hereof are for convenience only and they shall not limit, expand or otherwise affect the construction or interpretation of this Stock Option Certificate.
Syntax. A program is a list of function- and global variable declarations. There must be one function main. The abstract syntax of SECA is shown in Fig.
Syntax. Wherever the feminine pronoun is used in this Agreement, it includes the masculine pronoun and vice versa where the context so requires.
Syntax. The syntax of the test specification language is given by a grammar as shown in Table 3.1. In general, the grammar of the test specification resembles that of the programming language given in Table 2.1 with small replacements and some extensions. To stress the extending character of the specification language the cutdecl ::= test class C; s ::= cutdecl T x; mokdecl { stmt } mokdecl ::= mock class C{C(T, . . . , T ); T m(T, . . . , T ); }; stmt ::= x = e | x = new C() | ε | stmt ; stmt | {T x; stmt } specification test unit class mock class statements | while (e) {stmt } | if (e) {stmt } else {stmt } stmtin ::= (C x)?m(T x).where(e) {T x; stmt ; !return e} | stmtin | stmtout | case { stmt in ; stmt } incoming stmt stmtout ::= e!m(e, . . . , e) {T x; stmt ; x =?return(T x).where(e) } | new(C x)?C(T x).where(e) {T x; stmt ; !return} outgoing stmt e ::= x | null | op(e, . . . , e) | new!C(e, . . . , e) {T x; stmt ; x =?return(T x).where(e) } expressions
Table 3.1: Specification language for Japl: syntax extensions are highlighted in the grammar definition. Similar to the original defi- nition of a program p which consists of class import declarations, global variable definitions, class definitions, and a main body, the definition of a specification s consists of unit class declarations, global variable definitions, class declarations, and a specification body. In particular the class import declaration is replaced by the unit class declarations which also mention the names of the classes only. The class definition of a program is replaced by the mock class declaration where only the signature of the classes are specified. The method bodies are omitted since the specification body basically consists of the interaction trace and therefore implic- itly stipulates the behavior of the classes, rendering the method body definitions unnecessary. As the classes do not provide method bodies or field declarations it wouldn’t make sense to internally call their methods. Thus we omit the statements for (internal) method calls and field updates. For the same reason, the specifica- tion language only provides a simplified new construct which actually does not entail a constructor call but rather merely specifies the creation of a new object of a tester class. Furthermore, the specification language also provides sequential composition of statements, block statements, conditional statements, while loops, and the empty statement. Finally, the language allows for explicitly...
Syntax. The grammar of the Java-like programming language is given in Table 2.1. A program consists of a list of global variables, a set of classes, and a main program (or main body). Note, that due to simplicity, our language slightly differs from Java already on the program level in two aspects: first, Java does not provide a designated construct for specifying global variables but rather requires them to be introduced by static fields. Second, in Java also the main program is not represented by a special construct on the program level but is given by a static method with a special name. However, to keep the language small and simple, we omit static fields and methods. Adding special constructs also allows for a clearer separation of concerns.
Syntax. The extension of the syntax is very simple and straightforward, as can be seen in Table 2.8. We merely add a construct for declaring imported classes which intro- duces the name of the class only. For the sake of simplicity we do not introduce name spaces, but instead we assume that the names of all imported and all locally defined classes are different. The grammar introduces a new non-terminal symbol p′ which replaces p of the former grammar. An element of p′ is called a compo- nent. Thus, the program does not only import classes of other components but it constitutes a component itself. In particular, all components contain a main body. This is again due to simplicity, because otherwise we would have to differentiate components and programs (and in this case only component classes could be im- ported but a component could not import a program class). However, we will see in the operational semantics that only the main body of one single component is in execution.2 In the following we will use the word program in order to refer to the component whose code is given and processed in the operational semantics. Note 2Assuming that each component provides its own main body is comparable to the widely used technique to equip a Java package with a static main method allowing for the stand-alone execution of the package due to testing or demonstration purposes. import D; class C1 { C1() { stmt; return } D(int x) { D y; stmt; return y }
