Difference between revisions of "Denotative continuous-time programming (Conal Elliott)"
From apm
(added basic definition) |
(→Related: * Tracing trajectories of component in machine phase) |
||
| Line 20: | Line 20: | ||
== Related == | == Related == | ||
| + | |||
| + | * Somewhat related: [[Tracing trajectories of component in machine phase]] | ||
| + | |||
| + | == External links == | ||
| + | |||
| + | === Related === | ||
* [https://futureofcoding.org/essays/dctp.html The Misunderstood Roots of FRP Can Save Programming (on futureofcoding.org – 2019)] | * [https://futureofcoding.org/essays/dctp.html The Misunderstood Roots of FRP Can Save Programming (on futureofcoding.org – 2019)] | ||
Revision as of 12:20, 11 October 2023
Formerly called "functional reactive programming" (FRP).
But the meaning associated with the term drifted so far away from the original idea that
it was renamed to "denotative continuous-time programming" (DCTP).
Definition
(Taken from Conal Elliotts' slides)
Two fundamental properties of DCTP:
- Precise, simple denotation. (Elegant & rigorous.)
- Continuous time. (Natural & composable.)
Not DCTP:
- graphs
- updates and propagation
- streams (since they are a discrete model, despite the name)
- doing
Related
- Somewhat related: Tracing trajectories of component in machine phase
External links
Related
- The Misunderstood Roots of FRP Can Save Programming (on futureofcoding.org – 2019)
- Why program with continuous time? (blog-post 2010-01-02)
- Aswer to "Specification for a Functional Reactive Programming language" (2011)
- Video: Lambda Jam 2015 - Conal Elliott - The Essence and Origins of Functional Reactive Programming (2015-01-18)
Links needing review
- Notes of Steve Krouse of DCTP (2018)
- An Introduction to Denotative Continuous Spacetime Programming (Work in Progress) – (Mon 16 Nov 2020) – Adriaan Leijnse – Universidade NOVA de Lisboa
- discussion of DCTP on ycombinator hacker news (2019-11-03)
