Joule (programming language)

Joule
Paradigm	multi-paradigm: object-oriented, distributed, Dataflow
Designed by	E. Dean Tribble
First appeared	1996
Typing discipline	untyped
Influenced by
	Concurrent Logic Programming, Actors
Influenced
	E

Joule is a capability-secure massively-concurrent dataflow programming language, designed for building distributed applications.^[1] It is so concurrent that the order of statements within a block is irrelevant to the operation of the block. Statements are executed whenever possible, based on their inputs. Everything in Joule happens by sending messages. There is no control flow. Instead, the programmer describes the flow of data, making it a dataflow programming language.^{[citation needed]}

Joule development started in 1994 at Agorics in Palo Alto, California.^[2] It is considered the precursor to the E programming language.^[3]^[4]

Language syntax

Numerals consist of ASCII digits 0–9; identifiers are Unicode sequences of digits, letters, and operator characters that begin with a letter. It is also possible to form identifiers by using Unicode sequences (including whitespace) enclosed by either straight (' ') or standard (‘ ’) single quotes, where the backslash is the escape character. Keywords have to start with a letter, except the • keyword to send information. Operators consist of Unicode sequences of digits, letters, and operator characters, beginning with an operator character. Labels are identifiers followed by a colon (':').^[5]

At the root, Joule is an imperative language and because of that a statement-based language. It has a rich expression syntax, which transforms easily to its relational syntax underneath. Complex expressions become separate statements, where the site of the original expression is replaced by a reference to the acceptor of the results channel. Therefore, nested expressions still compute completely concurrently with their embedding statement.^[5]

   If amount <= balance
       • account withdraw: amount
   else
       • account report-bounce:
   end

An identifiers may name a channel to communicate with the server. If this is the case, it is said to be bound to that channel.^[5]

References

^ Miller, Mark Samuel (2006). "Robust composition: towards a unified approach to access control and concurrency control". Johns Hopkins University. Cite journal requires |journal= (help)
^ Fremont, David (October 1994). "Waiting for the cyber-ax". Spin. 10 (7): 88.
^ "Related Links to Agoric Computing & Smart Contracts". erights.org. E's debt to Joule cannot be overstated.
^ "The E Programmer's Manual". Electric Communities. 19 July 1996. The E programming language was largely inspired by the language Joule, currently being developed by Dean Tribble, Norm Hardy, and their colleagues at Agorics, Inc.
^ ^a ^b ^c "Joule: Distributed Application Foundations: 4.2. Expressions" (PDF). 1. Agorics, Inc. 20 December 2004: 31–33. Retrieved 2012-08-29. Cite journal requires |journal= (help)

External links

This programming-language-related article is a stub. You can help Wikipedia by expanding it.

[1] Miller, Mark Samuel (2006). "Robust composition: towards a unified approach to access control and concurrency control". Johns Hopkins University. Cite journal requires |journal= (help)

[2] Fremont, David (October 1994). "Waiting for the cyber-ax". Spin. 10 (7): 88.

[3] "Related Links to Agoric Computing & Smart Contracts". erights.org. E's debt to Joule cannot be overstated.

[4] "The E Programmer's Manual". Electric Communities. 19 July 1996. The E programming language was largely inspired by the language Joule, currently being developed by Dean Tribble, Norm Hardy, and their colleagues at Agorics, Inc.

[Draft95-5] "Joule: Distributed Application Foundations: 4.2. Expressions" (PDF). 1. Agorics, Inc. 20 December 2004: 31–33. Retrieved 2012-08-29. Cite journal requires |journal= (help)

[1]

[2]

[3]

[4]

[5]