R. Clayton (rclayton@monmouth.edu)
(no date)
I have updated the assignment 5 object files to include a slight, special-case
optimization to my solution and to correct the labels printed when an error is
found.
As a reminder, it is your responsibility to make sure you're using the most
recent versions of any files I make available. There are no valid excuses
about assignment problems that involve using old files. The easiest way to
meet your responsibility is to link out of the class directory:
g++ -o pick-pairs /export/home/class/cs-509/pa5/solaris-main.o your-files
Those of you familiar with makefiles can add the following dependency to
automatically keep up to date when you run make:
main.o : /export/home/class/cs-509/pa5/solaris-main.o
cp $< $@
I will try to announce significant changes to assignment files via e-mail, but
see the comments below. Whether or not announcements are made or get through,
it is still your responsibility to make sure you are using the most recent
versions of the assignment files.
A few people have misinterpreted my previous comments about the performance of
assignment 5. I won't repeat those comments out of a fear of further confusing
more people. However, the most important thing you can do is submit a working
solution to the problem. If you submit a solution that doesn't work, or don't
submit anything at all, you can't even hope to get a good grade. Once you have
a working solution, you should make it as efficient as you can without changing
the correctness of your solution. "Efficient" is a slippery term, but let's
assume it means "within 2 to 5 times the performance of my solution as given in
the assignment files." Whatever "efficient" means, the point here is that "But
sir, you said we couldn't implement it like that" is not a valid excuse for not
submitting a solution, for submitting a late solution, or submitting an
incorrect solution.
My e-mail is still not working (outbound appears o.k., inbound is broken); I'll
try and have it fixed by next Tuesday. Because you have everything you need to
compile, link and test your code, the current e-mail problems are not a valid
excuse for for not submitting a solution, for submitting a late solution, or
submitting an incorrect solution.
This archive was generated by hypermail 2.0b3 on Fri May 10 2002 - 12:45:04 EDT