The goal for this week is to do even more structured programming in C, using strings, pointers, functions and header files to organize processing. You will really need pointers to update data (function parameters) this time.

Part A: Card Library [75 points]

[25 points] We have written a header file "CardOps.h" for a set of operations to manipulate playing cards. You must implement these functions by writing a corresponding definition file "CardOps.c". You must not change the way any of these functions are declared!

[20 points] In order to know if your functions are working properly, you need a test program. Write a main program (CardOpsTest.c) that thoroughly tests the operation of all the functions in CardOps.c. Check both good and invalid values for suits and faces. There should not be any user input for your test program. Use gcov to insure that every statement in your implementation of CardOps is executed at least once. Include the gcov output log in your submitted zip file.

[20 points] Write a second main program (pg3a.c) to read a file containing card strings, one per line. Use a command-line argument when you run the program to get the name of the input file. Store only valid and unique cards in a dynamically allocated array that starts with size 5, and is doubled in size as necessary. Then sort them according to their rank and print them out. Hopefully you all know how to implement at least one type of sorting algorithm. You can use other people's existing code for the basis of your sorting as long as you cite the original source. You should check for memory leaks with valgrind and eliminate them all.

Think about how you want to store the card information and try to find a way to do this efficiently, so that you don't have to keep parsing card strings over and over again. (Hint: make a Card struct and use that as your array base type.) You are encouraged to add other functions to help with the processing. You should (and we will) use gprof to check for inefficient coding decisions.

[5 points] You must also write a makefile called "MakeCards" that can be used to compile the CardOps files along with your test program and your main driver program. It must have at least two executable targets, CardOpsTest and pg3a.

Grading: 5 points style, submission, reflection & warnings, 25 points CardOps.c, 20 points CardOpsTest.c, 20 points pg3a.c, 5 points makefile.

Part B: Version Control Prep [0 points]

In preparation for our working session on version control in class on Tuesday 6/11, you all need to have the following steps completed and ready to use. There is nothing to submit for this part of the assignment.

General assignment requirements, style and submission details:

Readings: Make sure you do the reading for each week, preferably before lectures and attempting homework.
Reflections: Reflect briefly on each program you write, as a comment at either the beginning or end of each main file. Comment on things like: how hard was the program and why? what did you learn from it? where did you need help? how long did it take to complete? what was the best part of the assignment and why? how would you redesign this assignment if you were the teacher? You should have a paragraph of well-written (properly formed English) reflections for each program. These reflections are part of your assignment grades.
Style: All files with main must be named according to the assignment number they solve (and part if relevant), such as pg1a.c or pg5.cpp. Other files should be named descriptively. Use a consistent layout style for your programs, as well as recommended naming practices for variables and functions. For C programs, we suggest following Kernighan & Ritchie's style.
Identification: You must include a header comment with your name, this course number (600.120), the date, the assignment number, your phone number, Blackboard login, and preferred email address in every source file you write.
Compilation: Source code must compile with our standard compilers and options, on the ugrad machines. These are:
```
gcc -std=c99 -pedantic -Wall -Wextra -O
g++ -std=c++98 -pedantic -Wall -Wextra -O 
```
Remember: you will receive NO credit for programs that do not compile. Use incremental coding to insure that you always have a working program, even though it might be incomplete.
Electronic Submission: Submit an electronic copy of all assignment parts on Blackboard, together in one zip file. You may submit on Blackboard multiple times for any assignment - we will only grade the last (most recent) submission unless you request otherwise. You must include all parts for an assignment in each zipped submission attempt. If you need to explain anything in general about an assignment, include a README plain text file with your submission.
Deadlines: Assignments will be due at 9am on the due date. There is a 1/2 hour grace period for program submission from 9-9:30. If you submit in this timeframe, you will get a standard 5 point late penalty, even if it is only 10 seconds late. After the grace period, programs will not be accepted and you will receive no credit. Exceptions will be given only for illness, and only by Joanne.
Printouts: Submit a printout of all your original program source files (C code, not the program output) for each assignment part when you come to class on the due date. You must staple together all the printouts for each assignment.
Ethics: Assignments will be individual unless otherwise noted. Remember that you may use or adapt code from your texts and lectures, but you MUST include a comment to cite the original source. You may not use code from other sources. This not a research course, it is a skills development course.

600.120 Intermediate Programming Summer 2013 -- Assignment 3 Due by 9am on Tuesday, 6/11

Part A: Card Library [75 points]

Part B: Version Control Prep [0 points]

600.120 Intermediate Programming
Summer 2013 -- Assignment 3
Due by 9am on Tuesday, 6/11