| Table of |
§1. Teams and Roles |
| §0. About this document |
Levels of this document
![]() |
|
| Terms, concepts | Each chapter of this document starts with a short synopsis of concepts covered by the chapter (like this). |
![]() |
|
| Definition | The actual definition is given in small numbered paragraphs. |
![]() |
|
| Examples | Examples and accompanying explanations will be interspersed into the definition. |
![]() |
|
§0.1. Purpose(s) of this document
§0.2. Text structure
Each chapter of this document starts with a short synopsis of concepts covered by the chapter (see above).
| (a) | The actual definition is structured into small paragraphs for easy referral. |
| (b) | Links to the syntax precede definitions whenever new syntax is introduced. |
Interspersed you will find some example program listings. Examples are typeset in a box with striped background. Explanations for examples appear on a colored background. Examples are given for illustration only.
|
Effects:
- Lines 1-3 show a minimal OT/J program, which should not cause any headache.
Additional paragraphs like "Language implementation", or "open issues" provide some background information which is not necessary for understanding the definition, which might however, help to understand why things are the way they are and what other things might be added to the language in the future.
§0.3. Compiler messages
Error messages given by the Object Teams compiler refer to this definition whenever apropriate. This way it should be easy to find out, why the compiler rejected your program. Please make sure you are using a language definition whose version matches the version of your compiler.
§0.4. Versions
The structure of this document has changed between versions
0.6.1 and 0.7 of this document. This change reflects the
transition from our first compiler for OT/J (called otc)
and the OTDT (Object Teams Development Tooling)
plugin for Eclipse.
| Table of |
§1. Teams and Roles |

