Return to the
comp.compilers page.
Search the
comp.compilers archives again.
| Related articles |
|---|
| Incremental compiling torleifs@idi.ntnu.no (Torleif Sandnes) (2000-09-09) |
| Re: Incremental compiling jpsecher@mailme.dk (Jens Peter Secher) (2000-09-15) |
| Re: Incremental compiling torleifs@idi.ntnu.no (2000-09-21) |
| Re: Incremental compiling donawa@home.com (2000-10-15) |
| Incremental compiling yaqob@compsci.bristol.ac.uk (H. Yaqob) (1997-06-30) |
| Re: Incremental compiling dglaston@asc.corp.mot.com (Daniel Glastonbury) (1997-07-04) |
| From: | Jens Peter Secher <jpsecher@mailme.dk> |
| Newsgroups: | comp.compilers |
| Date: | 15 Sep 2000 01:35:04 -0400 |
| Organization: | DIKU |
| References: | 00-09-082 |
| Keywords: | incremental |
A (very theoretical) treatment can be found in
Trevor Jim, "<a href =
"http://www.cis.upenn.edu/~tjim/papers/principal-typings.ps.gz">What
are Principal Typings and What are they Good For?</a>"
The paper is about how to design type systems such that they infer a
(least) type for a module and what is /needed by the type environment/
for this type to be correct. In effect, one can avoid recompilation as
long as the /type/ interfaces do not change.
Cheers,
Jens Peter
--
echo "J. P. Secher, DIKU (DK)" |tr -d '. )'|tr ',([:upper:]' '@.[:lower:]'\
|awk -F@ '{print $0 "\t\twww." $2 "/~" $1}'
Return to the
comp.compilers page.
Search the
comp.compilers archives again.