Writing systems software in a functional language: an experience report

Authors:
Iavor S. Diatchki;Thomas Hallgren;Mark P. Jones;Rebekah Leslie;Andrew Tolmach
Affiliations:
-;-;-;-;-
Venue:
Proceedings of the 4th workshop on Programming languages and operating systems
Year:
2007

Citing 8
Cited 1

How to make ad-hoc polymorphism less ad hoc

POPL '89 Proceedings of the 16th ACM SIGPLAN-SIGACT symposium on Principles of programming languages
The C programming language

The C programming language
Building reliable, high-performance communication systems from components

Proceedings of the seventeenth ACM symposium on Operating systems principles
A principled approach to operating system construction in Haskell

Proceedings of the tenth ACM SIGPLAN international conference on Functional programming
High-level views on low-level representations

Proceedings of the tenth ACM SIGPLAN international conference on Functional programming
Strongly typed memory areas programming systems-level data structures in a functional language

Proceedings of the 2006 ACM SIGPLAN workshop on Haskell
Singularity: rethinking the software stack

ACM SIGOPS Operating Systems Review - Systems work at Microsoft Research
A general framework for certifying garbage collectors and their mutators

Proceedings of the 2007 ACM SIGPLAN conference on Programming language design and implementation

Kenro: a virtual machine monitor mostly described in Haskell

Proceedings of the 2009 ACM symposium on Applied Computing

Quantified Score

Hi-index	0.00

Visualization

Abstract

Current practices for developing systems software usually rely on fairly low-level programming languages and tools. As an alternative, our group has been investigating the possibility of using a high-level functional language, Haskell, for kernel and device driver construction, with the hope that it will allow us to produce more reliable and secure software. In this paper, we describe our experience developing a prototype operating system, House, in which the kernel, device drivers, and even a simple GUI, are all written in Haskell. The House system demonstrates that it is indeed possible to construct systems software in a functional language. However, it also suggests some ideas for a new Haskell dialect with features that target specific needs in this domain, including strongly typed support for low-level data structures and facilities for explicit memory accounting.