The interactive ambienttalk shell (aka iat) is the command-line interpreter of AmbientTalk. iat supports a very simple read-eval-print loop mode: you can type in expressions (currently only single-line expressions), evaluate them by pressing return and see the value of the expression, for example:
>[1,2,3].map: { |e| e*e }
>>[1,4,9]
To start iat, it suffices to execute it from the command-line, provided the java executable of a JDK1.3.3 or higher JVM is on your executable search path. The shell script that starts iat works as follows:
iat [options] [file] [arguments]
Perhaps the most useful usage of iat is to start it with an AmbientTalk source file as argument, e.g.:
iat foo.at
This will make iat evaluate all of the contents of the file foo.at and print out the value of the last expression in the file. If -p was not specified on the command line, iat falls into a read-eval-print loop such that you can play around with the definitions loaded from the file. Any arguments following the filename are treated as arguments to the AmbientTalk program, not to iat. They are accessible by evaluating system.getArgv().
To get an overview of all available options, execute:
iat --help
The AmbientTalk shell understands a limited number of “shell commands”. All input starting with a colon (“:”) is treated by iat as a shell command. The following commands are supported:
:q or :quit ⇒ quit the interpreter.:l or :load filepath ⇒ load a file (relative to the directory in which iat was invoked). The content of the file is evaluated as if the file was passed as argument to the shell during startup. The public definitions of the loaded file will be available at top-level.
The AmbientTalk shell enables very simple input and output operations by means of the top-level system object. Here is how to output text to the command-line:
system.println("Hello world");
Reading a line of text from the command-line is a bit less straightforward:
system.readNextLine: { |line|
system.println("I read: "+line)
} catch: { |ioException| /* ignored */ }
The code between { and } basically serves as a callback function which will be invoked when the next line has been read. The reason for this callback-style read function is that AmbientTalk code may never be blocking. The rationale behind this execution model is explained later, in the chapter on actors.