Turn in complete source code.
Use prtext to print it out.
Include the burst page as the first page turned in.
Write a statement on the first page indicating exactly
what worked and what did not.
Be prepared to demonstrate that your program works.
Part 1:
From PUP, section 2.15.1 on page 73.
Part 2:
From PUP, section 2.15.2 on page 75.
Note that you do not have to post to a newsgroup to test your program. Set the environment variable, NEWSDIR, to one of your local directories. You can then add (or delete) files from that directory to test your program.
Start this assignment ASAP. If your run into trouble, come and see me before it is too late.
Additional information added 2/5/96:
When you are asked to write a function with a given prototype, you must write it exactly as described. No modification is allowed unless ou first talk with me.
update_list is like the get_data of the original list object in that it retuns data about what is stored at the current entry in the list and then updates the traverse pointer to point to the next entry. It returns -1 if it was at the end of the list. In this case no values are returned for modifyname and modtime. update_list will call lastmod and compare its stored modification date with the current modification date. If they are the same, update_list returns 0. If they differ, update_list will store the new date in the list and return 1. In either case, modifyname and modtime will be returned. update_list should not do any I/O (except in your debugging phase). An error in lastmod should be treated as if there was no change in the modification date.