1. Warmup Write a function to add two integer parameters and return the result

2. CMSC 202 Lesson 1 Introduction

3. Welcome! Who am I? – Dana Wortman, Instructor What is this class? – CMSC 202: Computer Science 2 – Design and Development of Software – C++ by Torture (…I mean…no, that’s what I mean) Why should you care? – The “Gateway”

4. Tips for Success 1. Attend Class 2. Keep your Text handy 3. Read Carefully 4. Memorize the Coding Standard 5. Start EARLY (>= 15 hours per project!) 6. Learn a Linux editor 7. Ditch Visual C++ 8. Review the Resources page 9. Read the Blackboard discussion 10. Ask Questions

5. MOST IMPORTANT Save Early, Save Often Modular Composition – Write no more than 5 lines – Save – Compile – Test (optional) – Repeat

6. Submitting Work Use GL machines Log into: – linux.gl.umbc.edu Project 0 will: – Ensure the submit system is setup for you – Help you learn the submit system

7. Need Help? Teaching Assistants: – 2.5 Graduate Instructor – Me! Help Center – Open M-F 10-4 (ish?) TBA

8. What is Computer Science? The systematic study of computing systems and computation. The body of knowledge resulting from this discipline contains – theories for understanding computing systems and methods; – design methodology, algorithms, and tools; – methods for the testing of concepts; – methods of analysis and verification; and – knowledge representation and implementation.

9. Where does this class fit? CMSC 202 is primarily focused on: – Design methodology – Algorithms – Tools Why C++? – C++ is a superset of C – Objects: greater organization & easier maintenance – More than 50% of jobs in CS request C++

10. Debugging What is a bug? – Application does the unexpected – May not cause a failure (core dump, crash, etc.) Three primary types: – Syntax – caught by compiler – Modular – caught by the linker – Logic – caught by….uh oh…the developer!!!

11. Logic Bugs – Where’s the Bug? int a = 7; int b = 6; int c = 2; float d = a + b + c / 3.0;

12. Debugging Two basic strategies – Print each variable during run… quick for some bugs, but tedious – Use a debugging tool Preferred method! – GDB – Visual C++ Debugger – Eclipse CDT and other opensource C++ IDE/Debuggers

13. Essential Debugger Features Line by line code execution Stacktrace of previously called functions View variable values at any line View POINTER values at any line Stop the code at a certain point (breakpoint) Show line where program core-dumps

14. Challenge For next class: – Write a function that sorts an array that is passed as a parameter (your function can also accept the size of the array) – Use the FEWEST lines of code Can you do it in less than 10? Less than 5?