This preview has intentionally blurred sections. Sign up to view the full version.View Full Document
Unformatted text preview: CS31: Introduction to Computer Science I Discussion 4 April 22, 2011 TA: Paul Wais ( [email protected] ) Discussion Section 1L Information TA: Paul Wais ( [email protected] ) Office Hours: Thursdays 11:30am - 1:30pm in Boelter Hall 2432 Discusion Website: http://www.cs.ucla.edu/ ˜ pwais Notes and other resources will be posted on the Discussion Website. If you would like to meet me outside of the posted office hours, please email me. Also, if you’d like for me to cover something specific during discussion section, please send me email. If there is anything I can do to improve Discussion Section, please feel free to let me know. 1 Announcements 1.1 Project 3 is Hard! Start early! The next Project is due Tuesday, April 26th, and comprises several parts: • A warm-up exercise on functions. This exercise is ungraded, and there’s nothing to turn in, but it’s still helpful practice. We’ll see more examples of functions today. • A warm-up exercise on getting the project set up in Visual Studio or Xcode. This exercise is also ungraded, and there’s nothing to turn in, but it helps you get started on the project. • A test plan for the report. Tip: do this part before writing any code. List example inputs you could use to validate each function described in the specification. The specification provides lots of examples to help. If you do this first, while you read the specification, then you’ll already have about half the report written. • The Project, Part 1. The first part of the project requires writing 9 plotting functions that exercise loops and the basic sting concepts. There are couple of tricky algorithms that may take a while (perhaps a couple hours) to get right. We’ll go over some examples today that should help. • The Project, Part 2. The second part of the project requires writing a command parser for 8 of the plotting functions from Part 1. This part exercises some tricky details about strings, which we’ll go over today. • The Report. The first part of the report is to write a description of the program. The second part of the report should contain a list of the tests you used. Try to give at least two or three tests for every function and every text command . Most of the tests can be based upon examples given in the specification. 1 1.2 The Debugger is Awesome! Last time, we discussed how to use the debugger. If you haven’t already, try it with the example code given for the second Project 3 warm-up. See these references on how to use the debugger: For Visual Studio, check out this video (try to fast forward until 1:30 or so): http://www.youtube.com/user/UCLAChuck#p/c/2775EB517DDA7A95/0/z5gBIizwsY0 The debugger in Xcode is very similar to the one in Visual Studio. Check out this tutorial: http://bit.ly/iecq83 2 More on Functions 2.1 Function Prototypes There are two different ways to define functions. On one hand, you canThere are two different ways to define functions....
View Full Document
- Spring '00
- Computer Science, ASCII, Void type, function prototypes