Gradual typing of erlang programs: A wrangler experience

Sagonas, K; Luna, D

dc.contributor.author	Sagonas, K	en
dc.contributor.author	Luna, D	en
dc.date.accessioned	2014-03-01T02:45:18Z
dc.date.available	2014-03-01T02:45:18Z
dc.date.issued	2008	en
dc.identifier.uri	https://dspace.lib.ntua.gr/xmlui/handle/123456789/32262
dc.subject	Contracts	en
dc.subject	Dialyzer	en
dc.subject	Erlang	en
dc.subject	Software defect detection	en
dc.subject.other	Code re-factoring	en
dc.subject.other	Dialyzer	en
dc.subject.other	Erlang	en
dc.subject.other	Erlang programs	en
dc.subject.other	Large parts	en
dc.subject.other	Software defect detection	en
dc.subject.other	Source codes	en
dc.subject.other	Type informations	en
dc.subject.other	Defects	en
dc.title	Gradual typing of erlang programs: A wrangler experience	en
heal.type	conferenceItem	en
heal.identifier.primary	10.1145/1411273.1411284	en
heal.identifier.secondary	http://dx.doi.org/10.1145/1411273.1411284	en
heal.publicationDate	2008	en
heal.abstract	Currently most Erlang programs contain no or very little type information. This sometimes makes them unreliable, hard to use, and difficult to understand and maintain. In this paper we describe our experiences from using static analysis tools to gradually add type information to a medium sized Erlang application that we did not write ourselves: the code base of Wrangler. We carefully document the approach we followed, the exact steps we took, and discuss possible difficulties that one is expected to deal with and the effort which is required in the process. We also show the type of software defects that are typically brought forward, the opportunities for code refactoring and improvement, and the expected benefits from embarking in such a project. We have chosen Wrangler for our experiment because the process is better explained on a code base which is small enough so that the interested reader can retrace its steps, yet large enough to make the experiment quite challenging and the experiences worth writing about. However, we have also done something similar on large parts of Erlang/OTP. The result can partly be seen in the source code of Erlang/OTP R12B-3. Copyright © 2008 ACM.	en
heal.journalName	Erlang'08: Proceedings of the 2008 SIGPLAN Erlang Workshop	en
dc.identifier.doi	10.1145/1411273.1411284	en
dc.identifier.spage	73	en
dc.identifier.epage	81	en