CS 1321 (Principles of Algorithm Design II):
Old Announcements

Old "latest news" entries, in reverse chronological order

• May 1: A review sheet for the final is available.
• May 1: Sample solutions for all homeworks are available; see the Homeworks and other assignments page.
• April 28: Homework #8 has been graded; scores have been mailed. A sample solution is available via the assignments page, with information about testing.
• April 24: Homework #7 has been graded; scores have been mailed. Information has been added to the solution page describing testing.
• April 20: Homework #6 has been graded; scores have been mailed. Information has been added to the solution page describing testing.
• April 19: Homework #9 is available; it is due April 28. Also, please read Chapter 12 of the textbook.
• April 12: The due date for Homework #8 has been changed to Monday, April 17.
• April 11: A sample solution for Homework #7 is available (code only so far; information about testing coming soon); see the Homeworks and other assignments page.
• April 6: Homework #8 is available; it is due April 14. Also, please read Chapter 10 of the textbook.
• April 3: Revised code for the dll-plus-iterators code presented in class today is available via the Sample programs page.
• April 3: Code for the double-ended queue class presented last week is available via the Sample programs page.
• April 3: A sample solution for Homework #6 is available (code only so far; information about testing coming soon); see the Homeworks and other assignments page.
• March 31: Homework #7 is available; it is due April 7. Also, please read Chapters 6 and 7 of the textbook.
• March 23: Homework #6 is available; it is due March 31. Also, please read Chapter 5 of the textbook, and start reading Chapter 6.
• March 21: The solutions for Homework #4 and #5 have been updated to include information about testing.
• March 21: Information about testing your solution to optional Homework #4i is available linked from the Homeworks and other assignments page.
• March 18: A sample solution for Homework #5 is available (code only so far; information about testing coming soon); see the Homeworks and other assignments page.
• March 17: A review sheet for Exam #2 is available. There will be a review session on Monday, March 21, from 7pm to 8pm in HAS 228.
• March 13: Several changes were made over spring break to the mail configuration on the CS lab machines. These changes do not affect the procedure for submitting homework, except that they should make it easier for you to get feedback on whether your homework arrived at the proper mailbox. See the updated document Reading and forwarding mail under Unix for details.
• March 13: Homework #5, due this Friday, will not be accepted past Saturday noon, due to the upcoming exam (next Wednesday).
• March 3: Homework #5 is available; it is due March 17. Also, please read Chapter 4 of the textbook, and start reading Chapter 5.
• March 2: A sample solution for Homework #4 is available (code only so far; information about testing coming soon); see the Homeworks and other assignments page.
• February 28: You may submit Homework #4i for up to 10 points extra homework credit if you choose.
• February 25: Exam 1 is graded; it and a solution will be distributed in class.
• February 25: Homework #4i is available. This homework is not for credit; it need not be submitted and will not be graded, but should help you prepare for the next exam.
• February 23: The due date for Homework #4 has been extended to Wednesday, March 1, at noon. This is a firm deadline; no late homework will be accepted.
• February 23: The sample solution for Homework #3 now includes information about testing.
• February 16: Homework #4 is available; it is due February 25. Also, please read Chapter 3 of the textbook.
• February 16: I have updated the guidelines for programming assignments with tips about how to tell whether your assignment was submitted properly.
• February 14: Homework #3 is graded; scores and comments have been sent out by e-mail.
• February 14: A sample solution for Homework #3 is available (code only so far; information about testing coming soon); see the Homeworks and other assignments page.
• February 11: A review sheet for Exam #1 is available. (Updated 7pm February 11.)
• February 9: Homework #2 is graded; grades were mailed to students' TUCC accounts. See the Homeworks and other assignments page for a sample solution, including a description of what was tested in the grading process.
• February 9: Some additional last-minute tips about Homework #3 are available via J. Oldham's Homework #3 FAQ.
• February 8: A sample solution for Homework #2 is available; see the Homeworks and other assignments page.
• February 5: The starter code search-engine.cc for Homework #3 has been revised to make it compile without changes.
• February 2: Links to additional information about the C++ Standard Template Library have been added to the links page.
• January 31: Homework #3 is available; it is due February 11.
• January 28: Several students have reported problems in compiling the provided code for Homework #2. The due date has thus been changed to Monday at 5pm. To the best of my knowledge, problems compiling this code with the g++ compiler can all be traced back to errors in the student's code. Visual C++ may be another story. I have added a section "Problems using Visual C++ for this assignment" to the end of the Homework #2 writeup describing the problems and what to do about them.
• January 27: Homework #1 is graded; grades were mailed to students' TUCC accounts. See the Homeworks and other assignments page for a sample solution, including a description of what was tested in the grading process.
• January 26: Additional changes have been made to starter file unary.h for Homework #2. These changes should not affect the code you write (they're in function operator>> only), but you may want to obtain a revised copy, since the changes fix a bug that could affect your testing.
• January 25: A few changes have been made to the starter file unary.h for Homework #2. These changes should not affect the code you write, but you may want to obtain a revised copy anyway.
• January 21: Homework #2 is available; it is due January 28. Also, read chapter 9.
• January 19: If you are having any difficulty with the file input/output aspects of Homework #1, try reading J. Oldham's notes on patterns for C++ input.
• January 19: Code for the list ADT presented in class today is available here.
• January 19: Homework #1 has been updated with instructions for submitting programs electronically. The general instructions are available in the Guidelines for programming assignments page (also linked from "Homeworks and other assignments" below).
• January 17: Start reading Chapter 2 of the textbook; plan to finish by next Monday.
• January 14: Homework #1 is available; it is due January 21. Also, start reading Chapter 1 of the textbook, and plan to finish by January 21 as well.
• January 12: If you missed class Tuesday, please complete the background questionnaire, available as Homework #0.
• January 12: Class will meet in HAS 329 rather than in HAS 228.
• January 12: See the CS1320 FAQ for information on obtaining an account on the department Linux (Unix) machines. If you have problems setting up your account, check with me, or with Dr. Howland (HAS 201C) or Dr. Konstam (HAS 339B).