1
Q
top down
A
top down is good when you have a high-level idea of what the software should do, and you are working to design the parts that will create and support that required functionality
2
Q
bottom up
A
bottom up is good for when you know what much [or most] of the underlying functionality will be, but you don’t know yet how that will be implemented at a higher level
3
Q
cast
A
ex: double (int value)
4
Q
pointers
A
identifiers that refer to some object in memory
5
Q
string
A
an array of characters, just like in many other languages, that ends with the NULL character
6
Q
function prototype
A
definition of the function without the innards
7
Q
format specifier
A
control what the output looks like
CSO
flashcards
Decks in class (5)
# Cards
