at:introduction
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revisionNext revisionBoth sides next revision | ||
at:introduction [2007/04/11 12:39] – tvcutsem | at:introduction [2007/10/11 15:17] – * tvcutsem | ||
---|---|---|---|
Line 8: | Line 8: | ||
* flexible: like Smalltalk, Self and Ruby, AmbientTalk embraces the use of elegant and expressive **block closures** to achieve a level of reusability far exceeding that of Java or similar languages lacking true closures. | * flexible: like Smalltalk, Self and Ruby, AmbientTalk embraces the use of elegant and expressive **block closures** to achieve a level of reusability far exceeding that of Java or similar languages lacking true closures. | ||
* event-driven: | * event-driven: | ||
- | * distributed: | + | * distributed: |
* **symbiotic**: | * **symbiotic**: | ||
Line 40: | Line 40: | ||
| | ||
// engage in peer-to-peer service discovery | // engage in peer-to-peer service discovery | ||
- | | + | |
export: remoteInterface as: InstantMessenger; | export: remoteInterface as: InstantMessenger; | ||
whenever: InstantMessenger discovered: { |messenger| | whenever: InstantMessenger discovered: { |messenger| | ||
Line 51: | Line 51: | ||
An instant messenger object is created by invoking a function called '' | An instant messenger object is created by invoking a function called '' | ||
- | Within the lexical scope of the '' | + | Within the lexical scope of the '' |
The '' | The '' | ||
Line 79: | Line 79: | ||
The '' | The '' | ||
- | Also interesting is the initialisation code of the '' | + | Also interesting is the initialisation code of the '' |
Now let us delve into the details of the local interface object: | Now let us delve into the details of the local interface object: | ||
Line 132: | Line 132: | ||
< | < | ||
- | | + | |
export: remoteInterface as: InstantMessenger; | export: remoteInterface as: InstantMessenger; | ||
whenever: InstantMessenger discovered: { |messenger| | whenever: InstantMessenger discovered: { |messenger| | ||
Line 152: | Line 152: | ||
</ | </ | ||
- | The '' | + | The '' |
Finally, notice how AmbientTalk allows you to deal with //partial failures//: you can register two kinds of // | Finally, notice how AmbientTalk allows you to deal with //partial failures//: you can register two kinds of // | ||
Line 170: | Line 170: | ||
* no need to generate stubs, skeletons or other kinds of proxies to manage remote objects | * no need to generate stubs, skeletons or other kinds of proxies to manage remote objects | ||
- | Of course, we are not claiming that AmbientTalk is a good replacement for standards such as CORBA, which are much more flexible, at the cost of increasted | + | Of course, we are not claiming that AmbientTalk is a good replacement for distributed computing |
So, you read the introduction and are interested in all of the gory details of the language? In that case, you can go ahead and [[at: | So, you read the introduction and are interested in all of the gory details of the language? In that case, you can go ahead and [[at: |
at/introduction.txt · Last modified: 2008/07/15 12:19 by tvcutsem