blob: c9cfd0920cd293054d9791d4893aed2ae36484cb (
plain) (
blame)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
|
CST116
Module 4: Lab 4
7a 6.8 pg 132-133 #1-9
1. 3
2. -nan(ind)
3. 32
4. .25
5. 6
6. 6
7. 5
8. 5
9. 4
9.3 pg 207 #1
1.
a. return always has to have any number after it, it can't be 'void'. ex: return(0); or return(1); or even return(variable); if variable is stored as a number.
b. You can not use return as a variable, return can only be used to return a number back if the code ran successfully, use a different word. ex: int number; or int variable;
c. this is correct, but only if var_a is initialized as a number of any kind either by the user or defined earlier in the code. ex: int var_a=2; return var_a;
d. This is fine as well, as long as the variables used are defined. It will only return with the number of var_c though.
e. This is fine as well, as long as var_a and var_b are defined as numbers, it will return with the 2 variables added together.
f. This does not work, the return function has to return with a number. ex: return(1); or return(97);
g. This is ok. True will be shown as a 1 value and false will be shown as a 0 value.
h. This is fine. It will return with code 66 for some reason, but it works. note: only doing return('A') returns with code 65 for some reason.
7b 9.4 pg 214 #1
1.
7c 9.5 pg 216 #2
2.
8a 9.13 pg 226-229 #1
1.
8b 9.14 pg 229 #1
1.
|