Term
|
Definition
|
|
Term
|
Definition
| breaking up of a program (into modules) |
|
|
Term
|
Definition
| a block of code that will execute in response to a |
|
|
Term
|
Definition
| the first line that declares the sub |
|
|
Term
|
Definition
| a sub procedure that can be accessed from any module within the project |
|
|
Term
|
Definition
| a sub procedure that can be accessed only from within the same module |
|
|
Term
|
Definition
| optional keyword that triggers a sub procedure |
|
|
Term
|
Definition
| assumptions or initial requirements of a procedure |
|
|
Term
|
Definition
| statements of what must be true at the end of an execution of a procedure if the procedure has worked properly |
|
|
Term
|
Definition
| assigning a data type to ALL variables including those in procedure calls |
|
|
Term
|
Definition
| allows you to see object properties and other members as you type in your code; also allows the compiler to perform type checking |
|
|
Term
|
Definition
| setting in IDE that will require all variables to have data types declared, |
|
|
Term
| arguments or actual parameters |
|
Definition
|
|
Term
|
Definition
| sub procedures that triggered when events are called (i.e. button click) |
|
|
Term
|
Definition
| pass the value (not the variable) to the sub procedure |
|
|
Term
|
Definition
| passes a reference to the variable itself; can change the value of the variable |
|
|
Term
|
Definition
| a special type of procedure that return a valueto the main program using a return statement. |
|
|
Term
|
Definition
| used to assign the function which returns a value to a variable |
|
|
Term
|
Definition
| keyword included in the last line of a function |
|
|
