Hostname: page-component-89b8bd64d-46n74 Total loading time: 0 Render date: 2026-05-13T22:17:56.255Z Has data issue: false hasContentIssue false

Refactoring tools for functional languages

Published online by Cambridge University Press:  22 October 2013

SIMON THOMPSON
Affiliation:
School of Computing, University of Kent, Kent, UK (e-mail: s.j.thompson@kent.ac.uk, h.li@kent.ac.uk)
HUIQING LI
Affiliation:
School of Computing, University of Kent, Kent, UK (e-mail: s.j.thompson@kent.ac.uk, h.li@kent.ac.uk)
Rights & Permissions [Opens in a new window]

Abstract

Core share and HTML view are not available for this content. However, as you have access to this content, a full PDF is available via the 'Save PDF' action button.

Refactoring is the process of changing the design of a program without changing what it does. Typical refactorings, such as function extraction and generalisation, are intended to make a program more amenable to extension, more comprehensible and so on. Refactorings differ from other sorts of program transformation in being applied to source code, rather than to a ‘core’ language within a compiler, and also in having an effect across a code base, rather than to a single function definition, say. Because of this, there is a need to give automated support to the process. This paper reflects on our experience of building tools to refactor functional programs written in Haskell (HaRe) and Erlang (Wrangler). We begin by discussing what refactoring means for functional programming languages, first in theory, and then in the context of a larger example. Next, we address system design and details of system implementation as well as contrasting the style of refactoring and tooling for Haskell and Erlang. Building both tools led to reflections about what particular refactorings mean, as well as requiring analyses of various kinds, and we discuss both of these. We also discuss various extensions to the core tools, including integrating the tools with test frameworks; facilities for detecting and eliminating code clones; and facilities to make the systems extensible by users. We then reflect on our work by drawing some general conclusions, some of which apply particularly to functional languages, while many others are of general value.

Information

Type
Articles
Copyright
Copyright © Cambridge University Press 2013 
Submit a response

Discussions

No Discussions have been published for this article.