Difference between revisions of "Control Structures"
From CompSciWiki
m (Change italic to bold in intro) |
|||
| (10 intermediate revisions by 4 users not shown) | |||
| Line 1: | Line 1: | ||
| − | {{1010Chapter|Introduction='''Control Structures''' are blocks of code that force the computer to make a decision. Sometimes you will want your program to perform different tasks depending on certain [[boolean]] conditions. For example if you were writing a game you would probably find it very useful to be able to know when the user has won the game so that you could show a high scores page. | + | {{1010Chapter |
| + | |ChapterNum=4 | ||
| + | |Picture=Wiki_sign01.jpg | ||
| + | |Introduction='''Control Structures''' are blocks of code that force the computer to make a decision. Sometimes you will want your program to perform different tasks depending on certain [[Common Primitive Variables#Primitive Type boolean|boolean]] conditions. For example if you were writing a game you would probably find it very useful to be able to know when the user has won the game so that you could show a high scores page. | ||
| − | If control structures were not used then programs would begin at the first line and excecute every line of code in order, giving the same output every time. Imagine how boring ''Tetris'' would be if there was only one piece! Control structures allow you to change the order of execution, jumping from one section of code to another as needed. | + | If control structures were not used then programs would begin at the first line and excecute every line of code in order, giving the same output every time. Imagine how boring ''Tetris'' would be if there was only one piece! Control structures allow you to change the order of execution, jumping from one section of code to another as needed. |
| − | + | ||
| − | + | ||
| + | |Body= | ||
==[[The If-Statement]]== | ==[[The If-Statement]]== | ||
| Line 13: | Line 15: | ||
==[[Nesting]]== | ==[[Nesting]]== | ||
| − | ==[[Review Questions and Exercises | + | ==[[Control Structures Review Questions and Exercises|Review Questions and Exercises]]== |
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | == | + | |
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | 3 | + | |PChapterNum=3 |
| + | |PChapterLink=[[Calling Methods]] | ||
| + | |NChapterNum=5 | ||
| + | |NChapterLink=[[Loops]] | ||
| + | }} | ||
| − | |||
{{Category:COMP 1010}} | {{Category:COMP 1010}} | ||
| − | |||
Latest revision as of 13:57, 7 December 2011
 Chapter 4Control Structures are blocks of code that force the computer to make a decision. Sometimes you will want your program to perform different tasks depending on certain boolean conditions. For example if you were writing a game you would probably find it very useful to be able to know when the user has won the game so that you could show a high scores page. If control structures were not used then programs would begin at the first line and excecute every line of code in order, giving the same output every time. Imagine how boring Tetris would be if there was only one piece! Control structures allow you to change the order of execution, jumping from one section of code to another as needed. | ||
|---|---|---|
| Write a Program a Day | Case Studies | |
The If-Statement
The If-Else Statement
Conditions
Nesting
Review Questions and Exercises
| Chapter 3: Calling Methods | Table of Contents | Chapter 5: Loops |
|---|
Template loop detected:
