CSCI 103L Lecture Notes - Lecture 5: Compile Time, Null Character
10 Mar 2016
School
Department
Course
Professor
Document Summary
The loops that keep on giving: bad to get stuck in an in nite loop. Control + c force quits out of an in nite loop. Single statement loops and if statements don"t need { }"s, but it"s good practice to always use them: nested loops. Inner loops execute fully inside the body of the outer loop. Nested loops are useful for tables, row and column: break and continue. Break: end the current loop immediately and continue execution after its last statement. Ex: if (tries > 100) { break; } Continue: begins the next iteration of the nearest loop: Ex: if guess is wrong continue; (start the loop over again) Break is used more commonly continue not as much: preprocessor and directives. Compiler will scan through c code looking for directives: ex: #include #de ne, anything that starts with , inserts text from an outside le, #include < lename> or #include lename, #de ne nd_pattern replace_pattern.
