CS 159 Lab 5

In downward communication it is only a copy of the data that is sent from the calling function to the called function

true

It is not possible to access a variable in the calling function by its identifier when inside the called function.

true

Given the address of a variable the called function can access and manipulate the value of a variable in the calling function

true

The called function must declare a special type of variable known as a pointer to store a memory address that is sent from the calling function

true

The asterisk (*) when used in a variable declaration indicates that such variables are not data variables but address (pointer) variables which can store the addresses of other variables in the program.

true

The asterisk has two different uses, declaring an address variable (pointer) and indirectly accessing the data (in the memory location to which the variable points).

true

When only one data item needs to be returned to the calling function then we should use the standard return statement rather than passing a single parameter by address.

true

The scope of an object determines the region of the program in which it is visible (and defined).

true

A variable declared in the local declaration section of a function has a scope that extends until the end of that function.

true

Objects with a global scope are visible (defined) everywhere in the program.

true

It is poor programming style to reuse identifiers within the same scope.

true

A structure chart should be created after your program has been written.

false

Each rectangle on a structure chart represents the user-defined and standard library functions used in a program

false, not stdlib functions

No code is contained in a structure chart as it only demonstrates the function flow of the program.

true

A structure chart may show the data that is exchanged between functions.

true

Functional cohesion is a measure of how closely the processes in a function are related.

true

A function that does one and only one process is functionally cohesive.

true

It is a good design practice to limit user-defined functions to only a single task.

true

It is a good design practice to not repeat the logic of one function in other functions of the program.

true

It is a good design practice to design a user-defined function such that it is testable apart from the rest of the program.

true

It is possible to determine if any parameters are passed to a function by address from the declaration statement of the function.

true

It is never possible to determine if any parameters are passed to a function by address from an example call to the function.

false; will have the & in front of the variable

It is possible to determine if any parameters are passed to a function by address based on the first line of the definition of the function (also known as the function header).

true

A function that passes at least one parameter by address must pass them all by address

false

All functions that utilize pass by address must be void functions.

false

One benefit of pass by address is that it allows multiple changes to be made in a function and to have those changes available in the calling function.

true

With the use of pass by address it is now permissible for a function to be written to complete several subtasks of the program.

false; of course not

When working with a parameter that has been passed by address it is unnecessary to use the & (address) operator in the scanf because the parameter already represents a memory location.

true

The * and & operators are inverse operations of each other.

true

& gets the address, * tells to store at that address

true