1997
DOI: 10.1007/bfb0032736
|View full text |Cite
|
Sign up to set email alerts
|

Towards a cost-effective estimation of uncaught exceptions in SML programs

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
4
1

Citation Types

0
21
0

Year Published

1998
1998
2014
2014

Publication Types

Select...
5
3
2

Relationship

0
10

Authors

Journals

citations
Cited by 18 publications
(21 citation statements)
references
References 9 publications
0
21
0
Order By: Relevance
“…Our choice of the terms constructor and destructor is inspired by work on detecting uncaught exceptions in functional programs [18,17] and soft typing [4,1]. A core issue in both bodies of work is tracking which datatype constructors a program value may actually have at run-time.…”
Section: Related Workmentioning
confidence: 99%
“…Our choice of the terms constructor and destructor is inspired by work on detecting uncaught exceptions in functional programs [18,17] and soft typing [4,1]. A core issue in both bodies of work is tracking which datatype constructors a program value may actually have at run-time.…”
Section: Related Workmentioning
confidence: 99%
“…Robillard and G.C. Murphy Yi and Ryu [1997] developed a more efficient one using control-flow analysis and a set-constraints framework [Heintze 1992].…”
Section: Related Workmentioning
confidence: 99%
“…Many exception flow analyses augment the type system of the underlying programming language with information about the exceptions that can be thrown by a particular language construct [9,10,11,12,13,14,15,16]. The analyses differ in their representation of the inferred exception clauses, and the speed and precision of the analysis, but the principle is always the same.…”
Section: Related Workmentioning
confidence: 99%