Lazy Dynamic Input/Output in the Lazy Functional Language Clean

Vervoort, Martijn; Plasmeijer, Rinus

doi:10.1007/3-540-44854-3_7

Cited by 17 publications

(14 citation statements)

References 5 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…Rossberg's language Alice likewise supports type-safe distributed programming [16]. The Clean language supports type-safe saving of arbitrary values (including function closures) into files [19]; a recent paper proposes a mechanism (not yet implemented) for solving class constraints at runtime [18, §4.2].…”

Section: Related Workmentioning

confidence: 99%

Towards Haskell in the cloud

2011

View full text Add to dashboard Cite

We present Cloud Haskell, a domain-specific language for developing programs for a distributed computing environment. Implemented as a shallow embedding in Haskell, it provides a messagepassing communication model, inspired by Erlang, without introducing incompatibility with Haskell's established shared-memory concurrency. A key contribution is a method for serializing function closures for transmission across the network. Cloud Haskell has been implemented; we present example code and some preliminary performance measurements.

show abstract

Section: Related Workmentioning

confidence: 99%

Towards Haskell in the cloud

2011

View full text Add to dashboard Cite

show abstract

“…It is also possible to reuse earlier created functions, which are stored on disk. Its implementation relies on the dynamic type system [1,21,25] of Clean.…”

Section: Higher-order G Ecsmentioning

confidence: 99%

GEC: A Toolkit for Generic Rapid Prototyping of Type Safe Interactive Applications

Achten

Eekelen

Plasmeijer

et al. 2005

Advanced Functional Programming

Self Cite

View full text Add to dashboard Cite

Programming GUIs with conventional GUI APIs is notori ously tedious. In these notes we present the GEC toolkit in which the programmer can create user interfaces without any knowledge of lowlevel I/O handling. Instead, he works with Graphical Editor Components (GEC). A GEC is an interactive component that is automatically derived from an arbitrary monomorphic data type, including higher order types. It contains a value of that data type, visualizes it, and allows the user to manipulate it in a type-safe way. The toolkit has a library of data types that represent standard GUI elements such as buttons, text fields, and so on. As a consequence, the programmer works with data types that model the interactive system that he is interested in. Programs are con structed as a collection of communicating GECs. This communication can be arranged in an ad-hoc way, or in a disciplined way, using a combinator library based on arrows. GECs are suitable for rapid prototyping of real world applications, for teaching and for debugging. These notes focus on the use of the GEC toolkit for functional programmers, only briefly explaining its inner workings and underlying principles.

show abstract

“…m em ory access violations, ty p e errors) in op eratin g system s by im plem enting a m icro kernel in C lean th a t provides ty p e safe com m unication of any value of any ty p e betw een functional processes, called Fam ke (F u n c tio n AE M icro K ernel E x perim ent) [15]. T his has shown th a t (m oderate) use of dynam ic typing [3], in com bination w ith C lean 's dynam ic ru n -tim e system and dynam ic linker [4,16], enables processes to com m unicate any d a ta (and even code) of any ty p e in a ty p e safe way. D uring th e developm ent of a shell/com m and line interface for our pro to ty p e functional o p eratin g system it becam e clear th a t a norm al shell cannot really m ake use (at run-tim e) of th e ty p e inform ation derived by th e com piler (at com pile-tim e).…”

Section: Introductionmentioning

confidence: 99%