This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision | ||
at:introduction [2007/04/07 11:12] tvcutsem *minor |
at:introduction [2008/07/15 12:19] tvcutsem * |
||
---|---|---|---|
Line 1: | Line 1: | ||
- | ===== What is AmbientTalk? | ||
- | |||
- | {{: | ||
- | |||
- | For the programming language adepts: AmbientTalk is: | ||
- | * **dynamically typed**, which is **not** the same as being untyped: AmbientTalk //values// are typed, but // | ||
- | * object-oriented, | ||
- | * event-driven: | ||
- | * distributed: | ||
- | * **symbiotic**: | ||
- | |||
- | A word of warning, though: AmbientTalk is **not** a stable development platform. Rather, it is a research artifact used as a " | ||
- | |||
- | ==== AmbientTalk in a nutshell ==== | ||
- | |||
- | Enough talking, let's delve into some AmbientTalk code by means of a simple example to see whether we can spark your interest in AmbientTalk. The demo program we're about to explore is an extremely simple instant messenger program. Each instant messenger runs on e.g. a PDA, laptop or cell phone. When peers join the ad hoc network, the instant messenger should issue a warning to the user that a new buddy is available for chatting. The user can then send simple text messages to that buddy. Off we go: | ||
- | |||