Tips

• Think about what you need to do to synchronize your threads before you start writing code. Have the strategy clear in your head or on paper before you write code. This strategy is always the best way.

• We highly recommend that you write and thorougly test your code in small increments to make debugging and trouble shooting as easy as possible. It is easier to get rid of compile time and runtime errors for one routine at a time, than it is for all the code that you write at once. In the same vein, use small easy test cases first and more rigorous tests once the easy cases work.

• If you are getting a lot of errors while compiling, get rid of the first few errors. Doing this often eliminates other error messages you get.

• Make sure you are working on a delux machine.

• When you are certain your submission is ready, run your programs in your directory as the graders would run them. It is your responsibility to set up all the files in your /cs377/lab2 directory. If the graders are not able to run your program, do not expect to be regraded because you forgot to put something in the right place. Test yourself before you think you are ready to be tested by the graders.

• Remember to set the permissions for the graders.

• Remember to turn in a hard copy of all the files you create or modify. You will lose points if you do not do so.