COMPSCI 61B Lecture Notes - Lecture 16: Abstract Type, Design Issues, Halting Problem
27 May 2017
School
Department
Course
Professor
Document Summary
If you haven"t make sure you"ve watched the video on getting started. Detailed information about project grading will be added early next week. Guerilla section this saturday (02/25) from 12-2 pm at soda 2nd oor labs. Majority of cost is in maintenance, not development. Good: checks for errors early, reads more like a story, speeds up runtime. Bad: not too exible, (casting), more verbose code. Bad: is a relationships only, the path of debugging gets annoying, can"t instantiate interfaces, implement every method of an interface. Testing: create automated code veri cation tools to bolster (but not prove) correctness. A general framework for proving that code is correct is impossible. Not even possible that a piece of code avoids going into an in nite loop (halting problem) Module: a set of methods that work together as a whole to perform some task or a set of related tasks.
