e02 : Midterm Exam E02
|e02||true||Midterm Exam E02||Tue 02/26 02:00PM|
THE LOCATION: Regular lecture hall
What is covered
- Labs 1 to 5
- Homeworks 1 to 8 All topics in chapters 2,3, 4.1,4.2, 5 with high emphasis on chapter 5 (loops) Format will be similar to midterm -1 with more conceptual questions. You will also be expected to write code.
Links to past exams
Here are some exams from past offerings of CS8 that you can look at to get an idea of the style of exam questions I typically write.
Please note that this quarter we may have covered MORE MATERIAL or LESS MATERAL than the point at which midterm 1 was given in previous quarters. Also, these courses all used a different textbook, and there were different homeworks and different labs. So your exam may cover much more or much less material. Use these as guides for style of exam rather than precise content.
- E01: http://www.cs.ucsb.edu/~pconrad/cs8/10F/exams/E01/
- E02: http://www.cs.ucsb.edu/~pconrad/cs8/10F/exams/E02/actualExam
- E03: http://www.cs.ucsb.edu/~pconrad/cs8/10F/exams/E03/actualExam
- E01: http://www.cs.ucsb.edu/~pconrad/cs8/10M/exams/E01/
- E02: http://www.cs.ucsb.edu/~pconrad/cs8/10M/exams/E02/actualExam
- E03: http://www.cs.ucsb.edu/~pconrad/cs8/10M/exams/E03/actualExam
- E01: http://www.cs.ucsb.edu/~pconrad/cs8/09M/exams/E01/
- E01: Actual Exam http://www.cs.ucsb.edu/~pconrad/cs8/09M/exams/E01/actualExam/
- E01: Practice Exam 1 http://www.cs.ucsb.edu/~pconrad/cs8/09M/exams/E01/CS8_09M_E01_practiceExam_1.html
- E01: Practice Exam 1, partial answer key and discussion http://www.cs.ucsb.edu/~pconrad/cs8/09M/exams/E01/CS8_09M_E01_practiceExam_1_notes.html
- E02: http://www.cs.ucsb.edu/~pconrad/cs8/09M/exams/E02/
- E03: http://www.cs.ucsb.edu/~pconrad/cs8/09M/exams/E03/
ANSWER KEY FOR Fall 2010, E02, Question 2
>>> squared(7) 49 >>>
Answer: CAN’T TELL. If we name the two versions
squaredB and run them both, we see this:
>>> squaredA(7) 49 >>> squaredB(7) 49 >>>
Now, what about this one:
>>> for i in range (4): squared(i) 0 1 4 9 >>>
This one is much more subtle. As it turns out, the answer depends on whether you define the
squared function in the shell, interactively, or whether you define it in a file before you run!
Suppose you defined it in the shell, like this. Note that the
... characters are not what you type—those come up automatically when you hit return in the Python Shell while defining a function.
>>> def squaredA(x): ... return x * x ... >>> def squaredB(x): ... print(x * x) ... >>>
If you define the functions this way, then the answer is CAN’T TELL! See for yourself:
>>> for i in range(4): ... squaredA(i) ... 0 1 4 9 >>> for i in range(4): ... squaredB(i) ... 0 1 4 9 >>> squaredA(i)
BUT if you define the functions in a file, with
File => New File, then choose
Run Module and then type in exactly
the same thing at the Python prompt, you end up with DIFFERENT OUTPUT!
For example this file:
def squared(x): print( x * x) for i in range(4): squared(i)
produces this output:
>>> RESTART: /Users/pconrad/github/ucsb-cs8/Lecture7_0822/squaredA_vs_squaredB.py 0 1 4 9 >>>
But this file:
def squared(x): return x * x for i in range(4): squared(i)
produces this output (i.e. NO OUTPUT).
RESTART: /Users/pconrad/github/ucsb-cs8/Lecture7_0822/squaredA_vs_squaredB.py >>>
This is unsatisfying. But, it’s true. When function calls return a value and nothing is done with that value (i.e. it isn’t stored in a variable, it isn’t passed to another function), the result in the Python Prompt (i.e. the Python REPL) is that the value is printed. But inside a file, that value just disappears.
So, in the end, the answer to the question, as it appeared on the exam, is CAN’T TELL, because clearly the code was being typed in at the Python Prompt (Python REPL).
But, I have to confess that there was a moment when I thought the answer was B. If the code had appeared in a file, the answer would definitely have been B.
Ok, let’s move on.
>>> 2 * squared(3) 18 >>>
This one is easy. Must be A.
for i in range(4): print(squared(i))
This one must be B. NOTE that it does NOT produce any Python error messages (sometimes called “Python Vomit”.) Also note that there are two print statements involved here: the one inside the function definition and the one inside the code we are running.