AmbientTalk
| Paradigm | object-oriented (prototype-based) Concurrent Event-driven Reflective |
|---|---|
| Designed by | Tom Van Cutsem, Stijn Mostinckx, Jessie Dedecker, Wolfgang De Meuter |
| Developer | Software Languages Lab, University of Brussels |
| First appeared | 2006 |
| Stable release | 2.19
/ April 2011 |
| Typing discipline | dynamic, strong |
| OS | Platform-independent |
| License | MIT License |
| Filename extensions | .at |
| Website | http://soft.vub.ac.be/amop |
| Major implementations | |
| AmbientTalk (interpreter) | |
| Influenced by | |
| Smalltalk, Self, Scheme, E, ABCL | |
| Influenced | |
| ECMAScript Harmony | |
AmbientTalk is an experimental object-oriented distributed programming language developed at the Programming Technology Laboratory at the Vrije Universiteit Brussel, Belgium. The language is primarily targeted at writing programs deployed in mobile ad hoc networks.
AmbientTalk is meant to serve as an experimentation platform to experiment with new language features or programming abstractions to facilitate the construction of software that has to run in highly volatile networks exhibiting intermittent connectivity and little infrastructure.[1] It is implemented in Java which enables interpretation on various platforms, including Android. The interpreter standard library also provides a seamless interface between Java and AmbientTalk objects, called the symbiosis.
The language's concurrency features, which include support for futures and event-loop concurrency, are founded on the actor model and have been largely influenced by the E programming language. The language's object-oriented features find their influence in languages like Smalltalk (i.e. block closures, keyworded messages) and Self (prototype-based programming, traits, delegation).
Hello world
system.println("Hello world");
The classical "Hello, World!" program is not very representative of the language features. However, consider its distributed version:
/* Define types that could be discovered on the network */
deftype Greeter;
def makeGreeter(myName) {
/* Spawn an actor */
actor: {
/* Actors have a separate namespace, include the language futures in it */
import /.at.lang.futures;
/* A method that could be called by other greeters */
def getName(){myName};
/* Export this actor on the network */
export: self as: Greeter;
/* Main logic: if we discover another Greeter ... */
whenever: Greeter discovered: {|other|
/* Asynchronously get his name, and greet him */
when: other<-getName()@FutureMessage becomes: {|name|
system.println("Hello " + name + " from " + myName);
};
};
};
};
/* Spawn 2 actors that will greet each other */
makeGreeter("Alice");
makeGreeter("Bob");
References
- ^ Dedecker J., Van Cutsem T., Mostinckx S., D'Hondt T., De Meuter W. Ambient-oriented Programming in AmbientTalk. In “Proceedings of the 20th European Conference on Object-Oriented Programming (ECOOP), Dave Thomas (Ed.), Lecture Notes in Computer Science Vol. 4067, pp. 230-254, Springer-Verlag.”, 2006