at:tutorial:symbiosis
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:tutorial:symbiosis [2007/06/19 10:39] – jdedecker | at:tutorial:symbiosis [2007/06/19 10:58] – jdedecker | ||
---|---|---|---|
Line 12: | Line 12: | ||
AmbientTalk has been implemented in Java. Because of this, Java plays two roles: it is both a symbiont language and the implementation language of AmbientTalk (and hence of the linguistic symbiosis itself). Figure \ref{fig: | AmbientTalk has been implemented in Java. Because of this, Java plays two roles: it is both a symbiont language and the implementation language of AmbientTalk (and hence of the linguistic symbiosis itself). Figure \ref{fig: | ||
- | {{: | + | {{: |
- | ===== Accessing Java classes | + | ===== Accessing Java from within AmbientTalk |
+ | |||
+ | |||
+ | ==== Accessing Java classes | ||
The complete set of classes that are available in the class path of a running JVM are accessible from AmbientTalk through the jlobby object. | The complete set of classes that are available in the class path of a running JVM are accessible from AmbientTalk through the jlobby object. | ||
Line 22: | Line 25: | ||
</ | </ | ||
- | ===== Creating Java objects | + | ==== Creating Java objects ==== |
Java classes can be instantiated in AmbientTalk similar to how AmbientTalk objects are instantiated, | Java classes can be instantiated in AmbientTalk similar to how AmbientTalk objects are instantiated, | ||
the Java constructor. For example, in the snippet code below **new** method is invoked on the class **Vector**. | the Java constructor. For example, in the snippet code below **new** method is invoked on the class **Vector**. | ||
Line 38: | Line 41: | ||
</ | </ | ||
- | ===== Invoking methods on Java objects | + | ==== Invoking methods on Java objects ==== |
Java objects appear as AmbientTalk objects whose field and method slots correspond to public instance-level fields and methods in the Java object. These are accessed or invoked as if they were plain AmbientTalk slots. | Java objects appear as AmbientTalk objects whose field and method slots correspond to public instance-level fields and methods in the Java object. These are accessed or invoked as if they were plain AmbientTalk slots. | ||
Line 48: | Line 51: | ||
</ | </ | ||
+ | The AmbientTalk/ | ||
- | ===== Overloading ===== | + | ==== Overloading ==== |
+ | In Java methods can be overloaded based on the number of arguments and the types of the arguments. | ||
+ | If the Java method is overloaded based on arity (i.e. each overloaded method takes a different number of arguments), the number of arguments in the AmbientTalk invocation can be used to identify a unique Java method. Hence, overloading based on arity does not require special attention. If the Java method is overloaded based solely on argument types, the interpreter may derive that the actual arguments can only be converted from AmbientTalk to the appropriate Java types for one of the matching overloaded signatures. Again, if only one match remains, the unique match is invoked. In the remaining case in which the actual AmbientTalk arguments satisfy more than one overloaded method signature, the symbiotic invocation fails. It is then the AmbientTalk programmer' | ||
+ | |||
+ | < | ||
+ | Add code that shows how to disambiguate between overloaded methods | ||
+ | </ | ||
- | ===== Concurrency | + | ==== Concurrency ==== |
- | ===== Distribution | + | ===== Accessing AmbientTalk from within Java ===== |
===== Using Java wrappers ===== | ===== Using Java wrappers ===== |
at/tutorial/symbiosis.txt · Last modified: 2013/05/17 20:25 by tvcutsem