• Does submit check for memory leaks and to see if I used a linked-list? [4/27]
• Do we have to use the cxx compiler with the -w0 and -std strict_ansi options in our makefile? [4/26]
• [MSG] Don't forget to "clean up" project #5 (and others) and BACKUP often.
• When is Project #6 due?

• [UNIX Tip] None posted. [4/26]

List of Answers to FAQ

• Does submit check for memory leaks and to see if I used a linked-list?

  THIS IS VERY IMPORTANT - submit DOES check for memory leaks (using the checkMemory tool) and if there are leaks it will NOT accept the project. Submit will NOT check to see if your program used a linked-list - HOWEVER we will run an AUTOMATED as well as manual check of your code to see if it uses a linked list or not and if it does NOT then you may be forwarded to the Office of Judicial Programs for "fabrication" - IN PARTICULAR IT IS VERY OBVIOUS THAT SUBMITTING YOUR PROJECT #5 CODE FOR CREDIT AS PROJECT #6 is NOT PERMITTED and will be considered similar to "hardcoding" and a violation of the University's Honor Code. Do NOT attempt to submit a project that does NOT use linked lists otherwise the result may be an XF for the course.

• Do we have to use the cxx compiler with the -w0 and -std strict_ansi options in our makefile?

  Yes. Although not explicitly required on the project description the course syllabus specifies that the cxx compiler must be used with -w0 and -std strict_ansi options unless explicitly permitted otherwise.

  Students who did NOT use the cxx compiler WITH the -w0 and -std strict_ansi options on PROJECT #4 will not lose points BUT you MUST use the cxx compiler with the specified options in your makefile otherwise points may be deducted for this on Project #5 (and beyond).

  IF YOU SAW "ODD" compiler warnings ON YOUR pre-graded PROJECT #4, chances are they were due to your makefile not using the -w0 and -std strict_ansi options with the cxx compiler - again as mentioned above you will not be deducted for this for project #4 (also this was specified in the email you received with the PRE-graded project #4 - reread that message if you didn't see this).

• [MSG] Don't forget to "clean up" project #5 (and others) and BACKUP often.

  Meaning delete any old executable files (like a.out) and delete the cxx_repository directory (if it exists). See project #2 FAQ for more detailed information about quota and other related items.

• When is Project #6 due?

  Project #6 is due by 11PM on SUNDAY, May 2nd, 2004. As always, students should strive to submit a working project that passes primary one or more days "early" and then finish up any last minute special case testing and "cleaning up of code" and submit the final "polished" version the day the project is due.

  Submit is now accepting project #6 and you must include all of your .h (header) files as well as your source files - note that submit will check your project using the posted main.cc file and if it does not work properly with that main.cc file you will receive a 0 on this project. ADDITIONALLY NOTE that submit will check your program for memory leaks and will not accept your program if it has any memory leaks.

UNIX Tip(s)

• [UNIX Tip] None posted.

  None posted.

See the class syllabus for policies concerning email Last Modified: Mon Apr 26 18:00:18 EDT 2004

Web Accessibility