AmbientTalk

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
Paradigmobject-oriented (prototype-based) Concurrent Event-driven Reflective
Designed byTom Van Cutsem, Stijn Mostinckx, Jessie Dedecker, Wolfgang De Meuter
DeveloperSoftware Languages Lab, University of Brussels
First appeared2006
Stable release
2.19 / April 2011
Typing disciplinedynamic, strong
OSPlatform-independent
LicenseMIT License
Filename extensions.at
Websitehttp://soft.vub.ac.be/amop
Major implementations
AmbientTalk (interpreter)
Influenced by
Smalltalk, Self, Scheme, E, ABCL
Influenced
ECMAScript Harmony

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 their name, and greet them */
            when: other<-getName()@FutureMessage becomes: {|name|
                system.println("Hello " + name + " from " + myName);
            };
        };
    };
};

/* Spawn 2 actors that will greet each other */
makeGreeter("Alice");
makeGreeter("Bob");
gollark: GTech™ nation 84102/A6-H.
gollark: <@319753218592866315> Is this canon?
gollark: What if Macron uses NFTs for borrow checking?
gollark: If they agree to buy it, our ethics machines think it's entirely okay.
gollark: Actually, if the market wills it, it's ethical.

References
  1. 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
This article is issued from Wikipedia. The text is licensed under Creative Commons - Attribution - Sharealike. Additional terms may apply for the media files.