TutorialFundraiserApplication培训教程文件.pptVIP

Tutorial 11 – Fundraiser Application: Introducing Scope and Function Prototypes Objectives In this tutorial, you will learn to: Create variables that can be used in all the application’s functions. Use argument coercion to implicitly convert the value of an argument to a function. Use function prototypes to validate your function calls. 11.1 Test-Driving the Fundraiser Application 11.1 Test-Driving the Fundraiser Application (Cont.) 11.1 Test-Driving the Fundraiser Application (Cont.) 11.1 Test-Driving the Fundraiser Application (Cont.) 11.2 Constructing the Fundraiser Application 11.2 Constructing the Fundraiser Application (Cont.) Scope is the portion of the application where a variable can be accessed Global variables have file scope File scope is from the variable declaration to the end of the file Should be avoided to prevent subtle logic errors or used as a constant Local variables have block scope Block scope is from the variable declaration to the end of the block (the closing right brace) Local variables hide any global variables with the same name while in scope 11.2 Constructing the Fundraiser Application (Cont.) 11.2 Constructing the Fundraiser Application (Cont.) 11.2 Constructing the Fundraiser Application (Cont.) 11.3 Function Prototypes Function prototype Contains the function’s return type, name and parameter list Allows the compiler to validate function calls Argument coercion occurs when arguments do not match the types specified in the prototype A prototype is not necessary if a function is defined before it is called (the header acts as prototype) Writing the function prototype is “declaring” the function; writing the function body is “defining” the function Function signature is the function name and parameter list 11.3 Function Prototypes (Cont.) 11.3 Function Prototypes (Cont.) Function prototype errors Forgetting the semicolon after a function prototype is a syntax error Invoking a function before the function prototype has been