Lucid (programming language)
{{Short description|Dataflow programming language}}
{{For|the Lisp software company|Lucid Inc.}}
{{primary sources|date=April 2018}}
{{Infobox programming language
|name = Lucid
|logo =
|paradigm = Dataflow
|year = 1976
|designer = Edward A. Ashcroft
William W. Wadge
|developer =
|latest release version =
|latest release date =
|typing = Typeless
|implementations = pLucid, GIPSY
|dialects = Granular Lucid, Indexical Lucid, Tensor Lucid, Forensic Lucid, Lucx, JOOIPL
|influenced_by = ISWIM
|influenced = SISAL, PureData, Lustre
}}
Lucid is a dataflow programming language designed to experiment with non-von Neumann programming models. It was designed by Bill Wadge and Ed Ashcroft and described in the 1985 book Lucid, the Dataflow Programming Language.
pLucid was the first interpreter for Lucid.
Model
Lucid uses a demand-driven model for data computation. Each statement can be understood as an equation defining a network of processors and communication lines between them through which data flows. Each variable is an infinite stream of values and every function is a filter or a transformer. Iteration is simulated by 'current' values and 'fby' (read as 'followed by') operator allowing composition of streams.
Lucid is based on an algebra of histories, a history being an infinite sequence of data items. Operationally, a history can be thought of as a record of the changing values of a variable, history operations such as first and next can be understood in ways suggested by their names. Lucid was originally conceived as a disciplined, mathematically pure, single-assignment language, in which verification would be simplified. However, the dataflow interpretation has been an important influence on the direction in which Lucid has evolved.[https://web.archive.org/web/20110514103454/http://hopl.murdoch.edu.au/showlanguage2.prx?exp=960]
Details
In Lucid (and other dataflow languages) an expression that contains a variable that has not yet been bound waits until the variable has been bound, before proceeding. An expression like x + y
will wait until both x and y are bound before returning with the output of the expression. An important consequence of this is that explicit logic for updating related values is avoided, which results in substantial code reduction, compared to mainstream languages.
Each variable in Lucid is a stream of values. An expression n = 1 fby n + 1
defines a stream
using the operator 'fby' (a mnemonic for "followed by"). fby defines what comes after the previous
expression. (In this instance the stream produces 1,2,3,...).
The values in a stream can be addressed by these operators (assuming x is the variable being used):
'first x'
- fetches the first value in the stream x,
'x'
- the current value of the stream,
'next x'
- fetches the next value in the stream.
'asa'
- an operator that does some thing 'as soon as' the condition given becomes true.
'x upon p'
- upon is an operator that repeats the old value of the stream x, and updates to the new values only when the stream p makes a true
value available. (It serves to slow down the stream x)
i.e.: x upon p
is the stream x with new values appearing upon the truth of p.
The computation is carried out by defining filters or transformation functions that act on these time-varying streams of data.
Examples
=Factorial=
{{main|Factorial}}
fac
where
n = 0 fby (n + 1);
fac = 1 fby ( fac * (n + 1) );
end
=Fibonacci sequence=
{{main|Fibonacci sequence}}
fib
where
fib = 0 fby ( 1 fby fib + next fib );
end
=Total of a Sequence=
total
where
total = 0 fby total + x
end;
=Running average=
{{main|Running average}}
running_avg
where
sum = first(input) fby sum + next(input);
n = 1 fby n + 1;
running_avg = sum / n;
end;
=Prime numbers=
{{main|Prime number}}
prime
where
prime = 2 fby (n whenever isprime(n));
n = 3 fby n+1;
isprime(n) = not(divs) asa divs or prime*prime > N
where
N is current n;
divs = N mod prime eq 0;
end;
end
==Dataflow diagram==
{{main|Dataflow diagram}}
=Quick sort=
{{main|Quick sort}}
qsort(a) = if eof(first a) then {{not a typo|a}} else follow(qsort(b0),qsort(b1)) fi
where
p = first a < a;
b0 = a whenever p;
b1 = a whenever not p;
follow(x,y) = if xdone then y upon xdone else x fi
where
xdone = iseod x fby xdone or iseod x;
end
end
==Data flow diagram==
--------> whenever -----> qsort ---------
| ^ |
| | |
| not |
| ^ |
|---> first | |
| | | |
| V | |
|---> less --- |
| | |
| V V
---+--------> whenever -----> qsort -----> conc -------> ifthenelse ----->
| ^ ^
| | |
--------> next ----> first ------> iseod -------------- |
| |
-----------------------------------------------------------
=Root mean square=
{{main|Root mean square}}
sqroot(avg(square(a)))
where
square(x) = x*x;
avg(y) = mean
where
n = 1 fby n+1;
mean = first y fby mean + d;
d = (next y - mean)/(n+1);
end;
sqroot(z) = approx asa err < 0.0001
where
Z is current z;
approx = Z/2 fby (approx + Z/approx)/2;
err = abs(square(approx)-Z);
end;
end
=Hamming problem=
{{main|Hamming problem}}
h
where
h = 1 fby merge(merge(2 * h, 3 * h), 5 * h);
merge(x,y) = if xx <= yy then xx else yy fi
where
xx = x upon xx <= yy;
yy = y upon yy <= xx;
end;
end;
==Dataflow Diagram==
File:Hamming problem dataflow diagram (Lucid).png dataflow diagram]]
References
{{Reflist|refs=
| first1 = William W.
| last1 = Wadge
| first2 = Edward A.
| last2 = Ashcroft
| date = 1985
| title = Lucid, the Dataflow Programming Language
| publisher = Academic Press
| isbn = 0-12-729650-6
| url = https://archive.org/details/luciddataflowpro00wadg_0
| access-date = 8 January 2015
| url-access = registration
}}
}}
External links
- [https://code.google.com/p/plucid/ pLucid]
{{Authority control}}
Category:Academic programming languages
Category:Concurrent programming languages
Category:Declarative programming languages
Category:Experimental programming languages