Fork me on GitHub

Script Format

A script is a text file containing SARL code. Each script must follow the format:

<package declaration>
<top-level features>

##1. Package Declaration

To structure your software, it is common to put scripts in different packages (as Java does for the classes).

The keyword package permits you to define the name of the package associated with a SARL file. Consequently, all the features defined in the script are contained in this package, and their names are qualified with the name of the package.

The package’s name also affects the generation of the Java files implementing the SARL script. Indeed, all the Java files are generated in a folder with the name of the package.

In the following example, the qualified name of an agent defined in the file is

If the `package` keyword is not used, the default package will be used. The default package has an empty name. It is recommended in the SARL Best Practices to specify a package's name.

##2. Import Directive

The imports section of a SARL script is dedicated to declaring imported classes. Each time you want to use a feature defined in another package, (a different file) you include it with the import directive.

This directive works in a similar way as in the Java language.

The import keyword is followed by the qualified name of the feature to import. In the following code, the first directive imports java.util.List.

Optionally, you can import all the features defined by a package. This can be done by replacing the name of the feature by the wildcard character *. The second import directive is an example of the inclusion of all the classes defined in

import java.util.List

##3. Static Import Directive

Sometimes, it is necessary to import a class to access its statically defined functions, i.e., a function that can be called without any associated object’s instance.

To do this, you may invoke the static function with the fully qualified name of the class. For example, the function max is invoked with this syntax in the example below.

import java.util.Collections

		var col : Collection<Integer>

As an alternative, the static-import mechanism permits you to reference the function directly. A static import is specified with the static keyword just after the import keyword. The following identifier must be a fully qualified name of one or more functions (with the wildcard character).

In the example below, all the functions defined in java.util.Collections are imported. Following this import, it is possible to invoke a static function with its unqualified name, as the call to max below.

import static java.util.Collections.*

		var col : Collection<Integer>

##4. Top-Level Features

Most of a SARL script consists of the definitions of top-level features. These features are the core concepts of SARL, such as agent, event, or capacity. All these top-level features are documented in their own reference documents.

agent MyAgent {

event MyEvent

capacity MyCapacity {

Additionally, it is possible to write object-oriented statements with the SARL syntax for class, interface, enum, and annotation. The inclusion of these object-oriented statements will help you to write your application with a single language: SARL. The object-oriented programmation support is described in the reference documentation.


class MyClass {

interface MyInterface {

enum MyEnum {

annotation MyAnnotation {

##5. Acknowledgements

This documentation is inspired by the documentations from the Xtext and Xtend projects.

##6. Legal Notice

Copyright © 2014-2019 the original authors or authors.

Licensed under the Apache License, Version 2.0; you may not use this file except in compliance with the License. You may obtain a copy of the License.

You are free to reproduce the content of this page on copyleft websites such as Wikipedia.

Generated with the translator 0.10.0.