Proceedings of the 6th ACM SIGACT-SIGPLAN Symposium on Principles of Programming Languages - POPL '79 1979
DOI: 10.1145/567752.567775
|View full text |Cite
|
Sign up to set email alerts
|

Type checking in an imperfect world

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
1
1
1

Citation Types

0
3
0

Year Published

1987
1987
1993
1993

Publication Types

Select...
3
2
1

Relationship

0
6

Authors

Journals

citations
Cited by 13 publications
(3 citation statements)
references
References 3 publications
0
3
0
Order By: Relevance
“…A forward inference makes predictions which are guaranteed to be correct, whereas backwardinferences only provide information which is required to be correct for the program to succeed at run-time. This distinction can be used to warn the programmer about type inconsistencies or to automatically generate minimal run-time time checks which guarantee the safety of the code [5]. We have currently focused primarily on forward inference rules.…”
Section: The Type Inference Systemmentioning
confidence: 99%
See 1 more Smart Citation
“…A forward inference makes predictions which are guaranteed to be correct, whereas backwardinferences only provide information which is required to be correct for the program to succeed at run-time. This distinction can be used to warn the programmer about type inconsistencies or to automatically generate minimal run-time time checks which guarantee the safety of the code [5]. We have currently focused primarily on forward inference rules.…”
Section: The Type Inference Systemmentioning
confidence: 99%
“…The imperative approach [4], [5], on the other hand, represents a program as a flowgraph whose nodes are assignment statements of the form Z ~ ~(XpX2,...,Xk). The types of all variables in a program are determined by repeatedly performing forward and backward inferences across these statements until fixed points are achieved.…”
Section: Introductionmentioning
confidence: 99%
“…Jones and Muchnick (31) also developed a general scheme for type determination, though their work was directed toward the language TEMPO. Miller (35) applied the work of Kaplan and Ullman to type checking. Type determination for the SETL language was studied by Tenenbaum (52,53) and Sharir (47).…”
Section: Literature Reviewmentioning
confidence: 99%