at:tutorial:reflection
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:reflection [2007/06/29 11:14] – Added stijnm | at:tutorial:reflection [2007/07/18 13:21] – tvcutsem | ||
---|---|---|---|
Line 6: | Line 6: | ||
===== Mirrors ===== | ===== Mirrors ===== | ||
- | As we have already mentioned in the introduction, | + | AmbientTalk uses a mirror-based architecture to provide reflective access to its objects. The basic principle of a mirror-based architecture is that all reflective facilities are encapsulated in a mirror object which provides reflective access to precisely one object, its reflectee. Moreover, the mirror of the object is not directly accessible as a slot of the object. Instead, a separate factory must be used to create mirrors, which allows the program to hand out different mirrors according to the dynamic call chain, the requesting object etc. The factory can be used implicitly using the '' |
< | < | ||
def baseObject := object: { | def baseObject := object: { | ||
def field := nil; | def field := nil; | ||
- | def canonicalMethod() { nil } | + | def canonicalMethod() { nil }; |
- | def keyworded: arg1 method: arg2 { nil } | + | def keyworded: arg1 method: arg2 { nil }; |
}; | }; | ||
def mirror := reflect: baseObject; | def mirror := reflect: baseObject; | ||
def slots := mirror.listSlots(); | def slots := mirror.listSlots(); | ||
- | slots.each: { | slot | system.println() }; | + | slots.each: { | slot | system.println(slot) }; |
</ | </ | ||
Line 34: | Line 34: | ||
===== Mirages ===== | ===== Mirages ===== | ||
- | Extending the AmbientTalk core language involves adding objects which have a different implementation for some of the default meta-operations. In this part of the tutorial we describe how a programmer could define objects which allow for the dynamic addition of unknown methods and fields. First of all, we need to create a mirror instance which we can use to create new objects from. This can be performed using the '' | + | Extending the AmbientTalk core language involves adding objects which have a different implementation for some of the default meta-operations. In this part of the tutorial, we describe how a programmer could define objects which allow for the dynamic addition of unknown methods and fields. First of all, we need to create a mirror instance which we can use to create new objects from. This can be performed using the '' |
< | < | ||
Line 47: | Line 47: | ||
} else: { | } else: { | ||
super^doesNotUnderstand(selector); | super^doesNotUnderstand(selector); | ||
- | } | + | }; |
- | } | + | }; |
} | } | ||
</ | </ | ||
- | This mirror overrides the default implementation of the meta-operation '' | + | This mirror overrides the default implementation of the meta-operation '' |
< | < | ||
Line 68: | Line 68: | ||
Whereas the example provided above may seem a little contrived, the reflective capabilities of AmbientTalk allow it to be extended with many abstraction relating to distributed computing for mobile ad hoc networks (AmbientTalk' | Whereas the example provided above may seem a little contrived, the reflective capabilities of AmbientTalk allow it to be extended with many abstraction relating to distributed computing for mobile ad hoc networks (AmbientTalk' | ||
- | ===== Meta-Object | + | ===== The Metaobject |
The Meta-Object Protocol of AmbientTalk can be divided into a series of independent protocols. Whereas the full semantics and signature of the meta-methods can be found in the [[http:// | The Meta-Object Protocol of AmbientTalk can be divided into a series of independent protocols. Whereas the full semantics and signature of the meta-methods can be found in the [[http:// |
at/tutorial/reflection.txt · Last modified: 2010/11/16 16:32 by tvcutsem