| Website: | website containing additional information | |||||||||||||||
| Course code: | INFOMTBPA | |||||||||||||||
| Credits: | 7.5 ECTS | |||||||||||||||
| Period: | periode 1 (week 36 t/m 45, dwz 3-9-2008 t/m 7-11-2008; herkansing week 1) | ![]() | ||||||||||||||
| Timeslot: | C | |||||||||||||||
| Participants: | up till now 3 subscriptions | |||||||||||||||
| Schedule: | Note: from now on the schedule is to be found in Osiris | |||||||||||||||
| Teachers: | Dit is een oud rooster!
| |||||||||||||||
| Contents: | Static program analysis aims at determining properties about the run-time behaviour of programs without actually executing the program. These properties are then typically used to either verify or optimise the program under analysis. Over the years, several methodologies for static program analysis have been developed. These include data-flow analysis, constraint-based approaches, and abstract interpretation. In this seminar, we focus on so-called type-based analyses. A type-based program analysis equips the programming language at hand with a nonstandard type system that stores the properties of interest in the types assignable to programs. An apparent advantage of the type-based approach is that we can reuse to a large extent the tools and techniques developed for ordinary type systems. Examples include polymorphism, subtyping, and type-inference algorithms. Within the seminar, we will read about and review the state of the art in type-based program analysis. A recurring theme in our exploration will be the intrinsic tension between accuracy and modularity, and the various ways to deal with this tension. | |||||||||||||||
| Literature: | Research papers (available on line). | |||||||||||||||
| Course form: | Introductory lectures, group discussions, presentations by participants. | |||||||||||||||
| Exam form: | Paper presentation (30%), mini-project (50%), participation (20%). | |||||||||||||||
| Minimum effort to qualify for 2nd chance exam: | To qualify for a second chance, the initial mark be at least 4. | |||||||||||||||