Unfortunately the Event class is very "restricted" and there are no "set" functions provided so this is a little difficult - but not impossible.

In particular this question arises when you try to add someone to the participants list. More hints will be posted here soon but note that it just requires thinking about what type of access you have to the EventList class and how you update events in that list.

UPDATE (9/24/04): Ok, so the hint was to think about how you "update" events in the EventList class - and the answer is "by using the update function" - so how does the update function work, should be the next question. Looking at update's prototype we see that it takes an Event object by value (yes this is inefficient, and const reference would be better, but such is how it is) - so we have to have an Event object (a local variable "outside" the update function) in order to call update and then the update function goes through the linked list looking for a node that contains an Event with the same title and when it finds it, it "overwrites" that Event (there are a couple ways to do this - some "safer" than others). And that's it.

So if we think about that, and how things work just before we call the update function (for the EventList class) hopefully it is possible to see that even though the Event class has no set functions and it is nearly impossible to modify an Event object (even non-const ones) after it's ctor has been run it is still very easy to "update" an Event in the EventList - just declare an Event object (non-dynamic is perfectly fine) with the title, start_date, ... and participant list that you want (either bigger or smaller than the old participants list - which you can get a copy of since there are many "get" functions available for Event objects (just no "set" ones)) and then pass in this updated Event into the update function and it will find the corresponding event in the EventList and update it to be like the one passed in.

UPDATE (9/27/04): So after reading the above if it still isn't clear here is some (not quite complete) code:

Event e1( .... );  // has some title, namelist, etc.
... // some code

// now we want to change the title of e1 - but how?
string s1;
cout << "Enter the new title you want: ";
cin >> s1;

Event temp( s1, e1.getYear(), e1.getVenue(), ..., e1.getParticipants() );
// so now we have temp which is basically a copy of e1 but with a different
// title HOWEVER what we wanted to do was change e1's title
e1 = temp;
// and now we are done - e1 has been changed.

There were several errors in the originally posted primary.output   In particular the following errors:

• When printing an event the old output did not have a colon (:) after the word Duration - this was incorrect and has now been fixed (and the colon is now printed correctly).
• The <add_succ> message was not printed when Wrestling and Marathon were added - this has been corrected and the correct "Event ... added successfully." message is now in the updated primary.output
• The second time the events were printed forward, Wrestling was printed before Marathon, but it should have been the other way around (to keep them in lexicographical order) - this has been corrected and Marathon is now printed properly before Wrestling.
• The last error was that the <add_to_part_succ> message was not printed when Daniel Browne was added to Marathon - this has been corrected and the correct message is now in the updated primary.output

On the project description the <find_same_venue_fail> BNF is listed as follows:

<find_same_venue_fail> ::= "Events with the same duration:"<endl>
                                 "No events found."<endl><endl><endl> 

<find_same_venue_fail> ::= "Events with the same venue:"<endl>
                                 "No events found."<endl><endl><endl> 

After each project is completed and you have submitted it, it is recommended that you "clean up your account a little" - by deleting any unneeded files. NOTE HOWEVER YOU SHOULD KEEP A BACKUP COPY OF YOUR SOURCE files for your own reference. By "cleaning up" we mean deleting any old .o (object) files, old core files, old executable programs (a.out or p0 or ...) and the cxx_repository directory (if it exists). Note that these things just listed may take up a lot of your "Disk Space" of which your account has a limited supply. Your account has enough space to store all the code for all of your projects and the executables for one project (the "current" one) but it does not have enough space to store old core dumps, old executable files, ... for all of the projects.

If you encounter disk quota/space issues you should try to clean out your account and then if necessary see someone in office hours. Note that a common problem that occurs when you use up all of your disk space is that your program may fail to compile. You can always check your quota by running the UNIX quota command and if the blocks used is almost as high as your quota limit or you have about 20% left then chances are this could be the source of some problems.

When you come to see someone in office hours for help on your project, you should always bring a current printout of your code and if possible a printout of the compiler error messages (if there are any) and if it compiles a printout of the programs output (and the input used to generate that output). If you want to get the output of the compiler's error messages you will need to redirect error output as follows:

%  cxx  main.cpp  csll.cpp  >&  my.comp.errors

Having the requested information above will assist the instructional staff in being better able to assist you and others who are waiting to be assisted. Please also understand that the office hour room is a shared resource with other classes and we ask that you be respectful of the room and others using the room.