CIS 2250 Lecture 3: Reading Code
22 Apr 2017
School
Department
Course
Professor
Document Summary
Who are you: developer, maintenance, quality assurance, tester, manager, student/trainee. Loops particularly how they begin and end one off errors. Clues to the meaning of the function or variable. Don"t (cid:271)e afraid to do a glo(cid:271)al repla(cid:272)e! Loops so much fun, so little time! Loops are the source of many errors so if you are reading for errors, pay special attention to loops. Loops do much work for a program they are one of the keys to performance. Read documentation on the library and this particular call. Examine the parameters how were they set and how does this affect called procedure. If the code is long then break it into chunks (may be the authors of the software should have done this) to read it and then see if indeed it should have been modularized more. Investigate known problems with code (this particular code or code in general) Depends on why you are reading the code: debugging, security, refactoring.
